Revenue Leak Repair Manual

Revenue Leak Repair Manual™

Resource: RLR-00 · Role: START HERE · Kit: Revenue Leak Repair Kit™ Framework: ShiFt 6-Link Revenue Chain Framework™ Governing logic: Diagnose → Measure → Quantify → Prioritize → Repair → Verify

0. Read this first

The Revenue Leak Repair Kit is a guided implementation system, not a folder of downloads. This Manual is the operating system for the Kit: it tells you what to do, in what order, and how to know whether it worked.

Work the Kit in sequence. Every resource in the Kit exists to move you through one loop:

Diagnose → Measure → Quantify → Prioritize → Repair → Verify

There is one rule that governs everything below, and it is the rule most revenue programs break:

Installing a workflow is not proof that a leak is closed.

A leak is only closed when a re-measurement, taken after the repair, shows the

metric moved and held. Until then, a repair is *implemented*, not *verified*.

If you internalize nothing else, internalize that. The Kit is built to keep you honest about the difference between "we shipped something" and "the money came back."

1. Understand the Revenue Chain (Step A)

Every business runs a Revenue Chain: the ordered path a buyer travels from first demand to booked revenue and back into your decisions. ShiFt models it as six links. A leak in any link silently drains revenue you already paid to create.

The six links of the ShiFt 6-Link Revenue Chain Framework™:

1. Demand + Source — attract and correctly attribute qualified demand to its true source.
2. Speed-to-Lead — acknowledge and make first two-way contact within the response standard.
3. Qualification — determine fit, intent, urgency, and routing without falsely disqualifying good buyers.
4. Follow-Up — persist through event-aware sequences until a clear stop condition.
5. Booking + Handoff — convert readiness into a confirmed appointment and an acknowledged handoff.
6. Attribution + Decision Intelligence — reconcile source-to-revenue outcomes and feed them back to Link 1.

The chain is a loop, not a line. Link 6 feeds measured outcomes back into Link 1 so that demand spend follows evidence instead of guesswork. The full definition of each link, what leaks there, and how to read it lives in the 6-Link Revenue Chain Framework™ (RLR-01), which you should read alongside this Manual.

Why chain order matters: a repair upstream changes the inputs to every link below it. Fixing Speed-to-Lead (Link 2) increases the volume reaching Qualification (Link 3). If you repair out of order, you can mistake a downstream overload for a downstream defect. Always diagnose the whole chain before you repair any single link.

2. Run the Revenue Leak Diagnostic (Step B)

The Revenue Leak Diagnostic™ (RLR-02) is your first pass. It is a fast, structured self-assessment that scores how reliably each link is doing its job and surfaces your single biggest leak.

What it does today: the current Diagnostic asks 15 weighted questions and returns an overall system score (0–100%) plus a per-area breakdown across five operating areas — Speed-to-Lead, Qualification, Follow-Up, Booking + Handoff, and Attribution — and names your top leak area.

Overall score bands:

Honest scope note (do not skip): the Diagnostic in its current form assesses Links 2–6. Link 1 (Demand + Source) is not yet a scored area inside the Diagnostic. Until that integration lands, establish your Demand + Source baseline using the Revenue Chain Baseline Scorecard™ (RLR-03) together with the Link 1 audit (Lead Source Quality Audit, RLR-07, delivered with the Demand + Source Playbook). Treat the Diagnostic as a screen, not the whole measurement.

The Diagnostic is an *indicator*. It tells you where to look. It does not, by itself, establish your true operating baseline — that is Step C.

3. Establish the actual baseline (Step C)

A score is not a baseline. A baseline is the set of real, observed numbers your business produces right now, before any repair. You cannot prove recovery later without a truthful baseline captured first.

Use the Revenue Chain Baseline Scorecard™ (RLR-03) to record, per link, the current-state metric, how you measured it, the measurement window, and your confidence in the number. The Scorecard forces a data-source and a confidence level on every entry, because an unmeasured link cannot be quantified or prioritized — it can only be flagged for a measurement plan.

Where a link has no reliable instrumentation yet, mark it Unknown. Unknown is a valid, honest state. It is never the same as "fine," and it is never treated as a disqualified leak. An Unknown link routes to a measurement plan before it can carry any financial claim.

Pair the Scorecard with the Lead Journey Mystery-Shop Audit (RLR-04) when you need first-hand evidence of what a real buyer experiences through Links 2 and 5.

4. Use the Revenue Leak Calculator (Step D)

The Revenue Leak Calculator™ (RLR-05) converts your baseline into a per-link economic model. It is the quantification engine of the Kit.

What it models: the Calculator (algorithm v3.0.0) takes your funnel inputs — monthly leads, ad spend, baseline appointments, appointment capacity, average deal value, close rate, bookable-lead ceiling, gross margin, and monthly ShiFt cost — and models appointment and revenue lift across all six zones, which map one-to-one to the six links: Demand + Source, Speed-to-Lead, Qualification, Follow-Up, Booking + Handoff, and Attribution + Decisions.

It runs against scenarios so you never present a single fragile number:

Data-integrity rule: the Calculator's industry defaults are editable planning assumptions, not verified or audited industry data. When you present numbers, either use your own baseline inputs from Step C or clearly label the defaults as planning assumptions. Never present a planning default as a measured result or an industry benchmark. Fabricated benchmarks and unverified performance claims are prohibited throughout the Kit.

5. Quantify economic impact (Step E)

Quantification means attaching a defensible dollar range to each leak, sourced from your baseline (Step C) run through the Calculator (Step D).

Rules for a defensible quantification:

• Range, not a point. Always carry Conservative / Expected / Upside together.
• Traceable to a baseline. Every dollar figure must trace back to a Scorecard

