Skip to content
GullySales

Software development companies · Sales discovery process design

Learn what the build really needs before a number is spoken aloud.

Sales discovery process design for a software firm is the written method for the first real conversation with a founder or IT head: what to learn about the system, the users and the budget owner, in what order, and when to stop. GullySales writes the question sets, the discovery note your CRM holds, and the rules for moving a buyer to a paid discovery phase or letting the enquiry go.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A trainer develops discovery questions while a colleague practises buyer notes

What sales discovery process design means

Sales discovery process design is the written method for a salesperson's first real conversation with a buyer: what to learn, in what order, and when to stop. GullySales writes the question sets, the discovery note your CRM holds, and the rules for moving a buyer on or letting the enquiry go.

Last updated 14 Nov 2026.

For software development companies

Where it usually goes wrong, and what we would do.

  • “A two-line idea arrives with a price request”

    The founder who writes in wants a total cost for an app described in two lines. Whatever figure the seller gives becomes the ceiling. A set of questions about users, integrations and the first release lets the seller reply with something other than a number.

  • “The person on the call is not the person who signs”

    A startup founder, an operations manager at an established business and an IT head each decide differently. One consults an investor, another a technical adviser. Discovery that asks who else reviews the proposal saves a second round of explanation.

  • “Engineers join the call and answer the wrong question”

    A solution architect on a first call starts designing in real time. The buyer hears a plan before the problem has been stated. Rules for what the technical person does on call one keep discovery about the buyer's need.

  • “Notes live in memory, so proposals start from nothing”

    After a call, the seller recalls the headline and forgets the constraints: the legacy database, the deadline tied to a funding round, the earlier vendor who left. A discovery note records them, and the proposal writer starts from facts.

What we do

What we deliver for software development companies.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Discovery topic list for software projects

    The facts a seller must learn before a proposal: the business problem, the users, the systems it must connect to, the decision-maker, the budget owner, the date that matters and the alternatives being weighed. Your head of sales strikes out anything your cycle does not need.

    Result: Every seller asks about the same set of topics.

  2. Question sets per kind of engagement

    Separate questions for a new product build, a rescue of a half-finished project, a dedicated team request and a government bid. A rescue call asks what was built and who holds the code.

    Result: The questions match the type of buyer in front of you.

  3. Discovery note template

    A one-page note the seller completes after every first conversation, with a line for each topic and a place to mark an answer as unknown. A filled sample shows the level of detail expected.

    Result: A colleague can pick up the enquiry from the note alone.

  4. CRM fields for the note

    The note's fields set up in the CRM you already use, or a shared sheet if you have none, within what the system allows. Choosing a new CRM is separate work.

    Result: What was learned is searchable, not buried in a chat thread.

  5. Move-on and stop rules

    Written criteria for offering a paid discovery phase, sending a proposal, referring the buyer elsewhere or closing the enquiry politely.

    Result: The team knows when to invest more time and when to stop.

How the result is measured

  • Discovery notes completed after first meetings
  • Unknown answers by topic, such as budget owner or timeline
  • First meetings that led to a proposal or a second meeting

Recorded as a baseline before work starts, so every later report has an honest comparison.

Who it is for

This is written for these software development companies.

  • Custom software development companies
  • Mobile app developers for Android and iOS
  • Product engineering firms working with startups
  • IT consultants and technology advisers
  • SaaS product companies selling to Indian businesses
  • Offshore development centres serving overseas clients
  • Firms specialising in one domain, such as healthcare, logistics or fintech
  • Low-code and automation developers
  • Software firms bidding for government work on GeM

Before you decide

Agree the work. Know how to judge it.

Sales discovery process design for software development 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 software development companies. Anything missing is noted in the written scope, with who will supply it.

