RevOps for a Software Development Company: A Pipeline Built for Project Work, Not SaaS

Almost everything written about revenue operations assumes you sell subscription software. Short sales cycles, and a buyer who swipes a card and expands next quarter on their own. If you run a custom-software shop or an IT-services firm, that world is not yours. Your deals take months. Clients pick you on trust and reputation, and the feature list matters far less. The work is a project with a start and an end. It does not renew on its own once you deliver it.

So when a founder in your position hires help and gets handed the standard playbook, most of it slides off. The metrics do not map, and the stages describe a motion you do not run. We have built the revenue operations for exactly this kind of business, including a US custom-software consultancy, and the useful version looks quite different from what the SaaS crowd will sell you.

The championLikes you, runs the calls, cannot sign.

The economic buyerOwns the budget, and usually goes quiet.

The technical evaluatorCan kill it on risk or fit alone.

The quiet blockerNever in the room, still decides.

Thread into the champion alone and the deal dies the moment they stop replying. Map the other three early, or you are guessing at a number.

Why the SaaS playbook does not fit you

Start with how the deal actually moves. A subscription tool gets bought fast, often by one person. Your engagement gets bought slowly, by a committee, after several conversations where the client decides whether they trust you to touch something that matters to their business. That length comes with the kind of work you sell. A pipeline that assumes otherwise will mislead you every week.

Then there is the split buyer. In your deals the person who understands the technical problem is almost never the person who signs. A VP of engineering or a technical lead scopes the work and vouches for you, while a CFO or a founder approves the spend. Those two people want different things and worry about different risks, so a deal that only reaches one of them stalls the moment the other asks a question nobody prepared for. SaaS RevOps barely accounts for this, because in SaaS the two roles often collapse into one person.

The revenue shape is different too. SaaS lives on recurring revenue that compounds, so the whole system is tuned to retention and expansion. Your revenue arrives in chunks tied to projects and phases, and a finished build does not renew itself. If you want next quarter to hold up, someone has to sell the next phase or the next referral. That selling has to live inside your pipeline where the team can see it, instead of staying in the founder's head. We wrote more about this gap in RevOps when you are not SaaS.

What a predictable pipeline actually looks like

Predictable has nothing to do with a bigger CRM. It means you can look at your pipeline on a Monday and know which deals are real and where to spend the week. A few habits get you there.

Start by defining who is winnable, and take that definition from your own history instead of from a workshop. Your closed-won deals already tell you which clients you win and why they picked you, and which of them turned into the profitable long-term relationships you want more of. Read that record honestly and a shape appears: a certain size of company, a certain kind of problem. That is your ideal client profile, and it is worth defining precisely, because almost every later decision rests on it. Sizing how many of those clients exist, and how many you can realistically win in a year, is the exercise we lay out in TAM, SAM and SOM.

Then decide who to call first. Not every lead deserves the same effort, and a services firm with a small sales team cannot afford to treat them as if they do. A warm referral from a past client who matches your winnable profile is worth ten cold inbounds that do not. Scoring leads is really about protecting your most expensive resource, the senior person's time, and spending it where it converts. If you are building or fixing the front end of this motion, our BDR function blueprint covers how to structure the people and the handoffs.

Then map the buying group so no deal rests on one person. For every live opportunity you should be able to name the technical champion who wants the work done and the economic buyer who controls the budget, plus anyone else with the standing to kill it. A deal where you know only one of those names is single-threaded, and single-threaded deals die when your one contact changes jobs or loses an internal argument you never saw happen. The fix is dull and it works. Build more than one thread into every account, and keep those threads visible in the pipeline.

Where the money leaks

In services firms the losses tend to cluster in the same few places, and none of them need new tools to fix.

Deals stall and nobody notices. A proposal goes out, the client stops replying, and the opportunity sits at the same stage for two months while still looking healthy on the forecast. It is not healthy. Set a rule for how long a deal can sit before someone chases it, or the pipeline fills with opportunities that are already dead and tells you nothing reliable about next quarter.

You do not know why you lose. Most services firms never write down a lost reason, so the same losable deals keep arriving and the same objections keep landing, and nobody can point to the pattern. When we started capturing lost reasons for the US consultancy, no single deal was the point. After about thirty of them, one kind of prospect stood out as a client that was never going to close, and the team stopped spending weeks on that profile.

The forecast is built on hope. A number the founder feels good about does not make a forecast. A real forecast only counts deals that each have a live next step and a named buying group, with a close date the client would actually recognize. Strip out the deals that fail those tests and the number gets smaller and much closer to true, and you can finally plan hiring and cash against it. We went deeper on this in why your sales forecast is always wrong.

Where to start

You do not need to rebuild anything to find out where you stand. Pull your closed-won and closed-lost from the last year or two and read them as a record of who you win and where deals die. Most of the leaks above show up in that reading before you change a single setting.

If you would rather see it laid out for your own numbers, our free GTM and RevOps diagnostic walks through the same questions and shows where a services pipeline is losing money. And if you want a senior person to run the whole exercise with you, that is what fractional RevOps is for: someone who has built this motion for a software firm before, working inside your business a few days a month instead of as a full-time hire.

Common questions