Agency and service business plan example
An illustrative agency business example: utilisation, pricing model, dependency risk, evidence gaps and the questions investors and lenders ask.
Quick answer
This illustrative agency example sells project-based delivery to a defined client type. Its credibility rests on realistic utilisation, pricing that reflects delivery cost, and a plan for the client concentration and founder dependency that most small agencies carry.
Important note
Illustrative fictional example. This is not a real CEO? customer, and every figure below is a labelled working assumption for illustration — not an observed result, benchmark or projection you should rely on.
Business summary
A fictional three-person agency delivering technical implementation projects for mid-market clients. Revenue is project-based, referral-driven, and concentrated in two clients.
The problem
Clients need short bursts of specialist delivery capability without hiring permanently. Generalist suppliers are cheap but slow to become useful; large consultancies are expensive and poorly suited to small engagements.
Target customer
Operations and technology leaders at mid-market companies with a defined project need and budget authority up to a moderate threshold, buying on trust and speed rather than through formal procurement.
Business model
Fixed-price projects with an optional monthly retainer. Profitability depends on utilisation, estimation accuracy and the ratio of billable to non-billable time. The retainer is the route to predictable revenue but changes the delivery discipline required.
Go-to-market assumptions
These are the routes to market this fictional business would test first. Each is an assumption until it produces measurable results.
- Referral from completed projects as the primary channel
- Narrow positioning around one repeatable engagement type
- Partnerships with adjacent suppliers serving the same clients
- Productised entry engagement at a fixed scope and price
Key evidence still needed
The gaps that would stop this plan being credible to an investor, a lender or the founder's own decision-making.
- Actual utilisation over a full quarter, not a good month
- Estimation accuracy against delivered hours
- Whether the retainer is something clients will actually buy
- Pipeline that is not dependent on the founder's personal network
- Client concentration risk quantified honestly
Financial assumptions to validate
Working assumptions used for illustration only. Each would need to be replaced with observed data before it belongs in a real forecast.
- Assumed billable utilisation, typically over-stated in early plans
- Assumed day rate before discounting
- Assumed project length and payment terms
- Assumed no bench time between projects
- Assumed a new hire is productive immediately, which is rarely true
Questions an investor would ask
The questions this business should be able to answer without hesitation before a first meeting.
- What proportion of revenue comes from your largest client?
- What is your actual utilisation, and how do you measure it?
- What happens to delivery if the founder stops selling?
- How do you scale without proportionally scaling headcount?
- What is repeatable here, and what is bespoke every time?
Common contradictions and risk areas
Where documents in a business like this typically fall out of step with each other, and where the underlying risk sits.
- Day rate in the model higher than the rate actually invoiced
- Utilisation assumption incompatible with the stated sales effort
- Retainer revenue in the forecast with no retainer clients
- Headcount plan that ignores ramp time
- Client concentration omitted from the risk section but visible in the numbers
Home · Features · How it works · Pricing · Compare · For founders · Try free