On Revenue Engineering and
Impact Intelligence.
Bill Merrill
7 August 2025

I seek out revenue work, both fundamental like payments, and growth-oriented like pricing and packaging, because the path to impact is very clear. Success makes the dollars go up 📈

I read this piece on "Impact Intelligence" and thought through my experiences leading revenue engineering at Zapier as it grew wildly.

When Zapier was just big enough to have a dedicated Revenue Growth team, we had a small room of people trying to deliver impact. Inputs came from several sources, often our CMO. A single build team (PM, fractional EM, fractional Designer, a couple of engineers) would rank and discuss the merits and feasibility of experiments. They could be pricing or entitlement changes, promotions, or quality of life improvements. We weighed these projects based on anticipated impacts and with the help of Zapier's incredible data team, attributed the resulting increases (or not). We had a loop that build SaaS revenue experts.

When the company had grown an order of magnitude and expanded beyond self-serve into custom deals, the ideas of revenue growth were owned by many people, teams, and business units. Owing to our scrappy ethos, we'd still have a room of people throw darts at the wall and discuss the merits, but this was no longer the team getting the work done. These were people from across the company with their own contexts hopefully talking about the same thing.

Justifications were looser and we rarely developed a shared model of outcomes. Build teams would take these directives and get them done; monetary results were tracked, but we lost the feedback loop of results because parties involved had different understandings. This group accomplished some good things but the disconnects reduced our opportunities to build knowledge and expertise. I like to think about how we could have done even better.

Narayan's piece reminded me of this journey and helped me think about how we could have been even more successful. Sometimes you take big swings because you know what must be done, but often you're iterating for improvement, balancing many futures. Doing the work to expose your efforts and their expected outcomes brings people along creating an opportunity to learn from success.