Narrowing to one vertical when it shrinks the pipeline
The hypothesis put to the council
A generalist consultant should narrow to a single industry vertical even though doing so shrinks their addressable pipeline in the short term.
The situation
A composite. Every number below is a working fact for the debate, and describes no real person or company.
Independent data and analytics consultant, five years solo. $180,000 across 11 engagements in the trailing year, averaging $16,400 each, spread across e-commerce, healthcare, professional services, manufacturing, non-profit and fintech.
70% of leads come from referral, 30% from a general-interest blog. Close rate on qualified conversations is 34%. Domain ramp-up eats an estimated 15-25% of the first month on every engagement.
The two healthcare engagements were the most profitable — roughly 40% higher effective rate — and also had the longest ramp-up. Rates have been flat at $150/hr equivalent for two years. Seven months of runway, no debt, no intention of hiring. The goal is $240,000 without adding hours.
The verdict
Invalidated
Invalidated, on two grounds. The seven-month runway cannot absorb the pipeline replacement risk of declining roughly 82% of incoming referrals while a new vertical-specific channel is built from nothing.
And the evidence for narrowing is thinner than it looks: the 40% healthcare premium rests on two engagements. There is no way to tell from n=2 whether the premium is specific to healthcare, or simply what regulated work pays regardless of industry — and those imply completely different strategies.
Where the verdict flips
Months of committed revenue — cash plus signed backlog — at the moment declining begins, at 12
Below 12 months, stay general and productize the offer instead. At or above 12, narrowing becomes viable.
The useful reframe here is that narrowing is not one decision but two, and they are usually conflated. You can narrow the *offer* — fixed shapes, fixed prices, a repeatable deliverable — without narrowing the *industry*. The first captures most of the ramp-up and proposal-reuse savings. The second is what costs you the referral base, and it is the one that needs the runway behind it.
Where the council disagreed
Kept as it came out of the session. The chairman states which way the evidence points, but the split is the useful part.
Whether the premium is industry-specific or regulation-specific
The case for narrowing assumes the 40% is a healthcare premium. The counter is that it may be a regulated-work premium that would appear equally in fintech — and the case file contains exactly one fintech engagement, which is not enough to tell. The council named this as the decisive missing input rather than guessing.
Whether generalist buyers would pay the higher rate
One line of argument held that the premium can only be captured by narrowing, because generalist buyers will not pay it and the referral engine is industry-clustered anyway. The chairman did not accept the clustering claim as established from the case file.
Whether repackaging is a real alternative or a delay
The opposing read is that fixed-price shapes are what a consultant does when they are avoiding the harder positioning decision, and that it postpones rather than resolves the rate problem. The council took the shapes route anyway, on the runway argument.
The strongest case against this verdict
Stated so its advocate would accept it.
The 40% premium and the ramp-up recovery can only be captured by narrowing, because generalist buyers will not accept the higher rate and the referral engine is already industry-clustered.
That case wins if the fintech engagement's effective rate sits at the portfolio mean rather than clustering with the two healthcare engagements — which would show the premium is about the industry rather than about regulation.
First three moves
This week
Define two fixed-fee shapes with named deliverables and fixed durations, and add a regulated-data tier as a separate, higher-priced item with the compliance work listed as an included deliverable rather than a discount to absorb.
Next 30 days
Send the rate increase and the new shapes to existing clients at renewal, build one reusable proposal template per shape, and test the shapes on the next two qualified conversations — without changing the website headline yet.
Weeks 5-8
Decline any engagement that does not fit one of the two shapes, and measure effective hourly rate on closed deals. That number, not the positioning, tells you whether it worked.
Note what is deliberately not in move one: changing the website. Positioning is the expensive, hard-to-reverse part, and it is last rather than first.
How this goes wrong
Failure mode
The phantom price rise. The rate card and the shapes change, but actual contracts get discounted back toward the old number, so the repositioning shows up in the marketing and never in the bank.
Early warning signal
The first two proposals at the new pricing close with zero price objection. That sounds like success and is the opposite — it means the number was never tested.
What we checked
All 7 factual claims in this session were checked against primary sources afterwards, and 3 survived as sourced fact. The most consequential are below; the outcome of every one is in the fact-check ledger. The reasoning above stands on its own. Most of the numbers the council reached for do not.
Verified and citable
Cut — no locatable source
- A third named competitor selling “diagnostic sprints”. The company is real but sells nothing of that name and publishes no pricing — the product was invented. This is the clearest single hallucination in the corpus.
- Specific figures for how much industry specialization lifts consulting rates or win rates. The percentages the session reached for do not appear in the source they were attributed to.
The council's assumptions, not established facts
- That regulated-industry work commands a 25-40% premium. The range is widely repeated in vendor commentary about compliant software and managed services, but no primary study supports it and nothing ties it to consulting engagements specifically.
- That executing a BAA and providing access controls are billable differentiators. Plausible business reasoning, but nothing published establishes it as market practice.
- The 12-month committed-revenue threshold, which is the council's own derivation from the case file rather than a benchmark.
Two things are worth saying about how this one was checked. First, the heuristic that a small company quoted with a precise price is probably invented turned out to be wrong twice over — both audit prices above are real and exact. Second, one fabricated statistic in this session did not originate with the council at all: it came from an AI search summary that attributed figures to a real page which does not contain them. Verifying a citation now means opening the page, not reading a summary of it.
How this session ran
- Council
- Claude Opus 5 · GPT-5.5 · Gemini 3.1 Pro · Grok 4.3 · Kimi K2.6
- Chairman
- Grok 4.3
- Written for
- Solo consultants and independent specialists
- Shape
- Five independent proposals, anonymized peer review, chairman synthesis. One round.
Also in the ledger
A Council Audit on your own decision
Every external claim is checked against primary sources before you read it. What survives is cited. What doesn't is printed as cut, the same way it is above.
You get one recommendation and the number at which it flips, the strongest argument against it, and the first three moves in order.
$299. Written brief in 48 hours. No call.