Lesson 6 — Discovery, Insights, and Account Development¶
"We focus very heavily on a concept that we refer to as not reporting the news. We want to give them insights, not the news."
— David Russell
1. Discovery vs. Due Diligence — They Are Not the Same Thing¶
Before anything else, get this distinction right. These two terms are easy to confuse and mean very different things.
| Due Diligence | Discovery | |
|---|---|---|
| What it is | An explicit, standalone project for exploring a business | The opening phase of any engagement, where we validate our hypothesis with real data |
| When it happens | At acquisition (pre-buy) or pre-exit (pre-sale) | At the start of every single project |
| Who requests it | The PE firm, before committing capital | Already baked into how we structure all engagements |
| Client attitude | Expected — they know they bought an inspection | Often resisted — they hired us to fix a specific thing, not go looking |
2. Discovery Happens on Every Project. Every Time.¶
This is not optional. It is not something we do only when we suspect the hypothesis is wrong.
"Every single project."
— David Russell
The reason is simple: we cannot validate or disprove our hypothesis without data. We sold a solution based on what the client told us from the outside. Discovery is how we find out whether we guessed right.
"We always start with a data request... You think pricing is the problem? Bring me your sales history, bring me your account histories, bring me all this stuff. We will often ask for slightly more than what is exactly necessary to solve exactly the problem. Because maybe that reaction you're having is not to the food. Maybe there's an allergen in your environment that you just didn't have a reaction to until just now."
— David Russell
The data request is the opening move of every engagement. It is not bureaucratic overhead — it is how we find the actual problem.
Project Coordinator Habit: Own the Data Request Log
The data request goes out at the start of every engagement. As the Project Coordinator, you own tracking whether it came back, when it came back, and whether what came back is complete. A delayed or incomplete data request is a patient, not a cadaver (see Lesson 3) — flag it while there is still time to recover, not after the timeline has slipped.
3. Why Clients Resist Discovery¶
Clients hired us to fix a specific thing. When we start asking for data beyond that specific thing, they notice — and many of them push back.
"Hey, by the way, I need you to fix the plumbing in the kitchen. Why are you looking at my motor? I told you, my brakes. Why are you in the motor? Because you touch it, you're likely to break some small plastic piece and then suddenly tell me, 'By the way, that was going to break anyway.' Now I owe you $50,000. So don't touch shit."
— David Russell
There are three layers to this resistance:
Scope suspicion. They think we are looking for more billable work.
"Am I paying you to do this shit? Is that what went into that bid that I gave you?"
Privacy and self-protection. They do not want us finding things they do not want found.
"I don't want you rooting through my house looking for random stuff... you might find children I have stashed in the garage."
Time impatience. They want the solution delivered now, not a research project first.
"The moment sales training is done, the salespeople are just better. I come in and I install a new air conditioner and the moment I install it, the air is cold."
That last one is worth holding onto. PE firms especially believe that once a deliverable is done, the problem is solved instantly. Discovery delays that moment, and they find it frustrating — even when it is the most valuable thing we do.
The goal is not to hide what we are doing. It is to run discovery fast and efficiently enough that we are not visibly "wandering around their house" for weeks before producing any value.
4. The Three Client Reactions When Discovery Finds Something Different¶
Once discovery is complete, we have findings. Sometimes those findings confirm the hypothesis. Often they do not — and how we present that gap determines everything.
David lays out three possible reactions:
| Reaction | What It Sounds Like | What Is Driving It |
|---|---|---|
| Scope anger | "Why are you looking at things other than what I hired you for?" | They feel we overstepped; they want only the thing they paid for |
| Validation frustration | "Why are you telling me what I already know?" | They had already diagnosed this themselves; they are insulted we are presenting it as a finding |
| Genuine surprise | "Wow, I had no idea." | We actually found something they missed — this is the outcome that builds trust |
Reaction 3 — the good one — is not the most common. But it is the one that opens the door to more work, more trust, and a longer relationship.
5. Insights, Not News¶
The way you frame a finding determines which of the three reactions you get.
"The news is that you lost $40,000 last year. Yeah, that's why we hired you. Why are you telling me what I already know? Or we could say — we figured out where that $40,000 went. It was actually one of your sales people. Wow, I had no idea."
— David Russell
| News | Insight |
|---|---|
| "You lost $40,000 last year." | "We found where it went — one rep is systematically discounting at 25% and the delta is unaccounted for." |
| "Your sales team isn't closing deals." | "Reps know the product but have no materials for handling competitive objections. They are consistently losing at the late stage." |
| "Your churn is high." | "Three customers left in Q3 for the same competitor, all on the legacy pricing tier. The pattern looks like price sensitivity at renewal, not product dissatisfaction." |
The first column tells them what they already know or what you were hired to fix. The second column tells them something they could not see without you.
"While we were researching your pricing information, we noticed an interesting correlation. All of the deals that went to Bob seemed to be sold at about 25% discount. We think he's pocketing that."
— David Russell (illustrating how to frame an uncomfortable finding)
The Project Coordinator's role: You do not write the insights. But when you pull together the weekly status deck, your job is to push the consulting team toward the second column. Ask them: "What does this mean? What would the client not have known without us here?" That pressure — consistently applied — is the difference between a deck that earns trust and one that earns frustration.
6. The 10x Complaint Rule and What It Means¶
One of the data sources David flags for understanding client health is customer satisfaction — not necessarily from surveys, but from signals like churn, help desk tickets, and public reviews.
"There's a golden rule in customer success — for every person who complains, there are ten people who leave silently for the same reason."
— David Russell
The implication runs in two directions:
For PortCo analysis: If we see complaints or negative reviews about a client's product, assume the actual dissatisfaction in their customer base is at least ten times what the visible complaints show. Churn analysis often reveals this pattern — customers stop buying without explanation.
For our own client relationships: If a client gives you a signal of frustration — a terse email, a missed checkpoint, slow data responses — do not wait for them to say explicitly that something is wrong. By the time a client formally complains, the relationship may already be damaged. Treat early signals as the one complaint representing ten silent unhappy customers.
7. The Economics of an Existing Client¶
The account development plan matters because of a simple economic reality:
"The amount of money that you spend on selling to, marketing to a client you already have has four times the impact as money spent on a brand new client."
— David Russell
To put it plainly: the return on a dollar spent pursuing an existing client is four times higher than a dollar spent chasing a new one. Landing a new client is expensive — travel, proposals, discovery calls, trust built from zero. Once a client already knows and trusts you, the next deal barely takes effort.
When discovery goes well and we find more than we were hired to fix, we build an account development plan — a structured list of what we noticed, what is high impact, and what we could do next to materially improve their condition.
"It is never 'Let's just take more money.' It is always 'How could we help them?'"
— David Russell
This is both the ethical framing and the business framing. We are not up-selling for its own sake. We are identifying real problems that, if left unfixed, will hurt the client's results — and therefore their relationship with us.
8. The Client Size Sweet Spot¶
Not every organization is the right fit for Cortado. The clients we target occupy a specific band:
"There's a certain organizational size where you would never hire a lawyer at all because you're just too damned small to care. Then there's a certain organizational size where you simply have your own lawyer on staff... We work for the companies in between — the ones who know they need a lawyer but can't quite afford one."
— David Russell
Applied to us: we target organizations that have clearly identified a commercial problem and have some budget to address it, but are not large enough to staff the solution internally. They need our expertise temporarily — long enough to build something sustainable, after which they may hire a permanent leader to run what we built.
That is the interim model: a 1099 consultant holds the function together while the client recruits a permanent hire. Sometimes the client hires our interim directly — which costs them a buyout fee, but when the fit is right, it works for everyone.
9. Phase Zero — A Placeholder¶
David introduced a concept at the end of this session that will be covered in a future lesson: Phase Zero (also called Week Zero).
The brief version: before discovery can start, we have to get our own internal machinery in place. The Statement of Work is signed. The kickoff is scheduled. But the consultants need to be onboarded, the data request needs to be finalized, the project plan needs to be stood up in Asana, and roles need to be assigned.
That preparation is Phase Zero. It is not billed discovery time. It is the time before discovery begins — and it is where the Project Coordinator's work starts.
"We have to get our shit together. And that getting our shit together is phase zero."
— David Russell
The full treatment of Phase Zero will come in a future session. For now: know the term, know that it exists before every engagement, and know that the calendar work, tool setup, data request preparation, and internal kickoff coordination all live here.
Knowledge Check¶
Scenario
It is Week 2 of an engagement. Cortado was hired to audit and redesign a PortCo's sales territory structure. During discovery, the consulting team pulls three months of closed-won and closed-lost data and finds something unexpected: 60% of lost deals were lost to one specific competitor, always in the same geographic region, always on price. The territory structure appears fine. The real issue may be a pricing problem in one market.
- Using the "insights vs. news" framework, how should this finding be framed in the weekly status deck — and what would the "news" version of this finding look like?
- The client hired Cortado for territory design, not pricing analysis. Which of the three client reactions is most likely when you present this finding — and how should the team prepare before the meeting?
Discussion guide
1. Insights vs. news framing: The news version: "Your win rate in the Northeast is below average." The insight version: "60% of lost deals last quarter went to one competitor, exclusively in the Northeast, consistently on price. The territory structure looks sound — the concentration points to a market-specific pricing gap rather than a coverage or rep performance issue." The insight names the competitor, quantifies the concentration, identifies the region, separates the finding from the original scope, and proposes a cause. All things the client could not see without the data we pulled.
2. Most likely client reaction and how to prepare: Scope anger is the most likely reaction — the client hired Cortado for territory design, and surfacing an out-of-scope finding can feel like we are fishing for more billable work. Prepare before the meeting: brief the account lead so they are not surprised; frame the finding as something the territory data surfaced, not a deliberate detour ("while analyzing deal flow by region, we noticed a pattern"); and present the observation without attaching a proposed new scope. The phrase "and here is what we should do about it" is what triggers scope anger — that sounds like an upsell. "Here is what the data showed" is insight, and gives the client room to decide what to do with it.
This completes the current curriculum. Return to the overview or continue to First 30 Days — everything in it should make considerably more sense now.