## Asset Header

- **Asset ID:** MPB-BVH-CHTSM-HighTicketSales-v01
- **Version:** v01
- **Status:** Draft
- **Owner:** Victor Heredia
- **IntellBank:** IB-BVH-Publications
- **Tipo:** MPB — MasterPlaybook
- **Propósito:** CANONICAL HIGH-TICKET SALES MetaPlaybook
- **Última actualización:** 2026-04-11

---

# CANONICAL HIGH-TICKET SALES MetaPlaybook
## MTB-CHTSM v1.1 — Demand & Conversion MetaFactory Deployment

---

| Field | Detail |
|---|---|
| **Asset Classification** | Type D MetaPlaybook — Layer L2 Domain MetaFactory |
| **Domain** | Demand & Conversion |
| **Governing Architecture** | Big MetaFactory (L0–L6) — MetaPlaybook of MetaPlaybooks |
| **Primary Authority** | Human Owner: Victor Heredia \| AI Role: AISherpa |
| **Track** | Track A — Heavy / Governed |
| **Offer Encoded** | Demand & Conversion MetaFactory Deployment |
| **Price Band** | $25,000 – $75,000 \| Milestone-Based Payments |
| **ICP (90-Day Freeze)** | Founder-Led Service Business \| $1M–$5M ARR \| Founder/CEO Decision-Maker |
| **Transformation** | Operational Clarity + AI-Deployable Sales Engine |
| **Founder Touchpoints** | Strategy Validation + Final Close (2 appearances only) |
| **Deployment Model** | AI Pre-Qualification → Victor Strategy Confirmation → Victor Close |
| **Status** | New Canonical Asset — No improvisation allowed |

---

## TABLE OF CONTENTS

