SaaS and software companies · CRM
A stage with no exit criterion turns your forecast into a mood.
A CRM for a software company is the pipeline record: the account, the stage, the next step with a date, the champion and the person who signs. Product usage belongs on it too. GullySales defines the stages and the fields, then builds the read-out your board questions are answered from.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Also for SaaS and software companies
- Lead generation for SaaS and software companies
- Follow-up systems for SaaS and software companies
- SEO for SaaS and software companies
- PPC ads for SaaS and software companies
- Digital marketing for SaaS and software companies
- Reputation management for SaaS and software companies
- Local SEO for SaaS and software companies
- Branding and identity for SaaS and software companies
Sales and marketing for SaaS and software companies, the overview.
Last updated 5 Oct 2026.
For SaaS and software companies
Where it usually goes wrong, and what we would do.
“A stage needs one thing that must be true”
If demo means whatever the rep felt after the call, the forecast is a feeling. Each stage needs a written exit criterion your AEs signed off on, and a deal that fails it moves backwards.
“Product usage belongs on the account record”
Seats gone quiet, an integration disconnected, a workspace with one active user. Leave that in the product database and the CRM cannot see the renewal coming apart.
“Two contacts, not one”
The champion and the person who signs the order have different problems. Most records hold one name, which is why a deal dies the week the champion changes jobs.
What we do
What we deliver for SaaS and software companies.
Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.
Stages with written exit criteria
Each stage defined by one thing that must be true, agreed with your AEs and applied, so no deal sits in negotiation for a quarter without moving.
Result: The forecast survives a question from your board.
A next step and a date on every open deal
A rule that no open opportunity exists without a scheduled next action and an owner, checked in the pipeline review rather than assumed.
Result: Deals stop ageing quietly in the middle of the funnel.
Champion and economic buyer held separately
Both contacts on the record with their roles noted, and a flag on any deal that has never reached somebody with signing authority.
Result: You know which deals are one resignation away from dying.
Product usage joined to the account
Seats, activation state and last login pulled onto the record, so sales and customer success are reading the same account.
Result: A quiet workspace becomes visible before the renewal date.
Closed-lost reasons on a short fixed list
A small set of reasons, one of them mandatory, with a free-text line for the detail, so lost deals can be read as a group instead of one by one.
Result: You can separate price losses from product losses.
A pipeline read-out for the board
Pipeline by stage with deal age, stage-to-stage conversion and coverage against target, built from the baseline taken before work starts.
Result: The number in the deck comes out of the system, not a spreadsheet.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
What to record, and when
What a software company should record about every account and deal, and whether a CRM is needed yet.
- Lead source from a fixed list
- Separate signup, demo request, outbound reply, partner and event. Founder-led teams often cannot say which channel produced their paying accounts.
- The use case and the tool they use today
- Record the problem they wanted solved and what they use now, even if it is a spreadsheet. Your comparison pages and your pricing answers come from this field.
- Trial or pilot status
- Note start date, seats activated and whether the champion has logged in. A pilot with no logins is a deal that needs a conversation now, not a place in the forecast.
- Procurement, security and legal steps
- Record whether a security questionnaire, legal review, vendor onboarding or GST invoice details are needed, and who owns each. These steps stall deals where nobody is looking.
- Closed-lost reason from a short list
- Use no budget, no decision, chose a competitor, built in-house or bad timing. Free text cannot be counted, and a count is what changes your next plan.
- Do you need software yet?
- A sheet suffices while the founder sells to a short list. Move to a CRM when a second person sells, when sequences go out, or when product usage must sit beside the deal.
Who it is for
This is written for these SaaS and software companies.
- Seed and Series A B2B SaaS still selling founder-led
- Bootstrapped vertical SaaS with a small team
- Product-led companies adding a sales motion
- Developer tools moving upmarket into team plans
- Healthcare, fintech and other compliance-heavy software
- Agencies and services firms productising a platform
- Marketplaces with a supply side to recruit
- Companies with a full AE bench and no pipeline to feed it
- Software companies entering the US from another market
Not for
It is not the right fit if.
- Your team is mid-way through changing CRM tools, and a new stage design would be rebuilt after the move
- The owner will not agree one list of stages, and each rep wants to keep their own
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Map the sales process
We sit with the people who sell and write down how a deal moves from enquiry to payment, including where it stalls.
- 2
Agree stages, fields and owners
Each stage gets a name your team already uses and a proof that the deal has left it. We agree which fields are required at which stage, and who may change what.
- 3
Build on a copy
Pipeline, fields and views are built on a trial copy where the CRM offers one, or in a separate pipeline where the plan allows. Live work stays untouched.
- 4
Connect channels, then switch on automations
Channels are connected first. Each automation is then switched on separately, so a misfiring rule is easy to find.
- 5
Test with real deals
The people who will use the CRM run open deals through it. Gaps are fixed before the whole team switches over.
- 6
Switch over and trim
Once real use shows which fields stay empty and which stages nobody uses, those are cut and the handover record is updated.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
We already have a CRM nobody updates. What changes?
Do you work in our system or bring your own?
Should product usage data go into the CRM?
Who owns the CRM account if an outside team works in it?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
What if we are not happy with the work?
From the blog
Further reading for SaaS and software companies.
5 min read · 6 Oct 2026How buyers choose between IT, software and SaaS vendorsTechnology buyers take a name from a peer, test it against an engineer and sign after a finance check. This post follows the choice in four stages and shows where vendors drop out.
7 min read · 21 Sept 2026How to advertise to software engineersThey block your ads, distrust your copy and will not talk to your sales team. What reaches them is documentation, a free tier and someone they already read saying your name.
7 min read · 21 Sept 2026How to advertise to sales heads, who see the playbook comingA sales head runs the same sequences you are about to send them. They buy on a missed number, a hiring problem or a handover, and only what they can defend upward.
More for SaaS and software companies
Everything else we would do for you.
Closest to this: leads and follow-up
Also for SaaS and software companies
Or start from the overview: sales and marketing for SaaS and software companies.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.