Sales Can Finally Learn to Under Promise and Over Deliver

There’s always been tension between Sales and Engineering. As long as I’ve been building software, that tug of war has been there.

When I was a younger developer, I chalked it up to incentives.

Sales is rewarded for closing the deal, even if the deal is a little… optimistic. Engineering is rewarded for delivering what was promised, even when the promise was made in a vacuum.

So you end up with the classic dynamic: Sales overpromises because they’re trying to win. Engineering underpromises because they’re trying to survive.

What’s interesting is what “vibe coding” just did to that equation.

For the first time, a purely sales, non-developer type can pick up tools and try to build the thing they’ve been selling.

And when you see someone complain that their vibe-coded project cost them thousands in prospects, I don’t see that as some new tragedy.

I see it as a new form of empathy.

They’re feeling the same pain engineering has felt forever: The gap between “that sounds simple” and “that works in production” is where dreams go to die.

Because the real work isn’t the demo. It’s auth, edge cases, permissions, data integrity, UX states, performance, integrations, deployment, monitoring, compliance.

All the unsexy parts that don’t show up in a pitch deck, but absolutely show up in the customer’s experience.

The other side of this is the message vibe coding sends to engineers.

It’s not enough to be frontend or backend anymore. It’s not even enough to call yourself “full stack” and stop there.

The bar is shifting toward outcome ownership.

That’s why the rise of concepts like Forward Deployed Engineer matters. Not because it’s a cool title, but because it’s an organizational admission that the translation layer is the real bottleneck:

Customer reality → technical reality → delivered outcome.

FDEs shrink the distance between what customers mean and what gets built, in real time, with real tradeoffs.

But of course, it brings new problems too.

You can accidentally create two classes of engineers: the ones closest to "impact" and the ones quietly holding the platform together. You risk turning FDEs into human glue that everything depends on. Or, you might convince sales that "engineering closer to the customer" means "engineering will say yes more often," when the real value is saying no faster, with better alternatives.

Still, I think this is a net positive shift.

Vibe coding is forcing the business side to touch the stove. And it’s forcing the technical side to step up from code ownership to outcome ownership.

So here’s the real question:

In a world where anyone can generate a demo, what’s the new minimum bar for something being “sellable”?