RevOps for Small Business: The Minimum Viable Revenue Engine

RevOps has a branding problem. The term arrived from enterprise software, dressed in org charts and six-figure tooling, so founders of 20-person companies assume it is not for them yet. Then I look inside their business and find the exact disease RevOps exists to treat: marketing, sales and customer success each keeping their own numbers, in their own tools, with their own definitions of a customer — and a founder trying to steer by reconciling three spreadsheets that disagree.

You do not need a RevOps department. Under 150 people, you need a revenue engine that is instrumented — one pipeline, one set of definitions, one place where the truth lives. In my engagements this is usually four pieces of work, in a specific order.

Piece 1: One customer record, one lifecycle

Before dashboards, before automation, agree on nouns. What is a lead? When does a lead become an opportunity? What does "closed" mean — signed, paid, or onboarded? Small companies skip this because everyone fits in one room and definitions feel bureaucratic. Then the room grows, and the ambiguity that was charming at 10 people becomes a reporting crisis at 40.

The deliverable is boring and decisive: a lifecycle model written down — I use five to seven stages, never more — implemented as actual fields in the CRM, with entry and exit criteria for each stage. Every argument about "whose number is right" traces back to this document being missing.

Piece 2: A pipeline that tells the truth

Most small-company CRMs are diaries, not instruments. Deals sit in "negotiation" for eight months; the pipeline shows $2M because nobody archives dead opportunities; close dates are wishes. The fix is process, not software:

• Every stage has a maximum age. A deal that exceeds it gets discussed or downgraded — automatically flagged, humanly decided.
• Closed-lost requires a reason, from a short fixed list plus free text. This single field, six months later, is the most valuable dataset in the company.
• The pipeline review happens weekly, takes 30 minutes, and works from the CRM screen — never from a spreadsheet exported the night before. The moment someone preps a parallel document, your CRM has failed and the meeting will make decisions on stale data.

Piece 3: The handoffs nobody owns

Revenue leaks at the seams between teams: the marketing-qualified lead that sales touches four days later; the closed deal that onboarding hears about from the customer; the renewal that surprises everyone including the account owner. Each seam needs an explicit handoff — who is notified, within what window, with what information attached.

This is where automation earns its keep, and where I start with tooling. A routing workflow that assigns and notifies within minutes, a deal-won trigger that opens the onboarding project with the context copied over, a renewal reminder that fires at 90 days with usage data attached. I have built these in HubSpot workflows where the company lives in HubSpot, and in n8n where the stack is fragmented — I wrote about those patterns separately. Across engagements, automating handoffs and the manual copying around them reliably removes on the order of 40–60% of the manual coordination work — an estimate from my own projects, not a benchmark, but a consistent one.

Piece 4: Reporting the founder actually reads

The goal is not a dashboard. The goal is that the same five numbers appear every Monday without anyone assembling them: new qualified pipeline, conversion by stage, revenue closed, cost per acquisition by channel, and net revenue movement in the existing base. If a number requires manual export-and-paste to produce, it will eventually be produced late, then wrong, then not at all.

Resist the urge to measure everything. In a small business, ten metrics tracked weekly beat forty tracked never. I keep a rule from my operating years: every number on the report must have a named owner and must have changed a decision at least once a quarter, or it comes off the report.

The tooling question, answered plainly

Under 150 people you need: a CRM that is the single system of record (HubSpot is my default for this size; Salesforce when the sales motion genuinely demands it), one automation layer (native workflows first, n8n or Make when you outgrow them), a form-to-CRM path with attribution captured at the source, and a reporting surface — which can be the CRM itself far longer than vendors want you to believe.

What you do not need yet: a customer data platform, a dedicated attribution tool, revenue-intelligence software that records calls you never review, or any tool whose pitch begins with "AI-powered insights." Buy tools to remove work you already do manually, never to create new categories of work. AI belongs in this stack doing specific jobs — qualification, enrichment, reporting prep — after the pipeline is honest, not before. Automating a broken process gets you a faster broken process.

Who does this work when there's no RevOps hire

At this size, RevOps is a project, then a habit — not a headcount. The build takes a focused operator one to two quarters part-time. Ownership then lands with whoever runs the weekly pipeline review: a sales lead, an ops manager, sometimes the founder. The mistake is assigning it to "whoever knows the CRM best," which optimizes for tool familiarity over judgment. The operating system of the company is an executive concern; the tool administration is not the same job.

If nobody inside has built this before, this is one of the cleaner use cases for fractional help — the work is definable, the transfer of ownership is explicit, and the engagement has a natural end. It is a large part of what I do inside the operations-first marketing framework: the marketing layer and the revenue plumbing are the same build, done in the right order.

A Monday-morning starting point

If you want to begin without any outside help, run this sequence:

1. Write your lifecycle stages on one page. Get sales and marketing to sign the same page.
2. Archive every deal in the CRM with no activity in 60 days. Yes, all of them. The pipeline that remains is your actual pipeline.
3. Add a mandatory closed-lost reason field. Review the reasons monthly.
4. Pick the one handoff that fails most often and automate the notification — just the notification — this week.
5. Book a recurring 30-minute pipeline review, run from the live CRM.

That is RevOps for a small business. Not a department — a discipline, installed once, maintained weekly, and quietly compounding while your competitors reconcile spreadsheets.