Skip to content
GullySales

Box cricket and turf venues · B2B customer reference programme

When a buyer asks to speak to a customer, you should know who agreed and what they agreed to.

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.

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

A turf venue manager checks a booking with two cricket players

Start with the buying decision

What does the customer need after the first commitment?

Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief.

Your team approves the scope and any commitments to buyers. GullySales does not assume authority over pricing, staffing, or delivery promises unless a specific responsibility is agreed in writing.

The context for Box cricket and turf venues

Start with the decisions in your own enquiry records.

Read the accepted scope and the subsequent service record. Separate adoption, complaints, repeat requirements, and renewal decisions before selecting a follow-up programme.

How people choose in this industry

Groups choose on availability, price and location. They search for box cricket or turf near me, check the slot they want, and book wherever answers first. Photographs of the turf, the lighting and the nets matter, and so do reviews about whether the booking was honoured. Lights, floor surface, parking, washrooms and drinking water decide whether a group comes back, so the page should show them honestly.

Regulars are the real business. A group that plays every Thursday is worth more than a dozen one-off bookings. Venues that keep a list of regulars and hold their slot keep them.

Corporates and communities fill the quiet hours. Offices book tournaments, societies run weekend leagues, and schools hire grounds on weekday mornings. Those bookings come from asking, not from waiting.

The decision before implementation

Resolve an outstanding delivery issue before asking for advocacy or another purchase. Respect contact preferences.

Existing industry priorities to review

  • Hourly turf bookings
  • Regular weekly slots
  • Corporate tournaments and leagues
  • Society and community events
  • Birthday and celebration bookings

These describe the industry's wider priorities. The written scope identifies which this service will address.

Industry application review

Test the service against a problem in your own records.

These review scenarios connect the industry context to a possible output and a checkable next step. They are scope questions, not client results or a promise that every industry problem belongs in this engagement.

Reviews mention the lights, the floor or the washroom and nobody replies

A group that loses a match to a dim corner writes it down. A written reply that says what the venue will fix, and does so, tells the next group that complaints are heard.

Output to assess: Contact limit and cool-off rules

Review whether “Contact limit and cool-off rules” addresses this specific issue. Confirm that connection from the example before including the work in the scope.

What to bring

Bring the accepted commitment and the later service or contact record, with permission to use the example for review.

Proposed completion check

Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

Birthday and celebration bookings are taken as favours

Parents and friends ask for the turf for a party. With no package, the owner prices each one on the spot and the work of cake tables, seating and clean-up is not counted.

Output to assess: Candidate review sheet

Review whether “Candidate review sheet” addresses this specific issue. Confirm that connection from the example before including the work in the scope.

What to bring

Bring the accepted commitment and the later service or contact record, with permission to use the example for review.

Proposed completion check

Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

The problem

What b2b customer reference programme is meant to address.

  • “The same three customers take every call”

    Nobody records who was asked or when. The friendliest accounts become tired, and a reference that sounds reluctant costs you the deal it was meant to win.

  • “We do not know what the customer agreed to”

    A yes to a phone call gets treated as a yes to a logo on the website. The agreement lives in one email or one memory, and a request goes out that the customer never accepted.

  • “The reference does not match the buyer”

    A large manufacturer is put through to a small shop because that is who answered. The conversation is polite and answers nothing the buyer needed to know.

  • “We call a customer who is unhappy with us”

    An open complaint or a late delivery sits in one department while sales asks for a favour from another. The buyer hears the problem on the call.

Who it is for

Check your operating model against the scope.

  • Software and technology firms whose enterprise buyers ask for a reference call before the contract
  • Equipment makers and contractors whose buyers want to see or hear from a customer with the same installation
  • Professional and consulting firms whose clients value discretion and need a clear record of consent
  • Owner-led businesses where one or two long-standing customers carry every reference request
  • Sales teams that lose days finding out whether a customer can be approached at all

Before you decide

When this may not be the right fit.

  • You have too few completed customers to offer a genuine reference. Deliver and earn the relationship first.
  • You want praise written for customers to sign, or customers rewarded for saying yes. This programme records voluntary agreement and accepts refusal.
  • You need published case studies or testimonials produced. That is a separate content service.

Choose the right scope

