Skip to content
GullySales

Salesforce and CRM implementation partners · Customer advocacy and proof marketing

Buyers hesitate over a few doubts, and the right customer proof answers those doubts directly.

Customer advocacy and proof marketing turns genuine customer experiences into approved stories and quotes that answer a prospective buyer's doubts. GullySales organises the customer requests, records permission, writes the material, and places it on relevant pages or in sales conversations, so your team has credible evidence ready when a buyer asks.

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

Colleagues reviewing a customer management system on a laptop

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 Salesforce and CRM implementation partners

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

Salesforce, HubSpot, Zoho and Microsoft all route buyers to partners through account executives, partner directories and AppExchange or marketplace listings. A buyer who has already spoken to the vendor arrives with two or three names, so the vendor account executive has to know what the firm has delivered, in which industry and at what size.

The next step is a reference check and a scope conversation. Sales heads ask for a client in the same industry or with a similar sales cycle, and an operations or IT head asks about integration with billing, ERP, WhatsApp, telephony or the website. The partner that scopes these early looks like a firm that has done it before.

The decision is split across the sales head, the CFO and the IT or digital head. The CFO reads the statement of work for licences, implementation fees and change requests. The sales head reads whether the project plan includes training and a review after go-live. The IT head reads the integration and data security terms.

The decision before implementation

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

Existing industry priorities to review

  • Sales teams moving off Excel and WhatsApp
  • Lead-to-cash flows with billing and ERP integration
  • Service and case management for support teams
  • Mid-market firms replacing an unused CRM
  • Marketing automation and lead scoring setup

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 sell clouds and modules while the buyer wants adoption

Our proposals list features and certifications, and the sales head scans past them to find out whether reps will really log in.

Output to assess: Searchable proof library

Review whether “Searchable proof library” 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.

We cannot publish the client's name or screens

Our best deployments are confidential or the client will not agree to be named, so the website shows generic dashboards.

Confirm the scope first

Check whether this issue belongs in the customer advocacy and proof marketing 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.

The problem

What customer advocacy and proof marketing is meant to address.

  • “Praise stuck in private messages”

    Your customer sends a detailed thank-you, but only the account manager sees it. Nobody records what may be shared or asks for approval to publish it.

  • “Nothing relevant for the next proposal”

    You have a general testimonial, but the prospect wants evidence about installation support. Your salesperson has to start asking around instead of sending an approved example.

  • “Stories without enough detail”

    A case study says the customer was happy but never explains the original problem or the work delivered. A buyer cannot judge whether the experience applies to their requirement.

  • “Proof in the wrong place”

    All your testimonials sit on a page that buyers rarely visit. The product page and quotation leave the buyer's actual concern unanswered.

Who it is for

Check your operating model against the scope.

  • Manufacturers and equipment suppliers whose buyers ask for evidence from a similar installation
  • B2B service firms with completed assignments but little approved material for proposals
  • Builders and interior firms with handover stories scattered across photographs and WhatsApp
  • Dealers whose prospects want evidence of installation or after-sales support
  • Professional firms with genuine customer feedback that needs careful approval before publication

Before you decide

When this may not be the right fit.

  • You have no completed work or customer experience that can support a credible story.
  • You want invented praise, unsupported results, or publication without the customer's approval.
  • You need customers managed over time for reference calls. That is separate customer advocacy programme work.

Choose the right scope

Start with the work your business needs.

  1. Existing material recovery

    For teams with useful praise scattered across inboxes and phones. The starting scope is to verify what exists, obtain the necessary approval, and turn suitable material into a usable library.

  2. Evidence for a specific offer

    For a product or service that attracts enquiries but lacks a relevant customer example. We identify the unanswered buyer question and develop an approved story for that page and its sales conversations.

  3. Proposal and quotation support

    For sales teams repeatedly asked for similar-work evidence. We organise approved material around common objections and prepare shareable pieces, so the person sending the quotation knows which evidence belongs with it.