entry with a stated data source and confidence.

• No quantification without evidence. If the underlying link is Unknown, you

do not produce a dollar figure — you produce a measurement plan. "Evidence too weak to quantify" is a legitimate output and blocks any financial priority claim until resolved.

• Margin-aware. Recovered revenue is only meaningful net of the gross margin

and the cost to capture it. Model recovered *contribution*, not vanity top-line.

6. Prioritize leaks (Step F)

You do not fix everything at once. You fix what returns the most recoverable contribution for the least risk and effort, given the strength of your evidence.

Use the Revenue Leak Priority Matrix™ (RLR-06). It ranks each identified leak into one of four dispositions:

• Fix Now — high financial impact, sufficient evidence confidence, tractable effort.
• Fix Next — material impact, but gated behind a dependency, effort, or sequencing constraint.
• Monitor — low current impact or low severity; watch the metric.
• Insufficient Evidence — impact cannot be responsibly claimed yet; route to a measurement plan first.

The Matrix weighs six factors: financial impact, evidence confidence, operational severity, dependencies, effort, and risk. Do not substitute a new opaque scoring formula — use the approved method so priorities stay explainable to the buyer. A leak with weak evidence never outranks a well-evidenced one on impact alone; it routes to measurement.

Respect chain order when sequencing: when two leaks tie, repair the upstream link first, because its output feeds the downstream link.

7. Select the appropriate Revenue Chain Repair Playbook (Step G)

Each link has a dedicated Revenue Chain Repair Playbook. Your Priority Matrix tells you which link to enter; the finding-to-repair map tells you which specific resources inside that Playbook address your finding.

The master structure and navigation for all six Playbooks is defined in the Kit's playbook structure (see playbooks-structure.json). Each Playbook opens with its own audit so you confirm the leak is real before you install anything.

7.1 Link 1 — Demand + Source (worked path)

Link 1 is the first fully authored Repair Playbook. When your leak is in Demand + Source — untracked or misattributed sources, or doubts about source quality — work these three resources in order:

1. Lead Source Quality Audit™ (RLR-07) — evaluate every source through the

full downstream chain (Volume → Qualification → Booking → Show → Close → Revenue → Gross Profit), not by cost-per-lead.

1. Lead Source Scorecard & Budget Decision Matrix™ (RLR-08) — convert the

Audit into a management action: Scale / Maintain / Repair / Reduce / Stop / Insufficient Evidence.

1. UTM & Lead Source Tracking Standard™ (RLR-09) — repair attribution and

tracking wherever confidence is weak, so the numbers above can be trusted.

The Link 1 procedure:

1. Audit source quality with RLR-07 — read each source through the chain.
2. Determine whether the problem is traffic quality or downstream leakage. A

source that sends good-fit leads into a broken downstream link is a *conversion* problem, not a source problem.

1. Calculate the economic impact using your baseline (Step C) and the

Calculator (Step D) — CAC, revenue and gross profit per lead.

1. Decide Scale / Maintain / Repair / Reduce / Stop with RLR-08. Never reach

Stop on cost-per-lead, low volume, one weak metric, or small sample alone.

1. Repair attribution and tracking with RLR-09 wherever attribution

confidence is weak — fix tracking *before* trusting a cut/scale decision.

1. Re-measure before reallocating substantial budget where evidence is

insufficient. Insufficient Evidence routes to measurement, not to Stop.

Diagnostic coverage note (Link 1): the Revenue Leak Diagnostic (RLR-02)

does not yet score Demand + Source. Do not treat the Diagnostic as validated

coverage of all six links. Until that reconciliation lands (a scheduled later

phase), your Link 1 diagnostic depth comes from the **Lead Source Quality

Audit™ (RLR-07) and the Baseline Scorecard™** (RLR-03), not from the

Diagnostic.

7.2 Link 2 — Speed-to-Lead (worked path)

Link 2 is the second fully authored Repair Playbook. Enter it when your leak is slow or missing first contact — leads acknowledged but not worked, after-hours abandonment, or missed calls with no recovery. Work the six resources as one diagnosis-and-repair system, in this order:

1. Speed-to-Lead Audit™ (RLR-10) — measure how fast and how consistently new

inquiries reach *meaningful* first contact (a real two-way conversation, not an auto-reply), segmented by source, channel, responder, business-hours vs after-hours, and weekday vs weekend.

1. First-Response SLA™ (RLR-11) — set the explicit standard: target

acknowledgement, first-attempt, and meaningful-response times per inquiry class, with an owner, backup, escalation owner, and failure path.

1. Instant First-Response Script Pack™ (RLR-12) — deploy human, direct

first-response language across SMS, call, voicemail, email, web-chat, missed-form fallback, after-hours acknowledgement, and reconnect.

1. Missed-Call Recovery Playbook™ (RLR-13) — install detection, immediate

text-back, callback cadence, disposition, and stop rules so unanswered inbound calls are recovered.

1. After-Hours Revenue Recovery SOP™ (RLR-14) — choose the coverage model

(none / limited / AI-supported / 24-7) and define acknowledgement, routing, and next-business-day handoff.

1. Response Escalation Matrix™ (RLR-15) — make response failure visible and

assign a fallback owner before a lead is lost.

The Link 2 procedure:

1. Measure current response with RLR-10 — build the contact ladder per

inquiry from real timestamps; do not count an auto-acknowledgement as contact.

1. Find where delays happen — segment by hours/day/source/channel/responder

and tag the leak patterns (slow response, never attempted, after-hours abandonment, missed-call loss, channel/employee inconsistency, no fallback).

1. Set the standard with RLR-11 — define target times and owners per inquiry

class. Where no ShiFt-approved benchmark exists, set a deliberate operator target from RLR-10's measured distribution; never fabricate a benchmark.

