We launched the startup out of a garage in Greeley. Literal garage, three laptops, bad coffee, and a whiteboard covered in buzzwords. The product was a mess in the beginning. But we were fast, scrappy, and too dumb to quit.
By year two, we had a working prototype, a handful of early clients, and a growing team of six. People were starting to notice us. We even landed a write-up in a regional startup blog.
And from the outside, our numbers looked solid. Revenue was up. Burn rate seemed manageable. Investors liked the story, the traction, the grit.
But inside, something felt off.
Every time I checked the bank account, the balance was lower than expected. I’d look at our books, see a healthy month, and still feel nervous. We were collecting payments, hitting KPIs, even closing a small seed round. So why did it feel like we were drowning?
At first, I thought it was normal growing pains. A timing issue. Just a few late invoices or overlapping expenses. But then we missed payroll by two days. Our developer team lead sent a Slack message asking if the company was okay. That one hit like a punch to the stomach.
I went through our QuickBooks account line by line. Nothing jumped out. Our bookkeeper, a local freelancer we’d hired during the bootstrapped days, insisted everything was accounted for. But something wasn’t right.
Cash was bleeding out and no one could tell me exactly where it was going.
At our next investor call, one of them asked a simple question: “What’s your current runway based on net burn?” I gave him a number. He asked how I got it. I hesitated, then mumbled something about projections and averages.
That silence that followed still haunts me.
After the call, my co-founder pulled me aside.
“We need help,” he said. “Like, real help. Not spreadsheets duct-taped together. We need someone who actually knows how to run financials for a growing company.”
That’s when we started looking for a controller in Greeley who had experience with early-stage startups.
Her name was Melissa, and she walked into our office with a calm focus that instantly reset the room. She had worked as a controller for two other SaaS startups before they were acquired, and she didn’t waste time on small talk.
“Show me everything,” she said, and we did. Bank statements, invoicing history, contractor payments, equity agreements, subscription tools. By the second day, she had three questions that none of us could answer.
“Why are you paying out commissions two months before cash hits the account?”
“Why are SaaS renewals hitting as one-time revenue?”
“Do you realize you’re being double-charged for two payment processors?”
The silence in the room was different this time. We weren’t embarrassed—we were finally learning.
Melissa rebuilt our financial system from the ground up. She created real-time dashboards that tracked burn, actual cash flow, upcoming liabilities, and customer churn. She categorized every expense with surgical clarity. She taught our developer-turned-ops manager how to think in terms of cost centers and return on capital.
She even found two active contracts we had forgotten to cancel, both charging us monthly for tools we no longer used.
By month two, she gave us a report that made our investors take us seriously. It wasn’t just a snapshot—it was a blueprint. Forecasts by department, scenario modeling, even a cash conversion cycle that showed how long it took each dollar to flow from prospect to bank.
Our investor who had gone silent on the last call sent me a two-word email after seeing the report: “Nice work.”
Working with a seasoned controller in Greeley didn’t just help us survive. It helped us evolve. We stopped guessing and started leading. We made decisions based on data instead of hope.
The most surprising part? I started sleeping again. I stopped carrying the weight of “not knowing.” I could look our team in the eye and answer hard questions without spinning.
And when we pitched our next round, I stood in front of that room of investors, ran through our numbers, and when someone asked about burn versus growth trajectory, I didn’t flinch. I had the answer. Melissa had already modeled five versions of that scenario.
The hustle hadn’t stopped. The work was still hard. But now it had structure, clarity, and confidence behind it.
Numbers don’t lie—but if you don’t have someone who knows how to read them, they can absolutely ruin you.
Comments are closed.