B2B SaaS startups · B2B customer reference programme
When a prospect asks to speak to a customer, know who agreed and to what.
A customer reference programme for a B2B SaaS startup is a managed pool of paying customers who have agreed to take a call or to be named. GullySales asks for permission properly, records what each customer agreed to, matches a reference to a prospect by trade and need, and counts requests so nobody is over-used.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

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.
Also for B2B SaaS startups
- Account whitespace and contract expansion analysis for B2B SaaS startups
- Customer onboarding implementation assurance for B2B SaaS startups
- Lead generation for B2B SaaS startups
- SEO for B2B SaaS startups
- Social media marketing for B2B SaaS startups
- Content marketing for B2B SaaS startups
- Buyer persona for B2B SaaS startups
- CRM for B2B SaaS startups
Sales and marketing for B2B SaaS startups, the overview.
Last updated 14 Nov 2026.
For B2B SaaS startups
Where it usually goes wrong, and what we would do.
“Two or three friendly customers carry every call”
A young SaaS firm has a short customer list, and the founder knows which customers will pick up the phone. Those same customers take every request, from every salesperson, in the middle of their own working day. Goodwill wears thin, and a reluctant reference costs more than no reference. A register with a request count makes the wear visible.
“A yes to one thing becomes a yes to everything”
A customer agreed to a ten-minute call, and a month later their logo is on the pricing page. Nobody checked. In B2B software the customer's own legal or marketing team may object, and an unhappy customer is a worse outcome than a missing logo. Each permission, whether call, name, logo or quotation, needs its own record.
“The reference does not match the prospect”
A finance director at a mid-sized firm asks for a peer and is put through to a small team using the free plan. The call is polite and answers nothing about integration, security or support. Matching by trade, size, plan and the prospect's specific doubt matters more than choosing the happiest customer.
“A customer with an open problem gets asked for a favour”
Support has a ticket open on a failed import while sales requests a reference from the same account. The prospect hears about the failure on the call. A shared register that shows open complaints, renewals under discussion and unpaid invoices lets sales hold back the account before the request goes out.
What we do
What we deliver for B2B SaaS startups.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Candidate review sheet
Each customer is read against completed onboarding, how long they have been live, open tickets, renewal state and the account owner's view. The sheet shows why a customer is proposed and why another is held back.
Result: You can explain, for each customer, why they were or were not approached.
Permission request and wording
A short message asking separately about a private call with a prospect, being named, using a logo, a quotation and a site visit or screen share. The customer can accept some and decline others, and the message says plainly that no is fine and that nothing is offered in return.
Result: Each customer's reply maps to one permission you can point to.
Reference register
A shared list with the customer, trade, size, plan, integrations used, account owner, each permission, the date it was given and a review date. Sales checks it before asking anyone for anything.
Result: A salesperson can find out within the register whether a customer may be approached.
Prospect-to-reference matching guide
A method for pairing a prospect's concern with a customer's experience by trade, size, product area and the doubt the prospect has raised, with a list of questions buyers ask about software. It does not script the customer's answers.
Result: Each introduction records the match reason, so a poor match shows up in review.
Request limit and rest rules
An agreed ceiling on the number of times one customer can be asked, with a pause after a request, after a support issue and around a renewal. The account owner approves any exception and the exception is written down.
Result: No customer is asked beyond the limit you set without a written exception.
Refusal, withdrawal and outcome log
A record of every customer who declined or later withdrew, with the reason where given, and a note on each call: which opportunity, what the prospect asked and what followed. Withdrawal stops further requests for that permission and flags anything already published.
Result: A withdrawn permission is acted on in your materials and your sales notes.
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 B2B SaaS startups.
- Early-stage SaaS selling to Indian SMEs and mid-market firms
- Vertical SaaS for one trade, such as clinics, schools, dealers or builders
- Developer tools and APIs sold to engineering teams
- HR, payroll and compliance software for growing companies
- Finance and accounting tools sold through CA firms
- Indian-built SaaS selling to buyers in the US, UK or Middle East
- Spin-offs from services firms that turned an internal tool into a product
- Bootstrapped founders who have not raised and cannot hire a sales team yet
Before you decide
Agree the work. Know how to judge it.
B2B customer reference programme for B2B SaaS startups: 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 B2B SaaS startups. Anything missing is noted in the written scope, with who will supply it.
- Your customer list with plan details
- We need the customer names, trade, size, plan, go-live state and account owner. This is how we find candidates and match them to prospects. Where the list is only in a billing tool, an export with those columns is enough to begin.
- Support and renewal status per account
- A reference request must not land on an account with an open complaint or a renewal under discussion. We need a view of tickets and renewal dates, even as a short note from the account owner. Without it, we hold back every account we cannot check.
- A named person for each customer
- Someone on your side must be the voice the customer knows, such as the founder or the customer success lead. The request goes from that person. If nobody owns the relationship, the customer receives a message from a stranger and is less likely to agree.
- Past permissions already given
- Collect any email or message in which a customer agreed to be named, quoted or shown. We record what was actually said, not what was assumed. Where a permission cannot be found, it is treated as not given until the customer confirms again.
- A sense of what prospects ask
- Your sales team knows the questions buyers raise before signing: security, integration, support, data export. Share the last few that blocked a deal. They guide the matching guide and show which customers would answer them best.
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
Listing customers who have gone live
We start from your customer list and mark which accounts have completed onboarding and are using the product. A customer still being onboarded is not a reference yet. That shortens the list sharply, and that is the honest size of your pool.
- 2
Reviewing each account with its owner
For every candidate we sit with the founder or account owner and read the relationship: support history, the last conversation, the renewal, any dispute. The owner decides whether we ask. Where the owner hesitates, the account is held back without a reason being sent to anyone.
- 3
Writing the permission request
We draft the request in plain words and your account owner sends it from their own address, since the customer knows that person. The request separates call, name, logo and quotation and offers no reward, gift or discount. The customer's reply is recorded as written.
- 4
Building the register and the rules
Replies go into the register with the date and the sender. We then agree the contact limit, the rest period and who may approve an exception. Your sales team gets a short note on how to check the register before they ask for a reference.
- 5
Matching and briefing both sides
When a prospect asks, the account owner picks a reference using the matching guide and sends a short note to the customer saying who will call and what is to be discussed. The prospect gets a note on what the customer has agreed to share. Neither side meets a surprise.
- 6
Reading the record against the start
Before the work began we recorded how a reference request was handled: who was asked, how many requests went to which customer, how many agreements existed in writing. At the end we read the same record again and report what changed, including declines and withdrawals.
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.
Can we offer customers a discount for taking reference calls?
How many reference customers do we need?
Do you write the customer's testimonial?
What if a customer says yes and then changes their mind?
Should the prospect speak to the customer without us present?
Our customers are small firms. Does this still apply?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for B2B SaaS startups
Related work to consider.
Closest to this: customers after the sale
Also for B2B SaaS startups
Or start from the overview: sales and marketing for B2B SaaS startups.
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.