Building Recurring Revenue Into a Project Business
Last updated:
Why project businesses want recurring revenue
Project work is lumpy: feast and famine, constant selling, and revenue that stops when delivery stops. Recurring revenue smooths cash flow, funds a stable team and makes the business considerably more valuable if you ever sell it.
The difficulty is structuring it so that it is genuinely valuable to the client rather than a subscription to your availability.
Three retainer shapes
- Maintenance. Keeping something working: updates, monitoring, fixes. Clear scope, easy to justify, modest value.
- Capacity. A defined number of days or hours per month, used flexibly. Simple and prone to unused-hours disputes.
- Outcome. Responsibility for a result — uptime, response times, a metric. Highest value, requires trust on both sides.
Most firms start with the first, and the second is where most revenue sits.
Define the boundary explicitly
The killer question, agreed in writing at the start: is a change to how something works maintenance or a project? Every retainer dispute we have seen came down to that sentence being absent.
- What is included, with examples
- What is explicitly excluded, with examples
- The response commitment, and what response means
- What happens when included hours are exceeded
- Whether unused hours roll over, and for how long
Price it to be worth delivering
Retainers priced as a loss-leader to keep a client become work you resent and deprioritise, which is the worst outcome for both sides. Price at a rate you would be content to deliver at indefinitely.
A modest discount against project rates is reasonable in exchange for predictability. A heavy one is not, and it will show in the service.
Report on it, monthly
The most common cause of retainer cancellation is not poor service — it is the client not seeing what they received. A short monthly report of what was done, what was prevented and what is coming makes the value visible.
This is also how you catch the drift where a maintenance retainer has quietly become a development one.
Review annually
Scope creeps, systems grow, and the retainer set two years ago no longer reflects the work. An annual review with the actual hours in front of both parties is a normal business conversation and prevents resentment accumulating.
Frequently asked questions
What proportion of revenue should be recurring?
Should unused hours roll over?
How do we sell a retainer to a project client?
What if a client barely uses the retainer?
Delivering support with no agreement behind it?
That is unlimited demand at an unpredictable price. Happy to talk through how to structure it properly.
Related services
What we build for problems like this one