IT services and networking companies · B2B customer reference programme
Let a prospect speak to a client whose network you run, with that client's consent.
A customer reference programme for an IT services or networking company is a register of clients who have agreed, in writing and separately for each activity, to take a call, be named or host a site visit. GullySales builds the register, the request wording and the matching rules, and your account owners make every ask.
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 IT services and networking companies
- PPC ads for IT services and networking companies
- Lead generation for IT services and networking companies
- Digital marketing for IT services and networking companies
- Reputation management for IT services and networking companies
- Local SEO for IT services and networking companies
- Branding and identity for IT services and networking companies
- Social media marketing for IT services and networking companies
- Email marketing for IT services and networking companies
Sales and marketing for IT services and networking companies, the overview.
Last updated 14 Nov 2026.
For IT services and networking companies
Where it usually goes wrong, and what we would do.
“Clients keep their network details private”
A reference in your trade means a client letting a stranger talk about its servers, firewall and Wi-Fi. Some clients have security policies or contract clauses that forbid naming them or describing their setup, and a school or a clinic may have its own reasons. The programme therefore asks about each activity separately: a private call, a name, a logo, a site visit. A client who declines one may accept another.
“A tender or vendor desk asks for references on a form”
Larger buyers send a vendor registration form, a tender document or a security questionnaire that asks for a list of comparable clients with contact names. Without a register, the owner scrolls old invoices the night before the deadline and rings someone who has not heard from the firm in a long time. A register kept ahead of time holds the clients who have agreed, the work you did for them and when the permission was last confirmed.
“The best reference may be your busiest client”
The client whose AMC you hold, whose office you rewired and whose server you restored after a fault is the strongest reference and also the one phoned again and again. A reference that is called for every quote soon becomes a reference that no longer picks up. The contact limit and the rest period after each request protect the relationship, and the account owner can refuse a request on the client's behalf.
“Buyers ask doubts, not general praise”
A prospect with an ageing server room wants to hear from someone who moved to a new setup and kept running. A school wants to hear from another school about the term-time cutover. A finance head wants to know whether the invoices matched the quote. Matching a buyer's doubt to a client who has lived that situation matters more than offering the biggest name. The guide pairs by trade, size, product and the question being asked.
What we do
What we deliver for IT services and networking companies.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Candidate review sheet
Each completed client is reviewed against the work delivered, open tickets, complaints, contract status and the account owner's view. Clients with an unresolved fault or a change of contact are held back with the reason written down. You approve the final list before any request is made.
Result: Every client on the list has an approver on your side.
Permission request and wording
A short request that asks separately about a private call with a prospect, being named, using a logo, a quotation and a site visit. The client can accept some and decline others, and the form says so plainly. The account owner sends it, in your name, after you approve the wording.
Result: A client can say yes to one activity and no to the rest.
Reference register
A shared record of the client, the work done, the person who gave permission, each activity allowed, the date given and the date to review it. Sales checks the register before asking anyone. A permission for a call is never read as permission for a logo or a visit.
Result: No one in sales asks for something the register does not allow.
Matching guide for buyer doubts
A method for pairing the prospect's concern with a client's experience, with a list of questions buyers in your trade ask: downtime during a migration, how a fault is escalated, whether the quote matched the bill. It does not script the client's answers, which stay the client's own.
Result: Each match names the buyer's doubt and the client chosen to answer it.
Briefing notes for both sides
A one-page note for the client on who is calling, what they will ask and how long the call is meant to be, and one for the prospect on what the client has agreed to share. Neither side is surprised by the other, and the client knows they can end the call.
Result: Both sides hold a written note before the call begins.
Contact limit, rest period and withdrawal log
An agreed ceiling on requests per client, a pause after each request, a complaint or a renewal, and a log of every client who declined or later stepped back. Withdrawal stops further requests and flags anything already in use, such as a logo on a proposal.
Result: A client who withdrew is not asked again for that activity.
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 IT services and networking companies.
- Managed IT service providers for small offices
- Structured cabling and LAN and Wi-Fi installers
- Network security and firewall specialists
- Server, storage and backup solution providers
- Microsoft 365 and Google Workspace partners
- IT hardware system integrators
- Data centre and server room fit-out companies
- IT firms serving schools, hospitals and factories
Before you decide
Agree the work. Know how to judge it.
B2B customer reference programme for IT services and networking 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 IT services and networking companies. Anything missing is noted in the written scope, with who will supply it.
- A list of completed clients
- Candidates come only from clients whose work is finished or whose service is running well. A simple list with the account owner's name, the work done and the contract status is enough. Without it there is nobody to ask, and a programme with an empty register is not worth starting.
- Engineers' view of each client
- Your engineers and account managers know things the ticket system does not: a dispute over a visit charge, a retiring contact, a sensitive project. They must say who should not be asked. Without this, a request lands on a client who is annoyed with you, and one careless ask can damage a good AMC.
- Contract clauses on confidentiality
- Share the clauses on naming, confidentiality and security in your client contracts, or mark where you do not know. Some clients simply cannot be named. Without the clauses, permission may be sought from a client who is not free to give it, which embarrasses both sides.
- Recent tenders and questionnaires
- Real forms that asked for references show what buyers want to see and the clients they expect. Share the last few, including the ones you lost. Without them, the matching rules are built on assumption instead of the questions prospects actually put to firms like yours.
- One person to approve the wording
- Requests go out in your firm's name, so a single person must approve the wording and own the replies. Without that person, requests wait, answers are inconsistent and a client is left with no reply to a yes or a no.
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
Naming the owner and the client pool
After your requirements brief and a first conversation, we agree who in your firm owns the programme, the managing director or the head of service delivery, and which clients are in view. Scope, fee and term go in writing. We start with completed projects and live AMC clients, not prospects.
- 2
Reviewing clients with account owners
We go through the client list with the engineers and managers who know each account. They tell us who has an open fault, who has a new IT head or who is in a sensitive sector. You approve each client proposed and hold back anyone you are unsure of. A thin list at the start is acceptable.
- 3
Checking contract clauses on naming
Some service contracts and tender conditions forbid naming the client or describing its systems. You share the relevant clauses or mark them unknown, and your adviser reviews anything that looks restrictive. A client with a clause against naming can still be asked for a private call if the clause allows it.
- 4
Asking permission one client at a time
The person who knows the client makes the request using the approved wording, by call or message. The answer goes into the register before sales may act on it. Silence is not consent, and a refusal is recorded without pressure. No reward is offered for agreeing.
- 5
Matching a live buyer to a client
When a prospect asks for a reference, sales supplies the opportunity and the buyer's doubt. We propose a match from the register, the account owner confirms it, the client accepts that specific call and both sides receive a briefing note. The request counts against the client's contact limit.
- 6
Recording, thanking and reading the outcome
After the call the outcome is logged, the account owner thanks the client and the rest period starts. Before the work began we noted whether reference requests slowed a quote or tender, and we compare the register against that record. You decide who to ask next, and who to leave alone.
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.
Why would a client agree to be a reference for an IT firm?
Can we name a client's network or hardware to a prospect?
Is this the same as writing case studies?
How many references should we line up?
What if a prospect asks for a reference we are not allowed to give?
Will a reference programme win us tenders?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
From the blog
Further reading for IT services and networking companies.
5 min read · 6 Oct 2026How buyers choose between IT, software and SaaS vendorsTechnology 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.
7 min read · 21 Sept 2026How to advertise to software engineersEngineers block ads, distrust copy and avoid sales calls. What reaches them is documentation, a free tier and someone they already read naming you.
8 min read · 21 Sept 2026How to advertise to small business ownersThere is no committee and no budget line. One person decides, after the shutter comes down, and has been sold a website and an SEO package before.
More for IT services and networking companies
Related work to consider.
- PPC ads for IT services and networking companies
- Lead generation for IT services and networking companies
- Digital marketing for IT services and networking companies
- Reputation management for IT services and networking companies
- Local SEO for IT services and networking companies
- Branding and identity for IT services and networking companies
Or start from the overview: sales and marketing for IT services and networking companies.
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.