1. Say the right thing with RLR-12, recover missed calls with RLR-13, and

cover after-hours with RLR-14 — install the smallest change that closes the audited defect.

1. Assign the fallback with RLR-15 so SLA breaches, automation failures, and

uncontacted high-intent leads escalate to a named owner and get logged.

1. QA and re-measure — pass the workflow QA, then re-run RLR-10 at 14 and 30

days. A Link 2 leak is only repaired when re-measured response time, SLA compliance, unworked leads, missed-call recovery, after-hours coverage, and contact rate show the gap improved — not because scripts or automations were installed.

Existing-asset note (Link 2): ShiFt's public Missed-Call Recovery and

After-Hours Lead Response resource pages remain the outward-facing

explainers. RLR-13 and RLR-14 are the canonical *operational* instruments they

point to — there is no competing customer-facing name for the same workflow.

Diagnostic coverage note (Link 2): unlike Link 1, the Revenue Leak

Diagnostic (RLR-02) *does* score Speed-to-Lead. Its output is still a starting

signal — your operational depth for this link comes from the **Speed-to-Lead

Audit™** (RLR-10), which measures real response timestamps the Diagnostic does

not collect.

7.3 Link 3 — Qualification (worked path)

Link 3 is the third fully authored Repair Playbook. Enter it when your leak is inconsistent qualification — leads worked differently by different people, missing fit/intent/urgency evidence, good buyers marked "not a fit," or qualified opportunities left as unassigned, ambiguous CRM records. Qualification here is not data collection; it is consistently deciding fit, need, intent, urgency, value, next action, owner, and disposition. Two distinctions govern the whole link: source quality is not qualification quality, and a low-fit lead is not a poorly qualified lead — never let an inconsistent intake process make a valuable lead look unqualified. Work the six resources as one system, in this order:

1. Qualification Gap Audit™ (RLR-16) — measure whether you consistently

gather the evidence to judge fit, intent, urgency, value, and next action, segmented by responder, source, and channel; count how often leads are classified without sufficient evidence.

1. Qualification Framework & Checklist™ (RLR-17) — install the repeatable

structure: the categories (need, fit, intent, urgency, value, decision readiness, routing) and a configurable checklist that separates required from conditional questions so nothing is asked reflexively.

1. Lead Scoring Rubric™ (RLR-18) — classify every lead consistently as HIGH

INTENT, QUALIFIED, NURTURE, DISQUALIFIED, ESCALATE, or INSUFFICIENT INFORMATION from multi-factor evidence, never one variable, with a transparent score-to-classification mapping.

1. Qualification Conversation Scripts™ (RLR-19) — gather the evidence

conversationally across phone, SMS, and chat without interrogating, and close non-fit leads with dignity.

1. Lead Routing Matrix™ (RLR-20) — route every qualified opportunity to a

named owner and next action, with backup owner, escalation, and handling for no-owner, unavailable-owner, conflict, after-hours, and system-failure cases.

1. Lead Disposition Standard™ (RLR-21) — put every lead in exactly one known

state with a disposition, so no lead is ambiguous and NOT A FIT is never a catch-all for could-not-reach, incomplete qualification, or wrong timing.

The Link 3 procedure:

1. Measure current qualification with RLR-16 — from real records, not

assumptions; count unknowns explicitly and never convert an unknown into a disqualification.

1. Standardize what you ask with RLR-17 — establish the required categories

for every lead and make conditional questions trigger only when relevant.

1. Classify consistently with RLR-18 — separate DISQUALIFIED (evidence of

non-fit) from INSUFFICIENT INFORMATION (a process gap you must recover first).

1. Say it well with RLR-19 — gather evidence without turning the

conversation into a questionnaire, and preserve dignity on non-fit closes.

1. Assign the opportunity with RLR-20 so every qualified lead ends with an

owner and a next action — never an unassigned record — and categorize it with RLR-21 so reporting is trustworthy.

1. QA and re-measure — pass the workflow QA, then re-run RLR-16 at 14 and 30

days. A Link 3 leak is only repaired when re-measured qualification completeness, consistency across responders, qualified rate, ambiguous disposition rate, routing accuracy, qualified-with-next-action, and qualification-to-booking show the gap improved — not because a checklist or rubric was installed.

Existing-asset note (Link 3): ShiFt's public lead-routing / territory

resource page and the lead-scoring-vs-AI-qualification explainer remain the

outward-facing explainers, and the prior Lead Qualification Checklist and

intake scripts are reused and improved inside RLR-16 through RLR-21. RLR-17,

RLR-18, and RLR-20 are the canonical *operational* instruments those pages

point to — there is no competing customer-facing name for the same workflow.

Diagnostic coverage note (Link 3): the Revenue Leak Diagnostic (RLR-02)

only signals whether qualification may be inconsistent; it does not measure

qualification completeness. Your operational depth for this link comes from

the Qualification Gap Audit™ (RLR-16), which inspects real lead records.

Downstream handoff (Link 3): qualified output must carry classification,

intent, urgency, routing destination, disposition, next action, owner,

follow-up treatment, and relevant context so Link 4 (Follow-Up) and Link 5

(Booking + Handoff) can act without re-qualifying. Those links are authored in

later phases; Link 3 only prepares the clean handoff.

7.4 Link 4 — Follow-Up (worked path)