Start with the work your business needs.

  1. First reference register

    For a business where references live in one salesperson's phone. The starting scope is the candidate review, a permission form and a shared register, so the next request goes to someone who has agreed.

  2. Reference matching for live deals

    For a sales team already stuck behind buyer requests for a reference. The focus is the matching guide, the briefing notes and a written route from the buyer's concern to a willing customer.

  3. Repair after over-use

    For a business that has leaned on a few customers for years. We record what each has actually agreed to, set a contact limit, and widen the pool so the load is spread across more customers.

  4. Consent clean-up before a named use

    For a firm about to name customers in a tender or on its site. The permissions are checked one by one against what the customer wrote, and the gaps are listed before anything goes out.

What we do

Agree the outputs before work begins.

These are the b2b customer reference programme deliverables available for box cricket and turf venues. Your written scope identifies the included work and responsibilities.

  1. Candidate review sheet

    Each customer is reviewed against completed work, open complaints, contract status and the account owner's view. You can see why a customer is proposed and why another is held back.

  2. Permission form and wording

    A short request that asks separately about a private call, being named, a logo, a quotation and a visit. The customer can accept some and decline others, and the form says so plainly.

  3. Reference register

    A shared list showing the customer, industry, size, what was bought, the account owner, each permission, the date it was given and the date it can be reviewed. Sales checks it before asking anyone.

  4. Matching guide

    A method for pairing a buyer's concern with a customer's experience by industry, size, product and the doubt the buyer has. It lists the questions a buyer will ask, without scripting the customer's answers.

  5. Contact limit and cool-off rules

    An agreed ceiling on requests per customer, with a pause after a request, after a complaint and after a renewal. Account owners approve any exception and the exception is written down.

  6. Briefing notes for both sides

    A one-page note for the customer on who is calling and what is being discussed, and one for the buyer on what the customer has agreed to share. Neither side is surprised.

  7. Withdrawal and refusal log

    A record of every customer who declined or later stepped back, with the reason where given. Withdrawal stops further requests for that activity and flags anything already in use.

  8. Reference outcome log

    A note for each call: which opportunity, which customer, what the buyer asked and what happens next. Sales can see which references answered which doubts.

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
  • Reference calls linked to open opportunities
  • Opportunities that moved to the next stage after a call, without assuming the call caused it
  • Permissions due for review

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

Industry baseline

Keep the industry's wider measures beside the service measures.

Use the existing baseline to understand the context. These figures are not all targets for this engagement, and a change must not be attributed to the service without evidence.

  • Enquiries by source and slot
  • Utilisation by hour and day
  • One-off bookings that became regular
  • Corporate and society bookings
  • Double bookings and complaints
  • Reviews answered and issues fixed

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

Customer advocacy programmes
Choose customer advocacy programmes when you want willing customers to support sales in several ways, such as reviews and other approved participation. Choose the B2B customer reference programme when buyers ask to speak to a customer and you need a record of who agreed to take calls.
Customer case studies
Choose customer case studies when you need written accounts of a problem, the work done and an outcome the customer confirms. Choose the B2B customer reference programme when a prospect wants a live conversation with a similar customer, not a document, and permission must be tracked.
Customer testimonials
Choose customer testimonials when short approved quotes or videos would answer a buyer's doubt on a page. Choose the B2B customer reference programme when prospects want to speak with a customer directly and you need rules that stop one customer being asked again and again.

A sample of the output

A reference register records who agreed, to what, and when they rest.

This register is for a supplier of industrial goods. Each row is one customer, the use they agreed to, the kind of prospect they match, and the rule that protects them from being over-used.

Illustrative example, not client data. Yours is built from your own records.
CustomerWhat they agreed toMatches a prospect whoRest rule
Packaging manufacturerTake calls about the first stage of working togetherMakes similar goods and fears switchingRests after each call until the account owner clears them
Regional clinic groupBe named in proposals, no callsAsks for a named client in a formal bidNot contactable; name use only
Software resellerOne call at a time, arranged by email firstSells through partnersRests until the next request is approved
School trustWritten answers to questions onlyNeeds reassurance from the same sectorRests after each written reply
Logistics firmWithdrew after the first requestNoneRemoved from the pool; refusal logged

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

