How to audit your own growth system

To audit your own growth system, trace a client's journey backwards — from signed contract to first touch — and write down, at each stage, what actually happened and who made it happen. Most firms discover that the answer to "who made it happen" is the founder, at every stage, and that between stages there is no system at all, only memory and luck. The audit's job is to turn that vague unease into a specific list of what to fix first.

This is the DIY version of the diagnostic behind The Founder-as-Bottleneck Report. It will not be as thorough as an outside pair of eyes, but done honestly it gets you most of the way.

What are you actually auditing?

Five functions, in order. Demand generation: how strangers become aware of you. Capture: how interested people become recorded leads. Follow-up: what happens to leads who do not buy immediately. Conversion: how qualified leads become clients. Reporting: whether you can see any of the above in numbers without compiling a spreadsheet by hand.

A growth system is only as strong as its weakest of these five. Firms commonly obsess over conversion — the visible, dramatic stage — while leads die silently in follow-up, which is invisible and undramatic.

What questions do you ask at each stage?

Work through these with real data, not impressions.

• Demand: where did your last ten clients originate? If eight or more say "referral" or "existing network", you do not have demand generation — you have a depleting asset.
• Capture: when someone enquires through your website, what happens in the first hour? Test it yourself with a dummy enquiry and time the response.
• Follow-up: how many touches does a non-responsive lead receive before you stop? Most firms stop at two, while deals typically need five or more.
• Conversion: what is your win rate on proposals issued? If you cannot answer from records, that is itself a finding. If it is above 60%, you are underpriced — raise prices 15%.
• Reporting: can you state, today, how many open opportunities you have and their total value, without asking anyone or building anything?

How do you run the audit, step by step?

The mechanism is a paper trail exercise. When you pull your last ten closed deals, then you list each one's source, first contact date, and close date. When you plot those first-contact dates on a calendar, then you see whether new business arrives continuously or in bursts that correlate with the founder's free time — the pattern behind lumpy revenue. When you pull ten deals you lost or that went silent, then you count the follow-up touches each received and note who was supposed to send them. When you write down every stage where the answer to "who does this" is a person rather than a process, then you have your bottleneck list. When you rank that list by "what stops working if the founder takes a month off", then the top item is what you fix first.

The whole exercise takes half a day with honest records, longer if the records do not exist — which is, again, a finding.

What do the results usually show?

Three patterns recur across almost every firm I have audited. First, referral dependency: demand generation is not a system, it is a hope. Second, the follow-up void: capture works, initial response works, and then nothing — no sequence, no nurture, no reactivation. Third, founder gravity: every function that works, works because the founder personally drives it, which is the founder-led sales trap extended across the whole business.

Note what is usually not the problem: the service itself, the pricing, the market. Firms at this size have proven demand. The leak is structural.

What do you do with the findings?

Fix in sequence, not in parallel. The order that typically pays back fastest: instrument reporting first (you cannot manage what you cannot see), close the follow-up void second (cheapest revenue you will ever recover), then build demand generation that runs without the founder. Resist the urge to fix everything at once; a growth system is installed one mechanism at a time.

One caution: self-audits flatter. You will be tempted to grade "we sort of do this" as a pass. The rule I use — if it does not happen when the responsible person is on holiday, it is not a system, and it fails the audit. Related: infrastructure failures can masquerade as demand problems, so if outbound "stopped working", check deliverability before rewriting your copy.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.