Link 4 is the fourth fully authored Repair Playbook. Enter it when your leak is eligible leads abandoned — opportunities lost not because the buyer said no, but because follow-up was one-and-done, single-channel, too slow between attempts, missing a next action, stopped without a reason, or wrongly marked lost. The governing principle of the whole link is that silence is not a disqualification event. Link 4 keeps four states apart that businesses routinely collapse: NO RESPONSE (no reply yet) is not NOT INTERESTED (an explicit signal); NOT READY YET (a timing state that belongs in nurture) is not NOT A FIT (an evidence-based judgment); and UNREACHABLE AFTER REQUIRED ATTEMPTS is a valid stop only once the defined coverage was actually delivered. Work the five resources as one system, in this order:

1. Follow-Up Coverage Audit™ (RLR-22) — measure whether leads actually

receive sufficient, timely, multi-channel follow-up from real records: attempts per lead, channel mix, gaps, scheduled next actions, stop reasons, and abandoned-after-first-attempt rate, segmented by classification, owner, source, and channel. Where no approved benchmark exists, the operator configures the required coverage and this audit measures against it.

1. Persistent Follow-Up Sequence™ (RLR-23) — install the configurable,

multi-channel active sequence for valid opportunities that have not yet had a conversation. It absorbs and improves the prior 5-touch / 72-hour asset, evolves each touch with a distinct objective (no "just checking in" filler), and ends every touch in a next action, stop condition, and disposition.

1. No-Response Recovery Sequence™ (RLR-24) — re-engage prospects who

previously engaged and went quiet, using real prior context rather than pretending no conversation occurred, and escalating renewed high intent to a human instead of exhausting automation.

1. Long-Term Nurture Sequence™ (RLR-25) — preserve NOT READY YET future

opportunities with category-appropriate, non-spam touches, and define exactly how a nurtured lead returns to active treatment when new intent appears.

1. Follow-Up Stop & Escalation Rules™ (RLR-26) — decide when follow-up should

CONTINUE, CHANGE CADENCE, ESCALATE, ENTER NURTURE, STOP, DISQUALIFY, or RETURN TO ACTIVE, preventing both stopping too soon and following up forever, and keeping STOP FOLLOW-UP distinct from DISQUALIFY LEAD.

The Link 4 procedure:

1. Measure current coverage with RLR-22 — from real records; count unknowns

explicitly and never convert an unknown stop reason into "not interested."

1. Install active persistence with RLR-23 for opportunities not yet in a

conversation, configured per classification, intent, and urgency.

1. Recover the quiet-but-engaged with RLR-24 wherever prior engagement

exists, using the prior context and escalating high intent to a human.

1. Preserve future value with RLR-25 — move NOT READY YET opportunities into

nurture with a reason, owner, review date, and exit condition; never nurture a NOT A FIT lead and never disqualify a timing delay.

1. Govern stops and escalations with RLR-26 so every attempt is

dispositioned, opt-outs are honored, and no lead is abandoned before its own completion criteria or followed indefinitely without purpose.

1. QA and re-measure — pass the workflow QA, confirm dispositions and

suppression work, then re-run RLR-22 at 14 and 30 days. A Link 4 leak is only repaired when re-measured attempts-per-lead, multi-channel coverage, next-action completion, response and appointment-from-follow-up rates, unresolved volume, abandoned-after-first-attempt rate, and nurture conversion (where data exists) show the gap improved — not because sequences were installed.

Existing-asset note (Link 4): RLR-23 is the canonical *operational*

follow-up sequence and absorbs and materially improves ShiFt's prior narrow

5-touch / 72-hour follow-up asset; there is no competing customer-facing

sequence with a separate name. The public /follow-up page and the automated

lead follow-up explainer remain the outward-facing surfaces and point to these

instruments — they are not modified.

Diagnostic coverage note (Link 4): the Revenue Leak Diagnostic (RLR-02)

does score Follow-Up, but only as a starting signal. Your operational depth for

this link comes from the Follow-Up Coverage Audit™ (RLR-22), which inspects

real attempt-level lead records the Diagnostic does not collect.

Upstream handoff (Link 3 → Link 4): Link 4 consumes the Link 3 outputs —

classification, intent, urgency, routing destination, disposition, next action,

owner, follow-up treatment, and prospect context — and does not recreate

qualification logic. It measures and repairs whether that qualified output

actually received the follow-up it was routed for.

Downstream handoff (Link 4 → Link 5): Follow-Up produces clean output for

Booking + Handoff — prospect readiness, booking intent, appointment

opportunity, preferred timing if known, qualification summary, previous

follow-up context, owner, and recommended next action. Link 5 is authored in a

later phase; Link 4 only prepares the clean handoff.

Compliance guardrail (Link 4): every Follow-Up resource respects known

opt-out signals, channel permissions, business-implemented suppression, explicit

do-not-contact requests, and approved communication policy. None of them invent

legal requirements or bypass provider restrictions, opt-outs, or consent

controls; jurisdiction- and industry-specific rules are applied by the operator.

7.5 Link 5 — Booking + Handoff (worked path)

Link 5 is the fifth fully authored Repair Playbook. Enter it when your leak is booking or handoff friction — qualified, interested prospects who never get a confirmed appointment, book but are never confirmed or reminded, miss the appointment with no recovery, or arrive at the next person with no context and no clear owner. The governing principle of the whole link is that qualified is not booked: Link 5 keeps seven states apart that businesses routinely collapse — QUALIFIED, APPOINTMENT READY, APPOINTMENT BOOKED, APPOINTMENT CONFIRMED, SHOWED, NO-SHOW, and RESCHEDULED — and never treats a no-show as a lost or uninterested prospect. Work the six resources as one system, in this order:

1. Booking Friction Audit™ (RLR-27) — measure, from real records, where

appointment-ready prospects lose momentum: qualified-to-booked and ready-to-booked rates, time-to-book, earliest-availability delay, booking abandonment and steps, confirmation and reminder coverage, show / no-show / cancel / reschedule rates, and handoff completeness, segmented by source, owner, channel, and appointment type. Where no approved benchmark exists, the operator configures the required standard and this audit measures against it.

