Skip to content
GullySales

Software development companies · B2B customer reference programme

Know which client agreed to a call before a founder asks for one.

A customer reference programme for a software development company is the managed list of past and current clients who have agreed to speak to a prospective buyer about how a build went. GullySales records what each client agreed to, matches a referee to the prospect's kind of project, and keeps the list from wearing out one friendly founder.

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

Realistic editorial illustration of software development companies at work in India

What B2B customer reference programme means

A B2B customer reference programme is a managed pool of customers who have agreed to take reference calls or to be named. GullySales asks permission properly, records what each customer agreed to, matches a reference to a prospect by industry and need, and keeps count so nobody is over-used.

Last updated 14 Nov 2026.

For software development companies

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

  • “The referee is the client's founder or CTO”

    A buyer weighing a software build does not want a polished quote from a stranger. They want ten minutes with someone who handed over a spec and lived through the sprints. That person is a founder, a product owner or a CTO with no spare time. Ask badly, or ask the same person too frequently, and the goodwill from a good delivery is spent on your sales calls rather than on the next phase of work.

  • “Confidentiality limits who can be named”

    A good share of your strongest builds sit under an NDA or were delivered under another company's label. A referee may happily speak by phone but not allow a logo, a name or a product description on your website. A reference list that mixes those permissions in one spreadsheet column leads to a salesperson naming a client who only agreed to a private call. Each client's permission has to be recorded in plain words.

  • “The wrong project type reassures nobody”

    A founder planning a mobile app for patients is not reassured by a referee whose build was an internal finance tool. The buyer is checking a specific doubt: did the team understand a regulated domain, an integration, a deadline set by an investor, or a rebuild after a previous vendor left. A reference pool matched only by who is friendliest answers a question the buyer did not ask.

  • “A dispute makes a client unreachable”

    Every delivery firm has a client in the middle of a late milestone, a change request argument or an unpaid invoice. Putting that client in front of a prospect is a risk for both sides. The pool needs a plain status for each client, so the salesperson sees a pause marker before dialling, and the delivery lead decides when a relationship is repaired enough to be asked again.

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. Reference permission record

    One record per client showing exactly what they agreed to: a private call, a written note, a named mention, a logo, a site visit or a conversation with their engineers. It also records who gave the permission, on which date, and whether the client's legal or communications team must approve a request first. A salesperson reads one line and knows what may be offered.

    Result: Each client in the pool has a dated permission line the whole sales team can read.

  2. Referee profiles by project type

    A short profile for each willing referee covering the kind of build, the domain, the size of the client's team, the engagement model and the doubt this client can speak to best. It leaves out confidential detail, so a salesperson matches on facts the client has already cleared. A profile also notes who at the client is the right voice, such as the founder or the technical lead.

    Result: Any build type your firm sells has at least one named referee profile, or an honest gap noted.

  3. Matching sheet for live deals

    A working sheet that pairs each open opportunity with the referee of greatest use to that buyer, drawn from the discovery call notes. It records the buyer's stated doubt, such as handling scope change or taking over a half-built product, and the referee best placed to answer it. The sheet also shows who else was considered and why they were set aside.

    Result: Every deal that reaches proposal stage shows a chosen referee and the doubt that call will answer.

  4. Request and thank-you messages

    Written asks for a client to take a call, in your firm's voice, with the reason, the buyer's trade, the likely length of the conversation and an easy way to say no. A second message after the call thanks the referee and tells them whether the work was won. Both messages state that a refusal changes nothing about the relationship.

    Result: A referee can accept, decline or defer from the message itself, and nobody is chased.

  5. Usage log and rest rules

    A log of every request, every call that took place and every outcome, with a rule for how long a referee rests between calls. The rule is set with your delivery lead, because the person who manages the client knows when their patience is thin. The log shows who has been overused and who has never been asked.

    Result: The log shows the last request date for every referee and flags anyone due a rest.

  6. Briefing note for the salesperson

    A one-page guide for the salesperson who introduces a referee: what to tell the buyer in advance, what not to script for the referee, and how to follow up without pressing. It tells the salesperson never to write the referee's words. It lists the questions a buyer asks and which of them the client has said they will not discuss.

    Result: Each introduction is made with a briefing note and a clear list of topics the referee has put off limits.

How the result is measured

  • Customers available by industry, size and agreed activity
  • Requests accepted, declined or unanswered, with reasons where given
  • Requests per customer against the agreed limit

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.

B2B customer reference programme for software development companies: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Review repeat orders, inactive customers, and reasons for leaving. Separate a normal buying interval from a customer who stopped because of an unresolved problem.

Make the scope clear

Choose the customer group and the reason to contact them. Agree how complaints, renewal decisions, and additional offers are handled, including when a sales message is inappropriate.

Check the work in use

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.

Know when to change course