What we do

Agree the outputs before work begins.

These are the customer advocacy and proof marketing deliverables available for salesforce and crm implementation partners. Your written scope identifies the included work and responsibilities.

  1. Existing evidence register

    A record of usable material from emails, reviews, and customer conversations. Each entry shows its source, approval status, and missing facts, so you can distinguish ready material from leads for an interview.

  2. Buyer doubt and evidence map

    A list matching customer experiences to questions about your offer, such as installation disruption or service support. You check it against questions your sales team actually receives.

  3. Customer request plan

    An agreed point in delivery for asking, with a named person responsible and clear request wording. Your team can see who approaches the customer and what participation involves.

  4. Permission record

    Written approval linked to each final piece, covering the agreed use of names, logos, photographs, and quotations. You can check which version was approved and where it may appear.

  5. Approved customer stories

    Quotes and written case studies based on customer interviews and supporting records. The customer checks the facts and final wording before publication; unconfirmed results stay out.

  6. Searchable proof library

    Finished pieces organised by customer type, offer, and buyer doubt. Each entry links to its approval record, so your salesperson can find relevant material without guessing whether it is usable.

  7. Sales pack and page placements

    Ready-to-share material for WhatsApp or email, with agreed placement on relevant website pages and links for proposals. You check the live location and the version your sales team receives.

How the result is measured

  • Approved pieces available, with permission records
  • Priority buyer doubts still missing supporting evidence
  • Relevant proof sent during active sales conversations
  • Clicks on customer stories, reported as engagement rather than sales
  • Qualified opportunities where customer proof was shared
  • Enquiry-to-order conversion against the baseline, without attributing every change to proof

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.

  • Opportunities by source and vendor
  • Shortlist appearances against proposals sent
  • Proposal win rate by platform and industry
  • References agreed in writing
  • Support and expansion revenue from live clients
  • Time founders spend on proposal assembly

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 case studies
Choose customer case studies when a considered purchase needs one full account of the problem, the work and the outcome the customer confirms. Choose customer advocacy and proof marketing when buyers raise different doubts and the team needs quotes, stories and a searchable library to answer each.
Customer testimonials
Choose customer testimonials when a page or a call only needs short approved quotes or videos. Choose customer advocacy and proof marketing when the quotes must also connect to a map of buyer doubts, a permission record and named places in proposals and pages.
User-generated content programmes
Choose user-generated content programmes when customers already post reviews and photos and you need consent to reuse them. Choose customer advocacy and proof marketing when the material is interviewed, written and approved by the customer before any buyer sees it.

A sample of the output

A buyer doubt and evidence map pairs each hesitation with the proof that answers it.

This map starts from what buyers say before they commit, then names the proof that answers it and where that proof sits. Read each row from the doubt across to the approval that must exist before use.

Illustrative example, not client data. Yours is built from your own records.
Buyer doubtProof that answers itWhere it is placedApproval needed
Will the supplier cope with our kind of order?Customer story from a similar orderService page and proposal packWritten sign-off from the customer
Do other buyers stay after the first order?Short quote about reorderingSales pack for follow-up callsCustomer approves exact wording
Is the handover difficult?Story describing the setup stageOnboarding pageCustomer and delivery lead both approve
Is the price fair for what we get?Customer account of the decision and what they weighedQuotation cover noteCustomer approves; no figures used without records
Can we trust the support afterwards?Quote on how a fault was handledSupport page and sales packCustomer approves wording and name use

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 customers you can approach
The programme starts from real customers, so it needs names, contacts and the person who owns each relationship. A rough list is fine. Without it, requests have no route in and the evidence stays at whatever you already hold.
Buyer doubts heard in sales calls
Proof is chosen to answer what buyers actually hesitate over. Notes from lost and won conversations are enough if they are honest. Without them, the work falls back on generic praise that does not move a decision.
Existing reviews, messages and quotes
Material you already hold saves a customer a request and shows which doubts are covered. Screenshots and saved messages are acceptable if the source is clear. Missing material means every piece is gathered fresh.
One person who approves wording
Each story and quote needs a named approver on your side who can say yes or no. Without that person, drafts wait with the customer and your team, and nothing reaches a page or a sales pack.
Permission to approach customers
Customers are asked only when your account owners agree. Tell us who must not be contacted and why. If this is unclear, requests risk reaching a customer in a dispute, and the whole record loses trust.

