I've spent 15 years as a CTO, mostly in startups. I'm good at it. On paper, the teams I've built have usually shipped the best product in the room. We'd win the feature comparison, win the technical bake-off, and beat companies who had raised 100 times what we had.
And we still lost deals. Plenty of them.
That's the uncomfortable lesson of my career so far. The best product rarely wins. Distribution wins. A mediocre product with sharp messaging, a tight demo, and a real sales motion beats a brilliant one nobody hears about. Product matters. It just matters a lot less than the story you tell and how you get in front of people.
The product-led mirage
Like a lot of engineers, I tried to solve distribution with more product. Product-led growth. Let the thing sell itself. It's a lovely idea, and for a very specific kind of viral, self-serve product it genuinely works.
For most B2B, it's a trap. The kind you fall into precisely because it feels like the engineering-friendly answer: you get to keep building instead of selling. But it almost always starts with sales and outreach. PLG is an add-on you earn later. It's rarely the foundation you start on. I learned that the slow way.
Then I actually watched sales work
At Responsum, I ended up working closely with our sales team. I wasn't managing them. I was learning from them. Funnels, stages, objections, the grind of follow-up. The gritty craft of it. I went in expecting a dark art and found something that looked oddly familiar.
Sales process is engineering process
The moment I started mapping how sales actually runs, my engineering brain took over. A sales process and an engineering process are the same shape.
Both are about clarity and flow. Knowing the steps. Knowing the expected outcome of each one. Knowing where the work leaks out, and which levers route effort toward the highest yield. Both are about keeping people present, informed, motivated, and handed every tool they need to do the job well.
I'd spent 15 years building systems to give engineering teams exactly that. When I looked at a pipeline, I couldn't find the equivalent. The instruments weren't there.
The call that started it
Then I had a call with an investor. He half-jokingly begged me: did I know a tool that takes historical snapshots of HubSpot? He had a whole portfolio of companies doing it by hand, every month, exporting the state of their pipeline just to track how it moved over time.
I told him I didn't know one. But I'd know one tomorrow.
A few days later I had a rough visual prototype. Over the following weeks it grew into something real. That's Reven.eu. It connects to your CRM and records your whole pipeline, every deal, stage, and change, so you can rewind to any day and see exactly how you got here.
Where we are now
We're launching it alongside the sales team at Responsum, on a real pipeline with real money on the line. It's already pointing at places our own process leaks. I'm not at liberty to share the specifics yet. Ask me again in a quarter.
What this blog is for
This is the first post, so treat it as the ground floor. What comes next is the useful part: how to diagnose a sales process the way an engineer diagnoses a system. Where deals stall. Why weighted-pipeline forecasts lie. What your CRM quietly forgets, and what you can do about it.
If you own a number, and you've ever watched a quarter fall apart without knowing why until it was too late, you're who I'm writing for.