Skip to content
GullySales

Steel traders · Customer advocacy programmes

A buyer wants to speak to a customer like them, and your best relationships should not carry every call.

Customer advocacy programmes organise willing customers who agree to support your sales through reference calls, reviews, or other approved participation. GullySales identifies suitable advocates, records their permissions, and plans requests with your account owners so a prospect hears from someone with relevant experience, without repeatedly approaching the same customers.

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

Steel mills: show a real physical business scene illustrating Enquiries, quotations and orders. Log each enquiry by grade, section and tonnage, quote from your own price list, and commit orders only to dispatch slots the mill can meet.

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 Steel traders

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

Fabricators, builders and factories ask for the rate, the mill or brand, the availability and the credit period. They check that the material comes with a mill test certificate where specified, and that the lorry weighs at delivery as the invoice says. A trader who gives a rate and then changes it after the call loses the account for the year.

Larger buyers such as PEB makers and engineering units issue an RFQ to several traders, then compare on landed cost and past delivery. They prefer a trader who can supply several sections in one consignment, so a broad stock list earns the invitation to quote.

The decision before implementation

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

Existing industry priorities to review

  • A rate sheet in a fixed format, sent to a list segmented by product
  • A product page for each form of steel you hold, with sizes, grades and the mills you buy from
  • An RFQ response routine with a named person for each marketplace enquiry and a standard quote format
  • A buyer record showing last order, usual sections, credit and delivery town
  • A weighment and delivery record for each lorry

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.

We quote by phone and lose track of who asked

The rate goes out, the buyer promises to confirm, and nobody calls back when the rate has moved.

Confirm the scope first

Check whether this issue belongs in the customer advocacy programmes engagement or requires different work. The industry problem alone does not establish that this service will solve it.

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

Record the scope decision and its reason. If the issue is outside this engagement, identify the responsible team or the separate work required.

Buyers shop the rate on four phones

Without a relationship beyond the rate, the order goes to whoever is lowest that morning.

Output to assess: Participation and sales outcome log

Review whether “Participation and sales outcome log” 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 customer advocacy programmes is meant to address.

  • “The buyer asks for a reference and we scramble”

    Sales knows who bought, but not who is willing to take a call. The request reaches an account owner without enough detail to choose a suitable customer.

  • “The same customers get every request”

    A few helpful people carry the load because their names are easy to remember. Previous requests are not recorded, so nobody notices when another approach is too soon.

  • “We assume one yes covers everything”

    Agreement to a private conversation gets treated as permission for a public quote or logo. Each use needs its own recorded agreement.

  • “We never hear what happened after the call”

    The advocate receives no thanks, and the salesperson leaves no outcome note. You cannot see which buyer concern the conversation addressed or whether the order progressed.

Who it is for

Check your operating model against the scope.

  • Manufacturers selling equipment where buyers request an existing customer reference before ordering
  • Professional firms with satisfied customers whose participation needs careful permission
  • Builders and interior firms matching prospects with customers from comparable projects
  • Dealers whose salespeople repeatedly approach the same friendly accounts
  • Owner-led firms with strong customer relationships but no shared record of agreed advocacy

Before you decide

When this may not be the right fit.

  • Your customers have unresolved complaints or too little completed work to describe a genuine experience. Address that before asking for advocacy.
  • You only need a finished testimonial or case study. Commission that specific content service instead.
  • You want paid positive reviews or scripted praise. This programme records voluntary participation and accepts a refusal.

Choose the right scope

Start with the work your business needs.

  1. First advocate register

    For an owner whose willing customers exist only in individual salespeople's contacts. Start with candidate selection and permission records so the team knows whom it can approach.

  2. Reference support for active deals

    For equipment or project sales held up by a buyer's request to speak to an existing customer. The focus is matching relevant experience, briefing both sides, and returning the conversation outcome to sales.

  3. Shared management of existing advocates

    For teams already requesting customer participation across sales and marketing. Bring those requests into one record so a case study interview and a reference call do not reach the same customer without coordination.

What we do

Agree the outputs before work begins.

These are the customer advocacy programmes deliverables available for steel traders. Your written scope identifies the included work and responsibilities.

  1. Advocate selection record

    An account review using completed work, repeat orders, and known complaints. You can check why each customer is proposed and which concerns must be resolved before an approach.

  2. Shared advocate register

    A working list with the contact, account owner, relevant experience, and participation status. Sales can check suitability without relying on one colleague's memory.

  3. Permission and refusal record

    Separate entries for private calls, quotes, name or logo use, and recorded video. Each entry shows what was agreed or declined, with a record of that answer.

  4. Customer approach plan

    Suggested requests, an agreed limit on repeat approaches, and an owner for each relationship. You can check who contacts the customer and who approves an exception.

  5. Reference matching guide

    A guide for matching the buyer's concern to a customer's experience, with a briefing format for both sides. It identifies relevant topics without telling the advocate what to say.

  6. Recognition and contact plan

    Non-payment ways to acknowledge participation, such as a personal thank-you or an appropriate introduction. Account owners can check that contact between requests remains part of normal customer care.

  7. Participation and sales outcome log

    A record linking each completed reference activity to the relevant opportunity, where known. You can trace the request, customer response, and sales follow-up without treating participation as proof of a won order.

