# Playbook — Application / High-Ticket

**Derives from:** Sam Ovens (Consulting Accelerator model) and Alex Hormozi (*$100M Offers* framing of qualification). See MANUAL §4.5.

## Thesis

VSL or case-study page → application form → triage call → close. **Qualification IS the funnel** — the application filters so sales time only ever meets pre-sold, pre-qualified prospects. The application itself is a Fogg ability-cost gate (§2.6): it deliberately adds friction to filter for motivation, trading volume for close-rate.

## When to use it

- Price is $3k+ and/or delivery is high-touch (cohort, done-with-you, 1:1) — a page alone can't close this, and a call without pre-qualification wastes sales capacity on tire-kickers.
- You'd rather talk to 10 qualified prospects than 100 unqualified ones. Sales capacity is the scarce resource, not lead volume.
- The offer requires trust-building a page can't do alone (large investment, custom fit, cohort selection).

## When NOT to use it

- Volume is too low to fill calls — an application step on a trickle of traffic just adds friction with no filtering benefit; go straight to a booked-call CTA without the gate, or fix top-of-funnel volume first.
- The offer is cheap enough that a call is disproportionate friction relative to price (Fogg: you added ability-cost with no matching motivation payoff) — this is a B=MAP mismatch, not a qualification win.
- You don't actually have sales capacity to run the calls — a full application queue with no one to triage it is a bottleneck, not a filter.

## Step-by-step build

1. **VSL or case-study page** — ONE job: get the application click. Not "learn more," not "join our list" — apply. The page's proof inventory (MANUAL §8.2) must carry at least 2 tagged proof items (`[testimonial|data|demo|authority]`).
2. **Application form** — deliberately asks qualifying questions (budget, timeline, current situation, commitment) that do double duty: filter *and* pre-frame the triage call (the applicant has already answered the objections a cold call would have to surface).
3. **Triage/booking logic** — define disqualification criteria explicitly (budget floor, timeline mismatch, wrong-fit answers) so unqualified applicants are routed to a downsell or nurture path, not a wasted call slot.
4. **Triage call** — the call's job is to confirm fit and handle final objections, not to "sell from scratch." The application did the pre-suasion (Cialdini, §2.3) — the call closes what's already warm.
5. **Close** — payment/contract; explicit risk reversal stated verbally and in writing (Abraham, §2.5).
6. **Stage Map**: traffic → VSL/case-study page → application submitted → call booked → call held → closed/not-closed.
7. **Conversion Math**: page view→application start, application start→submit (watch for form-length ability-cost drop-off here), application→call booked, call→close — each tagged.
8. **Instrumentation**: `vsl_page_viewed`, `application_started`, `application_submitted`, `call_booked`, `call_held`, `deal_closed`.
9. **Failure Exits**: application disqualified → automatic downsell offer or nurture sequence (not silence — a disqualified lead today may qualify in 6 months); call held but no close → objection-specific follow-up sequence naming the actual stated objection.

## Worked mini-example

- **Offer:** $2,500 ZIION Capital Readiness Cohort (premium rung of the value ladder — see `value-ladder`).
- **VSL page:** 8-minute case-study video of one builder's readiness-to-funding path; 3 tagged proof items (1 testimonial, 1 data point on cohort outcomes, 1 authority credential).
- **Application:** 7 questions including current revenue stage, capital sought, and timeline — disqualifies anyone under a stated revenue floor to a $497 Core Passport downsell instead.
- **Triage call:** 20 minutes, scripted around the 3 most common objections the application data surfaces (price, timing, "will this actually work for my business").
- **Conversion Math:** VSL view→application start 12% `[guess]`; start→submit 65% `[benchmark, typical multi-field application completion]`; application→call booked 40% `[benchmark]`; call→close 30% `[guess, no historical cohort data yet]`.

## How the verify gate applies

`funnel-blueprint` (MANUAL §8.1): every stage transition (including the application-start→submit micro-transition, which is where most ability-cost leaks live) needs its own tagged number — collapsing "application" into one blended conversion figure hides exactly the leak this style is prone to. The VSL/case-study page also gets checked against the `landing-page-spec` linter (§8.2): one goal, one primary CTA (apply), attention-ratio ≤3:1, minimum 2 tagged proof items, minimum 3 objections addressed. Disqualification criteria must be named explicitly in the Failure Exits section — an application funnel with no stated disqualification logic hasn't actually built a filter, just a longer form.