Our take: most businesses need a partner, not another project
Why the project model produces a rebuild every few years and a decay in between, and why a continuous partnership serves a small business better.
The short answer
The project model is how most small businesses buy digital work: a website is built, handed over and left. Nobody maintains it, nobody improves it, nobody owns its numbers. It decays: dependencies age, forms fail, speed slips, the business changes and the site does not. Three years later it is rebuilt, and the cycle begins again. The business pays for the peaks and suffers the troughs, and the losses in between, customers lost to a slow site, incidents on an unmaintained platform, hours on workarounds, never appear on an invoice. A partnership replaces the cycle with a continuous relationship: the site kept current, secure, fast and improving, in the business’s own accounts, for a fixed monthly fee, with projects inside it when they are needed. Over five years the partnership is the cheaper of the two once sixty monthly fees come to less than the rebuilds in that period, plus the emergency work at hourly rates, plus the hours your own people spend coordinating suppliers. Fill in your own figures: how many rebuilds you expect, what your hourly rate is, how many incidents a year and how long they last. The exceptions are real; for most small businesses, the partner is the better model.
Project cycle versus partnership
| Project cycle | Partnership | |
|---|---|---|
| Shape | Build, hand over, decay, rebuild | Continuous: maintain, improve, project when needed |
| Cost shape | Large lumps every few years | A fixed monthly fee plus projects |
| Between projects | Nobody owns the site; it decays | Someone owns the working of everything |
| Speed and security | Good at launch, worse every month | Kept current and measured monthly |
| Changes | Wait for the next project or become emergencies | A change budget and a quarterly plan |
| Ownership | Often in the agency’s name until disputed | In the business’s name from day one |
| Knowledge | Leaves with the agency | Transferred continuously; documented |
| Losses | Invisible: lost customers, incidents, hours | Measured and reduced |
| Five-year total | Two or three rebuilds plus the invisible losses | Usually lower, with a better site throughout |
Why the project model persists
- It matches how budgets are approved: a project has a price and a date; a partnership is a line item forever.
- Its costs are visible and its losses are not: the rebuild is an invoice; the decay is customers who never called.
- Agencies are organised around projects: the model suits the seller.
- The first website is bought before the business knows better: the second one is usually a partnership.
When a project is enough
A genuinely static site for a business that will not change it: built properly, in your name, on a stack that needs almost no maintenance, with a light monitoring and update routine that can be bought cheaply. A business with its own team that will own the site after the build. A specific piece of software with a clear end and an internal owner. In each case the project sits inside a light form of ownership; what it should never sit inside is nothing.
What this means for you
If your digital history is a series of rebuilds with decay between them, the model is the problem. Choose a partner who keeps the site current, secure, fast and improving for a fixed fee in your own accounts, with projects when needed and a report every month. Compare five years, not one invoice. For most small businesses the partnership is cheaper and better, and it ends the cycle.
Frequently asked questions
Is a monthly fee not more expensive than paying for a project when we need one?
Compare five years: two or three rebuilds with emergencies, neglect and lost customers in between, against a continuous fee that keeps the site current and improving with projects inside it. Which of the two totals is lower depends on the assumptions you put in, and the arithmetic is worth doing with your own. What is not in the arithmetic is that in the second there is never a period when the site is decaying. The project model looks cheaper because its costs arrive as lumps and its losses arrive invisibly.
What if we just need a website built?
Then have it built, properly, on foundations that last, in your name, with light maintenance. That is a project inside a light partnership, and for a site that genuinely will not change much it is enough. The question is what happens in month four when the first change is needed, the first update is due and the first form fails. Someone must own that, or the decay begins.
How is a partnership different from an agency retainer?
A retainer buys hours; a partnership buys outcomes: the site kept current, secure, fast and improving, reported monthly, with a stated response time and a change budget. Retainers are consumed by small requests and nobody owns the whole; partnerships have someone accountable for the working of everything. The distinction is accountability, not billing.