How the result is measured

  • Advocates available by relevant experience and agreed activity
  • Requests accepted, declined, or unanswered, with reasons where known
  • Repeat requests against each customer's agreed contact limit
  • Reference activities linked to qualified sales opportunities
  • Opportunities progressing after a reference, without assuming the reference caused progress
  • Completed orders and order value linked to those opportunities, where records allow

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.

  • Rate calls and marketplace RFQs received, and orders won from them
  • Time taken for the first reply to an IndiaMART RFQ
  • Orders by buyer type and by product (TMT, angle, plate, pipe)
  • Loads where delivery weight differed from invoice weight
  • Overdue amounts by buyer and age of invoice
  • Buyers who ordered again within their own usual gap

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 testimonials
Choose customer testimonials when you need approved written or video quotes for a page or proposal. Choose customer advocacy programmes when prospects want to speak to a customer like them and the same few relationships should not be asked to carry every call.
Customer case studies
Choose customer case studies when you need a documented account that a buyer can read and share inside their own company. Choose customer advocacy programmes when a live conversation with a willing customer is what closes the doubt on an active deal.
Customer referral programmes
Choose customer referral programmes when existing customers should introduce new prospects, with rules for recording introductions and any reward. Choose customer advocacy programmes when prospects you already have need a customer to vouch for the work, with no reward attached.

A sample of the output

An advocate register records who agreed, for what, and when to ask again.

The register is the shared sheet account owners check before approaching a customer. Read across each row for the type of help agreed, the limits the customer set, and who owns the next request.

Illustrative example, not client data. Yours is built from your own records.
CustomerHelp agreedLimits setRequest owner
Pump dealer in the north regionReference call for similar dealersNo calls during stock-take; name shown only after approvalRegional account manager
Private clinic groupWritten review on a public siteNo patient detail; clinic council wording rules applyPractice manager and account lead
Software resellerCall and conference quoteCompetitors excluded from callsSales director
School transport operatorVisit to see the work in useVisits only with notice and a parent-safe agendaOperations lead
Wholesale food distributorReview onlyDeclined calls; asks to be left alone after a busy periodAccount manager

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.

Customer accounts and their owners
Advocates come from your existing relationships, so every customer needs a named owner who knows the history. A spreadsheet is enough. Without owners, nobody can say whether a request is welcome, and the programme stalls at the list.
A shortlist of likely advocates
You know which customers speak well of you. A rough shortlist lets the programme start with relationships that are healthy. If it is missing, candidates are picked by guesswork and an unhappy customer may be approached.
Customers who should not be contacted
Some customers are in a dispute, a renewal or a bad patch. Tell us who to leave out and why. Without this, a request could land at the worst moment and damage a relationship you are trying to protect.
Open deals that need a reference
A prospect waiting for a reference tells us which kind of advocate to find first. Names of the deals and the doubts raised are enough. Without them, the register fills in with no link to what sales needs.
A decision on what advocates receive
Willing customers should be thanked in a way you can afford and keep. Decide the form of recognition before asking. If it is undecided, early advocates get inconsistent treatment and later requests become harder.

Marketing and sales together

Your salesperson receives an approved reference match and records the next buyer decision.

The request starts with an opportunity record naming the buyer's unresolved concern. Sales receives the approved match, permitted topics, and arrangement details, then records whether the concern was answered and what happens next. A completed call is activity; an order remains a separate outcome.

Decisions to make before the work starts

  1. Account records and availability

    Selection depends on access to delivery history and account owners who know the relationship. Missing records or limited customer availability change how much preparation and coordination the programme needs.

  2. Permissions and compliance review

    Customers decide what they will share. Confidential projects and regulated professional work require your own compliance review before requests or disclosure; permission for one activity does not extend to another.

  3. Content production and system changes

    Writing customer stories, filming interviews, and publishing proof are separately scoped. CRM changes or automation are not assumed to be included; the programme's record format and maintenance responsibilities are agreed before work starts.

How it works

How customer advocacy programmes 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

    Candidate list approval

    We review account records with your account owners. You approve the proposed customers and hold back anyone with an unresolved issue or an unsuitable relationship.

  2. 2

    Customer permission

    The agreed contact asks what each customer is comfortable doing. Their answer enters the register before sales receives permission to approach them for that activity.

  3. 3

    Request ownership

    We agree who receives reference requests and who checks availability with the customer. Account owners approve contact limits and the circumstances that pause further requests.

  4. 4

    Reference handoff

    Sales provides the buyer's concern and opportunity details. The account owner approves a match, the customer accepts the specific request, and both sides receive a brief before the conversation.

  5. 5

    Outcome and relationship update

    After participation, the customer receives thanks and an appropriate update. Sales records the next decision, while the account owner updates availability 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.

  • Advocate selection record

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

  • Shared advocate 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.

  • Permission and refusal record

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

  • Customer approach plan

    Check that each proposed priority has a stated reason, a responsible person, and a next decision. Record any unsupported assumption before the owner approves the plan.

  • Reference 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.

  • Recognition and contact plan

    Check that each proposed priority has a stated reason, a responsible person, and a next decision. Record any unsupported assumption before the owner approves the plan.

  • Participation and sales 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 customer advocacy programmes scoped for steel traders?
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 a referral programme?
A referral programme asks customers to introduce potential buyers. Advocacy supports a buyer who may already be speaking to sales, for example through a reference call. A willing advocate does not have to bring you new enquiries.
Can we start with a small customer base?
Yes, if some customers have enough experience to speak honestly and want to participate. The starting scope should reflect that limited availability. Do not promise every prospect a reference when only one customer has agreed.
Who contacts customers and manages the programme?
The written scope assigns responsibilities between GullySales and your account owners. Your team provides the relationship context and approves suitable approaches. Requests should not bypass the person responsible for the account.
Does this include writing testimonials or managing Google reviews?
No. Testimonial production, case study writing, and online review generation and management are separate services. This programme records willingness and permission, then hands an approved request to the person responsible for that work.
What happens if a customer changes their mind?
Further requests stop for the activity they no longer accept. The account owner updates the permission record and alerts anyone preparing to use their participation. Any concern about material already published needs a separate review.

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.