How to build an operational backbone in a company that thinks it doesn't need one yet.
Every early stage founder I've worked with has said some version of the same thing: "We'll sort out operations once we've got more runs on the board." The logic seems reasonable. You're resource-constrained, you're trying to build a product and win customers, and operations feels like overhead. Something you backfill, once the real work is done.
I've been the COO in companies that believed this. I've watched what happens when "later" never quite arrives. And I've seen the moment, triggered by a cash crisis, a compliance failure, or a key person walking out the door, when founders realise that operations wasn't overhead at all. It was the thing holding everything else together.
So this is for the founder or CEO who knows, somewhere in the back of their mind, that the plumbing isn't right but hasn't yet made it a priority.
What is operational backbone?
People tend to conflate operations with admin. They're not the same thing.
Admin is processing what's already happening. Operations is the system that determines how your company makes decisions, manages money, meets obligations, and holds people accountable. A strong operational backbone means that when something goes wrong (and it will) you have the information, the processes, and the clarity of roles to respond. Without it, every problem becomes a crisis because you're solving it from scratch every time.
Concretely, it includes: how cash is tracked and reported; who owns financial obligations like payroll, superannuation, and tax; what the decision-making authority is at each level; how commitments are tracked and followed up; and what the board or leadership team actually reviews, and when. None of this is glamorous. All of it matters.
The warning signs you're flying blind
You probably don't need a full audit to know whether your operational foundation is solid or not. A few reliable signals:
The CEO is the only person who knows the true cash position, and they're often guessing. Nobody can tell you, at a moment's notice, what the company owes in the next 30 days. Decisions are made verbally, and nobody's sure what was actually agreed. Statutory obligations (super, Business Activity Statements, payroll tax) are being deferred because something else always feels more urgent. A key person leaves and takes the institutional knowledge with them.
If two or more of those are true, you don't have an operations problem. You have a risk problem.
Where to start
The good news is that building an operational backbone doesn't require a large team or a six-figure systems investment. In early-stage companies, it mostly requires clarity and consistency.
Start with cash visibility. A CFO I respect and admire uses an analogy I’ve never been able to improve on: running a business by watching your bank balance is like driving a car with your eyes on the fuel gauge. You’ll hit something long before you run out of fuel. The windshield is your cash flow position, and if you’re not looking through it, you’re flying blind regardless of how healthy the balance looks today.
Every company, regardless of size, needs a weekly cash position view: not a model, an actual view of what’s in the bank, what’s coming in, and what’s going out in the next 30 and 60 days. And cashflow projections alone are not enough. You need historical actuals to compare against so you can track how accurate your forecasts actually are. I’ve had a CEO, a Chair, and a Company Secretary all tell me that detailed weekly projections prepared by an accountant were more than adequate. They weren’t. Projections without actuals tell you what you hoped would happen, not what is happening. If your CEO or CFO can’t produce a reconciled view in under ten minutes, that’s the first thing to fix.
Next, map your statutory obligations. List every recurring payment the company is legally required to make: super, BAS, PAYG, payroll tax, any ATO arrangements you're managing. Assign a named owner for each. Not a function. A person. Put due dates in a shared calendar. This sounds basic because it is basic, but in my experience the number of startups that have come unstuck on obligations they knew about but didn't actively manage is not small.
Then clarify who decides what. Role confusion is one of the most expensive operational failures in early-stage companies, and it's almost never documented. Take a day and actually write down who has authority to commit to spending, to hire, to sign contracts, to make product decisions. If you don’t know where to start, the RAPID and RACI frameworks can be a simple and effective first step. Where there are gaps or overlaps, resolve them. A founder-CEO who is also effectively the COO, CFO, and head of sales is not a strength. It's a single point of failure.
Finally, build the rhythm. Operational health isn't a project you complete. It's a cadence you maintain. A weekly cash review. A monthly leadership meeting with a fixed agenda. A quarterly board report that tells the truth about performance. These rhythms create accountability without bureaucracy, and they mean that when something goes wrong, you have context and history to work from.
The cost of waiting
There's a version of this story where you build these foundations early, they become invisible because they work, and you scale on top of them. There's another version where you defer it, and the moment you can no longer defer it is also the moment you have the least capacity to deal with it.
I've lived both versions. The second one is significantly more expensive: in time, in money, and in goodwill with the people who were counting on you to have your house in order.
The companies that think they don't need operations yet are usually the ones that need it most. An operational backbone isn't something you build when you're ready to scale. It's what makes you ready.
Lessons learned
Operations deferred is risk accumulated. Every week without the basics in place is a week where a manageable problem can become an unmanageable one.
Projections without actuals are a false sense of control. The gap between what you planned and what happened is where companies get into trouble.
Role confusion is expensive and almost always undocumented. Accountability gaps exist not because people are careless but because nobody wrote down who was responsible for what.
Operational rhythm creates accountability without bureaucracy. A weekly cash review, a monthly leadership meeting, and a quarterly board report don’t slow a company down. They keep it from being blindsided.
Key takeaways
For founders and CEOs
If you’re the only person who knows your true cash position, you’re a single point of failure. Fix that first.
Statutory obligations are not optional. Deferring super, BAS, or PAYG to fund growth is borrowing from a lender with no patience and real consequences.
A weekly cash review is not overhead. It is the minimum information you need to make sound decisions.
For COOs and ops leads
Push for actuals alongside projections. If leadership is resistant, the fuel gauge analogy is useful: projections tell you how much fuel you planned to use, actuals tell you where you actually are on the road.
Document decision authority early and revisit it at every growth stage. The structure that worked at 10 people will cause problems at 30 and break at 100.
If you’re raising operational concerns and not being heard, document it in writing with dates. It matters more than you think, usually at a moment you don’t expect.
Frequently asked questions
When does a startup need a COO? Each company is different so there's no specific headcount trigger, but as a guide most startups will benefit from dedicated ops leadership when they have more than 15-20 people, multiple revenue streams, or statutory obligations across more than one entity. Personally, as a rule of thumb I use a 20: 1 ratio. For every 20 employees add one ops role, and if it looks like your company headcount is going to hit or exceed 100 people, that’s a pretty strong signal that you’ll need a COO if you don’t already have one. That said, if only one person in the company knows the true cash position, that's a sign the operational backbone needs attention regardless of size.
What's the difference between operations and admin? Admin processes what's already happening: paying invoices, filing documents, booking travel. Operations is the system that determines how decisions are made, how money is tracked, how obligations are met, and how accountability is maintained. Admin is execution. Operations is the structure that makes execution reliable.
What should a weekly cash review actually include? A reconciled view of current bank balance, confirmed cash coming in over the next 30 and 60 days, confirmed cash going out over the same period, and a comparison of the previous month’s forecast against what actually happened. If your CEO or CFO can't produce this in under ten minutes, the visibility isn't there.
All content is produced by me, reflecting my own experience and judgement. Generative AI tools were used for editorial support, in this case Claude specifically.