# Working Session

**Published:** 2026-09-06
**Last Updated:** 2026-09-06

START HERE: THE ANTI-AUDIT

# How Do We Start Fixing Growth Without Another Audit Sitting in a Folder?

Start with the decision at risk, not the channel you think is broken.

You already own the audit. Two of them, probably. One in a shared drive, one in a consultant's slide template, both describing a company that has since changed. What you do not own is a decision. Twenty minutes can change that, because twenty minutes is long enough to classify a problem and too short to sell you a program you did not ask for.

This page describes exactly what happens in a 20-Minute Pipeline Loss Recovery Working Session: what to bring, what happens minute by minute, what you leave with, and the honest conditions under which the right next step is something smaller than an engagement. Low friction. Specific. Commercially serious.

[Book a 20-Minute Pipeline Loss Recovery Working Session](/hire-me/)

Or [take the 4-Minute Bottleneck Diagnostic](#diagnostic) if you are not ready to book yet.

## You do not need another document. You need a decision.

Name the pattern honestly, because it deserves naming: the audit economy. You commissioned a report, received forty pages, held one meeting about it, and watched it dissolve into a shared drive the moment its author's invoice cleared. The audit did not fail because it was wrong. It failed because it was addressed to no decision. Describing a problem and changing a system are different professions, and the industry has been quietly invoicing you for the first while charging you as if it were the second.

The Working Session inverts the sequence. It starts with the decision you are trying to make, works backward to the evidence that decision needs, and identifies the single most likely leak standing between them. Twenty minutes is enough for that. It is not enough for much else, which is precisely the point: the format makes overpromising structurally difficult. A session that ends with a decision and a next step is honest by design, because there is no room in twenty minutes to hide a sales pitch inside a diagnosis.

<table>
<thead><tr><th>What you received before</th><th>What was missing</th><th>What a working session changes</th></tr></thead>
<tbody>
<tr><td>A 60-page audit</td><td>A named decision the work would change</td><td>The session opens with your decision, not a methodology</td></tr>
<tr><td>A content calendar</td><td>A link between content and pipeline evidence</td><td>The likely leak is classified before any content is discussed</td></tr>
<tr><td>A dashboard walkthrough</td><td>Reconciliation rules everyone accepts</td><td>You leave with one decision and one evidence gap, in writing</td></tr>
</tbody>
</table>

*If the last audit did not change a decision, it was not the answer to the problem. It was a very well-formatted delay.*

## The working session starts with the decision at risk

Every engagement begins the same way: not with a technical checklist, but with a question about what the company is trying to decide. It might be a budget decision, where next quarter&apos;s spend goes. A hiring decision, fractional leadership or a full-time executive. A rebuild decision, whether to migrate and what must survive. A channel decision, whether to keep funding something nobody can explain. Or a board narrative, what to say when the CFO asks what organic contributed. The diagnosis follows the decision, because the same symptom, flat pipeline, has different meanings under different stakes, and treating the stakeless version of a problem is how consultancies stay busy.

This ordering also protects you from the most expensive mistake in the category: commissioning work before the decision exists. Evidence gathered without a decision attached is trivia with formatting. Evidence gathered for a named decision is leverage, and twenty minutes is enough to tell the difference.

<table>
<thead><tr><th>Decision type</th><th>The question at risk</th><th>What the session examines</th></tr></thead>
<tbody>
<tr><td>Budget</td><td>Where does next quarter&apos;s spend go?</td><td>Unknown-source share, recapture signals, channel evidence</td></tr>
<tr><td>Hiring</td><td>Operator, partner, or internal owner?</td><td>Complexity, urgency, existing ownership</td></tr>
<tr><td>Rebuild</td><td>What must the migration protect?</td><td>Evidence continuity and priority pages</td></tr>
<tr><td>Board narrative</td><td>What can we defend about organic?</td><td>Sourced, influenced, and unknown pipeline</td></tr>
</tbody>
</table>

*Bring the decision, not the symptom. Symptoms multiply. Decisions are rare and expensive, which is why they deserve the first twenty minutes.*

## What to bring to the conversation

Preparation should be light, and the bar is deliberately low: incomplete evidence is itself useful diagnostic material, because how the company fails to record things is information. Bring what exists. If a category is missing, that absence is data too, and the session treats it as such rather than as a disqualification.

The board concern in one sentence anchors the whole session to a real decision. One competitor makes displacement concrete and testable. Top three pages by importance grounds the proof discussion in real assets. A recent pipeline report reveals where evidence dies, or its absence becomes the finding. And sales feedback, informal is fine, because first-call objections are the cheapest diagnostic in the building.

<table>
<thead><tr><th>Bring this</th><th>Why it matters</th><th>If you do not have it</th></tr></thead>
<tbody>
<tr><td>The board concern, in one sentence</td><td>Anchors the session to a real decision</td><td>Say it from memory; precision is not required</td></tr>
<tr><td>One competitor</td><td>Makes displacement concrete and testable</td><td>Skip it; the session works on internal leaks alone</td></tr>
<tr><td>Top three pages by importance</td><td>Grounds the proof discussion in real assets</td><td>Name them from memory</td></tr>
<tr><td>A recent pipeline report</td><td>Reveals where evidence dies</td><td>The absence of one is itself the finding</td></tr>
<tr><td>Sales feedback, informal is fine</td><td>First-call objections are the cheapest diagnostic</td><td>Bring one rep&apos;s quote if that is all you have</td></tr>
</tbody>
</table>

*Bring what exists. The gaps in your evidence are not a disqualification. They are the exhibit.*

## What happens during the 20 minutes

The structure is fixed, and its rigidity is the feature: it prevents the conversation from drifting into either a sales presentation or a therapy session about your last agency. Minutes zero to five clarify the business question. Five to ten identify the likely leak category: demand, proof, visibility, website delivery, or reporting. Ten to fifteen establish what evidence exists and what is missing. Fifteen to eighteen identify who owns the repair. Eighteen to twenty agree the next move, which may be a deeper diagnostic, a focused repair, or the honest answer that the problem is internal and smaller than feared.

<table>
<thead><tr><th>Minute range</th><th>Conversation focus</th><th>Output</th></tr></thead>
<tbody>
<tr><td>0 to 5</td><td>Clarify the decision at risk</td><td>One sentence, written down</td></tr>
<tr><td>5 to 10</td><td>Classify the likely leak</td><td>Demand, proof, visibility, delivery, or reporting</td></tr>
<tr><td>10 to 15</td><td>Establish the evidence gap</td><td>What exists, what is missing, what it would show</td></tr>
<tr><td>15 to 20</td><td>Agree owner and next step</td><td>One owner, one action, one deadline</td></tr>
</tbody>
</table>

*Twenty minutes, five segments, one decision. If it cannot be done in that shape, it was never a session. It was a pitch.*

## What you leave with

Four things, none of them a document trilogy. A primary hypothesis you can stress-test internally. A precisely named evidence gap, so the next internal conversation has a subject. A priority action with an owner and a time bound. And a stakeholder map: the two or three people whose cooperation the fix requires, identified before politics can ambush it. What you do not leave with is a forecast, a guarantee, or a feeling of having been sold, because the session&apos;s value proposition is the opposite of all three: clarity about the next decision, priced at twenty minutes.

<table>
<thead><tr><th>Output</th><th>Why it matters</th><th>Confidence</th></tr></thead>
<tbody>
<tr><td>Primary hypothesis</td><td>Gives the internal team something falsifiable to test</td><td>Stated with confidence label</td></tr>
<tr><td>Named evidence gap</td><td>Converts anxiety into an investigation</td><td>High, as a gap definition</td></tr>
<tr><td>Priority action with owner</td><td>Ends the meeting with motion, not notes</td><td>Depends on access provided</td></tr>
<tr><td>Stakeholder map</td><td>Prevents the repair from dying in a silo</td><td>Medium until names confirmed</td></tr>
</tbody>
</table>

*You leave with a hypothesis, a gap, an action, and an owner. Everything else you have read on this subject was decoration.*

## When the next step is not a larger engagement

Here is the clause most providers bury and this one leads with: sometimes the session concludes that the right next step is no engagement at all. If the leak is an internal fix a capable RevOps lead can execute in a fortnight, the session will say so, with the steps sketched. If the evidence needed does not yet exist in any system, the recommendation will be measurement before money. If the problem is genuinely product rather than growth, that will be said plainly, because diagnosing product problems as marketing problems is a specialty the industry does not need more of. Evidence before commitment is not modesty. It is the same standard the rest of this site applies to everyone else.

*A diagnostic that sometimes prescribes do-nothing-external is the only kind worth trusting with your budget.*

## Start with the bottleneck, not the channel

Six bottlenecks, one first question each, and the discipline of refusing to argue about channels until the bottleneck is named. Demand: is the market generating interest that never becomes visible? Proof: do buyers find enough to defend you in rooms you are not in? Visibility: do answer engines retrieve your evidence when buyers research? Website delivery: can buyers and machines actually reach the proof? Reporting: can the company explain its own pipeline? Shared ownership: does anyone hold the whole path, or only their piece of it? The Working Session exists to put your company in exactly one of those boxes, honestly, and to hand you the first move.

[Book a 20-Minute Pipeline Loss Recovery Working Session](/hire-me/)

*The channel is almost never the problem. The bottleneck is. Twenty minutes finds it before the next budget makes it permanent.*

## Frequently asked questions

<summary>How do I assess a B2B SaaS growth problem before hiring a consultant?</summary>
Start with the decision at risk and work backward to evidence: unknown-source share of pipeline, qualified engagement on priority pages, and where source dies between visit and CRM. A working session structures exactly that assessment in twenty minutes.

<summary>What should a first growth strategy call produce?</summary>
A written primary hypothesis, a named evidence gap, one priority action with an owner, and a stakeholder map. If a first call produces only rapport and a proposal, it was a sales call wearing a diagnostic costume.

<summary>How do I avoid another useless marketing audit?</summary>
Require that any diagnostic name the decision it will change before work begins, and weigh deliverables by decisions enabled rather than pages produced. Documents that attach to no decision are decorative by definition.

<summary>What does a practical SaaS pipeline recovery conversation look like?</summary>
Five fixed segments in twenty minutes: decision clarified, leak classified, evidence gap named, owner identified, next action agreed. Specific enough to be falsified, which is what makes it useful.

*Outcomes referenced on this site are career-reported and methodology-disclosed. They reflect operating conditions specific to each prior engagement and do not predict future performance for any organization.*