Working · 2026-11PrimaryAcquisitionSales

Secure reference rights in the contract

Get the customer’s written permission to use its name, logo or story at signing, ideally inside the order form or licence agreement, rather than asking later.

Also called: logo rights clause, reference clause

Claim and evidence

The claimReferences should be secured in writing - ideally in the contract/order form, in the standalone customer license agreement, or via email.

GitLab · handbook.gitlab.com · undated

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
Customer signs theorder formReference rightsagreed at signingAsk for permissionlaterCheck the trackerbefore use
Customer signs the order formReferencerights agreedat signingAsk forpermissionlaterCheck the tracker before use

At signing the customer is most motivated and the legal team is already reviewing paper, so permission costs little. Written rights let marketing use the logo without a fresh approval chain for every asset.

How to run it

  1. Add an optional logo/name/reference clause to the standard order form
  2. Let the customer choose levels (logo only, quote, case study, call)
  3. Record the agreed level in the CRM or reference tracker
  4. Check the tracker before any public use

Before / after

Before
Order form
Plan
Term
Sign
Order form with no reference terms
After
Order form
Plan
Term
Logo on website
Customer quote
Reference call
Sign
Optional reference levels at signing

Generalised wireframe of the pattern, not a copy of any company's screen.

Ways to run it

Design options to test, not promised results.

  1. Option AClause in the order form

    Add an optional logo and reference clause to the standard order form, as GitLab's handbook advises.

  2. Option BTiered permissions

    Let the customer choose levels such as logo only, quote, case study or reference call.

  3. Option CTracker before use

    Record the agreed level in the CRM and check it before any public use of the name.

Dated examples

  1. —

    GitLab

    Handbook tells sellers to secure references in writing, ideally in the contract or order form, and to check trackers before using a name or logo.

    “References should be secured in writing - ideally in the contract/order form, in the standalone customer license agreement, or via email.”
    ✓ quote checked word-for-word on the page

    handbook.gitlab.com · undated

Does it still work?

Workingas of 2026-11

Current GitLab handbook guidance. source

Risks

  • Procurement may strike the clause or trade it for discount
  • Using a logo beyond the agreed level damages trust

Sources

  1. handbook.gitlab.com · GitLab Handbook · undated
    “References should be secured in writing - ideally in the contract/order form, in the standalone customer license agreement, or via email.”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (pass2-loops)