If customers leave because delivery is unreliable, fix that before offering a loyalty reward. Repeated promotions can hide the cause without improving the experience.

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.

List of completed and current projects
A list of every build with the client, the type of work, the engagement model and the current state of the relationship. Without it we cannot tell a delivered success from a project still arguing over scope, and the first asks go to the wrong people. A rough list from your delivery leads is enough to begin.
Contract confidentiality clauses
The confidentiality and publicity clauses from your client agreements, or your lawyer's summary of them. They decide whether a name, a logo or even the existence of a project may be mentioned. If they are missing, we treat every client as private-call-only until your lawyer says otherwise, and the pool will be smaller than it might be.
A named delivery lead per client
The person at your firm who knows each client best and will make the introduction. A reference request from an unfamiliar sales contact sounds like an imposition. Where nobody owns a relationship, we mark the client as not ready to ask and suggest your founder decide who will look after it before anything is sent.
Your last few buyer questions
Notes from recent discovery calls and proposals where a buyer wanted proof: what they asked, which doubt sat behind it and what you sent. These tell us which referee profiles to build first. Without them we guess at the doubts, and the pool is arranged by project size rather than by what a buyer needs to hear.
Your sales tracker or CRM access
Access to wherever opportunities are recorded, so the reference fields sit beside the deal and not in a separate file. If you have no tracker yet, we build the pool in a shared sheet and say plainly that a salesperson will have to look in two places until the tracker is set up.

How it works

How the B2B customer reference programme 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

    Audit of delivered projects

    We start with your list of completed and running builds, not with a request to clients. For each we note the domain, the engagement model, who the client's decision maker was, how the project ended and whether the relationship is warm. We record contract clauses on confidentiality as your lawyer or founder reads them. This produces the long list from which no one has yet been asked anything.

  2. 2

    Delivery lead conversations

    The person who ran each project knows which clients would say yes, which are tired and which are in a delicate phase. We sit with your delivery leads and mark each client as ask now, ask later or do not ask. The delivery lead makes the introduction, because a request from a stranger at your firm will land worse than one from the person who handled their sprints.

  3. 3

    Asking clients with a way out

    We draft the request for each approved client, naming what is being asked in plain terms and offering a decline option that costs nothing. Your founder or delivery lead sends it, because the relationship is theirs. Replies, silences and refusals are all written into the permission record, and a client who declines is marked so nobody asks again by accident.

  4. 4

    Building the referee profiles

    For each client who agreed, we write the profile with your delivery lead and have the client's contact confirm what may be said. We map each profile to the doubts buyers raise in your discovery calls, such as a rebuild, a regulated domain or an overseas time zone. Gaps show up here: a build type you sell regularly with no referee is a finding for the founder.

  5. 5

    Wiring the pool into the pipeline

    We add the reference fields to your tracker, so a salesperson sees the matching referee at proposal stage and logs the call afterwards. We agree who may approve an introduction and write the rest rules into the sheet. A short session with your salespeople covers what to say when a buyer asks for a client whose permission was only private.

  6. 6

    Reading the log against the baseline

    Before the work started we recorded how many reference requests reached the sales team, who answered them and how long the delay felt to the buyer. We now read the usage log against that record. It shows how many requests were met from the pool, which referees were stretched and which build types still lack a voice, so the next round of asks is chosen on facts.

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.

Can a software firm run a reference programme if the best projects are under an NDA?
Yes, because a reference call and a public name are different permissions. A client under an NDA may still agree to a private conversation with a serious buyer, if your lawyer confirms the agreement allows it. We record each client's permission separately, so the salesperson offers only what was cleared and never a name the contract forbids.
How many referees does a development company need?
There is no fixed number. What matters is coverage of the builds you sell and the doubts buyers raise, such as a rebuild or a regulated domain. One referee per build type is a sensible start, with a second where a build type brings the bulk of your revenue, so a single founder is not asked every time.
Should we offer clients something for taking a call?
No. A payment or discount for a reference makes a buyer doubt what they hear, and it can breach a platform's or your client's own rules. A thank-you note and an honest update on the outcome are enough. The programme records voluntary agreement, and a client who declines is never pressed.
What if the best referee is also our largest client?
Protect that relationship before using it. A client that provides a large share of your income is the one you least want to tire out. We rest them between calls, ask your delivery lead to approve each request, and build a second and third referee so the buyer is never sent to the same founder.
Do reviews on a listing site replace reference calls?
No. A review on a listing site is a public statement written to a prompt, while a call lets a buyer ask their own question about scope changes, handover and what went wrong. Buyers read the reviews first and then ask for a call. The two work together, and this programme covers the call.
Will you speak to our clients for us?
We prepare the request, the profile and the log, but the introduction comes from your founder or delivery lead, because the relationship is theirs. We do not write words for referees to repeat or contact clients without your approval. The client decides what to say, and you decide whether to ask.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
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.

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.