Notes from your latest calls
However thin. They show the real starting point, and if nothing was written, we ask the salesperson to reconstruct three calls. A pencilled note on the back of a proposal also counts.
A proposal that went wrong on scope
A project where the estimate was far from what was needed, with the account of why. It tells us which questions would have prevented it. If the salesperson has left, ask the founder to retell one, because a reconstructed account is better than none.
A salesperson willing to trial the questions
One person on live calls who will use a new script and report honestly. Without a trial the questions stay theory. Estimate sheets and the later change requests are enough, even without the original mails.
The kinds of engagement you offer
A list of the models and sizes, so the question sets are written per type. A single list for all produces long calls and short answers. Have that person agree a call to be listened to, as the questions need a real ear.
The conditions for a paid discovery phase
The founder's rule for when a buyer is asked to pay before a scope. It decides what the move-on criteria say. We ask for the description of each service in your own words, however short, because the questions follow the way you sell it.

How it works

How the sales discovery process design 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. 1

    Read the notes of the last first meetings

    We ask for notes or mails from recent first conversations with founders and IT heads and mark what was learned and what was left unasked. You tell us which of those calls turned into projects. The gap between a good call and a thin one gives us the topics worth writing questions for. We also mark the calls where an engineer joined and the buyer's questions changed, since that shows where the seller needed support.

  2. 2

    Agree the topics with your sales lead

    From the notes we draft a list of what must be known before a proposal: the system's users, the funder, the deadline, the existing tools, the person who signs. Your sales lead strikes and adds. The agreed list is the spine of everything that follows. The list is limited to what changes a proposal, and curiosity questions that never alter the estimate are left out.

  3. 3

    Write questions and try them on a call

    We turn each topic into plain questions for the kinds of engagement you sell, such as a first build, a rescue or an add-on. A salesperson uses them on a live call while we listen. Questions that sound like an interrogation are reworded. A question the buyer found intrusive, such as asking who funds the project, is reworded with your sales lead until it sounds like help.

  4. 4

    Make the note and the fields

    We build a discovery note with a place for each topic and a matching set of fields in your CRM, so the answer on funding sits where a proposal writer will look. You test the note with a real call and decide which fields are compulsory. The template ends with a line for what the seller still does not know, so a proposal writer sees the gaps before starting.

  5. 5

    Sign off when to move on or stop

    We write the signals that mean this buyer should be offered a paid discovery phase, sent a polite decline or passed to a partner. You and your sales lead approve them. Without these criteria the salesperson answers every enquiry with an estimate. A rule for the enquiry that fits nobody, such as a request far below your minimum, is written as a polite decline.

  6. 6

    Read the first notes against the old ones

    After some live use we compare the new notes with the earlier ones from the start. You see whether proposals now begin from facts. We adjust the questions that buyers found odd and drop those that never produced useful answers. Notes that lack the funder or the signatory are picked out, and the question set is changed where it failed to draw that out.

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.

  1. 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.

  2. 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.

  3. 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.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Will this slow the sales cycle for founders who want an answer now?
The method is about the quality of the first conversation. A buyer who sees you ask sharp questions trusts the paid discovery phase sooner. Where an enquiry fits a standard offer, the stop rules let the seller move on.
Do we use one question set for all buyers?
No. A startup founder, an enterprise IT head and an overseas client need different questions. The sets are written per kind of engagement and per visit type, such as a video call or an on-site meeting.
Can this work if our sellers are engineers?
Yes, and it suits them. The topic list gives an engineer-seller a clear order to follow, and the note records what was learned. The method asks for listening more than pitching.
Who writes the discovery note, the salesperson or an engineer?
The person who held the call writes it, using the fields we set up, and a technical colleague adds to it if they joined. Writing it soon after the call matters, because memory fades faster than the buyer's patience. The note is short on purpose: topics answered, topics unknown and the next step agreed. A proposal writer should be able to start from it without calling the buyer again.
What if the buyer refuses to talk about budget?
The note records it as unknown, and the move-on rules say what follows. Some buyers cannot name a figure before they see a scope, so the question can be reframed as a range of effort or a stage of funding. If the buyer will not discuss money or who signs after two honest attempts, the criteria suggest a paid discovery phase or a polite pause, not a long proposal.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.
What if we are not happy with the work?
Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

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.