Client onboarding
Welcome sequences, contracts, access setup, briefing collection. All triggered when a project is confirmed, rather than assembled by hand each time.
Founders and small teams
10PM helps founders and small teams simplify repetitive administration before deciding whether to hire. We look at onboarding, billing, reporting and duplicated entry, then check which changes can create useful capacity.

At a glance
The problem
Founder-led teams of two to five hit a familiar ceiling: too much work, not enough people. The instinct is to hire. Before adding anyone, it is worth asking which of that work should not be done by a person at all.
The tasks that repeat with every client and every month are the ones worth looking at: onboarding, invoicing, status updates, reporting, moving the same data between two systems. None of it needs your team’s judgement. It needs consistency and speed, which a system does better than a person does.
The Review identifies what is genuinely worth automating, what the current situation costs you in a year, and whether building anything makes financial sense before you commit to it.
The useful question is how much repeatable work your team can remove, and what they would do with the released time. The Review starts with your actual tasks, rather than a promised team-size multiplier.
Where the time goes
The highest impact fixes tend to be the ones that touch every client, every cycle.
The arithmetic
The compounding matters more for a team than for one person. If two people each spend four hours a week on work a system could do, that is around 400 hours a year across the team, assuming a fifty-week year.
At a blended internal rate of £150 an hour, those 400 hours represent around £60,000 of capacity. Your own rate and your own hours give your own number, and the Review works it out with you rather than assuming it.
The point is not the headline figure. It is that the same fix removes the problem for everyone at once, which is what makes it different from hiring.
Premium Paye
At Premium Paye in France, invoice preparation, direct debits and online onboarding were connected. The founder reports around twelve hours of admin in a busy month with new clients before the change, and under one hour now across those processes.
Read the case studyRecruitment agency, London
Activity lived across spreadsheets, email and notes. It was all recorded and none of it could be used to decide anything. Reporting built backwards from the founder’s own questions changed that.
Read the case studyHow it works
We agree the right depth of discovery first. Each paid stage has its own deliverables and fixed fee; you decide whether to continue after it.
First, a free 15-minute conversation to understand the challenge and agree the appropriate next step.
We explore the process, what you want to achieve and how your team prefers to work. I challenge the proposed solution if the underlying problem is different.
You receiveA clear process map, written recommendations and an agreed priority.
During separately scoped Process Design, I check the connections, permissions, costs and exceptions that could affect the solution.
You receiveA documented workflow, feasibility findings and the requirements for a reliable build.
Before implementation, we agree what will be built, the timeline, responsibilities and how we will check that it works.
You receiveA written proposal with a fixed build price, acceptance checks and any ongoing costs.
I build the agreed solution and test normal cases, exceptions and approvals. Your team reviews it against the checks we agreed.
You receiveA working solution, a demonstration and the agreed checks completed before handover.
I show your team how to use the solution, what to monitor and how to handle exceptions. We clarify ownership and support.
You receivePractical instructions, a walkthrough and clear support terms so your team can run it.
Discovery, Process Design and implementation each have an agreed scope and fee. You choose the appropriate discovery service; buying both is not required. Testing, documentation and team handover are included in the agreed implementation scope.
Before we talk
Many of these come up in the free fifteen minutes, before anyone has spent anything.
Sometimes, yes. If the bottleneck is bespoke work that genuinely needs a person’s judgement, hire. If it is the weight of predictable admin sitting underneath the real work, removing the work first is often cheaper and faster.
The Review is designed to answer that question with your numbers rather than a rule of thumb.
I start with the tools you already use. Some workflows can use built-in features; others need a connector or an API-based service. We check access, usage limits, data handling and recurring costs before choosing the setup. You own the accounts, and the proposal identifies the subscriptions and support the agreed workflow needs.
No. Small teams often see the clearest result, because one person often carries most of the admin and removing it changes their week immediately.
Then you will hear that in the report, and you will have spent the price of the Review rather than the price of a build.
Keep reading
Your business
Tell me how your team spends its week. I will tell you whether removing work can create the capacity you need, or whether hiring is the better answer.
15 minutes · No charge
Prefer to write? anne@10pm.works