Why forecast confidence, not forecast ambition, is what buyers underwrite.
Charlie had done what every founder preparing for a sale is supposed to do. He sat down with his leadership team months before going to market, walked through the numbers, and built a thoughtful case for where Continuity Inc. was headed. Revenue growth. Margin improvement. New customer wins. Better utilization across the floor. The plan was detailed and logical, and when he presented it to his advisors and his bank, it landed well.
What Charlie didn’t fully appreciate, not yet, was that a forecast can win the boardroom and still fail diligence. Those are two very different audiences, and they ask very different questions.
His story is one I’ve seen play out in various forms throughout my years in this industry. The founder builds a compelling growth narrative. The forecast looks credible on its face. The valuation expectation climbs to reflect it. And then a buyer shows up, or a QoE team, or a lender, and starts asking the questions that the boardroom never did. That’s where things get uncomfortable.
I want to walk you through what happened with Charlie, because I think it explains something important that doesn’t get discussed clearly enough in the context of selling a wire harness or cable assembly business: the difference between a forecast that tells a story and a forecast that survives scrutiny.
01 | The Numbers Charlie Brought to Market
Continuity Inc. was generating about $6.5 million in EBITDA when Charlie began the sale process. His management team had forecast $8.1 million for the following year, a $1.6 million improvement built on four pillars: price increases across the customer base, new program wins with two automotive-adjacent OEMs, improved labor efficiency from a lean initiative underway on the floor, and volume growth from an existing medical customer who had signaled expansion.
At multiples appropriate for a business of Charlie’s size and profile, that $1.6 million in forecasted EBITDA improvement represented approximately $12 to $14 million in additional enterprise value, if believed.
The board believed it. The bank was encouraged by it. Charlie believed it. And by most internal measures, there was a reasonable basis for it.
The first buyer who came through diligence believed most of it, too. But “most of it” is where the problem began.
Buyers do not underwrite optimism. They underwrite evidence.
A forecast is not strong because it is detailed, it is strong when
every assumption can be traced back to something real.
02 | What the Buyer’s Diligence Team Actually Asked
The QoE team came in and started the way they always do: working backward from the forecast bridge, assumption by assumption. They weren’t adversarial about it. They were methodical. And the questions they asked were not unreasonable. They were, in fact, the questions Charlie should have been asking himself months earlier.
How much of the growth is already in backlog? The medical customer expansion Charlie had projected was real, in that the customer had expressed intent. But there was no firm purchase order, no contracted volume commitment, and no delivery schedule. The buyer’s team classified it as pipeline rather than backlog. It stayed in the model, but at a probability-weighted value that was roughly 60% of what Charlie had assumed.
Are the price increases contracted or assumed? Charlie’s team had modeled 3–4% price increases across most of the customer base, reflecting what they believed was a reasonable ask given the material cost pressure in the prior year. Some of those conversations had happened. A few had produced an informal agreement. None had produced signed amendments. When diligence asked to see the documentation, the answer was: they’re in process. The buyer discounted the price increase assumption by roughly a third.
Does the margin improvement have legs? The lean initiative on the floor was real and producing results. But it was still underway. The efficiency savings Charlie had projected assumed full implementation, which his operations team estimated was still six to nine months out. The buyer gave partial credit for savings already achieved and held back on the rest pending evidence.
Will working capital absorb the growth? This one caught Charlie off guard. He hadn’t modeled working capital as a constraint on his growth scenario. The buyer’s team pointed out that if revenue was going to grow at the rate Charlie projected, the business would need to fund that growth, more inventory, more receivables, and potentially more tooling investment. The cash conversion implications of the upside case hadn’t been built into the plan.
03 | How the Haircut Added Up
None of these haircuts were dramatic on their own. The buyer wasn’t saying the forecast was wrong. They were saying: here is the portion we can underwrite, and here is the portion we can’t, at least not at full value.
When it was over, the buyer accepted roughly $900,000 of the $1.6 million EBITDA uplift. The remaining $700,000 was allocated to an earnout structure. Charlie would receive additional consideration if Continuity Inc met certain performance targets over the 18 months following the close.
At an 8x multiple, that $700,000 of reclassified EBITDA represented between $5 and $6 million in value that shifted from a certain payment at closing to a conditional payment contingent on future performance. Charlie closed the deal. But he closed it with a structure that put a meaningful portion of his expected proceeds at risk.
He hit the earnout targets, as it turned out. But he didn’t know that going in. And the months of uncertainty that came with it, the operational pressure, the reporting requirements, the anxiety of not knowing whether the number he’d been counting on would actually arrive, those are costs that don’t show up in any model.
The buyer doesn’t need to say your forecast is wrong. They only
need to identify the piece they can’t underwrite, and reprice it
accordingly.
04 | The Difference Between a Growth Story and an Underwriting File
This is the thing I come back to every time I work through a pre-sale financial review with a client. Management teams almost always present their forecasts as growth stories. Buyers rebuild it as an underwriting file. Those two documents rarely look the same.
A growth story says: here is where we are going and here is why we believe it. An underwriting file asks: Which of these assumptions is already in the contract? Which is in the backlog? Which is a historical conversion translated forward? Which new behavior are we assuming a customer will adopt? Which savings are realized and which are projected? Which capex has already been approved, and which will need to be funded out of the deal proceeds?
The gap between those two documents is where valuation risk lives. And for most founders who haven’t gone through a transaction before, that gap is larger than they expect, not because their forecast is dishonest, but because it was built to be believed internally, not tested externally.
Charlie’s forecast wasn’t aggressive by any reasonable standard. The assumptions were grounded in real conversations and real operational initiatives. The problem was that they hadn’t been stress-tested against the questions a buyer would ask. When those questions arrived, the team was answering them in real time rather than having the documentation ready.
05 | What Charlie Would Have Done Differently
Charlie is thoughtful, and he’d processed the experience carefully. His answer was consistent across every conversation he had post sale.
He would have separated the forecast into layers. Contracted revenue. Backlog. High-confidence pipeline. Probable wins. Possible wins. Each layer is treated differently, with varying discount rates, documentation requirements, and confidence language. When diligence came in, he would have handed them a document that already reflected that thinking rather than having to reconstruct it under scrutiny.
He would have tied every assumption to evidence before going to market. The price increases should have been in signed letters before the data room opened. The medical program expansion should have had written confirmation of intent at a minimum. The lean savings should have been quantified against actual run-rate data, not projections. None of this was insurmountable; it just required time that Charlie hadn’t built into his process.
He would have modeled the working capital implications. The growth case should have included a working-capital bridge, clearly showing the cash required to fund the upside scenario. That kind of analysis doesn’t weaken the forecast; it strengthens it. It tells the buyer that management has thought through the full picture, not just the revenue line.
He would have tracked his own forecast accuracy. Buyers weigh management credibility heavily when they’re deciding how much of a forecast to underwrite. One of the most powerful things a management team can bring to a diligence process is a clean track record: here is what we said we would do for the past three years, and here is what we actually did. Charlie didn’t have that analysis prepared. It exists; his numbers were actually quite good, but assembling it under diligence pressure is not the same as presenting it proactively.
06 | What This Means Before You Go to Market
If you are planning a sale in the future, the time to test your forecast is now, before buyers, lenders, or a QoE team does it for you.
The question isn’t whether your growth assumptions are reasonable. The question is how much of your expected valuation rests on assumptions that a buyer will be able to underwrite, versus assumptions they will haircut, defer into an earnout, or discount entirely. For most founders who haven’t worked through this analysis, the answer is more of the latter than they expect.
At Blue Valley, the work we do with clients in the months and years leading up to a transaction includes exactly this kind of review. We go through the forecast bridge assumption by assumption, backlog, pricing, pipeline conversion, customer mix, capacity, capex requirements, working capital, historical accuracy, and we identify where the gaps are while there’s still time to close them. That’s very different from discovering them across the table from a buyer.
Charlie’s situation wasn’t a failure of ambition. His forecast was grounded and his business was good. What he needed was time to prepare, to translate a strong internal narrative into a document that could withstand external scrutiny. That’s a solvable problem, but only if you start early enough to solve it.