Building authority before your first case study

You build authority before your first case study by publishing your thinking: frameworks, definitions, numbers, and positions a buyer can test against their own experience. Buyers do not actually need proof you have done the work for someone identical to them — they need proof you think clearly about their problem, and written thinking demonstrates that directly. A case study says "trust the outcome"; published thinking says "check the reasoning yourself", and early on, the second is the only offer you can make honestly.

Why does published thinking convert?

Because it lets the buyer de-risk you before the first call. B2B service purchases fail on uncertainty — will these people understand my situation, do they have a method, or will they improvise at my expense? A specific article answers those questions in a way a logo wall never can. When a prospect reads your framework and recognises their own problem described precisely, then the first sales conversation starts from "how would this apply to us" rather than "convince me you're competent". The sale shortens because the qualification happened on the page.

There is a structural benefit too, and it compounds. An article is an asset that sells while you deliver — it works nights, weekends, and the months when delivery eats your diary. For a founder-led firm this is the first genuine exception to the trap described in The Founder-as-Bottleneck Report: almost everything else in early-stage sales consumes founder hours per deal, while published thinking is founder hours invested once and reused per reader.

What should you publish when you have no case studies?

Four types, in rough order of usefulness:

• Frameworks and diagnostics — the repeatable structure you would apply to a client's problem, given away in full. A scoring rubric or a decision rule shows method more convincingly than any claim about method.
• Definitions and positions — what you believe, stated plainly, including where you disagree with your industry's defaults. Positions filter as well as attract, which is what you want when your capacity is tiny.
• Numbers and mechanisms — the operating figures of your craft, hedged where they are rules of thumb, exact where they are yours. Specificity is the credibility; vague content reads as marketing because it is.
• Build logs and working notes — what you actually did, what broke, what you would change. Honesty about failure signals more expertise than a highlight reel, because only practitioners know where the failures live.

What not to publish: generic advice that any firm could have written. If a competitor could put their logo on it without lying, it builds their category, not your authority.

What is the mechanism for producing it consistently?

Treat publishing as a system with triggers, not an act of inspiration:

1. When you answer the same client or prospect question twice, then it goes on the article list. Repetition is the market telling you what it wants explained.
2. When you finish any piece of real work, then you extract one observation — a number, a failure, a pattern — into a note before the detail fades.
3. When the writing slot arrives each week, then you write the top item on the list — one fixed block, protected like a client meeting, because it is one.
4. When a piece is drafted, then it ships on schedule at "clear and specific", not "perfect". Authority accrues from the body of work, not from any single piece.

The trigger structure is the point: it removes the daily decision about whether to write, which is exactly the kind of recurring drain that pre-decided rules exist to eliminate — the broader method is in Decision rules: pre-deciding your way out of overwhelm.

How does this fit the founder-bottleneck problem?

Carefully, because writing consumes the same scarce hours as everything else. The discipline is to budget it inside an honest model of your week — the modelling approach is in Capacity: the constraint nobody models — rather than treating it as free evening work, which guarantees it stops the first busy month. A few hours a week, held consistently, beats a heroic burst followed by a silent quarter. The asset compounds only if the flow continues.

When do case studies take over?

They do not — they join. Delivered projects eventually produce outcomes worth writing up, and disciplined delivery is what makes them citable: fixed-scope builds that land on time, run through a defined sequence like the Gate system, generate clean before-and-after material almost as a by-product. But the thinking keeps doing distinct work. Case studies prove you did it; published thinking proves you know why it worked — and the buyer who needs both is the buyer you want.

---

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