Marketing and sales together

Your salesperson receives approved evidence for the decision in front of them.

The handover identifies the buyer doubt each piece addresses, its approved sharing locations, and the source record. Your sales lead receives the library and ready-to-send material, then records which piece was shared against the enquiry or opportunity. A request for a live customer reference is a separate permission decision, not an automatic right granted by a published testimonial.

Decisions to make before the work starts

  1. Customer access and approvals

    Your team must provide suitable introductions and records supporting the story. Customer availability and internal approval routes affect delivery; unanswered requests do not become permission.

  2. Publication and compliance review

    Regulated firms must have their own adviser review proposed claims and publication choices. Website placement also depends on access to the relevant pages; a redesign or technical rebuild is separate work.

  3. Production depth and ongoing work

    Interview volume, document checks, and revision rounds affect scope. Detailed standalone case-study projects, video production, and ongoing customer reference programmes require their own written scope rather than being assumed here.

How it works

How customer advocacy and proof marketing 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

    Priority and access agreement

    You identify the offer and buyer decision that need better evidence. We agree the starting scope, available records, customer contact route, and person responsible for approvals.

  2. 2

    Evidence selection

    We review existing material and record a baseline before changes begin. Your sales lead helps select stories that answer real objections, rather than choosing only the most recognisable customer name.

  3. 3

    Customer invitation and interview

    Your team agrees the approach before the customer is contacted. We explain the proposed use, confirm who must approve it, and gather the details needed to write accurately.

  4. 4

    Draft and approval handoff

    Your delivery team checks the work described, and the customer reviews the final wording. Publication waits for written approval; revisions remain linked to the approved version.

  5. 5

    Placement and sales handover

    Approved pieces go into the agreed pages and sales pack. We review their use against the baseline, separating engagement with the material from qualified enquiries and completed orders.

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.

  • Existing evidence 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.

  • Buyer doubt and evidence map

    Walk the selected record through the proposed steps. Identify who acts at each handover, what information they receive, and how an exception is assigned without inventing a missing step.

  • Customer request 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.

  • Permission record

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

  • Approved customer stories

    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.

  • Searchable proof library

    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.

  • Sales pack and page placements

    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 and proof marketing scoped for salesforce and crm implementation partners?
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.
Can you work with the WhatsApp messages and reviews we already have?
Yes, they are useful starting material. We check the source and proposed use before turning them into published content. A saved screenshot is not treated as permission to publish someone's identity or words elsewhere.
What if our customer will not let us use their name?
We can consider an anonymous story if the customer approves the wording and the remaining detail is useful. It must not identify them indirectly against their wishes. Some stories are better kept unpublished.
Do we need numerical results for every case study?
No. A specific account of the requirement and completed work can answer a buyer's question without a percentage improvement. We use figures only when supporting records are available and the customer confirms them.
Does this include video testimonials or ongoing review management?
Video production is not assumed in the scope; any requirement and production cost must be agreed separately. Ongoing review requests and replies are covered by online review generation and management. This service coordinates approved evidence and its use across marketing and sales.
How much does this cost, and how long does it take?
The fee and term depend on the material needed and the approval work involved. Start with the requirements brief; GullySales reads it, speaks with you, and sends the scope, fee, and term in writing. Fees separate GullySales time, your media spend, and production costs, where applicable.

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.