For a couple of years, every few months, somebody would ask me the same question: could we just have you embedded in our business? Talk to our staff, work out what needs doing, and get on with it. And every time I said no, that’s not really what we do.
I was wrong. This year I changed my business around that question, and I think it’s the model more growing businesses should be asking for.
Why I kept saying no
Back then I was chasing big projects. A large upfront build looks great on paper. But it was vanity revenue rather than profit, and it wasn’t what a lot of the businesses in front of me needed. I’m fairly sure there were people who would have worked with us if we’d offered them what they were actually asking for.
You already buy other expertise this way
Most businesses pay a retainer for an IT company. Plenty pay one for a marketing agency to work on their growth. Nobody finds that strange.
I think the way things are going, a business should have the same arrangement for operational efficiency, software, AI adoption and whatever new technology comes next. A set number of days each month, with a team that knows how your business runs. I think of it as an outsourced internal team.
The problem with a single hire
The obvious alternative is to hire a developer. Sometimes that’s right. But it comes with costs people don’t count. You often lose the first few months while they get up to speed. On top of the salary there’s equipment, pension, National Insurance and somewhere for them to sit. And if they’re off sick or on leave, the work stops.
You’re also getting one person’s skills. A team on retainer brings several, and someone else can step in when one of them is away. A hire will give you more hours, and experience counts for a lot, so it isn’t always a straight swap. But for most of the businesses I work with, a retainer covers a serious share of the same ground for a fraction of the cost.
There’s a leadership gap too. You can hire a graduate developer, but who is going to give them senior direction and drive the company forward? Without it, a junior hire can be busy all day building clever things and still create the very problems I’ve described above. A team on retainer gives you both: the senior leadership and the hands. You can delegate the accountability, the work doesn’t stop for holidays or sick days, and you get knowledge that runs from consulting right through to delivery.
The problem with one-off projects
Projects are fine for a big, well-defined build. What they miss is all the small things. The booking form that doesn’t quite work. The report somebody builds by hand every month. None of them is worth a project on its own, so they never get fixed.
On a retainer you just get through them, alongside the bigger work. That’s where a lot of the real value turns out to be.
“But a hire is here full time”
That’s the strongest argument against a retainer: price against time. A full-time employee is in the business all week, and a tech team is there for less. My answer is that what matters is what gets done in that time, not how much of it there is.
It’s the measure I see people get wrong most often: frequency of use against actual outcomes. I don’t mind if we spend fewer hours than a full-time hire. If the outcomes are better, your money was well spent. It’s the same with AI. If one person spends ten hours with it and produces less than someone who spent one, you wouldn’t complain about the one-hour person.
How to set one up properly
If you go down this route, with anyone, these are the things I’d insist on.
One named person on your side. A single point of contact means the team isn’t interrupting your staff all day, and somebody is steering the direction.
A visible plan. We keep a running list of improvement ideas, turn the agreed ones into a prioritised roadmap, and set a plan each month showing what will get done and how long each item should take. You should always know where your days are going.
Numbers before and after. Record how long a process takes and how many people touch it before anything changes, then measure it again afterwards. Otherwise you can’t tell what’s working.
Clear commitments. If we miss a day one month, it’s credited to the next. The same goes for missed response times on support. Ask what happens when your provider falls short.
Your accounts, from day one. Everything gets built in accounts the client owns. If we ever step away, you keep the lot and can hand it to someone else in a single move. You should never be locked in because the work lives in somebody else’s account.
Training as part of the job. Introducing something new isn’t finished until your team knows how to use it.
What I’d ask before signing anything
Whichever route you choose, ask who will actually understand your business well enough to tell you what not to build. I won’t build something a client hasn’t properly scoped, because it wastes their money. The value isn’t only in the development. It’s in having someone alongside you who knows the operation, spots the next improvement and is still there next month to see whether the last one worked.
Let’s talk
If this struck a chord, I’d like to hear what you’re building.