1. Appointment Booking Script Pack™ (RLR-28) — give humans and automations

low-friction language that moves a ready prospect into a specific scheduled time, favoring a concrete two-option offer over vague invitations while still preferring self-scheduling wherever that is operationally better.

1. Appointment Confirmation & Reminder Sequence™ (RLR-29) — install the

configurable confirmation, calendar invite, and reminder touches that convert a booking into an attended appointment. It absorbs and improves the prior two-message Appointment Confirmation Script, prevents duplicate/contradictory reminders across systems, and ships a reminder QA checklist.

1. No-Show Rescue Playbook™ (RLR-30) — the moment an outcome becomes

NO-SHOW, run a respectful, non-punitive recovery sequence that assumes scheduling friction before disinterest, escalates high-intent misses to a human, and moves unrecovered-but-valid prospects to nurture rather than closure.

1. Sales-Ready Handoff Template™ (RLR-31) — hand the appointment owner

complete source, need, qualification, conversation, appointment, follow-up, and next-action context (structured fields plus a concise summary) so the prospect never has to repeat themselves, capturing only necessary data.

1. Handoff SLA & Ownership Matrix™ (RLR-32) — make ownership explicit across

every state from BEFORE BOOKING to NEXT ACTION DUE, with a primary owner, backup, required action, SLA, escalation path, required disposition, next action, and logging requirement, so the question "who owns the prospect right now?" always has an answer.

The Link 5 procedure:

1. Measure current booking/show/handoff coverage with RLR-27 — from real

records; count unknowns explicitly and never relabel a friction leak as a bad-lead problem.

1. Reduce booking friction with RLR-28 — standardize concrete-offer language

and the self-service path per channel and segment.

1. Confirm and remind with RLR-29 — enable the touches that fit each

appointment type, with one system of record and no duplicate reminders.

1. Recover misses with RLR-30 wherever an appointment becomes a no-show,

escalating high intent to a human and preserving valid future opportunities in nurture.

1. Hand off cleanly with RLR-31 so the appointment owner starts prepared.
2. Govern ownership with RLR-32 so every state has an owner, an SLA, and a

required disposition, and no prospect is lost to unclear ownership.

1. QA and re-measure — pass the workflow QA, test end-to-end booking,

confirmation/reminders, the no-show path, the handoff, and ownership transitions, then re-run RLR-27 at 14 and 30 days. A Link 5 leak is only repaired when re-measured ready-to-booked rate, time-to-book, confirmation and reminder coverage, show rate, no-show recovery, reschedule rate, handoff completeness, and ownership completeness show the gap improved — not because a calendar workflow or reminders were installed.

Existing-asset note (Link 5): RLR-29 is the canonical *operational*

confirmation-and-reminder sequence and absorbs and materially improves

ShiFt's prior two-message Appointment Confirmation Script (the confirmation +

24-hour reminder shown in the Lead-to-Appointment Rescue Kit). There is no

competing customer-facing sequence with a separate name. The public Rescue Kit

page remains the outward-facing surface and points to these instruments — it is

not modified.

Diagnostic coverage note (Link 5): the Revenue Leak Diagnostic (RLR-02)

does score Booking + Handoff, but only as a starting signal. Your operational

depth for this link comes from the Booking Friction Audit™ (RLR-27), which

inspects real appointment-level records the Diagnostic does not collect.

Upstream handoff (Link 4 → Link 5): Link 5 consumes the Link 4 outputs —

prospect readiness, booking intent, preferred timing, qualification summary,

prior follow-up context, owner, and recommended next action — and does not

recreate Follow-Up logic. It converts qualified readiness into a confirmed,

attended appointment and a clean handoff.

Downstream handoff (Link 5 → Link 6): Booking + Handoff produces clean,

measurable output for Attribution + Decision Intelligence — original source,

qualification classification, booked status, booked date, appointment type,

assigned owner, show/no-show status, reschedule status, appointment outcome,

next-stage outcome, and retained/won status and revenue where available. Link 6

is authored in a later phase; Link 5 only prepares the clean handoff.

Compliance guardrail (Link 5): every Booking + Handoff resource respects

known opt-out signals, channel permissions, quiet-hours rules, business-

implemented suppression, explicit do-not-contact requests, data-retention and

privacy policy, and approved communication policy. None of them invent legal

requirements or bypass provider restrictions, opt-outs, or consent controls;

jurisdiction- and industry-specific rules are applied by the operator.

7.6 Link 6 — Attribution + Decision Intelligence (worked path)

Link 6 is the sixth and final fully authored Repair Playbook. Enter it when your leak is revenue cannot be reconciled — you cannot reliably trace an opportunity from its original source through the Revenue Chain to realized revenue, so you cannot trust which source or process to scale, fix, or stop. Link 6 converts operational data into management decisions through an explicit progression: CAPTURE → CONNECT → MEASURE → INTERPRET → DECIDE → ACT → RE-MEASURE. Two distinctions govern the whole link: attribution confidence is not attribution accuracy, and a modeled estimate is never a measured actual. Original source is captured once and never silently overwritten by later activity. Work the six resources as one system, in this order:

1. Attribution Integrity Audit™ (RLR-33) — from real records and systems,

measure how much of the chain actually connects source → inquiry → contact → qualification → follow-up → appointment → show → sale → revenue (and gross profit where available), run the integrity checks (missing/overwritten source, broken cross-system IDs, unreconciled revenue, unknown-source rate), and return an explicit attribution-confidence level: HIGH / MODERATE / LOW / INSUFFICIENT DATA.

1. Revenue Attribution Field Map™ (RLR-34) — install the canonical data

