Your customers would introduce you. Almost nobody asks them.
Gully Sales builds the referral programme inside your customer relationships: which customers have earned the ask, the moment it is made, who makes it, what the customer receives back, and how quickly every introduction is answered.
- Ask only the customers whose experience has earned it, on evidence you already hold.
- Give your team an agreed moment, agreed words and an agreed limit.
- Answer each introduction fast, then tell the referrer what happened to it.
Gully Sales Private Limited works with businesses across India, joining customer service, success and sales into one programme.
In one paragraph
What is Customer Referral Programmes?
A customer referral programme is the system that turns satisfied customers into introductions. Gully Sales decides which customers have earned the ask, the moment their own success makes it natural, who in your team asks, what the customer receives in return, and how each introduction is answered and reported back to the person who made it.
The problem
Referrals arrive by accident, and nobody can repeat them.
Most Indian SMBs already get introductions. A pleased customer mentions your name at a trade meeting. An old client forwards your number on WhatsApp. It was nobody's plan, nobody counted it, and nobody can make it happen again next month. Meanwhile the customers who value your work most are never asked, because asking feels awkward, or because the person who serves them every week is not sure it is their job to raise it.
You will recognise it as
- Introductions arrive, but nobody can say which customer sent them or in which month.
- Your team asks for names only when the pipeline looks thin, never when a customer is happiest.
- A customer says something generous in a review meeting and the conversation simply moves on.
- A referred contact sits in someone's personal inbox until it is too late to be useful.
- You cannot answer a plain question: how many of your customers introduced someone to you last year?
- Somebody once asked an account that had an open complaint, and the memory still makes the team cautious.
What it costs the business
- Growth stays tied to paid channels, so every new customer costs what the market charges rather than what a warm introduction would have cost you.
- The introductions you do receive go cold, because a referred contact who waits four days for a call assumes you were not very interested.
- Customers who did introduce someone never learn what happened, so they do not do it a second time and quietly decide it was not valued.
- The ask lands on the wrong accounts, usually the friendly and the recent ones, instead of the customers whose results would persuade a stranger.
- Two people chase the same referred name, or the referred name is already in your pipeline, and the customer sees a business that looks disorganised.
Why it persists. Asking is a social act, and social acts get postponed. The account manager does not want to spend relationship credit on a favour. The salesperson moved off the account months ago. Support closed the ticket and moved to the next one. There is no point in the calendar when the ask is expected, no wording anybody has agreed, and no record of who was asked and when, so the safest choice for each individual is to say nothing at all. The programme fails on politeness, not on unwillingness.
If it stays unresolved. The channel that costs you least stays the one you never manage. Acquisition spending rises to cover the gap. Your most satisfied customers stay unasked, and some of them leave one day without ever having recommended you. The introductions that still arrive keep depending on two or three people who happen to be good at remembering, and they leave when those people do.
What changes
What changes when the ask stops being awkward.
In the first weeks
- A ranked list of customers who have earned the ask, chosen on evidence rather than on who is friendly.
- Agreed wording for the ask, in English and in the languages your customers actually use.
- A written do-not-ask list, so no account with an open complaint is approached by mistake.
- A record of who has been asked, when, and when they may reasonably be asked again.
In how the work runs
- A named owner for every ask, every introduction received and every reply back to the referrer.
- Referrals captured in your CRM with the referring customer recorded against the new enquiry.
- A written response time for a referred contact, with somebody accountable for keeping it.
- One place where a team member can see whether a name is already in your pipeline.
In sales and marketing
- More new business arrives already warm, and referred buyers usually need less convincing than cold enquiries.
- Less strain on paid acquisition when campaign costs rise or a channel slows down.
- Introductions point at buyers who resemble your good customers, because you asked customers who resemble them.
- Referring customers have publicly backed you, which changes the tone of their own renewal conversation.
In what management can see
- A monthly count of asks made, introductions received, and business closed from them.
- Referral reported as a source in its own right instead of being buried inside word of mouth.
- A clear view of which segments, services and account owners produce introductions.
Over the longer term
- Introducing you becomes a normal part of the relationship rather than an unusual favour.
- The programme survives staff changes, because the rules and words are written down, not remembered.
- You build a base of customers who have already vouched for you in front of their own peers.
Gully Sales controls the eligibility rules, the moments, the wording, the reward design, the capture path and the reporting. Whether a customer introduces anyone depends on their own experience of your product, price and service, so we measure against your own signed baseline.
Who it is for
This suits businesses whose customers already speak well of them.
The businesses it suits
- Service firms, agencies and consultancies where trust decides who even gets shortlisted.
- Subscription and software businesses with a base of steady, active users.
- Clinics, institutes and professional practices where patients or students recommend by habit.
- B2B suppliers whose buyers move between companies and take good suppliers with them.
- Distributors, dealers and equipment suppliers selling into a closely connected trade community.
- Founders who know their customers are satisfied but cannot see that satisfaction in new business.
What usually prompts the call
- Paid acquisition is getting more expensive and you want a source that does not follow ad rates.
- Introductions already arrive occasionally and you want them to arrive predictably.
- A satisfaction or NPS programme has identified promoters and nobody has acted on the list.
- Your team hesitates to ask, or asks so rarely that nothing can be measured or improved.
- A referred contact was handled badly recently and you want the process repaired before asking again.
- You are entering a new city or segment where an introduction opens doors that advertising cannot.
What Gully Sales does
The work, component by component.
Referral baseline and honest count
We take one to two years of new customers and trace how each one arrived, separating true introductions from enquiries that only look warm. We count how many asks were actually made in that period, by whom, and what came of them. Where the source field was never filled, we reconstruct what we can and record the gap instead of guessing.
- Why it matters:
- Nobody can improve a channel that has never been counted, and most businesses over-estimate how often they ask and under-estimate how often customers say yes.
- You receive:
- A referral baseline showing introductions received, asks made and business closed, with the method beside it.
- Business value:
- You start from what your customers already do for you, rather than from a general assumption about referrals.
Who has earned the ask
We write the eligibility rules using signals you already hold: how long a customer has been with you, whether they reached the result they bought you for, whether their recent tickets were resolved well, whether a survey marked them a promoter, and whether anything is open on their account. The same rules produce a do-not-ask list.
- Why it matters:
- The ask is not a favour to be spread evenly. Asking a customer whose complaint is still open costs you the relationship; asking a customer who has just succeeded costs you nothing.
- You receive:
- Eligibility and exclusion rules, plus a ranked list of currently eligible accounts.
- Business value:
- Your team asks with confidence, because the list has already been checked against service and account history.
The moment and the words
We place the ask at points in the post-sale journey where value has just been felt: a first milestone reached, a complaint recovered well, a quarterly review, a renewal signed, a project handed over. For each moment we write what is said, in person, on a call, on WhatsApp and by email, with a version your team can say naturally.
- Why it matters:
- An ask attached to a moment of value is a conversation. The same words sent at random read as a request for help, and most people quietly ignore them.
- You receive:
- A moment map with a script for each moment and channel, in the languages your customers use.
- Business value:
- The person who knows the customer can ask without inventing the words or worrying about the timing.
What the referrer receives
We design what goes back to the customer who introduced someone, and check it against the constraints your buyers live with. Many corporate and institutional customers cannot accept personal gifts or cash. We work through the alternatives with you: service credit, an added scope, training seats, early access, a donation, or simple public recognition.
- Why it matters:
- A reward that a customer's own policy forbids turns a compliment into an embarrassment, and a reward that is too large makes the introduction look bought rather than meant.
- You receive:
- A recognition and reward structure with eligibility, limits, approvals and the wording to explain it.
- Business value:
- You thank people in a way they can actually accept, without putting anyone in an uncomfortable position.
Capture, credit and first response
We build the path an introduction travels: how it is recorded, whether by form, WhatsApp or a call to the account owner; how it is checked against your existing pipeline; how the referring customer is credited on the record; who receives it; and how fast the referred person is contacted, with the first message written in advance.
- Why it matters:
- Most referral programmes do not fail at the ask. They fail in the days after it, when a warm name waits in a personal inbox and the goodwill behind it evaporates.
- You receive:
- A capture and routing design in your CRM, with duplicate checks, credit rules and a written response time.
- Business value:
- Every introduction is answered while the customer's recommendation is still fresh in the buyer's mind.
Closing the loop with the referrer
We design what the referring customer hears back and when: an acknowledgement the same day, an update once contact is made, and an outcome either way. We also write what is said when the introduction goes nowhere, and what is said when the referred person turns out to be difficult, so that the referrer is never left uneasy.
- Why it matters:
- Silence after an introduction is what stops a customer making a second one. Being told what happened is worth more to most customers than the reward attached to it.
- You receive:
- A loop-closing sequence with message templates, timings and the point at which any reward is released.
- Business value:
- Customers who introduce someone once are willing to do it again, because they saw how it was handled.
Governance and relationship safety
We set the rules that protect the relationship: how often one customer may be asked, which accounts are permanently excluded, who approves an ask into a sensitive account, how consent is taken before contacting a name a customer has shared, and what happens if a referred deal is lost or disputed between two owners.
- Why it matters:
- A referral programme touches your customer relationships directly. Without limits, an enthusiastic quarter can quietly turn valued customers into a list that feels harvested.
- You receive:
- A governance note covering frequency caps, exclusions, consent wording, approvals and dispute handling.
- Business value:
- The programme can be pushed harder without anyone worrying about which relationship it will cost.
Enablement and review rhythm
We train the people who will ask, usually account managers, success and service staff rather than sales alone, with practice on real accounts. Then we set the rhythm: a monthly review of asks due and asks made, the introductions in flight, the loop-closing owed, and one quarterly session that revises eligibility, moments and rewards on evidence.
- Why it matters:
- A programme that lives in a document decays within a quarter. It needs a short recurring meeting with a named owner, or the asking stops the first week everyone is busy.
- You receive:
- A training session with recording, a one-page programme runbook, and a monthly review agenda with owners.
- Business value:
- The habit outlasts the launch, and a new joiner can run it from the runbook without being coached from scratch.
What you will have at the end.
- Referral baseline: introductions received, asks made and business closed, with the counting method recorded.
- Eligibility rules and a ranked list of customers who have currently earned the ask.
- A do-not-ask list with the reason and the review date beside each account.
- Moment map showing where in the post-sale journey each ask belongs, and who owns it.
- Ask scripts for conversation, call, WhatsApp and email, in the languages your customers use.
- Recognition and reward structure with limits, approvals and the wording that explains it.
- Capture and routing design in your CRM, with duplicate checks and referrer credit rules.
- A written response time for referred contacts, with the first outreach message drafted.
- Loop-closing sequence: acknowledgement, update and outcome messages with their timings.
- Governance note covering frequency caps, exclusions, consent wording and dispute handling.
- An anonymised extract of a completed eligibility list and ask script, shown in the first working session.
- A one-page programme runbook and a recorded walkthrough for staff who join later.
How it runs
The engagement, step by step.
- 1
Baseline and listening
We take your customer, enquiry and support exports and trace how recent customers arrived. We speak to a few customers who introduced someone and a few who never did, and to the team members expected to ask. The interviews are short and structured, and they usually explain more about why asking stalls than any report does.
- You provide:
- Customer and enquiry exports, support ticket history, and thirty minutes each from sales, service and delivery.
- We produce:
- The referral baseline, plus a written summary of what stops the ask today.
- Done when:
- You sign off the baseline numbers as the ones the programme will be measured against.
- 2
Eligibility and exclusions
We turn your own data into rules for who may be asked: tenure, value delivered, resolved service history, survey score where one exists, and account status. We test the rules against real accounts with your team present, then produce the first eligible list and the do-not-ask list side by side.
- You provide:
- Access to health, survey and ticket data, and a session with whoever knows the accounts well.
- We produce:
- Eligibility and exclusion rules, with the first ranked list of accounts that qualify.
- Done when:
- Your team agrees that every account on the list can be approached without hesitation.
- 3
Moments, words and reward
We map the post-sale journey and place the ask where value has just been felt. We write the wording for each moment and channel, then design what the referrer receives and check it against the policies your customers work under. Anything that a buyer's procurement rules would refuse is replaced before launch.
- You provide:
- Journey knowledge, examples of recent good outcomes, and a decision on what you are willing to offer.
- We produce:
- The moment map, the ask scripts, and the recognition and reward structure with its limits.
- Done when:
- You approve the words and the reward, and both are ready to be used unchanged.
- 4
Capture, credit and response path
We build the route an introduction travels through your systems: where it is entered, how duplicates against your existing pipeline are caught, how the referring customer is credited, who it reaches, and the response time attached to it. Where your CRM is simple, we build the same discipline into a shared list rather than forcing new software on you.
- You provide:
- CRM access or the shared sheet you use, and the name of the person who will own the response time.
- We produce:
- A working capture and routing setup, duplicate and credit rules, and the first outreach message.
- Done when:
- A test introduction travels the whole path and reaches an owner within the agreed time.
- 5
Enablement and pilot
We train the people who will ask and run a pilot with one team, segment or branch. They make real asks against the eligible list, we listen to what happens, and we adjust the wording, the moment and the reward on the evidence rather than on opinion. The pilot deliberately stays small enough to correct.
- You provide:
- A pilot team, their time for training and weekly reviews, and permission to approach the eligible accounts.
- We produce:
- A trained team, a revised script set, and a pilot report on asks made, responses and introductions.
- Done when:
- The pilot shows a repeatable ask that the team is comfortable making.
- 6
Rollout and loop closing
We extend the programme to the remaining teams and put the loop-closing sequence into service, so every referrer is acknowledged, updated and told the outcome. Governance rules go live at the same time: frequency caps, exclusions, consent wording and dispute handling.
- You provide:
- Owners named in each team, and agreement on the caps and approvals before the first wider ask.
- We produce:
- The rollout plan, the live loop-closing sequence, and the governance note in force.
- Done when:
- Every referrer in the pilot has received an outcome, and the wider teams have started asking.
- 7
Review and revision
Each month we read the programme scorecard with the owner: asks due against asks made, introductions received, response times kept, business closed, and loop-closing owed. Each quarter we revise eligibility, moments, wording and rewards, and retire whatever the evidence says is not working.
- You provide:
- The monthly review hour, and honest reporting of asks that were skipped and why.
- We produce:
- A monthly scorecard and a quarterly revision of the programme with reasons recorded.
- Done when:
- The programme runs on your team's own rhythm, with a written record of what changed and why.
Ways to work with us
You can begin with the count before you commit to a programme.
Referral readiness assessment
A short diagnostic: the baseline count, an eligibility test against your current accounts, and an honest view of whether your service experience can carry an ask yet. Useful when you want evidence before funding a programme.
Referral programme design
The full build: baseline, eligibility and exclusions, moment map, ask scripts, reward structure, capture and credit path, loop-closing sequence, governance and the runbook, handed over in working sessions with your team.
Design, pilot and embed
The design plus a period of running beside your team: training, a pilot with one group, weekly reviews, live coaching on real asks, and revisions to wording, moments and rewards as evidence arrives.
Quarterly programme review
For businesses already running a programme. Each quarter we read the scorecard against the baseline, listen to a sample of asks, and revise eligibility, moments, rewards and response times with the owner.
Why Gully Sales
What you are actually choosing when you choose us.
We ask only where the experience has earned it.
Eligibility comes out of your own service and account history, not from a mailing list. Accounts with open complaints, unpaid disputes or poor recent service are excluded on rules, so nobody has to make that judgement under pressure.
This is revenue work, not a campaign.
We come from sales and revenue operations as well as service. Referrals are tracked as a source, credited in your CRM, and judged on business closed, so the programme is defended in the same review as every other channel.
Rewards that your customers can accept.
Indian B2B buyers often work under procurement and gifting rules that make a personal incentive impossible. We design recognition and reward options around those rules first, so a thank-you never becomes something a customer has to refuse.
The referrer's experience is part of the design.
Most programmes stop at the ask. We write what the referrer hears afterwards, including what is said when the introduction leads nowhere, because that message decides whether a second introduction ever arrives.
Written down so it survives your team.
Eligibility rules, scripts, caps and the review agenda live in a runbook with a recorded walkthrough. When the account manager who was good at asking moves on, the programme does not leave with them.
Where it applies
The same service, in different businesses.
Industrial equipment and supply
- The situation:
- A supplier's customers meet each other constantly at trade bodies and exhibitions, yet introductions arrive only when a regional manager happens to think of it.
- How it applies:
- Eligibility built on repeat order history and clean service records, with the ask placed at commissioning and at the annual service visit, made by the service engineer's manager.
- Likely benefit:
- Introductions come from customers who have just seen the equipment working, which is when the recommendation carries most weight.
Healthcare clinics and specialist practices
- The situation:
- Patients recommend a doctor freely, but the front desk has no way to record who sent whom, and no way to thank the person who did.
- How it applies:
- A simple ask at the discharge or follow-up visit, consent taken before any contact detail is shared, and a recognition approach that stays within medical propriety.
- Likely benefit:
- The practice can see which patients bring others in and thank them properly, without pressure at a clinical moment.
Software and subscription businesses
- The situation:
- Support data shows a group of steady, satisfied users, but the only ask ever made is an in-product prompt that everybody dismisses.
- How it applies:
- Eligibility from usage and ticket history, an ask from the success owner after a milestone is reached, and referral credit recorded against the customer's own account.
- Likely benefit:
- Asks reach active users at the point of value instead of interrupting everyone at the same time.
Professional services and consultancies
- The situation:
- Partners get most of their work through introductions, but each one manages their own network privately and the firm cannot see or grow the channel.
- How it applies:
- A shared eligible-client list, an agreed ask at project handover and at review meetings, and central capture so credit and follow-up no longer depend on a single partner.
- Likely benefit:
- The firm's referral flow becomes visible and can be planned for, rather than resting on individual habits.
Education and training institutes
- The situation:
- Students and parents recommend the institute by word of mouth in a small community, but the admission team only asks during the enrolment rush.
- How it applies:
- The ask moved to results day and course completion, scripts written in the languages families speak, and recognition designed for a community setting rather than a cash incentive.
- Likely benefit:
- Recommendations are gathered when families feel proudest, not when the admission office is under pressure.
Interior design, architecture and project firms
- The situation:
- A finished home or office impresses everybody who visits it, but the firm's contact with the client ends at handover and the moment passes.
- How it applies:
- A handover ritual that includes the ask, photographs and a written note for the client to share, plus a follow-up at the three-month mark once the space has been lived in.
- Likely benefit:
- The firm stays present exactly when the client's friends and colleagues are asking who did the work.
Questions buyers ask
Before you enquire, the answers you will want.
What information do you need from us to start?
Exports of customers and enquiries for the last one to two years, support ticket history, any survey or NPS results, and access to your CRM or the sheet you use instead. We also need to know which accounts are sensitive. If the source of new enquiries was never recorded, we reconstruct what we can and note the gap rather than delaying the work until the data is perfect.
How much of our team's time does this take?
Expect thirty minutes each from sales, service and delivery for interviews, one session to test eligibility rules against real accounts, one session to approve wording and rewards, and a training session for the people who will ask. After launch it is a monthly review hour with the owner. The asking itself happens inside conversations your team is already having.
How long does the engagement take?
The baseline and eligibility work runs first, then moments, wording and reward design, then the capture path, then a pilot before wider rollout. We do not publish fixed timelines, because the pace depends on how usable your data is and how quickly customer interviews can be arranged. What is fixed at the start is the order of stages and the point where you can stop or continue.
How is success measured?
Against the baseline we sign off before starting. The programme is judged on asks made against asks due, introductions received, the share of new customers arriving through one, response time to a referred contact, and business closed. We also watch satisfaction, renewal and churn among the customers we asked, so we can see whether asking helped the relationship or strained it.
What is excluded from the scope?
We do not run paid affiliate networks, influencer campaigns or employee hiring referrals. We do not buy media for a consumer refer-a-friend campaign, and we do not sign commercial introducer agreements with people who are not your customers. We also do not act as your legal adviser on incentive rules; where a reward touches tax or procurement policy, we tell you to have it checked.
How is this different from referral marketing or a referral partner programme?
Referral marketing is a campaign channel with offers, creative and media behind it. A referral partner programme signs consultants and complementary suppliers on commercial terms. This page is about your existing customers: the ask is made by the person who serves them, at a moment their own success makes it natural, and it is governed to protect the relationship first.
Will asking annoy our customers?
It can, if you ask the wrong person at the wrong time. That is why eligibility rules and a do-not-ask list come before any script, and why frequency caps limit how often one customer is approached. Asked well, after a result they can point at, most customers treat it as a compliment. We also watch satisfaction among those asked, so any strain shows up quickly.
Should we pay customers for referrals?
Often you should not, and sometimes your customer's own policy forbids it. Many Indian corporate and institutional buyers cannot accept cash or personal gifts. We usually design recognition, service credit, added scope, training seats or a donation instead, and keep any value modest so the introduction stays a genuine recommendation rather than something that looks purchased.
4 more questions
We are B2B with only a few dozen customers. Is this worth it?
Usually yes, and often more than for a large base. With a small number of accounts, each introduction is significant and the ask can be made personally by someone the customer already trusts. The programme is lighter: a short eligible list, a handful of moments, and a discipline for responding fast and closing the loop every single time.
Do we need a CRM to run this?
A CRM helps, because credit, duplicate checks and response times are easier to keep there. But it is not a condition. Where a business runs on a shared sheet and WhatsApp, we build the same discipline into what exists and note what a CRM would add later. We would rather you run a simple programme properly than buy software you are not ready for.
Who should make the ask, sales or the service team?
Usually the person the customer trusts most, which is often the account, success or service owner rather than the salesperson who closed the deal. We name the owner for each moment during design. Sales still handles the referred enquiry, and the referral is credited to the account, so nobody feels an introduction was taken from them.
What happens when a referred lead is already in our pipeline?
The capture path checks every introduction against existing enquiries before anyone is contacted. If the name is already there, the rules decide what happens: who keeps the contact, whether the customer is still recognised for the intent, and what the referrer is told. Writing this down before launch prevents the internal argument that quietly kills most referral programmes.
Talk to us
Count the introductions you already receive by accident.
The assessment is a conversation, not a pitch. You will get an honest view of whether your customer experience is ready to carry an ask, and if it is not, we will say so and tell you what to fix first.
- No obligation and no sales script
- A reply from someone who does the work
- Your details are never sold or shared