The approach

Engine-first RevOps

Build the revenue machine before you staff it. The order is not a preference - it is the whole game.

Most RevOps is staffed before it is built. Teams hire reps, then bolt process and tooling onto the chaos afterward and call it scaling. The result is a function that spends its first year reverse-engineering its own mess.

I do the reverse. I build the machine first - routing, data model, instrumentation - and hire into a system that already works. A machine built before the team is one the team trusts on day one, and one you can increasingly hand to an agent instead of a headcount.

Strongly believed, loosely held. Now and then the right first hire beats the right first system. But almost never.

The sequence

  1. 01

    Build the machine

    Routing, the data model, the integrations. The thing that moves a lead to invoice without a human carrying it. Before headcount, before a sales motion, before a deck.

  2. 02

    Instrument it

    If it runs, it reports. Forecast accuracy, leak points, win rate by path. You cannot hand someone a system you cannot measure, and you cannot improve one you cannot see.

  3. 03

    Hire into it

    The first hire inherits a machine that already works, not a chaos they are asked to tame. Onboarding is learning the system, not inventing it. Trust on day one.

  4. 04

    Hand the rote to agents

    Once a path is instrumented and stable, it is a candidate for an agent, not another headcount. The machine you built first is the machine you can increasingly automate.

Proof

Engine-first is not a theory

  • CRM before the sales team

    Fluidmaster, 2012-2014. I built the CRM before a single rep was hired. Backorder efficiency doubled, lost sales fell 35%.

  • Routing agent before the website

    Vandfort, 2025. The agent that routes every prospect to the right engagement shipped before the landing page existed.

  • Dashboards as infrastructure

    A self-service hub that took 250 partners off the support queue, with board-level reporting built in from day one.

  • A business, built engine-first

    JMA Altuna, Colombia. At 26 I built the operating systems before scaling the team. Breakeven in two years, distributor base up 68.8%.

See the machines I'm building now →

Work with me

Revenue that should run itself? Let's build it.

Tell me what you're building and where it's stuck. If there's a RevOps engine or an AI system in it, that's my work. I read every message.

Prefer LinkedIn? Message me there.