SaaS and software companies · Consultative selling implementation
Your reps can demo every feature and still never learn why the buyer called.
Consultative selling for a software company means a rep diagnoses the buyer's workflow, cost and blockers before showing any screen. GullySales writes discovery questions for each product and plan, builds the call guide and note template, runs practice on your past deals, and sets up the manager's listening routine.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What consultative selling implementation means
Consultative selling implementation moves a sales team from presenting products to diagnosing the buyer's problem before recommending anything. GullySales writes the discovery questions for each offer, a call or visit guide and a note template, runs practice on your past deals, and gives your managers a way to listen and score.
Also for SaaS and software companies
- Dedicated sales team services for SaaS companies
- Product one-pager writing for SaaS and software companies
- Sales presentation and demo script writing for SaaS and software companies
- Sales process for saas and software companies
- Sales management for saas and software companies
- Sales strategy for saas and software companies
- SEO for SaaS and software companies
- PPC ads for SaaS and software companies
Sales and marketing for SaaS and software companies, the overview.
Last updated 14 Nov 2026.
For SaaS and software companies
Where it usually goes wrong, and what we would do.
“The demo starts before the problem is understood”
A rep opens the product, walks through the interface and reaches the end without the buyer saying what they use today. The follow-up email then lists features. Nothing in it answers why the buyer took the call in the first place.
“The trial signup is a question, not a lead”
Someone who starts a trial has a job in mind, but the form asks for a company size. A first call that asks what they hoped to do, and what they tried last, finds the real use case and whether the product fits it.
“The economic buyer never appears in the notes”
The user loves the tool, but the person who signs the budget has seen only a forwarded link. Discovery that asks who else decides, and what that person measures, surfaces the missing meeting before the proposal stalls.
“Reps explain the product to a buyer who wants a diagnosis”
Technical buyers in particular will not accept a recommendation until their own constraints, such as security review, data location and existing integrations, have been heard. Questions on those constraints build trust that no feature list can.
What we do
What we deliver for SaaS and software companies.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Discovery questions for each plan and use case
Written sets that move from the buyer's current tool and workflow to the cost of the problem to what a fix must do. A team plan and an enterprise plan get their own sets, checked by your product owner.
Result: Every rep asks the same core questions in a sensible order.
A call guide that stays open during the demo
A one or two page guide with the opening, the order of questions, the point to summarise back and the next step to agree before the call closes.
Result: A rep can follow it live without reading from a script.
A CRM note template
Fields for the buyer's stated problem in their own words, current tool, other people involved, and what was promised. The manager reads the same fields for every rep.
Result: A call can be reviewed without listening to the recording.
Practice cases from your won and lost deals
Real deals, with names removed, rewritten as practice scenarios so reps rehearse the objections your market raises, such as switching cost and security review.
Result: Practice uses situations your team has already met.
A listening and scoring routine for managers
A short checklist for scoring a recorded call on the quality of questions and the agreed next step, plus a way to give each rep one skill to practise.
Result: Coaching points to a skill, not a general impression.
How the result is measured
- Meetings where the buyer's problem is recorded in the buyer's words
- Quotations sent with a completed discovery note
- Checklist scores per rep, and the skill each rep is practising
Recorded as a baseline before work starts, so every later report has an honest comparison.
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
Before you decide
Agree the work. Know how to judge it.
Consultative selling implementation for SaaS companies: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Bring real questions, objections, and call examples that the team finds difficult. Agree which selling behaviour needs to change and how it will be observed at work.
Make the scope clear
Choose the roles and situations to practise. Separate a training session from coaching, manager follow-up, and any scripts or reference material to be produced.
Check the work in use
Use a realistic practice conversation, then review the same skill in live work with appropriate permission. Look for a change in behaviour before attributing a sales result to training.
Know when to change course
If the problem is an unclear offer, missing product knowledge, or no permission to make a decision, fix that first. A communication workshop cannot remove those barriers.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from SaaS and software companies. Anything missing is noted in the written scope, with who will supply it.
- Your plan and pricing sheet
- Questions differ by plan, so we need the sheet that sellers use, with limits and use cases. A deck or page works. If plans are still changing, we write the questions for the plan that carries the largest share of sales and revise later, once the team has used the guide on a few live calls.
- Recordings of recent calls and demos
- Practice cases come from real conversations, so we need recordings or detailed notes of both won and lost deals. A handful is enough. Without them, role-play uses invented buyers and the lessons carry less weight, because reps recognise an invented buyer at once.
- A CRM admin to add the note template
- The note template must live in the CRM or sellers will not use it. Name the admin who can add fields and page layouts. Without one, notes live in a document that managers cannot see, so the practice is hard to check and the template slowly stops being used.
- Manager time to listen to calls
- The routine fails if managers have no time. Block calendar time for each manager and the call library access. If time cannot be found, we scale the routine to one call per manager and extend only when the calendar allows, since a routine that is abandoned is worse than a small one that continues.
- A decision on the order of demo and discovery
- Some teams show a screen early for trial users. The head of sales must decide when a demo is allowed. Without a rule, reps default to showing the product first, and the discovery questions are skipped for lack of a reason to ask them.
How it works
How the consultative selling implementation 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
Read your offers, plans and recent deal records
We begin with your plan sheet, pricing page, demo recordings and the CRM notes of recent deals, to see how reps open a call and when they first show the product. Your head of sales tells us what each plan is for. We finish with a list of the points at which discovery was skipped, for instance when a trial user was handed a demo link before anyone asked what they were trying to achieve.
- 2
Sit in on live calls
We listen to a handful of live or recorded calls across new, trial and expansion conversations and mark where the rep explains instead of asking. Reps agree beforehand. The marked calls give the practice cases we use later, along with a note of the questions that already work well and should be kept in the guide.
- 3
Write discovery questions per plan and use case
For each plan and the main use cases we write the questions that uncover the workflow, the cost of the present way, who else is involved and what would block a purchase. Sellers cut any question they would feel awkward asking. Product checks that every question points at something the product can address, and a question that points at a missing feature is flagged for the founder so the rep is not left to improvise an answer.
- 4
Build the call guide and note template
We make a one-page guide that stays open during the demo, with the questions in order and a place for answers, and a CRM template for the notes. Your admin adds the template. Notes then show the buyer's problem and the economic buyer in the same place on every deal, which lets a manager read a record and see whether the person who signs has ever been named.
- 5
Practise on your own won and lost deals
We run role-play sessions in which one rep plays the buyer from a real deal, using the past notes, while another runs discovery. Managers watch. We repeat with a different deal until the questions feel natural, and we record which objections the reps found hardest to answer so that the objection sheet can be extended.
- 6
Start the manager's listening routine
Each manager listens to a few calls and scores them against the guide, then gives one piece of feedback per rep. Your head of sales decides the scoring. We compare note quality and stage movement with the records before the change, as well as the proportion of recent notes that name an economic buyer, and we agree with you which of those figures counts as the signal that the routine works.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.
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 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
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.
Will this slow down our sales cycle?
Do product-led teams need consultative selling?
Can you train the team in a classroom session instead?
Do product-led teams need this?
How does this differ from a classroom sales course?
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?
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 with an engineer and sign after a finance check. See the four stages and where vendors drop out.
7 min read · 21 Sept 2026How to advertise to software engineersEngineers block ads, distrust copy and avoid sales calls. What reaches them is documentation, a free tier and someone they already read naming you.
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. They buy on a missed number, a hiring gap or a handover, and only what they can defend.
More for SaaS and software companies
Related work to consider.
Closest to this: sales craft
- Dedicated sales team services for SaaS companies
- Product one-pager writing for SaaS and software companies
- Sales presentation and demo script writing for SaaS and software companies
- Sales process for saas and software companies
- Sales management for saas and software companies
- Sales strategy for saas and software companies
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.