- [0. BMF Governance Layer — v1.1 Patch](#0-bmf-governance-layer--v11-patch)
  - [0.1 Canonical Registry Header](#01-canonical-registry-header)
  - [0.2 L0 Strategic Alignment](#02-l0-strategic-alignment)
  - [0.3 Cross-MetaFactory Interface Map](#03-cross-metafactory-interface-map)
  - [0.4 Skill Decomposition Layer](#04-skill-decomposition-layer)
  - [0.5 Risk Governance](#05-risk-governance)
  - [0.6 Control Plane Synchronization Rule](#06-control-plane-synchronization-rule)
- [I. Domain Definition](#i-domain-definition)
- [II. Transformation Architecture](#ii-transformation-architecture)
- [III. Qualification System](#iii-qualification-system)
- [IV. Objection Architecture](#iv-objection-architecture)
- [V. Sales Call Protocol](#v-sales-call-protocol-canonical)
- [VI. Follow-Up & Escalation Logic](#vi-follow-up--escalation-logic)
- [VII. Metrics & Control Layer](#vii-metrics--control-layer)
- [Appendix: Validity Checklist](#appendix-validity-checklist)

---


# 0. BMF GOVERNANCE LAYER — v1.1 PATCH

> This governance layer upgrades CHTSM v1.0 to full Big MetaFactory compliance. No structural sales logic is altered. This layer adds registry traceability, cross-layer integration, skill decomposition, and risk governance.

---

## 0.1 Canonical Registry Header

```
ASSET ID:              MP-DAC-CHTSM-001
Version:               v1.1
Layer:                 L2 — Domain MetaFactory
MetaFactory:           Demand & Conversion
Asset Type:            Type D — Structural Authority Engine
Risk Tier:             R3 — Revenue-Critical Infrastructure
Registry Status:       Frozen (Track A)
Parent Architecture:   Big MetaFactory (L0–L6)

Upstream Dependencies:
  - ICP Freeze Protocol v1.0
  - AI Qualification Engine Spec
  - CRM Tagging Schema v1.0

Downstream Interfaces:
  - AI Demand Engine
  - Sales Rep Execution Layer
  - Control Plane Dashboard
```

---

## 0.2 L0 Strategic Alignment

*Purpose: This MetaPlaybook supports Big MetaFactory L0 as the foundational revenue authority layer.*

This asset is not a sales script. It is a **Revenue Authority Compression Engine.**

It supports L0 by:

1. Compressing founder authority into structured, transferable logic.
2. Converting tacit sales expertise into deployable decision trees.
3. Enabling AI-native orchestration of qualification and objection routing.
4. Reducing human bottlenecks in revenue generation without reducing authority.
5. Creating a self-correcting authority system governed by measurable metrics.

### BMF Layer Compliance Map

| BMF Layer | Role in This Asset |
|---|---|
| L0 — Strategic Foundation | Revenue authority compression objective |
| L1 — Taxonomy Enforcement | Asset classification, type, and domain lock |
| L2 — Domain MetaFactory | This document — deterministic sales engine |
| L3 — Instance Deployability | Per-client MetaFactory deployment logic |
| L4 — Human / AI Role Separation | SK-AI vs SK-HU skill decomposition |
| L5 — Measurable Control Loop | Section VII: Metrics & Control Layer |
| L6 — Mutation Governance | Version control + Sync Clause |

---

## 0.3 Cross-MetaFactory Interface Map

### Upstream Inputs

| Source MetaFactory | Interface |
|---|---|
| AI Publishing MetaFactory | Authority Extraction Output |
| ICP Strategy MetaPlaybook | Frozen ICP Definition |
| AI Skill Vault | Skill IDs for qualification & scoring |
| Control Plane | Reporting Infrastructure |

### Downstream Outputs

| Destination | Output |
|---|---|
| AI Demand Engine | Qualification scoring rules |
| CRM | Tagging taxonomy |
| Sales Rep Layer | Call protocol (Phases 1–5) |
| Dashboard | Stage metrics & drop-off data |
| Founder | Validation-only touchpoint |

### Isolation Rule

This MetaPlaybook **does NOT:**

- Design marketing funnels
- Generate demand
- Define brand strategy
- Configure CRM software

It **consumes qualified demand only.** All demand generation is upstream.

---

## 0.4 Skill Decomposition Layer

*This section decomposes all MetaPlaybook functions into atomic, assignable skills compatible with the AI Skill Marketplace architecture.*

### AI Skills (SK-AI)

| Skill ID | Function |
|---|---|
| SK-AI-QUAL-001 | ICP Match Scoring |
| SK-AI-SCORE-002 | Readiness Scoring (0–20) |
| SK-AI-OBJ-003 | Objection Classification |
| SK-AI-ROUTE-004 | Disposition Routing Logic |
| SK-AI-RECAP-005 | Structured Post-Call Recap Generation |
| SK-AI-FUP-006 | 48-Hour Reinforcement Message |
| SK-AI-METRIC-007 | Stage Drop-Off Analysis |
| SK-AI-LEAK-008 | Authority Leakage Detection |
| SK-AI-VERSION-009 | Version Sync Across Prompts |

### Human Skills (SK-HU)

| Skill ID | Function |
|---|---|
| SK-HU-DISC-001 | Phase 2 Diagnostic Delivery |
| SK-HU-QUAL-002 | Budget Signal Confirmation |
| SK-HU-POS-003 | Phase 4 Solution Framing |
| SK-HU-ADV-004 | Commitment Transition Execution |
| SK-HU-VAL-005 | Founder Strategy Validation |
| SK-HU-CLOSE-006 | Close Variant Deployment |
| SK-HU-AUDIT-007 | Monthly Control Review |

---

## 0.5 Risk Governance

**Risk Tier: R3 — Revenue-Critical Infrastructure**

**Definition:** Failure of this asset directly impacts close rate, founder time allocation, revenue stability, and brand authority.

### Escalation Triggers

Initiate the Escalation Protocol if ANY of the following occur:

- Overall close rate drops below **8%**
- Victor involvement exceeds **20%** of total sales hours
- Strategy validation close rate below **60%** for 2 consecutive months

### Escalation Protocol

1. Freeze deployment of new ICP variants immediately.
2. Initiate 72-hour Stage Audit across all drop-off points.
3. Trigger MetaPlaybook Revision Cycle (Section 0.6).
4. Increment version: v1.1 → v1.2.

> **No informal fixes allowed. All corrections must be encoded, tested, and version-logged.**

---

## 0.6 Control Plane Synchronization Rule

**When a version increment occurs, ALL of the following must be updated simultaneously:**

| Sync Target | Action Required |
|---|---|
| AI Prompt Libraries | Update qualification, scoring, and objection prompts |
| CRM Scoring Thresholds | Update readiness score thresholds and tagging logic |
| Sales Rep SOP | Update call protocol and close variant instructions |
| Dashboard Thresholds | Update benchmark ranges in Stage metrics |
| Registry Change Log | Log revision in REG-CHANGES with version, date, and trigger |

> ⛔ **No partial updates permitted. All sync targets must be updated in the same revision cycle.**

---

# I. DOMAIN DEFINITION

> This section defines the structural foundation of the Demand & Conversion MetaFactory. All downstream architecture — qualification, objection handling, and call protocol — is derived from this domain definition. Do not modify without triggering a full MetaPlaybook audit.

---

## 1.1 Problem Definition

Founder-led service businesses at $1M–$5M ARR have reached a growth ceiling caused by founder-dependent selling. Every qualified conversation requires the founder's presence, authority, time, and persuasion capacity.

This creates four compounding failure modes:

- **Revenue Ceiling** — Growth is constrained by the founder's bandwidth for sales conversations.
- **Quality Decay** — As the founder scales time across more calls, conversion quality and close rate decline.
- **Delegation Failure** — Without a structured system, sales logic cannot be transferred to reps or AI systems.
- **Authority Leakage** — When the founder is unavailable, deals stall, drift, or die entirely.

The root cause is not effort or skill. It is the absence of a structured, AI-deployable Demand & Conversion system. This MetaPlaybook encodes the solution.

---

## 1.2 Target ICP Definition

> **Frozen for 90 days from MetaPlaybook activation. No deviation without a formal ICP review.**

| ICP Field | Specification |
|---|---|
| Company Type | Founder-led consulting, advisory, or expert service firm |
| Revenue Range | $1M – $5M ARR |
| Decision-Maker Title | Founder / CEO |
| AI Maturity Level | 0 – 2 (no AI in sales process, or nascent experimentation) |
| Team Size | 2 – 15 employees |
| Current Sales Model | Founder closes all or most deals personally |
| Typical Deal Size (Client) | $5K – $50K per client engagement |
| Revenue Mix | Services > 70% of total revenue |
| Growth Stage | Post-product-market fit, pre-systematic scale |

---

## 1.3 Buying Context Map

### Trigger Events — What Causes a Prospect to Become a Buyer

| Trigger | Manifestation |
|---|---|
| Founder Exhaustion | "I can't take every sales call anymore." Founder is burning out on conversations that don't close. |
| Revenue Plateau | Growth has flatlined despite increasing founder effort and marketing spend. |
| Delegation Failure | Attempted to hand sales to a team member or VA — system collapsed. Now back to founder. |
| Competitive Pressure | Competitors appear to be scaling faster; founder suspects a structural gap. |
| Partnership / Exit Planning | Founder needs business to operate without them. Current model blocks that outcome. |
| Hiring Bottleneck | Cannot justify hiring a sales team without a documented, repeatable system. |

### Decision Context

| Context Dimension | Detail |
|---|---|
| Decision-Maker = Economic Buyer | Same person (founder). No committee approval required. |
| Purchase Driver (Emotional) | Desire for freedom, leverage, and the ability to step back from the business. |
| Purchase Driver (Rational) | ROI clarity, risk reduction, and competitive positioning. |
| Approval Complexity | Low — single signature. No procurement process. |
| Evaluation Timeline | Typically 2–8 weeks from first contact to commitment. |
| Information Sources | Peer referrals, content authority, direct outreach. Low reliance on review sites. |

---

## 1.4 Authority Gap Analysis

| Gap Type | Description | Implication for MetaFactory |
|---|---|---|
| Structural Gap | No documented sales system exists. | No basis for delegation or AI deployment. Encoding must happen from scratch. |
| Knowledge Gap | Founder's sales logic lives entirely in their head. | Cannot be replicated or scaled. Extraction is the first milestone. |
| Confidence Gap | Founder does not trust a rep to handle their clients. | Blocks delegation even when willing. Requires protocol proof before handoff. |
| Technology Gap | No AI infrastructure in the sales process. | Pre-qualification and follow-up are fully manual. Immediate leverage opportunity. |
| Time Gap | Founder spends 8–15 hours/week on sales calls. | Primary urgency driver. Quantify this in every discovery call. |

---

# II. TRANSFORMATION ARCHITECTURE

> Every element must be repeatable, measurable, and encodable into AI prompts and CRM logic.

---

## 2.1 Core Transformation Promise

> **FROM:** A founder who is personally required at every stage of the sales process — spending 8–15 hours per week on calls, with no predictable pipeline and no capacity to scale.

> **TO:** An operational clarity engine — a fully structured, AI-deployable Demand & Conversion MetaFactory that pre-qualifies leads, maps objections, and delivers only confirmed-ready prospects to the founder for strategy validation and final close.

*This is not a marketing system. It is not a CRM. It is not a funnel. It is a structural authority engine: the founder's sales logic, encoded into a deployable operating system.*

---

## 2.2 Before / After State Map

| Dimension | BEFORE State | AFTER State |
|---|---|---|
| Lead Qualification | Founder manually reviews every inquiry. | AI pre-qualification engine scores and routes leads by readiness. |
| Call Preparation | Founder relies on memory and intuition. | Structured pre-call brief auto-generated from ICP scoring data. |
| Objection Handling | Ad hoc, inconsistent, founder-dependent. | Encoded objection map with standardised responses deployed by AI or rep. |
| Close Process | Improvised based on call dynamics. | 5-phase call protocol with defined close variants and disposition tags. |
| Follow-Up | Founder sends manual follow-ups when they remember. | Automated 48-hour reinforcement sequence with case study injection. |
| Pipeline Visibility | No data — gut-feel assessment. | CRM-tagged readiness scoring with stage drop-off tracking. |
| Founder Dependency | Required on every call. | Appears at strategy validation and final close only (2 touchpoints). |
| Close Rate | Unknown or unmeasured. | Benchmarked, tracked, and optimised by stage with weekly reporting. |

---

## 2.3 Economic Framing Model

### Baseline Economics — ICP Profile

| Economic Variable | ICP Estimate |
|---|---|
| Average Deal Size | $15,000 – $40,000 |
| Current Close Rate | 20% – 35% (estimated; typically unmeasured) |
| Founder Hours Per Deal Closed | 4 – 8 hours |
| Deals Attempted Per Month | 3 – 6 |
| Founder Time in Sales Per Week | 8 – 15 hours |
| Revenue Left Per Unconverted Lead | $15K – $40K per unconverted qualified prospect |

### Post-MetaFactory Economics

| Economic Outcome | Projection |
|---|---|
| Target Close Rate Improvement | +15 – 25 percentage points above baseline |
| Founder Hours Per Deal | Reduced to 1 – 2 hours (strategy validation + close only) |
| AI Handles | Qualification, brief generation, objection pre-screening, follow-up sequencing |
| ROI Multiple Target | 3 – 8x on MetaFactory investment within 12 months |
| Payback Period | 1 – 3 additional closed deals post-deployment |

### Minimum Economic Justification Logic

- At $25K investment + $20K average deal: 2 additional deals per quarter = $40K incremental = **1.6x ROI in 90 days.**
- At $50K investment + $30K average deal: 2 additional deals = $60K = **1.2x ROI in 90 days.**
- Full ROI compounds as system scales, close rate improves, and founder time is reallocated to delivery.

> *Deploy this logic during Phase 4 (Solution Positioning) and in the post-call recap. Never use projections without grounding them in the prospect's own deal size and deal frequency.*

---

## 2.4 Time-to-Value Logic

> *This offer is milestone-based. Time-to-value is determined by milestone completion speed, not a fixed calendar.*

| Milestone | What Is Built | Deliverable | Immediate Value |
|---|---|---|---|
| Milestone 1 — Domain Foundation | ICP freeze, problem definition, authority gap mapped. | Frozen ICP doc + Authority Gap report. | Founder can disqualify bad-fit prospects immediately. Time saved from call 1. |
| Milestone 2 — Qualification Engine | Maturity scoring, readiness signals, disqualification criteria encoded. | Qualification Scoring System + AI prompt set. | AI pre-screens leads. Founder time recovery begins. |
| Milestone 3 — Sales Protocol | Call structure, objection architecture, close variants deployed. | Call Protocol + Objection Map + Close Variant Library. | AI or rep runs Phases 1–3. Founder enters at Phase 4 or 5 only. |
| Milestone 4 — Control Layer | Metrics live, CRM tags active, feedback loop operational. | Metrics Dashboard + Feedback Protocol. | System is self-improving. Founder touchpoints fully defined and minimal. |

---

## 2.5 Risk Reversal Framework

### Primary Buyer Risk: "I will pay $25K–$75K and the system will not work."

| Risk Reversal Mechanism | How It Works |
|---|---|
| Milestone-Based Payments | No payment until each milestone is delivered and validated by the client. Investment releases in stages. |
| Structural Validation | Each milestone has a defined, objective success criterion — not a subjective impression. |
| Founder Appears at Validation | Victor's strategy confirmation touchpoint ensures alignment before Milestone 2 begins. |
| Documented Output | Every milestone produces a tangible, auditable deliverable — not just a conversation. |
| No Post-Deployment Dependency | System is designed to operate without Victor after final delivery. |

### Secondary Buyer Risk: "My team will not use it."

The MetaFactory is AI-first. It does not require team adoption to function. The AI pre-qualifies and routes before any human is involved. Team adoption is a secondary phase, not a prerequisite for value.

---

# III. QUALIFICATION SYSTEM

> This system is the first line of the MetaFactory's authority protection. Its function is to ensure that only leads who meet the ICP definition, budget readiness, and psychological readiness criteria reach the sales call protocol.

---

## 3.1 Maturity Stages — Level 1 to 5

> *Every inbound lead is assigned a Maturity Level before any human contact. The AI pre-qualification engine assigns this score based on the intake form, lead source data, and initial engagement signals.*

---

### LEVEL 1 — Unstructured

| Field | Detail |
|---|---|
| Profile | All sales done by founder. No documentation. No CRM or basic CRM with no consistent use. |
| Revenue | $500K – $1M ARR |
| AI Maturity | 0 — No AI tools in use |
| Disposition | **NURTURE** — Not ready for MetaFactory. Needs foundational clarity first. |
| Action | Add to long-form nurture sequence. Re-qualify at 90-day interval. |

### LEVEL 2 — Structured Intent

| Field | Detail |
|---|---|
| Profile | Founder acknowledges the problem but has no solution. Has attempted to hire sales reps or VAs without success. |
| Revenue | $1M – $2M ARR |
| AI Maturity | 0 – 1 (aware of AI, not deployed) |
| Disposition | **ELIGIBLE** — Evaluate carefully before advancing. |
| Action | Confirm budget readiness and urgency before booking strategy call. |

### LEVEL 3 — Active Problem *(Primary Target)*

| Field | Detail |
|---|---|
| Profile | Founder is actively losing deals or time due to lack of system. Has tried DIY solutions — not working. |
| Revenue | $1.5M – $4M ARR |
| AI Maturity | 1 – 2 (using AI tools informally) |
| Disposition | **ADVANCE** — High fit. Confirm economic readiness and decision authority, then book call. |
| Action | Trigger pre-call brief generation. Schedule strategy call within 72 hours. |

### LEVEL 4 — System-Ready *(Premium ICP — Fastest Close)*

| Field | Detail |
|---|---|
| Profile | Founder has a team, has budget authority, has tried to build this before. Frustrated with prior results. |
| Revenue | $3M – $5M ARR |
| AI Maturity | 2 – 3 (actively deploying AI in operations) |
| Disposition | **PRIORITY** — Move to call protocol immediately. Close window is short. |
| Action | Escalate to Victor's calendar for strategy validation. Do not delay. |

### LEVEL 5 — Enterprise-Adjacent

| Field | Detail |
|---|---|
| Profile | Multiple decision-makers, longer procurement cycle. May need custom scoping. |
| Revenue | $5M+ ARR |
| AI Maturity | 3+ (structured AI infrastructure exists) |
| Disposition | **EVALUATE** — May require custom engagement. |
| Action | Flag for Victor's direct assessment before any call is scheduled. Standard protocol may not apply. |

---

## 3.2 Disqualification Criteria

> **Disqualify immediately if ANY of the following conditions are true.**

| Disqualification Trigger | Rationale |
|---|---|
| Budget authority is not the person in conversation | Must reach founder/CEO directly. No proxy qualification accepted. |
| Budget range stated below $25,000 | Misaligned price expectation. MetaFactory cannot be delivered at a lower investment. |
| Business is pre-revenue or below $750K ARR | Not ready for MetaFactory. |
| Primary product is physical goods or SaaS with no services | Wrong domain. |
| Founder is seeking marketing help, not a sales system | Wrong intent. Surface misalignment early. |
| Urgency is absent AND timeline is 6+ months | No activation energy. Add to nurture. Re-qualify in 90 days. |
| Founder has recently signed with a competing vendor | Irreversible commitment. |
| Founder unwilling to freeze ICP for 90 days | Structural misalignment. MetaFactory requires ICP discipline. |

---

## 3.3 Budget Readiness Signals

| Signal Level | Signal | Action |
|---|---|---|
| 🟢 GREEN | Prospect references a specific budget range voluntarily. | Advance immediately. Document exact figure in CRM. |
| 🟢 GREEN | Has previously invested $10K+ in a business system or program. | Strong credibility signal. Treat as budget-ready. |
| 🟢 GREEN | References competitive pressure or revenue ceiling as urgent problem. | Urgency + budget are typically co-present. |
| 🟢 GREEN | Has team budget allocated for operational improvements. | Confirm decision-maker authority before advancing. |
| 🟢 GREEN | Currently paying for underperforming sales support. | Switching cost already accounted for. |
| 🟡 YELLOW | "We have budget but it depends on what we are getting." | Economic framing required. Deploy ROI model in Phase 4. |
| 🟡 YELLOW | "I need to check with my partner/CFO." | Confirm authority chain before proceeding. |
| 🟡 YELLOW | "We have been burned before." | Risk reversal required before economic discussion. |
| 🔴 RED | "I was hoping this would be more affordable." | Price misalignment. Disqualify unless reframing resolves it. |
| 🔴 RED | "Can we start small and expand?" | Low commitment signal. Do not reduce scope. |
| 🔴 RED | "I need to think about it" with no follow-up scheduled. | Low urgency. Move to long-form nurture. |

---

## 3.4 Psychological Readiness Signals

### Ready Indicators — Advance to Call Protocol

- Expresses frustration or exhaustion with current state — unprompted.
- Has a specific emotional trigger: *"I missed my daughter's birthday because of a sales call."*
- Demonstrates awareness that the problem is structural, not effort-based.
- Has already decided to solve the problem — evaluating HOW, not IF.
- Asks implementation questions during pre-qualification (forward-leaning behaviour).

### Not-Ready Indicators — Nurture or Disqualify

- Still believes the solution is hiring the right person.
- Thinks more content or marketing will fix a conversion problem.
- Is exploring options without a commitment horizon.
- Is in denial about the founder-dependency issue.

---

## 3.5 Urgency Indicators

| Urgency Level | Signal |
|---|---|
| 🔴 HIGH — Activate Immediately | Q4 revenue pressure or missed annual target. |
| 🔴 HIGH — Activate Immediately | Recently lost a deal they know they should have closed. |
| 🔴 HIGH — Activate Immediately | Hired a new sales rep who is underperforming — founder back on all calls. |
| 🔴 HIGH — Activate Immediately | Public commitment to revenue growth (board, investors, team). |
| 🔴 HIGH — Activate Immediately | Founder planning vacation or parental leave — business must operate without them. |
| 🟡 MEDIUM — Advance with Confirmation | Has set a 90-day internal target but no external accountability. |
| 🟡 MEDIUM — Advance with Confirmation | Competitive pressure acknowledged but not yet quantified. |
| ⚪ LOW — Nurture | No specific timeline. Problem acknowledged but no activation energy. |

> **Urgency Amplification Rule:** Surface existing urgency from the prospect's own language. Reflect it back in the follow-up sequence. Do not manufacture urgency. Manufactured urgency destroys authority and credibility.

---

# IV. OBJECTION ARCHITECTURE

> Every objection is classified, mapped to its root assumption, and assigned a standardised response protocol. No improvisation. No personal interpretation. Deploy the response logic as written, then surface and advance.

---

## 4.1 Structural Objections

*Root: Belief that the MetaFactory requires something the prospect does not have.*

---

**Objection: "We do not have a sales team for this to work."**

| Field | Content |
|---|---|
| Root Assumption | MetaFactory requires humans to operate. |
| Reframe | The MetaFactory is AI-first. It is designed to deploy without a team. The AI pre-qualifies, briefs, and routes. The founder closes. The system reduces team dependency — it does not require it. |
| Evidence | Milestone 2 produces an AI qualification engine that operates without any human input until a lead reaches a pre-call readiness score of 12/20. |
| Return Question | If the system qualifies leads and delivers only confirmed-fit prospects to you — does the absence of a team still feel like a blocker? |

---

**Objection: "Our process is too custom or unique to systematise."**

| Field | Content |
|---|---|
| Root Assumption | Their offer is too complex for structural encoding. |
| Reframe | Every founder believes this. The MetaFactory encodes complexity into rules. The more nuanced the process, the higher the value of encoding it. Complexity is not an obstacle — it is the justification. |
| Evidence | The encoding process begins with extraction: we map your existing logic before we structure it. Nothing is invented. Everything is captured. |
| Return Question | What is the most complex part of your close process? That is exactly where we start. |

---

**Objection: "We have tried building systems before — they never stick."**

| Field | Content |
|---|---|
| Root Assumption | Past failure with playbooks, scripts, or CRMs predicts future failure. |
| Reframe | Previous systems failed because they were documentation — not engines. Documentation requires human adoption. The MetaFactory is AI-deployable from day one. It operates independently of human discipline. |
| Evidence | The Qualification Engine (Milestone 2) runs before any human is involved. It does not require a rep to follow a script. It follows rules. |
| Return Question | Did the previous systems fail because people did not follow them, or because the systems themselves were not built to run without people? |

---

## 4.2 Emotional Objections

*Root: Identity attachment to personal selling. Fear of brand dilution or loss of control.*

---

**Objection: "I am not sure I trust an AI to represent my brand in sales."**

| Field | Content |
|---|---|
| Root Assumption | AI will speak on the founder's behalf and damage their brand. |
| Reframe | The AI pre-qualifies — it does not pitch. Your brand, your authority, and your positioning are encoded into the system. The AI filters for fit. You appear only when fit is confirmed. This protects your brand more than the current model. |
| Return Question | Currently, how much of your authority is spent on conversations that do not close? The MetaFactory reserves your authority for the ones that do. |

---

**Objection: "What if it does not capture my voice?"**

| Field | Content |
|---|---|
| Root Assumption | An AI-generated system will feel inauthentic. |
| Reframe | Your voice is the input to the encoding process. We do not generate your authority — we extract and structure it. The output sounds like you because it is you, structured. The first milestone is entirely an extraction process, not a creation process. |
| Return Question | What would it mean to have your best thinking — your clearest framing — available every time, not just when you are at your best? |

---

## 4.3 Economic Objections

*Root: Price misalignment, incomplete economic framing, or risk aversion.*

---

**Objection: "The price is higher than I expected."**

| Field | Content |
|---|---|
| Root Assumption | The investment is not proportionate to the outcome. |
| Reframe | The question is not the price — it is the cost of not having the system. How much revenue is leaving the table per quarter from unqualified calls, stalled deals, and inconsistent follow-up? |
| Logic Deployment | Use the prospect's own deal size and deal frequency from Phase 2 discovery. Calculate: [deals not closed per month] × [average deal size] = monthly cost of the problem. Position $25K–$75K against that number. |
| Return Question | If the MetaFactory adds two closed deals per quarter that would not have happened otherwise — at your deal size — does the investment hold? |

---

**Objection: "I need to see ROI before I commit."**

| Field | Content |
|---|---|
| Root Assumption | Risk aversion. Reasonable request for evidence. |
| Reframe | The milestone structure is designed for exactly this. Milestone 1 costs [X]. You validate the output before Milestone 2 begins. You do not pay for the full engagement until you have confirmed value at each stage. |
| Return Question | If Milestone 1 delivered [specific output] and you could see the system working before committing to the full build — would that address the concern? |

---

**Objection: "Can we start with a smaller scope?"**

| Field | Content |
|---|---|
| Root Assumption | Budget constraint or low commitment. |
| Reframe | A partial MetaFactory is not a MetaFactory. A partial sales system creates partial results and full confusion. If budget is the constraint, we can structure milestone payments to extend the timeline. We cannot reduce the structural scope. |
| Return Question | Is the constraint a budget ceiling, or a cash flow timing issue? Those require different solutions. |

---

## 4.4 Identity-Level Objections

*Root: The founder's identity is fused with their selling style. Deepest resistance. Requires acknowledgement before reframing.*

---

**Objection: "I am a relationship-based seller — this removes the human element."**

| Field | Content |
|---|---|
| Root Assumption | The MetaFactory replaces relationship selling with automation. |
| Acknowledge First | "That makes sense. Relationship selling is your competitive advantage — and it should stay that way." |
| Reframe | The MetaFactory does not remove relationship selling. It protects it. Currently, your relationship capital is being spent on unqualified conversations. After deployment, your relationship capital is reserved exclusively for confirmed-fit, high-value prospects. |
| Return Question | What if the MetaFactory meant you only ever showed up in conversations where your relationship capital had the maximum chance of converting? |

---

**Objection: "I should be able to build this myself."**

| Field | Content |
|---|---|
| Root Assumption | Founder pride. Competence identity. |
| Acknowledge First | "You absolutely could. You have the domain knowledge." |
| Reframe | The question is the cost. Every hour spent building this system is an hour not spent closing deals or delivering your expertise. The MetaFactory is built once, by a team that has built it before. Your comparative advantage is your domain expertise — not system architecture. |
| Return Question | What is the hourly value of your time in client delivery? How does that compare to the hourly cost of building this yourself? |

---

## 4.5 Standardised Response Protocol

> *Apply this sequence to every objection, in order. Do not skip steps. Do not over-explain.*

| Step | Action |
|---|---|
| 1. Acknowledge | "That is a fair concern." — Do not deflect, dismiss, or minimise. |
| 2. Classify (Internal) | Identify: Structural / Emotional / Economic / Identity-Level. Do not state classification aloud. |
| 3. Reframe the Premise | Challenge the assumption beneath the objection — not the objection itself. |
| 4. Evidence or Logic | Provide one structural counter: data, case logic, or milestone proof. One only. |
| 5. Return to Pain | "Does that address the concern, or is there a deeper question underneath it?" |
| 6. Advance or Surface | If resolved: advance the call. If not resolved: surface the real objection beneath the stated one. |

> **Rule: Never argue. Never over-explain. Never apologise for price. One reframe. One question. Move.**

---

# V. SALES CALL PROTOCOL (CANONICAL)

> This is the operating script for every Demand & Conversion MetaFactory sales conversation. It is not a guide — it is a protocol. Execute in sequence. Do not improvise. Victor enters at strategy validation and at close only.

---

## 5.1 Pre-Call Data Requirements

> *Minimum data required before any strategy call is booked. Calls that do not meet this standard are rescheduled, not waived.*

### ICP Validation Data

| Data Point | Source |
|---|---|
| Company name and URL | Intake form or lead database |
| ARR estimate | Intake form or LinkedIn research |
| Founder/CEO name and LinkedIn | Intake form or LinkedIn research |
| Team size (approximate) | Intake form or LinkedIn company page |
| Current sales model | Intake form: "How do you currently sell?" |
| AI maturity level (0–5) | Intake form: "Which AI tools are you currently using?" |
| Urgency trigger | Intake form: "What prompted you to reach out now?" |
| Previous attempts to solve | Intake form: "Have you tried to fix this before? What happened?" |
| Budget range (if disclosed) | Intake form: "What is your budget range for solving this?" |

### Pre-Call Readiness Score — AI Generated

| Scoring Dimension | Score Range |
|---|---|
| ICP Match (company type, revenue, decision-maker) | /5 |
| Budget Readiness (signal level and specificity) | /5 |
| Psychological Readiness (urgency language, awareness level) | /5 |
| Urgency Level (trigger specificity and timeline) | /5 |
| **TOTAL SCORE** | **/20** |

> **Minimum required score to advance to strategy call: 12 / 20. Calls below 12/20 are rescheduled or disqualified before the founder is contacted.**

---

## 5.2 Call Structure — Phase 1 to 5

### Phase 1: Orientation *(5 minutes)*

| Element | Content |
|---|---|
| Objective | Set the diagnostic frame. Establish this call as a professional assessment — not a pitch. |
| Script Logic | "Before we get into specifics — this call is designed to determine whether there is a genuine fit between what you are building and what we deploy. I will ask structured questions. If there is alignment, I will tell you clearly what next steps look like. If there is not, I will tell you that directly as well. Does that work for you?" |
| Required Outcome | Prospect accepts the diagnostic frame. Power dynamic is established: you are the expert, they are being assessed. |
| CRM Tag | `[FRAME_SET]` |

---

### Phase 2: Problem Discovery *(15 minutes)*

| Element | Content |
|---|---|
| Objective | Surface the real problem. Quantify pain. Map urgency in the prospect's own words. |
| Question 1 | "Walk me through your current sales process — from first contact to close." |
| Question 2 | "Where does it break down most often?" |
| Question 3 | "How much of your own time goes into the sales process each week?" |
| Question 4 | "What have you tried to fix this? What happened?" |
| Question 5 | "If nothing changes in the next 12 months — what does that look like for the business?" |
| Required Outcome | Prospect has articulated the problem in their own words. Pain is quantified. Future cost of inaction is surfaced. |
| CRM Tag | `[PROBLEM_MAPPED]` |

---

### Phase 3: Qualification Confirmation *(10 minutes)*

| Element | Content |
|---|---|
| Objective | Confirm maturity level, budget readiness, and decision authority before positioning. |
| Question 1 | "When you imagine solving this — what does success look like, specifically?" |
| Question 2 | "Is there a specific revenue target or growth milestone tied to this?" |
| Question 3 | "What is your timeline for having this operational?" |
| Question 4 | "Is the investment in this something you would be authorising, or does someone else need to be involved?" |
| Required Outcome | Maturity level confirmed. Decision-maker confirmed. Budget signal received and classified. |
| CRM Tags | `[MATURITY_LEVEL_X]` + `[BUDGET_SIGNAL_GREEN/YELLOW/RED]` + `[DECISION_MAKER_CONFIRMED]` |

---

### Phase 4: Solution Positioning *(10 minutes)*

| Element | Content |
|---|---|
| Objective | Present the Demand & Conversion MetaFactory as the specific answer to their specific problem. No generic pitch. |
| Step 1 | Reflect their problem back verbatim: "What you have described is a founder-dependency problem — not a hustle problem." |
| Step 2 | Name the category: "What we build is called a Demand & Conversion MetaFactory." |
| Step 3 | Define what it is: "It is the encoded version of your sales authority — deployed as an AI-operable system." |
| Step 4 | Map to their pain: "In your case, the first milestone addresses [specific problem they named in Phase 2]." |
| Pricing Rule | **DO NOT present pricing in this phase.** Pricing is introduced at Phase 5 after commitment to fit is confirmed. |
| CRM Tag | `[SOLUTION_POSITIONED]` |

---

### Phase 5: Commitment Transition *(5–10 minutes)*

| Element | Content |
|---|---|
| Objective | Determine disposition. Advance or disqualify cleanly. |
| Opening Question | "Based on what we have covered — does this match the problem you are trying to solve?" |
| If YES | "Here is what I would suggest as a next step..." — introduce milestone structure and investment. |
| If UNCERTAIN | Surface the specific concern. Apply objection architecture (Section IV). One reframe. One question. |
| If NO | "What piece does not fit?" — surfaces the real objection. Probe once before accepting a no. |
| Advancement Criteria | Prospect confirms problem match AND is willing to discuss investment. Both conditions required. |
| CRM Tags | `[DISPOSITION_ADVANCE]` OR `[DISPOSITION_HOLD]` OR `[DISPOSITION_DISQUALIFIED]` |

---

## 5.3 Authority Confirmation Moments

### Victor Appears When ALL of the Following Are True

- Pre-call readiness score is 12/20 or above.
- Phase 3 confirms: Budget readiness is GREEN and decision-maker is confirmed.
- Phase 5 disposition is: ADVANCE.

### Victor Does NOT Appear For

- Initial inquiry or pre-qualification screening.
- First strategy call (AI or trained rep runs Phases 1–4).
- Follow-up sequences (automated per Section VI).
- Any call where qualification score is below 12/20.

### Victor Strategy Validation Agenda — 30 Minutes

| Agenda Item | Content |
|---|---|
| Strategic Fit Confirmation (10 min) | Victor validates the problem diagnosis and confirms strategic fit. |
| Structural Questions (10 min) | Answer one or two questions that require founder authority and cannot be delegated. |
| Milestone and Investment Alignment (5 min) | Confirm milestone structure and investment level. Ensure no ambiguity. |
| Close Context Set (5 min) | Establish the final close conversation: timing, next step, and decision criteria. |

---

## 5.4 Close Variants

### Close Variant A — Milestone Initiation Close *(Standard)*

> "The first milestone is [description]. The investment at this stage is [$X]. Once Milestone 1 is delivered and you have confirmed the value, you decide whether to advance. Does that structure work for you?"

*Deploy when: Prospect is ready but has residual risk concerns. The milestone structure addresses the concern structurally.*

---

### Close Variant B — Time-Frame Close *(Urgency-Aligned)*

> "You mentioned [urgency trigger the prospect stated]. If we start Milestone 1 now, you have [specific system component] operational before [their stated deadline]. Shall we schedule the kickoff?"

*Deploy when: Prospect has stated urgency with a specific timeline. Ground the close in their own deadline — not an invented one.*

---

### Close Variant C — Authority Confirmation Close *(Identity-Level)*

> "You have spent [X] years building this business on your authority. The MetaFactory does not replace that authority — it encodes it. You are not buying a system. You are structuring your own expertise into something that works without you present. Is that something you want to build?"

*Deploy when: Founder is emotionally attached to their selling style and has raised an identity-level objection. Never deploy as a first close.*

---

# VI. FOLLOW-UP & ESCALATION LOGIC

> No manual follow-up is acceptable as a default. Every follow-up action is triggered by CRM disposition tags and deployed without founder intervention.

---

## 6.1 Immediate Post-Call Flow *(0–2 Hours)*

*Trigger: Call ends with disposition `ADVANCE` or `HOLD`.*

| Action | Specification |
|---|---|
| Send Structured Recap Email | Not a generic "great to meet you." A specific problem/solution summary using the prospect's own words from Phase 2. |
| Include: Problem As Articulated | Reflect their exact language back: "You mentioned [quote from discovery]." |
| Include: MetaFactory Mapping | "What we discussed addresses [specific component of their problem]." |
| Include: Milestone 1 Summary | Name, deliverable, and investment for Milestone 1 only. Do not present full scope. |
| Include: Case Study Asset | One case study matched to their industry, revenue range, or specific objection raised. |
| Include: Next Step Link | Direct calendar link with a specific call purpose stated. Not "let me know when you are free." |
| CRM Tag | `[POST_CALL_RECAP_SENT]` |

---

## 6.2 48-Hour Reinforcement

*Trigger: 48 hours after post-call recap with no response. Deploy once only.*

| Element | Specification |
|---|---|
| Format | One paragraph. Plain text. No images. No attachments on this touch. |
| Content Structure | Reference their specific pain (from Phase 2) → Introduce one new proof point → Calendar link. |
| Example Logic | "You mentioned [specific problem]. I wanted to share one piece of evidence directly relevant to that: [case study stat or result]. Here is the link if now makes sense: [link]." |
| Tone Rule | Direct and specific — not a check-in. Not "just following up." Always reference something concrete. |
| CRM Tag | `[48HR_FOLLOWUP_SENT]` |

---

## 6.3 Case Study Injection Rules

> *One case study per communication. Never stack more than one per message.*

| Injection Trigger | Case Study Type to Deploy |
|---|---|
| Structural objection raised during call | Case study demonstrating system build speed and operational independence. |
| Economic objection raised during call | Case study with specific, quantified ROI data. |
| Identity objection raised during call | Case study featuring a quote from a relationship-based seller who retained their style post-deployment. |
| Post-call recap (standard) | Case study matched to prospect's industry or business model. |
| 48-hour reinforcement | Case study matched to the specific problem articulated in Phase 2. |
| Victor's strategy validation | Highest-credibility case study available — closest match to prospect's exact situation. |

---

## 6.4 Scarcity Logic

### Legitimate Scarcity — Deploy Only When True

- Victor's strategy validation slots are limited to [X] per month. Communicate specific availability.
- MetaFactory deployment capacity is limited by the milestone-based work structure. If a waitlist exists, communicate it specifically.

### Scarcity Communication Format

> "Currently, strategy validation sessions are available on [specific dates]. If this is not the right time for your business, the next availability would be [date]. I want to ensure we build when you are operationally ready — not because of a deadline."

> ⛔ **PROHIBITED:** Manufactured scarcity of any kind. No artificial deadlines, false urgency, or countdown timers. These destroy authority and disqualify credibility permanently.

---

## 6.5 Escalation to Implementation

*Trigger: Prospect confirms Milestone 1 investment. Remove from all sales follow-up sequences immediately.*

| Escalation Action | Specification |
|---|---|
| Send Milestone 1 Deliverable Brief | What will be built, what will be delivered, and the success criterion for Milestone 1. |
| Schedule Milestone 1 Kickoff Call | Within 72 hours of payment confirmation. |
| Send Data Intake Form | ICP freeze confirmation, current sales data, existing assets, team contacts. |
| CRM Status Update | `[STATUS: IMPLEMENTATION]` — removes from all sales sequences. |
| Remove from Follow-Up Sequences | Prospect is now a client. No further sales communication. |

---

# VII. METRICS & CONTROL LAYER

> Metrics are not vanity indicators — they are diagnostic instruments. Every metric below triggers a specific action when it falls outside its benchmark range.

---

## 7.1 Close Rate Benchmarks

| Stage Transition | Target Range | Action if Below Target | Action if Above Target |
|---|---|---|---|
| Pre-Qualification → Strategy Call | 20% – 35% | Audit ICP match quality or tighten pre-qual scoring criteria. | Investigate whether quality standards are being maintained. |
| Strategy Call → ADVANCE Disposition | 40% – 60% | Audit Phase 2–3 discovery quality; review objection architecture. | Document what is working and standardise it. |
| ADVANCE → Strategy Validation (Victor) | 70% – 85% | Audit post-call follow-up quality and case study relevance. | Maintain. No action required. |
| Strategy Validation → Close | 60% – 80% | Audit Victor's validation call structure and close variant selection. | Document close variant patterns and codify. |
| **Overall Pre-Qual → Close** | **8% – 15%** | **Full MetaPlaybook audit required. Root cause analysis across all stages.** | Investigate capacity constraints. May need to tighten ICP. |

---

## 7.2 Stage Drop-Off Analysis

> *Conduct weekly. Identify the specific stage where volume is being lost. Every drop-off points to a specific system failure.*

| Drop-Off Location | Root Cause and Corrective Action |
|---|---|
| Pre-Qualification | ICP mismatch at top of funnel. Tighten targeting criteria or intake form questions. |
| Phase 2: Discovery | Problem not being surfaced. Audit discovery question sequence and delivery. |
| Phase 3: Qualification | Economic mismatch. Adjust budget readiness signal scoring thresholds. |
| Phase 4: Positioning | Category mismatch. Audit positioning language and MetaFactory definition. |
| Phase 5: Commitment | Objection not resolved. Update objection architecture with new response logic. |
| Post-Call (no response) | Follow-up quality or timing issue. Audit 0–2hr recap and 48hr reinforcement. |
| Strategy Validation → No Close | Close variant not matched to prospect type. Review variant selection criteria. |

---

## 7.3 Objection Frequency Tracking

| Tracking Field | Specification |
|---|---|
| Log Format | Objection text \| Phase in which it appeared \| Response deployed \| Resolution (Y/N) |
| Review Cadence | Weekly by AI (automated report) \| Monthly by Victor (30-minute review) |
| Threshold for Action | Any objection appearing 3+ times per week triggers a response logic review. |
| Update Protocol | Revised response is encoded into the Objection Architecture within 48 hours of review. |
| Pattern Signal | New objection type not previously catalogued triggers an immediate MetaPlaybook update. |

---

## 7.4 Authority Leakage Detection

### Authority Leakage Occurs When

- Victor is brought into calls earlier than Strategy Validation stage.
- Prospects ask for Victor by name before qualification is complete.
- AI or rep cannot resolve objections without escalating to Victor.
- Victor is spending more than 2 hours per week in unqualified conversations.

### Detection Signals

| Detection Signal | Measurement Method |
|---|---|
| `[VICTOR_EARLY_ENTRY]` CRM Tag | Set manually by rep or AI when Victor appears before qualification is complete. |
| Victor Time Tracking | Logged call time: qualified vs. unqualified conversations — weekly comparison. |
| Involvement Ratio | Victor's sales hours / total sales hours — target ceiling: **20%.** |

### Leakage Response Protocol

1. Trace leakage to the specific stage where it originated.
2. Update the Qualification System or Objection Architecture at that stage.
3. Re-test the correction for 2 weeks with live leads.
4. Validate improvement against the involvement ratio metric.
5. If improvement not achieved within 4 weeks: full stage audit required.

---

## 7.5 Feedback Loop to MetaPlaybook

### Review Cadence

| Cadence | Owner and Scope |
|---|---|
| Weekly | AI system (automated report): close rate by stage, objection frequency log, drop-off analysis. |
| Monthly | Victor: 30-minute review of Stage Drop-Off + Authority Leakage data. Report auto-generated. |
| Quarterly | Full MetaPlaybook audit: ICP review, price architecture review, close variant performance, section-by-section validation. |

### Update Triggers

Any of the following conditions triggers a MetaPlaybook update:

- Close rate falls below benchmark for 3 consecutive weeks.
- New objection type emerges — 3+ occurrences before being catalogued.
- ICP definition needs adjustment (discovery data reveals pattern mismatch).
- Victor's validation close rate drops below 60% for 2 consecutive months.
- Market condition shifts that affect the urgency trigger landscape.

### Update Protocol

| Step | Action |
|---|---|
| 1. Flag | AI flags the anomaly with supporting data in the weekly automated report. |
| 2. Review | Victor reviews the flagged issue within 48 hours of report delivery. |
| 3. Revise | Relevant section is revised and the correction is encoded. |
| 4. Test | Revised section is deployed and monitored for 2 weeks before being confirmed. |
| 5. Version | MetaPlaybook version is incremented: CHTSM v1.0 → v1.1, etc. |
| 6. Synchronise | All AI prompts, decision trees, and CRM scoring logic updated simultaneously. |

---

# APPENDIX: VALIDITY CHECKLIST

> This MetaPlaybook is valid if ALL of the following conditions are true. If any condition fails, the relevant section must be revised before deployment.

| Success Criterion | Status |
|---|---|
| A trained sales rep can execute the full call protocol (Phases 1–5) without founder presence. | VALIDATE BEFORE DEPLOYMENT |
| An AI system can pre-qualify leads using Section III scoring criteria. | VALIDATE BEFORE DEPLOYMENT |
| A CRM can tag lead readiness from the qualification and disposition logic. | VALIDATE BEFORE DEPLOYMENT |
| Founder appears ONLY at strategy validation and final close. | VALIDATE BEFORE DEPLOYMENT |
| Every objection in Section IV has a mapped response that does not require founder input. | VALIDATE BEFORE DEPLOYMENT |
| Metrics in Section VII are live and generating weekly reports. | VALIDATE BEFORE DEPLOYMENT |
| All milestone deliverables have defined, objective success criteria. | VALIDATE BEFORE DEPLOYMENT |
| No narrative fluff. No vibes-based logic. Every section is encodable into a prompt or decision tree. | VALIDATED BY DESIGN |



## Deployment Certification Block

> **Deployment is not authorized until all boxes are checked and logged.**

```
DEPLOYMENT CERTIFICATION CHECK — MTB-CHTSM v1.1

□ Asset ID registered (MP-DAC-CHTSM-001)
□ Risk Tier assigned (R3 — Revenue-Critical)
□ AI Skills mapped (SK-AI-QUAL-001 through SK-AI-VERSION-009)
□ Human Skills mapped (SK-HU-DISC-001 through SK-HU-AUDIT-007)
□ CRM tagging schema validated
□ AI prompts synchronized with MetaPlaybook logic
□ Control dashboard live and reporting
□ Founder involvement confirmed < 20%
□ Weekly automated report active
□ Registry entry confirmed in REG-CHANGES
```
---

> **END OF CANONICAL HIGH-TICKET SALES METAPLAYBOOK — MTB-CHTSM v1.1**
>
> Human Owner: Victor Heredia | Asset: Demand & Conversion MetaFactory Deployment
>
> masterplaybooks.com | Confidential | Do not distribute without written authorisation