Fractional RevOps, with the build included.
One to two days a week. I fix the CRM, pipeline reporting and forecast so leadership can trust the numbers, stop leads going stale, and run the revenue cadence. Not advice about the revenue system. The revenue system.
What I take off you
The specific things that currently land on the founder and shouldn't.
The CRM, pipeline reporting and forecast. Qualification, routing, conversion, onboarding, retention, expansion and cost to serve — one owner for the whole lifecycle instead of three functions each holding a piece and nobody holding the join.
The operating cadence. The weekly rhythm, the numbers that get reviewed, the meetings that are worth having and the ones that quietly aren't. I've restructured meeting rhythms and experimentation frameworks specifically to cut waste and sharpen where leadership attention goes.
Stale leads. Every lead has an owner and a next step, and the ones going cold are flagged before they're lost rather than found at the end of the quarter.
The build. When a problem needs software, it gets built rather than added to a roadmap. That's why this moves faster than advice does.
The unfashionable half of the P&L. What each customer costs to serve, which segments are quietly unprofitable, and whether the pricing actually works. I've run a P&L, so I'll tell you when the problem isn't your funnel.
How it works in practice
I'm in your systems, not adjacent to them. Same tools, same channels, same access as anyone on the team. I'm reachable between the days I'm on, not only on them.
Reporting to you. This only works with a direct line to the founder or CEO, because the decisions involved are the ones you'd otherwise be making.
Instrument first, then change. Early weeks go into making the lifecycle visible, because changing a stage nobody is measuring is how businesses lose six months and learn nothing.
Everything documented as it's built. The point is to become unnecessary. Every system, decision and process is written down so the eventual full-time hire inherits a working machine rather than a mystery.
The first ninety days
When to hire this
You're past product-market fit and the constraint has moved. The problem isn't finding demand any more; it's that the business can't convert, keep or profitably serve what it already gets.
You're the bottleneck and you know it. Still the best salesperson, still the final escalation, still in the CRM at 11pm — and every week you don't fix it costs more than the week before.
A full-time RevOps hire isn't right yet. Either the budget doesn't work or the scope doesn't justify it. One to two days a week from someone who has built these systems beats a full-time hire who hasn't.
You want the systems, not just the judgement. If you only need advice, there are cheaper ways to get it. This is for when someone has to actually build and run the thing.
Well, ideally. It's designed to hand over: to a full-time RevOps lead when the business is big enough to warrant one, or to the team when the machine runs itself. Every system is documented as it's built, precisely so that leaving is a handover rather than a hole.
If you're the bottleneck, let's talk about RevOps.
Thirty minutes. No brief required. We'll work out where your customer lifecycle is losing money and whether it's a problem I can fix — and if it isn't a fit, I'll tell you inside the first ten minutes.