Revenue operations for startups under 20 people for public sector and GovTech

This edition is written for public-sector business development leads and GovTech commercial teams. In public sector and GovTech, public-sector buying is procurement-led and rewards credentialed, patient engagement, 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 public sector and GovTech is almost always procurement cycles and credentials, not product-market fit. 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 public sector and GovTech: one framework agreement unlocks years of downstream demand. That is the reason it is worth installing revenue operations properly rather than half-heartedly across three vendors.