A familiar month: busy, then quiet.
If you run a specialist firm, you know the pattern. One month your calendar is full and the business feels stable. The next month the work ends, follow-ups are scattered, and your pipeline is thinner than you thought. The work did not disappear overnight — it just stopped being fed.
This is the Founder’s Trap. It shows up in technical services, built environment practices, and training or consulting firms because all three share one constraint: the product is expertise, and delivery depends on people’s time. When time is scarce, growth work is the first thing postponed. There is a name for the feast–famine cycle: porpoising — you surface for air, then dive, again and again.
Porpoising is an operating-system problem.
It is tempting to blame marketing — "we need more content," "we should run ads." Those are tactics. The deeper issue is operational: delivery has deadlines and immediate feedback; marketing has ambiguous deadlines and delayed feedback. The brain chooses urgency over importance every time. So when a job runs late or a client calls, growth tasks get dropped.
If your pipeline depends on “when we have time,” you do not have a pipeline system. You have a manual hustle. The structural fix: always have at least one marketing activity running — no matter how much delivery is in progress.
The Alice Trap.
The Alice Trap is becoming excellent at fulfilling orders but never building the machine that creates the next one. You feel productive because you are always busy — but busyness is not growth.
- Technical services: producing high-quality reports that end relationships instead of starting programmes.
- Built environment: finishing a project and waiting for the next tender instead of tracking developer relationships across cycles.
- Training & consulting: delivering workshops without capturing demand or packaging renewal.
Selling is practising your profession.
When you help a client see that their problem is bigger than they thought — that their current approach leaves gaps they cannot see — that is your expertise applied to problem definition. The best business developers in professional services do not think of themselves as salespeople. They are problem identifiers who also happen to solve what they identify.
Production mindset vs marketing mindset.
Production mindset says: do great work and the market will notice. Marketing mindset says: do great work, then make the market notice — on purpose, with repetition. On average, ~70% of the buying decision is made before a prospect ever talks to you, and that share is rising. The article you publish today is where the sale actually happens; the meeting just confirms a decision your content already influenced.
A simple test: if you stopped marketing completely for 30 days, would new opportunities still appear? If not, your pipeline is not compounding — it is being pushed.
What breaks the trap: a minimum viable growth system.
The fix is not inspiration. It is installation — a simple set of assets and rules that keep the business visible and responsive.
A credibility website
That answers the buyer’s real question: "can these people solve my problem?"
A lead-capture asset
A useful playbook or checklist worth an email address.
A follow-up rule
No lead without a next action. Remove memory from the loop.
A simple pipeline view
Stages and dates, so nothing depends on how you feel that week.
A 30-day reset.
Plug the leaks
Every service page needs a clear next step; your lead magnet must work; your CRM enforces one rule — no lead without a next action.
Publish one proof page
Show the method, the criteria, and one anonymised "what changed and why."
Templates & stages
Follow-up templates and pipeline stages, so the loop no longer relies on memory.
Post-delivery re-entry
Every engagement should create the next conversation.
If you only do one thing this month
Stop letting delivered work end the relationship. Create a default post-delivery step: a review call and a programme option. Specialists win by being consistently present at the moment decisions are made.
The trap is not a motivation problem. It is a system problem — and systems can be designed. In Part 2, we make it measurable with a simple growth engine: Revenue = N × B × F.