Free: the GTM BlueprintThe stack, by funding stageThe CRM data model, written downSeven steps, six handoffsRoles, and when to hire themA 90-day plan you can run on MondayThe three numbers that decide itNo PDF, no drip sequenceGet the blueprintFree: the GTM BlueprintThe stack, by funding stageThe CRM data model, written downSeven steps, six handoffsRoles, and when to hire themA 90-day plan you can run on MondayThe three numbers that decide itNo PDF, no drip sequenceGet the blueprint
RevOpsXL
GTM Diagnostic Book the audit

RevOps when you're not SaaS.

Every competitor writes 'RevOps for B2B SaaS', so here is the horizontal version, for the longer, relationship-led, sometimes regulated pipelines the SaaS playbook was never written for.

In short

RevOps is not a SaaS thing, it is a revenue discipline, and it applies just as much to professional services, regulated finance, manufacturing, and agencies. The fixtures change (longer pipelines, relationship-led deals, no usage telemetry, compliance weight on the CRM) but the spine is the same: one source of truth, stages that mean one thing, a known ICP, clean data, and a forecast built on evidence.

On this page

Almost every RevOps article you will read is written for B2B SaaS. If you sell professional services, run a regulated lender, or make something and sell it through a long relationship, most of that advice does not fit your business - and the parts that do fit are rarely the parts the tools are selling.

So it is worth separating the two plainly. What actually changes when you are not SaaS, and what does not change at all.

The SaaS playbook assumes things you do not have

It assumes a self-serve signup, product usage telemetry, a free trial with a clock ticking on it, and revenue that arrives as a monthly subscription. Take those four away and half the standard metrics stop meaning anything.

You have no product logins to score. There is no trial timer counting down to a decision. Activation, for you, is a meeting that went well and a document that got signed - not a button someone clicked at two in the morning. A dashboard built to watch trial conversion has nothing to watch. None of that makes your revenue less measurable. It just makes it measurable in different units.

Your pipeline is longer and led by a relationship

A SaaS deal can close in a demo and a corporate card. Yours closes over quarters, across meetings, proposals, and slowly earned trust. So the velocity dashboards built for a two-week cycle are just noise stretched thin over a nine-month one.

The famous five-minute rule is the clean example. MIT lead-response research puts a reply within five minutes at about 21x the odds of qualifying a lead versus waiting thirty. That is real - for an inbound demo request. For a manufacturing tender that took eight months to form, five minutes against five hours changes nothing at all. Speed is a genuine advantage. It is just answering a question your buyer never asked.

Measure the relationship, since that is what moves

Losing usage telemetry does not leave you blind. It leaves you measuring different things.

The signals that actually predict a long, relationship-led deal are meetings that progress rather than repeat, the number of stakeholders you have met beyond your first contact, whether a real internal advocate exists, and how a proposal moves once it lands. Retention changes shape too. For you it is rarely a subscription that auto-renews - it is a repeat project, a renewed retainer, an engagement that quietly kept going, won on the relationship and the last piece of work. So the account where you only know one person is your real churn risk, whatever the revenue looks like today.

A stage means a real commitment, not a demo booked

In SaaS, a pipeline stage often maps to a step in the product funnel - signed up, activated, upgraded. In your business it maps to something in the actual world. A site visit completed. A scope signed. A compliance sign-off cleared.

That is a better foundation, if you let a stage mean the same thing to two different people. It is a worse one if you paste in a SaaS stage template that quietly describes a motion you do not run. A stage has to describe how your deals really move, not how someone else's do.

Regulated changes what the CRM is even for

I spent years in regulated financial services, inside an eleven-country group. There the CRM is not a sales convenience. It is a record.

Who said what to whom. What consent was given, and when. What was disclosed, and whether you can still prove it two years later. Data hygiene stops being tidiness and becomes evidence. A duplicate contact is not mildly annoying - it is a gap in the record you may one day have to stand behind. The SaaS playbook has almost nothing to say here, because it mostly never had to. When an auditor asks who approved a client and on what basis, a clean record is the difference between an afternoon and a very bad quarter.

What does not change is the spine

Now the part that travels everywhere, and the reason a serious RevOps practice is horizontal rather than one vertical wearing a costume.

Strip away the SaaS fixtures and the plumbing underneath is identical. You still need one place where the truth lives. You still need a stage to mean one thing. You still need to know your ICP well enough that two people would disqualify the same lead. You still need clean data, leads that get routed, and a forecast built on evidence instead of hope.

RevOps is not a SaaS invention. It is a revenue discipline, and revenue is a great deal older than software.

The pipe is the same. Only the fixtures on the end of it differ. That is why a lender, an agency, and a manufacturer with a real B2B sales motion all need the same spine, and why the way we work is built to be horizontal, not bolted to a single industry.

SaaS did not invent revenue operations. It just wrote the loudest blog posts about it. The discipline is older than the software, and it works perfectly well in a business that never ships a login.

Common questions

Does RevOps only apply to B2B SaaS?

No. RevOps is a revenue discipline, not a SaaS feature. Professional services, regulated finance, manufacturing, and agencies all need the same spine: one source of truth, clear stages, a known ICP, clean data, and an honest forecast.

What is different about RevOps for non-SaaS companies?

The pipeline is longer and led by a relationship, there is no self-serve signup or product usage data to score, stages map to real-world commitments rather than product steps, and in regulated sectors the CRM doubles as a compliance record.

What should you measure without product usage data?

Measure the relationship: whether meetings progress, how many stakeholders you have met beyond one contact, whether an internal advocate exists, and how proposals move. Single-threaded accounts, where you know only one person, are the clearest churn risk.

A pipeline you can trust and a forecast that holds. That is the work we do.

See how we work Run the GTM diagnostic

Get the next one

New field notes twice a month. We don’t do newsletters, follow RevOps XL on LinkedIn instead.

Follow on LinkedIn

Sound familiar?

If this is happening in your stack, tell me about it. A senior expert reads these, not a bot - and you’ll get a real answer, whether or not you ever hire us.

← More field notes