Revenue operations for startups under 20 people for B2B SaaS
How under-20-person startups get revenue operations live without hiring — the specific version of the playbook designed for constraint. Written for founders and revenue leaders at Series A–C B2B SaaS companies.
This edition is written for founders and revenue leaders at Series A–C B2B SaaS companies. In B2B SaaS, SaaS buyers have seen every playbook, and specificity is the only remaining differentiator, so the way you install revenue operations has to reflect that reality from day one.
The under-20-person version of revenue operations is not a diluted enterprise playbook. It is the function that owns the pipes between marketing, sales, and success with different constraints: no headcount, no politics, and no time to be wrong for long.
Own it personally as a founder or lean-in operator for the first quarter. Hiring a specialist too early replaces context with process.
Pick one channel, one trigger, one message. Two of anything at this stage is too many and none of them will work.
The binding constraint we see in B2B SaaS is almost always efficient growth under a fixed CAC ceiling. Revenue operations is only useful in this vertical when it is pointed at that constraint — not at a generic growth number borrowed from another category.
Instrument days-to-close and forecast accuracy in a spreadsheet if you have to. Legibility beats sophistication under 20 people.
The startup-specific trap is hiring RevOps to fix CRM instead of to own revenue, usually because a well-meaning advisor points at what worked at their $50m company. Ignore.
Budget rules: whatever you spend on tools, spend the same on the person operating them. Under-tooling is fine; under-humaning is not.
A working revenue operations function at 15 people is a genuine moat — most competitors of that size do not have one, and the discipline carries forward as the company grows.
Concretely for B2B SaaS: the SaaS teams that install this early compound category leadership inside 18 months. That is the reason it is worth installing revenue operations properly rather than half-heartedly across three vendors.
Frequently asked questions
RevOps · B2B SaaS — answered
- Does revenue operations work for B2B SaaS?
- Yes — provided it is aimed at efficient growth under a fixed CAC ceiling rather than a generic growth number. The SaaS teams that install this early compound category leadership inside 18 months.
- Can a five-person team run revenue operations?
- Yes, if the founder owns it. The lower headcount, the more concentrated the ownership.
- What is the smallest useful revenue operations setup?
- One channel, one trigger, one message, and a spreadsheet tracking days-to-close and forecast accuracy.
- Should we hire a specialist for revenue operations?
- Not in the first quarter. Own it personally until the model is proven.
- What common advice should startups ignore?
- Anything derived from a company more than 10x larger. Constraints differ.
- What is the B2B SaaS specific pitfall with revenue operations?
- Running the generic playbook without adapting to SaaS buyers have seen every playbook, and specificity is the only remaining differentiator. The install has to be vertical-first.
Growth Broker editorial
Filed under revops · b2b saas