Working · 2026-11PrimaryAcquisitionContent

Evergreen customer-story pipeline with quotas

A standing process that turns customer wins into case studies, blogs and videos at a fixed cadence, with selection rules tied to go-to-market priorities and a form for anyone to nominate a story.

Also called: case study pipeline

Claim and evidence

The claimWe strive to produce three customer stories per quarter and two marquee videos per year.

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
Set a storycadenceSelect bygo-to-marketgoalsAnyone cannominate astoryPublish toafilterablehubReuseacrosssales andinvestors
Set a story cadenceSelect by go-to-market goalsAnyone can nominate a storyPublish to a filterable hubReuse across sales and investors

Ad-hoc case studies come out late and skew to whoever shouts loudest. A pipeline with quotas and selection criteria produces stories where sales needs them (industry, use case, size) and keeps the library fresh.

How to run it

  1. Set a cadence target (e.g. stories per quarter, videos per year)
  2. Define selection criteria from GTM goals: segment, use case, account size
  3. Open a nomination form for sellers and CSMs
  4. Publish to a searchable hub sales can filter and pitch from
  5. Reuse stories internally and in investor or earnings material

Ways to run it

Design options to test, not promised results.

  1. Option AQuota-driven pipeline

    Commit to a fixed number of stories and videos per period, as GitLab's handbook sets out.

  2. Option BNomination form

    Let sellers and customer success managers submit candidate stories through one shared form.

  3. Option CFilterable story hub

    Publish stories to a hub sales can filter by industry, use case and account size.

Dated examples

  1. —

    GitLab

    Aims for three customer stories per quarter and two marquee videos per year, selected by GTM goals, account size and use case, with a submission form.

    “We strive to produce three customer stories per quarter and two marquee videos per year.”
    ✓ quote checked word-for-word on the page

    handbook.gitlab.com · undated

Does it still work?

Workingas of 2026-11

Current GitLab handbook. source

Risks

  • Approval cycles with customer legal can stall the pipeline
  • Stories without numbers persuade little

Sources

  1. handbook.gitlab.com · GitLab Handbook · undated
    “The Growth Community Programs team partners with Content, Brand, and Design to run a continual, evergreen pipeline of customer stories”
    ✓ quote checked word-for-word on the page

Change log

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