A list of completed customers
The pool can only come from customers whose work is finished and who were genuinely served. A simple list with the account owner's name is enough. Without it there are no candidates, and the programme has nobody to ask and cannot begin.
The account owner's view of each customer
Each relationship has history that records miss, such as a dispute, a change of contact or a sensitive project. Account owners must say who should not be asked. Without this, a request can damage a good relationship.
Contract clauses on confidentiality and naming
Some contracts forbid naming the customer or discussing the work. Share the relevant clauses or note where they are unknown. Without them, permission may be sought from customers who are not free to give it.
Live deals asking for references
Real prospect requests show what buyers want to hear and from which kind of customer. Share the deals where a reference was asked. Without them, matching rules are built on assumption, not on what prospects actually request.
One person who approves the wording
Permission requests go out in your name, so someone must approve the wording and own the replies. Without that person, requests wait, replies are inconsistent, and customers are left without an answer about whether their refusal or agreement was received.

Marketing and sales together

Your salesperson asks the register first, then the customer, and records what the buyer learned.

A reference request begins with an opportunity and a named buyer concern. Sales checks the register for an approved match and the account owner confirms availability. After the call, sales records the buyer's next step. A completed call is activity on the opportunity; a signed order is a separate outcome, and the programme does not treat the first as proof of the second.

Decisions to make before the work starts

  1. Customer records and relationship knowledge

    The review depends on delivery history, complaint records and account owners who know each customer. Where those are thin, more checking is needed and fewer customers will qualify at the start.

  2. Customer rules and confidentiality

    Customers decide what they will do, and some have policies that forbid references or naming. Confidential projects and regulated work need your own adviser's review. Agreement to one activity never extends to another.

  3. What stays outside this scope

    Writing case studies, filming customers, managing online reviews and changing your CRM are separate pieces of work. Contacting customers on your behalf is included only when the written scope says so.

How it works

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

    Agree the pool and the owner

    After your requirements brief and a first conversation, we agree who in your business owns the programme and which customers are in view. Scope, fee and term are set in writing.

  2. 2

    Review and approve candidates

    We go through the customer list with your account owners. You approve each proposed customer and hold back anyone with an open issue or an uncertain relationship.

  3. 3

    Ask permission, one customer at a time

    The person who knows the customer makes the request using the agreed wording. Each answer goes into the register before anyone in sales may act on it.

  4. 4

    Match and brief

    When a buyer asks, sales supplies the opportunity and the concern. We propose a match from the register, the account owner confirms it, the customer accepts that specific call, and both sides get a briefing note.

  5. 5

    Record, thank and rest the customer

    After the call the outcome is logged, the customer is thanked by the account owner, and the cool-off rule starts. The register is updated before another request is considered.

Approval and acceptance

Use an observable check before accepting an output.

These are proposed review checks for the named outputs. Agree the final conditions in the written scope, then record any missing requirement before accepting the handover.

  • Candidate review sheet

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Permission form and wording

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Reference register

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Matching guide

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Contact limit and cool-off rules

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Briefing notes for both sides

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Withdrawal and refusal log

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Reference outcome log

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

How is b2b customer reference programme scoped for box cricket and turf venues?
Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief. Resolve an outstanding delivery issue before asking for advocacy or another purchase. Respect contact preferences.
How is this different from customer advocacy programmes?
Advocacy is the wider activity: reviews, introductions, speaking and more. A reference programme is the narrower, managed pool built for reference calls and being named, with a register and matching. If you want both, say so in the brief and the scope will separate them.
Do we need a customer relationship management system?
No. A shared spreadsheet with the right columns and an owner works. If you already use a CRM, the register can be built there, but changes to the system are agreed separately.
Can we offer customers a gift or discount for taking calls?
We do not build the programme on payment for praise. A thank-you, an introduction or early sight of a product update is acceptable if the customer's own rules allow it. Check any gift with the customer's own compliance rules and with your adviser.
Will you contact our customers directly?
Only if the written scope says so. The default is that the person who owns the relationship makes the request, because a call from a stranger to a customer is a risk. We prepare the wording and the register.
What if a customer's company policy forbids references?
Some large buyers have such rules. The register records the refusal and the reason, and the customer is never approached for that activity again. Other proof, such as a finished and approved case study, belongs to a separate service.

Continue your review

Compare the service scope and the related work.

The scope, responsibilities, fee, reporting frequency, and term are agreed in writing after the requirements brief and conversation. Tell us what you need.

Your brief

Tell us what you need, and we will read it before we call.

Eight short steps about your business, what you want and who decides. Most questions are a tap, and you can skip any you would rather answer on the call.