Karim Hammad, Founder
Where do service businesses lose capacity?
Service businesses usually lose capacity in the repeated administration around delivery: onboarding, follow-ups, scheduling, document preparation, status updates, reporting, and the coordination required because tools do not share information. The bottleneck is the step that makes every additional client expensive in staff time.
Start from one real client
Pick a recent client and write the path from first yes to a delivered piece of work. Include every handoff, every place information is typed again, and every time someone waits.
The path that looks obvious to the person who runs it is usually invisible to the owner. That path is the source material. A generic process map is not.
Separate judgment from repetition
Mark the steps that require the firm’s expertise. Leave them. Mark the steps that are the same for almost every client: requesting a document, sending a reminder, opening a record in a second tool, building the weekly status.
The second list is where capacity is leaking. It is also the list that grows in a straight line with the client base, which is why hiring feels inevitable.
Look for the queue, not the complaint
People complain about the tool they touch most. The bottleneck is often the wait before that tool: information that has not arrived, an approval nobody can see, a report that cannot be built until three exports are merged.
Ask what would happen to the team’s week if that wait disappeared for the next ten clients. If the answer is “we could take the work,” you have found a capacity constraint. If the answer is “we still could not deliver,” the constraint is somewhere else.
Do not automate the first thing you see
A bottleneck worth a system is repeated, understood, and expensive in staff time. A one-off frustration, or a step that changes every week, will not repay the build.
Write the candidate in one sentence: who does it, how often, and what the next client costs in hours. That sentence is enough to decide whether a conversation about implementation is worth having.