contract: the Identity, Source, Response, Qualification, Follow-Up, Booking, Outcome, and Governance fields each stage must write, with a system of record, an update schedule, and — critically — an overwrite rule that protects original source.

1. Revenue Chain KPI Dictionary™ (RLR-35) — the single canonical definition

of every metric named across the Kit. It pre-existed from Phase 2A; Link 6 normalizes definitions against it and connects them to the Dashboard and Decision Matrix rather than redefining anything.

1. Revenue Chain Dashboard Template™ (RLR-36) — build one management view

organized by the six links, each metric shown as Actual / Target / Variance / Trend / Status with its data source and confidence, measured and modeled values kept apart, and the current highest-priority leak, its owner, and repair status surfaced on the Link 6 section.

1. Cut / Keep / Fix / Scale Decision Matrix™ (RLR-37) — turn measurement into

an explicit decision — SCALE / KEEP / FIX / REDUCE / STOP / INSUFFICIENT EVIDENCE — weighing evidence across the whole chain and separating a source problem from a Revenue Chain execution problem. It reuses the approved Priority Matrix (RLR-06) method and introduces no new opaque formula.

1. Weekly Revenue Chain Operating Review™ (RLR-38) — run a concise ~20-30

minute weekly review that names what changed, where the leak is, what it is costing, what is being done, who owns it, and when the fix will be verified, recording every issue with baseline/current/target/variance/economic-impact/ root-cause/action/owner/due-date/verification-date/status.

The Link 6 procedure:

1. Measure attribution integrity with RLR-33 — from real records; count

unknowns explicitly and never convert an Unknown source into zero revenue or a disqualified source.

1. Repair the data contract with RLR-34 (paired with the Link 1 UTM & Lead

Source Tracking Standard, RLR-09) wherever confidence is weak — fix capture and original-source protection *before* trusting any cut/scale decision.

1. Normalize definitions against RLR-35 so every team means the same thing by

each KPI.

1. See the whole chain with RLR-36 — build the dashboard with real, reconciled

data; never ship an empty or fabricated dashboard or invent target values.

1. Decide with RLR-37 — separate source problems from execution problems; a

good-fit source that converts poorly downstream routes to FIX CONVERSION SYSTEM, not STOP SOURCE, and low-confidence evidence routes to INSUFFICIENT EVIDENCE, never a guess.

1. Operate weekly with RLR-38 and prioritize repair with the Priority

Matrix (RLR-06), recording each on the Repair Plan (RLR-39).

1. QA and re-measure — re-run RLR-33 at 14 and 30 days. A Link 6 leak is only

repaired when re-measured source completeness, source-to-sale and revenue traceability, unknown-source rate, and attribution-confidence level improve on real records — not because a dashboard or field map was created.

Existing-asset note (Link 6): the Revenue Chain KPI Dictionary™

(RLR-35) and the Revenue Leak Repair Plan™ (RLR-39) both pre-existed from

Phase 2A. Link 6 integrates and references them in place — RLR-35 was

validated and connected to the Dashboard and Decision Matrix (definitions

unchanged); RLR-39 is referenced by the Weekly Operating Review — and does not

create competing assets. Attribution capture reuses the Link 1 UTM & Lead

Source Tracking Standard (RLR-09).

Diagnostic coverage note (Link 6): the Revenue Leak Diagnostic (RLR-02)

does score Attribution, but only as a starting signal. Your operational depth

for this link comes from the Attribution Integrity Audit™ (RLR-33), which

inspects real cross-system records the Diagnostic does not collect.

Upstream handoff (Link 5 → Link 6): Link 6 consumes the Link 5 outputs —

original source, qualification classification, booked status and date,

appointment type, assigned owner, show/no-show status, reschedule status,

appointment outcome, next-stage outcome, and retained/won status and revenue

where available — and does not recreate Link 5 booking or handoff logic. It

reconciles those outputs source-to-revenue and turns them into decisions.

Compliance guardrail (Link 6): every Attribution + Decision Intelligence

resource handles attribution, revenue, and personal data under the business's

approved privacy, retention, and consent policy, stores and displays only what

the decision requires, and respects opt-out/suppression constraints. None of

them invent legal requirements or bypass provider restrictions; jurisdiction-

and industry-specific rules are applied by the operator.

7A. Close the loop: Link 6 → Link 1

The Revenue Chain is a loop, not a line, and it does not terminate at a dashboard. Link 6 exists to feed measured, trustworthy decisions back into the business so demand spend and process investment follow evidence instead of guesswork. The operating loop is:

**Demand + Source → Speed-to-Lead → Qualification → Follow-Up →

Booking + Handoff → Attribution + Decision Intelligence → DECISION →

Demand + Source / the leaking link**

Decision Intelligence must inform, at minimum:

