Selling What's On the Truck

The CEO cut 60% of the pipeline.

They weren't intrinsically bad deals. But they required capabilities that the company didn't have a ready solution for yet. The sales team was selling the art of the possible. And in the middle, customer success and the services team were absorbing the gap between what was promised and what actually shipped.

After huge growth driven by a partner, new expansion had stalled. The board wanted answers. And the CEO realized that before they could fix anything, they had to get everyone aligned on a single question: what are we actually built to deliver today?

That alignment problem shows up everywhere in companies trying to scale past the messy middle. It's not that teams are incompetent or disconnected. It's that they're operating with fundamentally different definitions of what the company is.

Sales sees the product as what it could become with additional work. Product sees it as what's shipping next quarter. Customer success sees it as what customers can actually use right now. And the CEO is stuck translating between all three while the business drifts further from any coherent center.

Selling What's On the Truck, Not What's Still in the Factory

What's on the truck is what you can deliver today. It's loaded, secure, and ready to go. What's not on the truck might be in the warehouse, getting staged, in production being built, or still a sketch on a whiteboard. All of those things matter. But only one of them counts when a deal closes, or a customer calls with a problem.

The tension isn't whether you should build new capabilities. Of course you should. The tension is whether your entire organization is aligned on what's available now versus what's coming later. And in companies trying to scale from $25M to $50M and beyond, that alignment rarely exists.

When Different Functions See Different Inventories

Sales builds pipeline around what the product could do with additional engineering investment. They're not lying. They're selling the vision, which is part of the job. But when product strategy hasn't made it explicitly clear what's on the truck versus what's still being built, sales defaults to optimism. The roadmap becomes a closing tool instead of a commitment model.

Product is focused on what's next. Roadmaps are forward-looking by design. But when those roadmaps aren't connected to a shared understanding of current capacity and delivery state, they create an expectation mismatch. What product sees as "we're working on this" gets interpreted by GTM as "we can sell this."

Customer success ultimately manages the gap. They're the ones who have to explain why the item discussed in the sales cycle isn't available yet. They're the ones fielding escalations when a feature slips or a delivery timeline shifts. And because they're closest to the customer, they become the voice advocating for faster releases, which adds pressure back to product without clarifying what should actually be prioritized.

None of this is malicious. It's structural. And it compounds.

The Real Cost Is Hidden

The most obvious symptom is churn. Customers leave when the product they bought doesn't match the product they're using. But the deeper cost is strategic drift.

When alignment breaks down, prioritization becomes reactive. Product starts building toward deals in the pipeline rather than the outcomes in the strategy. Engineering absorbs scope creep as new deals introduce new edge cases that weren't part of the original plan. Roadmaps lose coherence because they're trying to serve too many different definitions of what the company is building toward.

You end up with a product that does a lot of things tolerably instead of a few things exceptionally well. And the farther you drift from a shared understanding of what's on the truck, the harder it becomes to make tradeoffs that stick.

The question isn't whether you're building the right things. It's whether the entire organization agrees on what you're built to deliver right now, and what that means for who you serve and how you sell.

Alignment as an Explicit System

The CEO who cut the pipeline wasn't being conservative. He was being precise. He recognized that trying to close deals requiring capabilities the company didn't have yet was creating execution strain across every function. The revenue looked good on paper, but the delivery model couldn't support it. So he made the current state explicit and rebuilt the pipeline around what was actually on the truck.

That's the outcome he's driving toward. Sales that can close with confidence because what they're selling matches what can be delivered. Product that can build toward a coherent strategy instead of reacting to pipeline pressure. Customer success that can manage expectations instead of apologizing for gaps. And a leadership team that can make decisions based on what the company is, not what it might become.

Alignment doesn't happen only through better communication. It also requires shared definitions. What counts as shippable. What qualifies as a capability. What falls inside the current delivery model versus what requires new infrastructure.

Those definitions need to be explicit, documented, and connected to how each function operates. Otherwise, you're running three different companies under one brand, and the only thing holding them together is the CEO's ability to translate between competing realities.

Most strategic drift starts here. Not because the strategy is wrong, but because different parts of the organization are executing against different versions of it. The roadmap says one thing. The pipeline implies another. And the customer experience reflects the gap.

If each function is looking at a different version of what's on the truck, you can't align the organization. And if the organization isn't aligned, the wheels can come off the truck.