Rekindl · proof-story template

The shape of every Rekindl case study,
and the first one filled in.

Four sections. Ten fields. One attribution. Clone the example below, swap in real numbers once a contractor has thirty days of data, and publish — the layout doesn’t move. Every proof story on the site follows this exact shape so a sales call lands on numbers the reader can line up against their own CRM.

The template

Four sections, in this order.

Every published Rekindl case study carries these four sections in this order. The field names printed on each tile are the exact keys in the persisted row — copy them straight into a new entry.

Section A
Contractor + vertical

Who the contractor is and what trade they work. The hero lands on a real company name — not a case number.

Fields

  • contractorName
  • vertical
  • outcome
Section B
Before-state

Three numbers from the auditor window — what the pipeline looked like the day before Rekindl turned it on.

Fields

  • leadsPerMonth
  • averageCloseRatePct (0–100)
  • ignoredFollowupCount
Section C
30-day engagement

What we actually ran for them across month one. How many sequences, how many homeowners touched, how many jobs recovered.

Fields

  • sequencesRun
  • leadsTouched
  • recoveredJobs
Section D
Recovered revenue + pull-quote

The headline dollar figure, the contractor's own words, the named attribution. The number a sales call leads with.

Fields

  • recoveredDollarsUsd (integer USD)
  • pullquote
  • pullquoteAttribution

Filled-in examples

The first one is up.

Apex Roofing & Restoration is the pilot story on the site right now. Open it for the full narrative and pull-quote — and use the URL pattern as the slug for your next entry.

Next step

Want this page anchored to your own CRM?

One short form. We’ll come back within one business day with what’s recoverable, what month one would look like, and a flat monthly quote if there’s a fit.

Book a free lost-lead audit