Why Most Project Businesses Don’t Have a Revenue Problem — They Have an Operating Rhythm Problem
As a COO in a project-based business, I don’t worry about whether we can deliver a project.
I worry about when the next one lands — and whether the organisation can absorb it without breaking cadence.
Most project businesses don’t fail because they can’t execute.
They struggle because they operate in spikes.
- Big win → scramble to resource
- Delivery pressure → firefight
- Project ends → panic
- Pipeline thin → slash costs
It’s not a revenue problem.
It’s a portfolio rhythm problem.
Here’s how I think about it.
1. You Must Manage the Business as a Portfolio, Not as Projects
Projects are episodic.
Operations must be continuous.
From a COO perspective, I don’t look at “Project A”.
I look at:
- Forward load (12–18 months)
- Revenue smoothing curve
- Capacity coverage ratio
- Fixed cost absorption
- Working capital exposure
If 60% of revenue ends in the same quarter, we have a structural risk.
The solution is deliberate diversification:
- Staggered start dates
- Mix of short-cycle and long-cycle work
- Blend of high-margin and high-volume contracts
- Recurring service revenue layered underneath delivery work
A portfolio view stabilises the machine.
2. Cadence Beats Heroics
Heroics win tenders.
Cadence builds companies.
I want:
- Monthly revenue predictability
- Steady labour utilisation
- Controlled procurement cycles
- Planned capital spend
- Forecast accuracy within ±5%
If your financial performance looks like a cardiogram, you don’t have a growth platform — you have a stress test.
A COO’s job is to build operational rhythm.
That means:
- Sales → Ops handover discipline
- No surprise project launches
- Resource planning embedded in pipeline reviews
- Weekly capacity heatmaps
- Cash forecasting embedded in project review
3. Revenue Without Margin Is Noise
When projects flood in, organisations get excited.
I get cautious.
Because volume without margin discipline creates:
- Working capital strain
- Overtime creep
- Subcontractor dependency
- Quality erosion
- Claims exposure
A COO must protect contribution margin first, revenue second.
That means:
- Bid governance gates
- Risk weighting in tender reviews
- Realistic programme modelling
- Cash curve modelling before contract signature
You don’t “win” projects.
You acquire risk.
The question is whether that risk aligns with capacity.
4. Working Capital Is the Silent Killer
Project businesses don’t die from lack of revenue.
They die from lack of cash visibility.
Every major job should be modelled with:
- Billing milestones
- Retention exposure
- Variations timing
- Procurement outflows
- Payment term lag
If your growth consumes cash faster than you generate it, you are scaling fragility.
COOs must embed:
- WIP ageing dashboards
- Debtor days discipline
- Milestone billing enforcement
- Variation approval velocity tracking
Growth must fund itself.
5. The COO Mandate
My mandate is simple:
Build a machine that delivers consistently, absorbs volatility, and scales without panic.
That requires:
- Portfolio balancing
- Resource smoothing
- Margin discipline
- Cash visibility
- Leadership rhythm alignment
If you solve operating rhythm, feast-or-famine disappears.
Not because revenue stops fluctuating —
but because the organisation is no longer fragile.