• source allocation (scale/keep/reduce/stop, fed back to Link 1);
• process repair (routed to the specific leaking link's Playbook);
• staffing and ownership;
• automation changes;
• workflow changes;
• follow-up changes;
• booking changes;
• measurement priorities (where confidence is too low to decide).

A SCALE/REDUCE/STOP decision returns to Link 1 (Demand + Source); a FIX decision returns to whichever link is leaking. Either way, the decision carries an owner and a verification date, so "installed" is never mistaken for "closed" and the next turn of the loop is measured, not assumed.

8. Implement the repair (Step H)

Inside the chosen Playbook you will find the scripts, SOPs, templates, controls, and workflows that close that link's leak. Implementation discipline:

1. Start from the Playbook's audit to confirm the specific defect.
2. Install the smallest change that addresses the audited defect — one leak, one repair, one measurable metric.
3. Record what you changed on the Revenue Leak Repair Plan™ (RLR-39): the leak, the link, the specific resources installed, the owner, the date, and the single metric that will prove or disprove closure.
4. Do not batch unrelated repairs into one change window, or you will not be able to attribute the result.

Installing the workflow completes Step H. It does not complete the loop. An implemented repair is still unproven.

9. QA the repair (Step I)

Before you claim anything, prove the repair actually functions as designed. QA is functional verification of the mechanism, separate from measuring the business result.

QA checklist for any repair:

• The trigger fires under real conditions (not just a test record).
• The workflow completes end-to-end, including edge cases (after-hours, missed

call, no-show, disqualified).

• Ownership and escalation paths resolve to a real person or system.
• The metric that proves closure is actually being captured and stored.

A repair that passes QA is confirmed to *work*. Whether it *recovered revenue* is still a separate question, answered in Steps J and K.

10. Re-measure performance (Step J)

Return to the exact metric and method you recorded in the baseline (Step C) and measure it again, over a comparable window, after the repair has been live long enough to produce data.

Re-measurement rules:

• Same metric, same method, comparable window. A different definition is not a

re-measurement.

• Let it accrue. Use a re-measurement window appropriate to your volume

(commonly a 14- or 30-day re-diagnostic). Reading the metric too early produces noise, not proof.

• Record it on the Before/After Scorecard. Keep the baseline and the

post-repair number side by side with their data sources.

11. Verify whether the leak is actually closed (Step K)

This is the step most programs skip, and it is the reason most "fixes" never show up in the bank. Verification compares the re-measurement (Step J) against the baseline (Step C) and applies an explicit closure test.

A leak is Verified Closed only when all of the following hold:

1. The repair passed QA (Step I).
2. The re-measured metric moved in the intended direction versus baseline.
3. The movement is beyond normal variation for that metric at your volume.
4. The movement held across the full re-measurement window.
5. The recovered contribution is consistent with the quantified estimate (Step E),

or the estimate is revised with the reason recorded.

If any condition fails, the leak is not closed. It returns to Prioritize (Step F) as either "repair insufficient" or "needs more evidence." Only recovery that clears this test may be recorded on the Recovered Revenue Tracker and counted as closed on the Revenue Leak Closure Checklist.

Restating the governing rule, because it is the whole point of the Kit:

a workflow being installed is never, by itself, proof that a leak is closed.

Proof is a held, above-noise, baseline-referenced re-measurement.

12. How the Kit resources fit the loop

Supporting reference throughout: the Revenue Chain KPI Dictionary™ (RLR-35) defines every metric named above so that "baseline," "re-measurement," and "recovered" mean the same thing at every step.

13. Where the standalone tools sit

The Revenue Leak Diagnostic™ and Revenue Leak Calculator™ remain fully usable on their own as entry points — you do not need the whole Kit to run them. Inside the Kit, the Diagnostic is your Diagnose step and the Calculator is your Quantify step. Their deeper functional integration into the Kit's saved session happens in a later phase; for now, run them, then transcribe their outputs onto the Scorecard and Repair Plan by hand. Nothing about their standalone behavior changes.

14. The complete Kit journey (never guess what comes next)

This is the whole system in order. At every step the Manual tells you exactly which resource to open next, so you never have to guess. Follow it top to bottom; the loop repeats.

1. START HERE — Revenue Leak Repair Manual™ (RLR-00). You are reading it.
2. UNDERSTAND — the ShiFt 6-Link Revenue Chain Framework™ (RLR-01): Demand +

Source → Speed-to-Lead → Qualification → Follow-Up → Booking + Handoff → Attribution + Decision Intelligence.

1. DIAGNOSE — Revenue Leak Diagnostic™ (RLR-02), plus the link-specific audits

(RLR-07, RLR-10, RLR-16, RLR-22, RLR-27, RLR-33) for operational depth.

1. MEASURE — Revenue Chain Baseline Scorecard™ (RLR-03), using the KPI

definitions in the Revenue Chain KPI Dictionary™ (RLR-35).

1. QUANTIFY — Revenue Leak Calculator™ (RLR-05). Its output is a modeled

estimate, not measured recovery.

1. PRIORITIZE — Revenue Leak Priority Matrix™ (RLR-06).
2. PLAN — Revenue Leak Repair Plan™ (RLR-39). One entry per leak.
3. REPAIR — enter the Playbook for the leaking link and install the fix:

• Link 1 Demand + Source (RLR-07…RLR-09)
• Link 2 Speed-to-Lead (RLR-10…RLR-15)
• Link 3 Qualification (RLR-16…RLR-21)
• Link 4 Follow-Up (RLR-22…RLR-26)
• Link 5 Booking + Handoff (RLR-27…RLR-32)
• Link 6 Attribution + Decision Intelligence (RLR-33…RLR-38)

1. IMPLEMENT — Workflow Implementation Checklist™ (RLR-40). Install safely,

with a rollback method and tested failure paths.

1. QA — Revenue Chain QA Test Script™ (RLR-41). Happy path alone is not a pass.
2. VERIFY — 14/30-Day Revenue Leak Re-Diagnostic™ (RLR-42). Same metric,

same method, comparable window.

1. COMPARE — Before/After Revenue Chain Scorecard™ (RLR-43). No causation

claims without the confounding-variables review.

1. MEASURE ECONOMIC IMPACT — Recovered Revenue Tracker™ (RLR-44). Measured

actual vs modeled estimate vs inferred impact, never conflated.

1. CLOSE OR CONTINUE — Revenue Leak Closure Checklist™ (RLR-45). CLOSED only

on held, above-noise, baseline-referenced improvement; otherwise it stays open.

1. OPERATE — Weekly Revenue Chain Operating Review™ (RLR-38). Run the chain

weekly; surface the current highest-priority leak and its owner.

1. REPEAT — the review and the decision matrix (RLR-37) feed the next leak

back to the top of the loop. The Revenue Chain is a loop, not a line.

15. Navigate the Kit two ways

You never need to memorize RL numbers to use the Kit. The RL identifiers are implementation labels; you navigate by process stage or by Revenue Chain link.

By process stage

• Diagnose — Diagnostic™ + the six link audits.
• Measure — Baseline Scorecard™ (definitions from the KPI Dictionary™).
• Quantify — Calculator™.
• Prioritize — Priority Matrix™.
• Repair — the six Playbooks + Repair Plan™ + Implementation Checklist™.
• Verify — QA Test Script™ → Re-Diagnostic™ → Before/After Scorecard™ →

Recovered Revenue Tracker™ → Closure Checklist™.

By Revenue Chain link

• Link 1 — Demand + Source — audit, then source scorecard + tracking standard.
• Link 2 — Speed-to-Lead — audit, SLA, script pack, missed-call + after-hours

recovery, escalation.

• Link 3 — Qualification — audit, framework/checklist, scoring, scripts,

routing, disposition standard.

• Link 4 — Follow-Up — audit, persistent sequence, no-response recovery,

long-term nurture, stop/escalation rules.

• Link 5 — Booking + Handoff — audit, booking scripts, confirmation/reminder,

no-show rescue, handoff template + SLA.

• Link 6 — Attribution + Decision Intelligence — audit, field map, KPI

dictionary, dashboard, decision matrix, weekly operating review.

Every resource is reachable from both paths, and the shared Verify library (Implementation Checklist™ through Closure Checklist™) applies to a repair in any link.

16. What the Diagnostic covers today (and what Phase 3 must reconcile)

Being precise here prevents overclaiming. Today, the live Revenue Leak Diagnostic™ scores Links 2–6 (Speed-to-Lead, Qualification, Follow-Up, Booking + Handoff, Attribution). Link 1 (Demand + Source) coverage in the Diagnostic is not yet complete; until it is, Link 1 is diagnosed and baselined by the Lead Source Quality Audit™ (RLR-07) and the Baseline Scorecard™ (RLR-03), which is why every link Playbook opens with its own audit rather than relying on the Diagnostic score alone.

• What it measures: a link-by-link diagnostic signal that routes you to the

leaking link and its Playbook.

• Links covered by the Diagnostic score: 2, 3, 4, 5, 6.
• Where Link 1 coverage comes from today: RLR-07 (audit) + RLR-03 (baseline).
• What Phase 3 must reconcile: integrate Link 1 (Demand + Source) coverage and

scoring into the Diagnostic so all six links are scored by one instrument, and reconcile Diagnostic question/scoring with the six-link model. This Manual does not claim validated six-link Diagnostic coverage; that is a Phase 3 outcome.

The Diagnostic and Calculator production logic are unchanged. Their deeper integration into a saved Kit session is a later-phase step.

17. A note on delivery status

Every Kit resource named here is authored and usable as content, but the Kit's one-click download/delivery mechanism is not built yet. Statuses read content_ready_delivery_pending on purpose: the content is real, but nothing in the Kit is represented as downloadable until its delivery path is actually implemented and tested. There are no download buttons that do not work.

18. One complete walkthrough (SAMPLE data)

The following is an ILLUSTRATIVE SAMPLE, not a ShiFt client result, showing that the Kit runs start to finish without gaps.

1. Manual (RLR-00). A home-services business starts here.
2. Understand (RLR-01). They learn the six links.
3. Diagnose (RLR-02 + audits). The Diagnostic flags Link 2 (Speed-to-Lead);

the Speed-to-Lead Audit™ (RLR-10) confirms first response averages hours, not minutes.

1. Measure (RLR-03 / RLR-35). SAMPLE baseline: median first-response time

6h 12m; lead-to-appointment rate 18% — both defined via the KPI Dictionary™.

1. Quantify (RLR-05). SAMPLE modeled estimate: faster response could recover

an estimated ~$4,000/mo — labeled an estimate, not recovered revenue.

1. Prioritize (RLR-06). SAMPLE: "Fix Now" — high impact, high confidence,

moderate effort.

1. Plan (RLR-39). One entry: leak = slow first contact (Link 2); baseline

6h 12m; target < 5 min; KPI = median first-response time; owner = Ops Lead; status = PLANNED.

1. Repair (RLR-11, RLR-12, RLR-13). They install a First-Response SLA™, the

Instant First-Response Script Pack™, and the Missed-Call Recovery Playbook™.

1. Implement (RLR-40). Rollback method defined; test records prepared;

after-hours and missed-call paths configured.

1. QA (RLR-41). Happy path, failure path, after-hours, and opt-out all PASS

with recorded evidence; status → VERIFYING.

1. Re-Diagnostic (RLR-42). SAMPLE 30-day: median first-response 4m 30s,

held across the window; DATA_CONFIDENCE = HIGH.

1. Compare (RLR-43). SAMPLE: before 6h 12m → after 4m 30s; confounding-

variables review notes no ad or staffing change in the window.

1. Economic impact (RLR-44). SAMPLE: +7 incremental appointments recorded

as MEASURED ACTUAL; a larger figure kept separately as ESTIMATED OPPORTUNITY.

1. Close (RLR-45). All gates pass → CLOSED - VERIFIED; RLR-39 status → CLOSED.
2. Operate (RLR-38). The weekly review now shows Link 3 as the next

highest-priority leak.

1. Repeat. The decision matrix (RLR-37) routes the team back to PLAN for

Link 3, and the loop continues.

No undocumented gaps were found in this walkthrough: every step names the next resource, and no step depends on a resource that does not exist.