You spent six weeks scoping a deal before anybody signed anything, and now your operations lead is looking at the internal budget sheet like you personally lit it on fire. Sarah Shepard, our COO and my co-host, and I have been having some version of that conversation for more than ten years, and this episode is the two of us having it out loud instead of letting it curdle into passive-aggressive comments in a retrospective meeting.
You'll come away with a clearer read on why the handoff from sales into delivery creates so much friction in consulting businesses specifically, and a short list of upfront questions that separate the projects where we hit our profitability targets from the ones that quietly go sideways.
This post is based on Episode 71 of Revenue Rewired | How Much Should You Give Away Before the Contract Is Signed.
If you'd rather listen than read, find the full episode on Apple Podcasts, YouTube, Spotify, or Amazon. It's worth your time.
Why Does the Sales and Delivery Handoff Break Down So Often?
Sarah opened the episode by calling this a departmental disagreement rather than a fight, which was generous of her. She runs operations, I run sales, and everything I sell turns into something her team has to build. We talked a few episodes back about the visionary and integrator split that Gino Wickman lays out in Traction, and it maps onto us almost too cleanly. My strength is ideation, hers is taking action and building the plan, and Cameron Herold's point about COOs who have zero interest in being first in command describes Sarah exactly.
I've noticed this friction runs harder in consulting than in product businesses. If you're selling a widget or a transactional service, the handoff is close to templatized, and after you've run five hundred SEO audits you know almost to the minute how long a page takes. Our work doesn't behave that way, because every engagement gets customized and clients aren't templates. Forcing a custom problem into a template is how you end up nickel-and-diming somebody six weeks into a project.
It gets harder still when the handoff crosses both a department line and a person line. Smaller firms sometimes dodge this because one person wears three hats, but we have dedicated people at each stage, so every transition is another chance for the game of telephone to start. By the time the work reaches the person building it, what "done" means has already drifted from whatever got sold.
Is Free Scoping Work Buying Trust or Burning Margin?
Sarah's position is that we pour an enormous amount into biz dev and never make it back, and she's right about the volume. If clients saw what goes into the way we scope and propose, so we're not coming back later with surprise charges, I think they'd be a little stunned at what never shows up on an invoice.
The reason I keep doing it anyway traces back to something Susan Baier shared when she joined us on episode 68. Her research found that prospects walk into agency conversations already distrusting you, before you've opened your mouth. You're starting in a hole, and the only way out is doing enough real work upfront that somebody can see you understand their problem. After twenty-five-plus years in consulting, my read is that the first engagement isn't where the math has to work; the relationship is.
Sarah's counter is that the numbers have to work somewhere, and my anxiety heading into project retrospectives tells me she's onto something. I love exceeding expectations, so when a complicated project is near the finish line and I get pulled in, I see openings everywhere and struggle to leave them alone. Her telling me we've beyond exceeded what the scope required is what keeps me in line, even in the moments where I'm a little disappointed we're not celebrating instead.
What Separates the Profitable Projects From the Painful Ones?
We've worked with three hundred-plus companies over the years, and the engagements where the client was over the moon and we still hit our numbers share one trait. We did a better job up front of asking questions that sound almost too basic to bother asking.
Five-plus years ago, we'd run an entire analysis, build a beautiful presentation where every data-heavy slide eats an hour, and then learn the client wanted a spreadsheet. We'd think we were finished and instead land in a gray area with more work in front of us. It isn't the client's job to dictate those nuances, so now I ask upfront who the audience is, what the desired outcome looks like, and whether they'd rather work in Google Docs or Microsoft. Those little things are what make the experience land as a ten instead of an eight.
Sarah's team built internal budget sheets that are detailed and pretty painful to fill out, and they earn their keep because they force the definition of done to hold steady across every handoff. If a landing page runs fifty steps on our side once you count QA and staging and reviews and testing, sales has to know that before a number goes on a proposal. Letting that expectation loosen at each step is a revenue leak sitting inside your own business, and it's one we didn't even put in the book.
How Do You Build a Team That Will Push Back on You?
Some people who've come to us from more rigid agencies dread retrospectives, because they've only ever watched them get used to assign blame. Ours work because the feedback runs both directions and nobody's protecting a story. When a project goes upside down, which tends to happen on the complicated builds, I still count it as a win if we learned something that changes how we scope the next engagement.
Whoever owns profitability owes it to sales to close that loop. Not as an accusation about what got sold, but as information about what the work actually took, so the next quote reflects reality instead of hope. Skip that step, and you're building client relationships on top of something that can't be delivered the way it was promised, which manufactures internal drama nobody signed up for.
Sarah raised something at the end that stuck with me. She's been frustrated with AI tools lately because they rush to produce a file instead of asking who's reading this and what the output needs to be. I have an easier time with them only because I've set every LLM I use to challenge me rather than flatter me. A tool that tells me a deliverable takes 1.25 hours, while ignoring the nine hours I spent thinking about it on the drive in and the three hours cleaning it up afterward, is doing the exact thing a yes-person on your team would do.
FAQ
Q: How much unpaid work is too much during biz dev?
A: There's no universal number, and the leadership team has to decide what's allowed rather than leaving it to whoever's closest to the deal. Our rule of thumb is that upfront effort should buy you information you actually need to scope accurately, and once you've got that, keep going only if you've talked to the client about it first.
Q: Why do sales and delivery keep disagreeing about scope?
A: Because they're optimizing for different things and both are correct. Sales is protecting a long-term relationship, delivery is protecting capacity and margin, and the disagreement only turns toxic when nobody feels free to name it.
Q: Should the first project with a new client be profitable?
A: Sarah says yes; I say it depends on whether you believe the lifetime value shows up. What we agree on is that if you're going to lose money on that first project, that needs to be a decision somebody made on purpose, not a surprise you discover in the retrospective.
Q: How do we keep scope from drifting after the deal closes?
A: Write down what done looks like before the proposal goes out, and make it detailed enough that it survives every handoff. Internal budget sheets are tedious, and they're the cheapest insurance you'll find against a project that quietly triples in effort.
Q: What should we ask a client before we send a quote?
A: Find out who's going to read the deliverable, what outcome they're picturing, and what format it needs to land in. Those sound almost embarrassingly obvious, and skipping them is what leaves you renegotiating when the work is nearly done.
Ready to Close the Gap Between What You Sell and What You Deliver?
At StringCan Interactive, we spend our days inside mid-market companies where sales and marketing look aligned on paper and leak revenue in practice. A lot of that leakage stays invisible in a dashboard, because it lives in the handoffs, the assumptions nobody wrote down, and the scope that grew while everyone was being agreeable. We wrote the Revenue Rewired book about exactly that pattern, and this episode is one more version of it playing out inside our own company.
If any of this sounds like a conversation happening in your organization right now, listen to the full episode and then reach out to us at podcast@stringcaninteractive.com. Sarah and I read every question that comes in, and a fair number of them end up shaping future episodes.
