Notes for owners · Industry playbooks
How buyers choose between IT, software and SaaS vendors
Technology 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.
The GullySales team · Updated 13 Nov 2026 · 5 min read

On this page
- Stage one: who gives the buyer a name?
- Stage two: what does the check look for?
- Stage three: where do free demos and assessments go wrong?
- Stage four: who signs, and what do they fear?
- What happens after the first project?
- The shortlist is built in conversations you cannot see
- Four questions every technical buyer asks
- Demos that follow the buyer's day
- The pilot with a pass mark
- Price, in a form a finance head can use
- An invented case: the demo that lost the finance head
- Staying in the account after go-live
- What to do next
Technology buyers choose in four stages, and most vendors lose at the second or third. Someone gives them a name. They check the name against a website and an engineer. They test it with a pilot, a demo or an assessment. Then a finance head or owner signs. Marketing is mostly noticed in stage two, sales is mostly lost in stage three, and the second order is won or lost long after stage four.
Stage one: who gives the buyer a name?
A CTO whose cloud bill jumped asks two other CTOs. A finance head with a regulator's circular on the desk asks the internal auditor. A founder who needs an app built asks other founders. By the time any of them reaches your website, a shortlist of two or three names exists.
This is why search, review sites and LinkedIn behave as checks, not discovery. A buyer types your firm's name, or the problem plus a city, to see whether the name holds up. A page that matches the exact problem, such as a GST-linked ERP migration or an AWS cost review, makes that check come out well. A generic services page does not.
Stage two: what does the check look for?
The buyer is trying to learn two things in a few minutes about a firm in the IT, software and SaaS group. Does this firm work on my kind of problem, and are real people behind it? Both answers come from specifics.
| Group | What the buyer looks for | What loses the check |
|---|---|---|
| SaaS companies | Who it is built for, what a trial shows | A trial signup nobody replies to |
| ERP providers | Closing entries and reports in the buyer's own trade | A demo that skips the accountant's questions |
| Software development | Named engineers, what happens after launch | Rates and logos with no detail |
| IT services and networking | A local firm that picks up after a move | No sign of support afterwards |
| Cybersecurity | Credentials, an auditor's comfort | Vague claims about "protection" |
| Managed IT | What the agreement covers, in plain words | A quiet year that looks expensive |
| Cloud and DevOps | A fixed-scope assessment | An open-ended proposal |
| Automation and RPA | A pilot with a pass mark | A bot that broke at the last vendor |
The best work in the group can sit under an NDA, so the case study cannot name the client. Describe the problem, the systems and what was done in terms an engineer can test, and say plainly that the client is under NDA. Offer a reference call once the client agrees. Never invent a logo or a figure.
Stage three: where do free demos and assessments go wrong?
The buyer asks for a customised demo, a free assessment or a proof of concept, and some vendors say yes to everything. Then the buyer carries the plan to a cheaper partner. It happens.
For example, a Pune cloud partner is asked for a free assessment by a manufacturer whose bill has jumped. The partner spends days on it and sends a long document. The manufacturer's finance head forwards it to a cheaper firm and the partner hears nothing. Had the partner agreed the scope, what the buyer would provide, and what decision the assessment would lead to, the assessment would have been a step, not a gift.
Before any free effort, agree three things in writing: what you will look at, what the buyer will supply, and what happens next if the result is good. For pilots, agree the pass mark before the pilot starts. A buyer who will not agree to that may only be collecting a plan.
Stage four: who signs, and what do they fear?
The person who felt the pain is rarely the person who signs. The CTO or IT head fears a risky architecture. The accountant or finance head fears an audit trail that does not hold and a renewal that arrives without warning. The owner fears paying for something that nobody uses.
A sales process that talks only to the person who filled the form loses to one that has answered the others. Ask early who else has to be comfortable. Send the engineer the technical note. Send the finance head the terms, the renewal and what is covered in plain words. The sales enablement page for cybersecurity firms shows how those documents are prepared.
What happens after the first project?
Maintenance, retainers, the second bot, the next phase of the product and the annual retest all follow the first delivery. They are rarely proposed. A client who has heard nothing since go-live calls whoever is nearest, and that is not always you.
Put the next offer in the handover document, with a date for the first review. Keep a renewal calendar with a named person for each account. The buyer persona page for cloud and DevOps firms is a good place to start writing down who each account's three people are.
The shortlist is built in conversations you cannot see
A buyer's first message to a vendor is the end of a research trail. Somebody forwarded a name on WhatsApp. A colleague mentioned a tool in a meeting. A podcast guest used a phrase that stuck. By the time the buyer opens your site, they are testing a name they already hold.
So the work before stage one is to be easy to describe. If a customer cannot say in one sentence what you do and for whom, they cannot pass your name on. Ask your last five customers how they would describe you to a friend, and write the sentences down. The gaps between those sentences and your homepage are where names get lost.
Four questions every technical buyer asks
Whatever the product, an engineer or IT head asks the same four things in the first call.
- Where does the data live, and who can see it?
- What does it connect to, and how?
- What happens when it breaks, and who picks up?
- How do we leave if it does not work?
Write the answers once, plainly, in a document that a non-specialist can read. Do not claim a certification you do not hold. Do not name a security standard unless you can produce the audit. If an answer is "it depends", say what it depends on. A vendor who answers the fourth question without being pushed has already passed a test.
Demos that follow the buyer's day
A demo that walks through every feature loses the room. Ask beforehand for three real tasks the buyer's team does every day, and build the demo around those. Use the buyer's own data or a close copy of it, if the buyer agrees and the data is safe to share.
Stop after each task and ask whether it matches how the team works. A buyer who says "we do not do it that way" has given you the most useful line of the call. Write it down, and say what you will do about it.
The pilot with a pass mark
A pilot without a pass mark is a free trial that lasts as long as the buyer likes. Agree before it starts what has to be true for the pilot to be called a success, who will judge it, and what the buyer will do if it succeeds. Write it on one page and have both sides initial it.
Keep the pilot small. One team, one process, one site. If the buyer wants more, that is a sign of interest, not a reason to expand the free work. Quote the larger piece separately.
Price, in a form a finance head can use
A finance head compares what is included, what renews and what leaves. Set out the price in a table: the one-time cost, the recurring cost, what triggers an increase, what is excluded and how the term ends. Use the figures you have actually agreed, and do not round them for effect.
If you cannot give a price before a scoping call, say so and say what the call will cover. A page that hides everything behind a form suggests there is something to hide. A page that says what the price depends on does not.
An invented case: the demo that lost the finance head
Take an invented ERP provider in Coimbatore that gave a polished demo to a textile mill's owner and plant head. The owner liked it. The finance head, who was not in the room, asked afterwards how the software handled a return of goods against a GST invoice. Nobody could answer from memory.
The provider's next step was to send a short written note covering returns, credit notes and the period-end close, with screenshots of the actual screens. The finance head replied with two corrections, which the provider fixed in the note. The deal moved on. The first demo had been good. It had spoken to the wrong person.
Staying in the account after go-live
A vendor that disappears after go-live is remembered as one that disappeared. Set a time for a first review, in the handover note, and keep it. Ask what the team still does by hand. Ask what they wish it did. Write both down. The second answer is your next offer, and it comes from the customer.
Keep one name at the client who will answer the phone when the project head leaves. Projects move on, and people change jobs. An account held only by the person who bought it ends the day that person resigns.
What to do next
Pick your last five lost deals and mark the stage where each one stopped answering. If three stopped after the demo, the problem is stage three, not your advertising. Never reached a call? Then the check in stage two is failing. Tell us what you need and we will read it before we call, starting with how your enquiries arrive and where they go quiet.
Put the reading to work
Try this with your own records.
Review repeat orders, inactive customers, and reasons for leaving. Separate a normal buying interval from a customer who stopped because of an unresolved problem.
How to review the result
Track the response through to a retained or repeat order, with discounts and service costs visible. Record why the customer returned rather than crediting every repeat purchase to the campaign.
Related services








