This supersedes the original Mirror Method thread and the Adaptive Mirror 2 expansion. Nothing has been dropped — where the two disagreed, or where market and legal review changed the answer, the change is marked rather than quietly applied.
May 2026 thread. A personalised sales page assembled from a prospect conversation. Four mirror layers, JVZoo funnel, launch math.
The expansion. Multi-channel input, universal profile, fifteen assets, nine modes, seventeen verticals, realtime-native architecture.
Both, merged, plus the competitive scan, the legal register, corrected launch math and a build plan with kill criteria.
| Decision | Resolution |
|---|---|
| Emotional Mirror | Removed. Replaced by a Proof Mirror plus register-matching inside the Language Mirror. Emotional-state inference from free text is the highest-risk, lowest-value feature in the spec. §03 |
| Budget Mirror | Retained but hard-bounded: option hierarchy and presentation may change; the numbers may not. Price never varies by person. §03 |
| Phone Mirror | Kept as a channel, removed from the launch funnel. Imported transcript delivers most of the value with none of the telecom exposure. §02, §15 |
| Mirror Memory | Kept, but derived-codes-only by default, opt-in for verbatim, and off entirely for health-adjacent verticals. §07 |
| Positioning lead | Leads on component re-composition, not headline personalisation. Headline generation is a funded, crowded category; re-composition is empty. §01 |
| Vertical scope | Seventeen verticals retained as a map, but real estate, automotive and recruitment are reclassified as regulated markets needing their own legal workstream. §09 |
| Launch math | MRR projection corrected — the v1 figure conflated MRR with ARR and was out by roughly an order of magnitude. §16 |
Avoid describing this as an AI chatbot, an AI landing-page generator, an AI proposal writer, or generic personalisation software. All four are crowded, commoditised categories with an established price ceiling.
The branded mechanism stays: The Mirror Method™ — Listen → Understand → Mirror → Create → Route → Remember.
It sits on pages that already exist. No new URLs, no new funnel, no changes to an email sequence.
Three or four questions and it's finished. No persona, no name, no ongoing relationship. It asks, then it leaves.
A human wrote every commercial sentence. The engine decides which of them this person sees. That distinction is the product.
Four interfaces, one backend intelligence.
Inbound or outbound AI phone conversation over SIP.
"Talk to AI" — browser voice, no phone number required, no telecom.
Website chat or embedded text conversation.
An existing human or AI sales-call transcript, processed after the fact.
Every conversation, on any channel, is converted into one structured profile. This single schema is what lets the same engine serve local business, agency, affiliate, SaaS, high-ticket, professional services and beyond.
| Signal | What AI Mirror understands | v3 handling |
|---|---|---|
| Situation | What is happening now? | store |
| Problem | What problem needs solving? | store |
| Desired outcome | What result does the prospect actually want? | store |
| Motivation | Why does that result matter? | store |
| Priority | What matters most in the decision? | store |
| Timeline | When do they need the result? | store |
| Budget sensitivity | What financial constraints or ROI concerns exist? | routing only |
| Objections | What is stopping them moving forward? | store |
| Preferences | What do they prefer or want to avoid? | store |
| Awareness | Researching, comparing, solution-aware, product-aware, ready? | store |
| Intent | Low, medium or high purchase/action intent. | store |
| Decision criteria | What will make them choose one option over another? | store |
| Exact language | Phrases and vocabulary worth reflecting. | session only |
| Sentiment | Sceptical, worried, excited, impatient, uncertain. | routing only |
| Best next action | Buy, book, quote, compare, apply, learn, follow up. | store |
Silent mode in §03.
The Brain takes the profile and answers ten questions:
Implemented as structured extraction plus an editable decision and routing layer — never an LLM freestyling the entire commercial journey.
Each layer reads a different signal and changes a different thing. They run separately, so a weak answer on one doesn't degrade the others.
| Layer | What changes | Defensibility |
|---|---|---|
| Language | Headline, bullets and explanations reflect the customer's natural vocabulary and register. | Low — copyable |
| Problem | Focuses on the problem actually described, not the one the page assumed. | Medium |
| Goal | Frames the solution around the stated desired outcome. | Medium |
| Awareness | Controls the balance of education vs comparison vs direct offer. | Medium |
| Objection | Surfaces only the relevant handlers, FAQs and reassurance — and plants none of the others. | Highest |
| Proof | Selects the testimonial, case study, review or example that matches their situation. | High |
| Offer | Selects or emphasises the right service, package, product or bonus. The offer itself moves. | Highest |
| Timeline | Adjusts scheduling, urgency and implementation framing to their stated date. | Medium |
| Budget | Changes which option leads, and how financing is presented. Never the number. | Bounded |
| CTA | Buy, book, quote, apply, compare, watch, save, talk. | Medium |
| Format | Page, proposal, report, recommendation, quote, comparison or summary — the asset type changes. | Highest |
AI Mirror should not blindly repeat sensitive or awkward prospect language. Every asset declares a reflection strength per field:
Safe business language quoted closely. "the work that pays the bills"
Meaning preserved, wording polished. Reads written rather than transcribed.
The concern is addressed without obvious repetition. Used for anything embarrassing.
Signal routes the asset and never appears in visible copy. Default for sentiment.
Silent as the default for any field that could carry health, financial-distress or protected-class content, and make the escalation to Exact a deliberate, per-field decision made by whoever authors the pack. A single sensitive: true flag on the extraction object should force the whole asset down to a lower personalisation tier and suppress verbatim quoting entirely.
This is the core expansion from v1. The product is not a landing-page generator — it is an asset-generation layer, and the asset type is itself a personalisation decision.
A personalised sales, recommendation or follow-up page.
Current situation · desired outcome · recommended solution · scope · deliverables · timeline · relevant proof · pricing options · objection handling · approval step.
An individualised estimate experience. Strongest in home services and B2B services.
Answers: based on what you told us, what should you choose or do next?
Services, packages, products, affiliate offers, properties or alternatives, weighted to the prospect's stated priorities.
A diagnostic, assessment, audit or consultation report.
The conversation turned into a practical personalised roadmap.
A structured scope of work generated from a discovery conversation.
The most appropriate service, package or product, with the right framing around it.
For affiliates: the three to five bonuses most valuable to that specific buyer, out of twenty.
The right service, the preparation information they need, relevant availability and CTA.
Creates or pre-populates an application from the conversation.
Personalised email, SMS, messaging-app message or follow-up page referencing what was actually discussed.
A polished prospect-facing summary of the conversation and the agreed next steps.
Internal sales intelligence: lead summary, opportunity score, main needs, objections, decision criteria, buying readiness, recommended next action, CRM notes.
The strongest single capability in the product. From one agency discovery call:
Industry is a content pack (§08). Mode is what the engine actually does. Nine modes cover the commercial surface.
| Mode | Produces | Where it earns its keep |
|---|---|---|
| Mirror Sell | Sales pages, offer pages, adaptive sales experiences | The demo asset. Fifteen seconds, no context needed. |
| Mirror Propose | Proposals, scopes, pricing presentations | The agency flagship. Turns a Tuesday call into a Tuesday-afternoon send. |
| Mirror Recommend | Product, service, package and affiliate recommendations | Affiliates and catalogue owners. Includes recommending not buying. |
| Mirror Quote | Quotes and estimate experiences | Home services and B2B. Competes on legibility, not on being cheapest. |
| Mirror Compare | Products, plans, services or options | The highest-converting affiliate format, written for the actual reader. |
| Mirror Report | Audits, assessments, diagnostics | The foot-in-the-door for local consultants. Finally scales. |
| Mirror Plan | Roadmaps and action plans | Delivered with the purchase, it is the cheapest refund reduction available. |
| Mirror Follow | Follow-up pages, messages, continuations | A continuation engine, not an email writer. See §06. |
| Mirror Book | Appointments, demos, consultations, service bookings | Fewer no-shows, and no first ten minutes re-running discovery. |
This is what turns the product from conversation → content generation into conversation → understanding → asset selection → personalisation → next action.
suppress([pricing, packages, close_cta]) is more persuasive than any amount of output.
Follow-up is a first-class mode, and the route depends on what happened next.
| What happened | What the engine sends |
|---|---|
| High intent, no action | Concise reminder plus the direct proposal, booking or payment CTA. |
| Medium intent, unresolved objection | The case study, comparison, proof or FAQ specific to that objection. |
| Low intent | Education, recommendation or a low-friction next step — not another push. |
| Quote or proposal viewed, not accepted | A follow-up built around the sections actually viewed, the open questions and the known objections. Optionally an offer to continue by voice. |
| Prospect replies | The reply becomes new Mirror data, updating the same profile, proposal and next-action logic. |
A follow-up is not always another email. The engine may decide the right next move is a revised proposal, a simplified quote, a comparison page, a relevant case study, a short personalised video script, a booking page, another live conversation, or a "here's what changed since we spoke" page. It is a continuation engine.
Memory is what turns a one-time asset generator into a persistent adaptive customer journey. It is also the single highest-risk feature in the specification, so it ships with constraints.
A roofing prospect previously said they had storm damage, were worried about insurance, and did not want to be pressured into a replacement. When they return, the engine should continue from that context — not open with "how can I help you?".
goal 10 qualified implant consults/mo previous_attempt paid social main_concern lead_quality budget_band ~$3,000/mo timeline next_month intent medium_high open_question proof_of_qualification
| Prospect-facing | Seller-facing |
|---|---|
| Proposal | Lead summary |
| Page | Opportunity score |
| Quote | Needs analysis |
| Recommendation | Objections |
| Comparison | Decision criteria |
| Report | Recommended follow-up |
| Action plan | CRM fields |
| Booking | Sales coaching notes |
This is the architectural decision that makes every new vertical a content project rather than an engineering project — and it is also the recurring revenue and the defensibility.
LAYER 3 — CAMPAIGN owned by the customer their offer, links, proof, brand, their 3–4 questions LAYER 2 — VAULT owned by you, sold by niche master templates · slot maps · component libraries · fallback ladders LAYER 1 — ENGINE built once, never rebuilt conversation · extraction · routing · assembly · render · moderationThe engine knows nothing about dentists, roofers or affiliates. It knows slots, components, codes and tiers. A new vertical is a new pack. Never an engine change. If a vertical requires an engine change, the pack architecture is wrong.
The signals each conversation surfaces, and the assets each one should produce. Treat this as a map of where packs could go — not as a roadmap commitment.
The "Should I Buy?" advisor can credibly recommend not buying when fit is poor. It costs a percentage of sales and buys a list that opens the next twelve emails.
v3: pain and anxiety signals are health data about an identified person. Memory off by default, verbatim never stored, and a covered-entity determination required before this pack ships.
A seven-person sales team worried about inconsistent follow-up sees the workflow, features and proof for follow-up automation and management visibility — not the full feature list. v3 note: this is Fibr's and Mutiny's home turf at $479/mo to $45k/yr with procurement attached. Serve it opportunistically; don't wedge here.
High intent → offer and buy CTA. Medium → comparison, FAQ, proof. Low → replay, education, reminder. Replay traffic is the largest single wasted asset in info products.
v3: "schools" and "location preference" as personalisation inputs is textbook steering exposure. Needs its own legal workstream before any pack is built.
Strong demo vertical: seasonality lets the engine volunteer bad news — "peonies, June only" — which is the cleanest available answer to "isn't this just AI slop?"
v3: a candidate summary carrying a score is an automated employment decision tool. Published bias audits are required in some jurisdictions. This is a separate product, not a pack.
Whoever we sell to buys the engine, not the vertical. These three are the ones with money, urgency and an existing habit of buying tools.
Discovery calls, proposals, retainers. Highest willingness to pay, longest cycle, and the only one with a real recurring-payment habit. Escapes the $47 ceiling.
Bonus pages, review pages, a list. Buys fast, refunds fast, competing against four hundred identical bonus pages. Cheapest acquisition.
Webinars, VSLs, applications. Their real enemy isn't conversion — it's refunds and non-completion. Best retention story.
| Mode | Produces | Agency | Affiliate | Creator |
|---|---|---|---|---|
| Mirror Sell | Personalised page | ●●● | ●●● | ●●● |
| Mirror Propose | Proposal / scope | ●●● | ● | ●● |
| Mirror Quote | Estimate / configuration | ●●● | ●● | ●● |
| Mirror Recommend | What to choose | ●● | ●●● | ●●● |
| Mirror Compare | Weighted comparison | ●● | ●●● | ●●● |
| Mirror Report | Audit / diagnostic | ●●● | ●● | ●●● |
| Mirror Plan | Roadmap / study plan | ●●● | ●● | ●●● |
| Mirror Follow | Continuation | ●●● | ●●● | ●●● |
| Mirror Book | Booking | ●●● | ● | ●● |
| Layer | Agency | Affiliate | Creator |
|---|---|---|---|
| Language | "tyre kickers" → "You're not short of enquiries. You're short of the right ones." | "building every report by hand" → "Stop building every report by hand." | "bought three courses, finished none" → "You don't need another course. You need to finish one." |
| Proof | Dentist sees the dental case at a matching practice size. Seven-figure logos suppressed. | Five-client operator sees the four-client testimonial, not the $2M guru. | Identity proof — the nurse retraining sees the student who was a nurse. |
| Offer | "10 implant consults" vs "3 chairs full" → two different service packages. | Bonus stack swaps 3-of-12 by stated goal. | Curriculum re-orders; default tier flips from self-study to cohort. |
| Objection | "burned on retainers" → fixed-scope clause. Price handler suppressed. | "another dashboard to learn" → setup call only. 1 of 14. | "I never finish anything" → completion mechanics. Lifetime access suppressed — it's a negative to this buyer. |
Adaptive Mirror must not wait for the conversation to finish and then generate. Mirror State, routing and asset composition update continuously while the prospect is still talking, so the finished asset can appear in a split second.
Support realtime engines through an adapter, never a hard dependency on one vendor.
RealtimeProvider connect() sendAudio() receiveAudio() receiveTranscript() registerTools() receiveToolCall() interrupt() close() implementations GeminiLiveProvider · OpenAIRealtimeProvider · FutureRealtimeProvider
Campaigns can eventually support Auto — the engine selected per conversation on channel, language, cost, latency, complexity and availability.
The model isn't only speaking. While the conversation runs, it updates structured commercial understanding through narrow tool calls:
update_mirror_profile() set_primary_problem() set_goal() set_timeline() set_budget_context() add_objection() set_decision_criteria() set_intent() select_offer() select_proof() update_proposal_section() set_next_action()
Prospect: "We want more implant patients."
industry = dental primary_goal = more implant cases
Later: "We tried Facebook ads but most of the leads weren't serious."
previous_attempt = facebook_ads main_objection = lead_quality decision_priority = qualified_implant_prospects
The proposal, page or recommendation updates during the conversation rather than after it.
The realtime engine is the listener, conversational brain and signal extractor. It should not spend the session writing a long proposal from scratch.
CHAT / WEBRTC / PHONE
↓
REALTIME CONVERSATION ENGINE
↓ tool calls
MIRROR STATE
↓
ROUTER + APPROVED LIBRARY + ASSET COMPOSER
↓
PROPOSAL / PAGE / QUOTE / REPORT / RECOMMENDATION
↓
INSTANT FINAL REVEAL
Every asset has a predefined schema, and sections fill as answers arrive:
Proposal ├── Current Situation ✓ / building ├── Desired Outcome ✓ / building ├── Recommended Solution ✓ / building ├── Deliverables preset ├── Relevant Proof selected dynamically ├── Timeline ✓ / building ├── Pricing approved / preset └── Next Step ✓ / building
{
"profile": {},
"intent": {},
"recommended_route": "proposal",
"recommended_offer": "implant_growth",
"selected_proof": ["case_17"],
"selected_objections": ["lead_quality"],
"asset": {},
"completion": 0.92
}
The frontend subscribes to Mirror State and updates visually as information arrives.
Not a fixed questionnaire. The agent knows which fields the selected outcome still needs:
Problem ✓ Goal ✓ Timeline ? Budget ? Objection ✓ Intent medium
It then asks the smallest number of further questions required to complete the asset and choose the route.
Approved component libraries rather than generating every commercial statement.
Layouts · services · pricing · deliverables · guarantees · proof · allowed offers · CTA structures
Situation summary · goal wording · reasoning · connective copy · natural reflection of the prospect's language
Proof, offers, bonuses, FAQs and templates are retrieved as soon as the profile has enough — not after the call.
industry = dental · service = implants · problem = lead_quality → retrieve matching case studies + objection blocks during conversation
By the time the call ends the system is selecting from already-prepared candidates, not beginning a search.
Proposals, reports and quotes render first as responsive web experiences from Mirror State. PDF export is generated afterwards from the same structured asset.
turn detection → transcript ≤ 300 ms
extraction (streaming, strict JSON) ≤ 900 ms
moderation + confidence scoring ≤ 200 ms
component selection + render ≤ 400 ms
─────────────────────────────────────────
visible update per answer ≤ 1.8 s
This is a kill criterion, not a target. Prove it in a two-week spike on one template before anything else is built. If the loop can't hold 1.8s at p90, the magic doesn't exist and the product should not be built as specified — the entire differentiation is a latency phenomenon.
Do not allow the AI to invent commercial facts. Approved libraries control:
Generative text is used only inside bounded fields.
| Tier | Trigger | What the visitor sees |
|---|---|---|
| T1 | All layers confident | Full mirror — their words, proof, offer, objections |
| T2 | ≥2 layers confident | Soft mirror — goal and objections mirrored, generic headline |
| T3 | Thin or weak answers | Segment-level page |
| T4 | Junk · abuse · injection · timeout · sensitive flag | The customer's ordinary page, unchanged |
Output generated at the end of the conversation and sent by SMS, email or link.
The asset visibly assembles during the conversation. This is the demo mechanic, and it is the reason the clip travels.
This section did not exist in either source document. It is the one most likely to change what gets built, so it sits before the money and the plan rather than after them.
| Risk | Assessment and mitigation |
|---|---|
| Price / buyer mismatch | The load-bearing risk. Building runtime infrastructure comparable to a $479/mo enterprise product and selling it into a channel whose front-end mode is ~$17 and whose buyers have no recurring-payment habit. Mitigation is the agency motion (§16), built into the launch rather than bolted on after. |
| Personalisation theatre | The number-one refund driver. If output is "insert first name plus one phrase", buyers see through it. The Vault is the answer — and the 580-component authoring load in §08 is not padding, it is the product. |
| Latency | Not a risk — a kill criterion. Answered in two weeks (§11, §17). |
| Adversarial input | Strict JSON schema does most of the work; the four-tier ladder does the rest. Add an adversarial suite as a phase gate. |
| Fast-following | Positioning is copyable within a launch cycle. The Vault is not — 580 hand-written components per pack is a real moat, just not a technical one. |
High-volume, statutory-damages, private-right-of-action territory in some US states, with an active demand-letter industry. The specific hook is whether an AI vendor counts as a third party — which turns on whether they may use the data for their own benefit, including model training. Fix: contractual carve-out plus pre-chat consent.
An AI presenting as helpful discovery while optimising for conversion is the textbook fact pattern regulators have begun describing. Fix: one plain purpose sentence, in-widget. Terms-of-service burial does not count.
Any agency, reseller or white-label tier carrying an income representation likely triggers disclosure-document obligations. Enforcement in this exact market has produced eight-figure judgments and permanent bans. Fix: sell capability and sub-accounts. Zero income claims anywhere.
A free-text "biggest problem" box will surface illness, burnout and financial ruin across any real population, and a dataset containing one sensitive item can be treated as sensitive in its entirety. Fix: sensitive flag forces a lower tier and suppresses verbatim.
Multiple regimes now require telling people they're talking to an AI at first interaction. Cheap, and the safe harbour is usually absolute. Fix: in-widget label.
Countdown timers implying scarcity that isn't real are explicitly named in enforcement guidance. Fix: if a template ships a countdown, the deadline must be real — and the engine must never generate one where no deadline exists.
Not legal advice. Items in this section need counsel review before launch, and specifically before any agency or reseller page goes live.
The launch channel is the cheapest customer acquisition in the world for this buyer and the worst revenue model for this product. Use it for what it's good at.
Purpose: 2,000–3,000 buyers, a case-study base and JV relationships. Not the revenue event.
| Tier | Price | Contents |
|---|---|---|
| FE | $47 | Engine + 5 done-for-you master templates + 3 campaigns + 1,000 conversations/month |
| OTO 1 | $97 | Mirror Vault — 30 professionally written master templates. Highest take-rate; where the margin lives. |
| OTO 2 | $147 | Pro — unlimited campaigns and conversations, in-browser voice, multilingual |
| OTO 3 | $97 | Mirror Intelligence — aggregate voice-of-customer analytics across all their traffic |
| OTO 4 | $197 | Agency — 20 sub-accounts, commercial rights, white-label |
| OTO 5 | $67 | Live training — template authoring and personalisation mastery |
| Bundle | $397 | Everything |
Consultants and agencies paying monthly to run Mirror on client sites.
The pitch is a ratio, not a feature: a consultant paying $197 runs it on ten client sites at $300/month each.
$49 / $99 / $249 per month, self-serve. Price-comparable to the mid-market personalisation tools and massively undercutting the enterprise ones. Do not open this until the Vault covers three or more verticals — a thin vault plus self-serve signup produces churn and bad reviews.
1,000/mo resets; overage is a $27/mo top-up. Usage-based, so it only bills people getting value.
One new niche pack per month for subscribers. Highest-margin revenue in the stack.
Accumulated objection data is the switching cost.
Anyone buying the agency tier is a Motion B prospect. Onboard personally — that cohort is worth 20× an FE buyer.
| Scenario | FE buyers | Retain @12mo | Month-12 MRR | ARR run-rate |
|---|---|---|---|---|
| Conservative | 2,000 | 10% | ~$9.4K | ~$113K |
| Base | 2,500 | 15% | ~$17.6K | ~$212K |
| Upside | 3,500 | 22% | ~$36K | ~$434K |
Three packs across three very different commercial models is the proof that the engine is genuinely universal.
| Phase | Weeks | Output | Go / kill criterion |
|---|---|---|---|
| 0 — Latency spike | 2 | One template, one campaign, end to end, instrumented | Per-answer visible update ≤1.8s at p90. If it can't be hit, stop. |
| 1 — Engine MVP | 4 | Extraction schema, routing, assembly, four-tier fallback, moderation, campaign wizard | Adversarial suite renders T4 100% of the time |
| 2 — Vault v1 | 4 (parallel from wk 3) | 5 master templates × ~580 components, written by a real DR copywriter | Blind test: 10 marketers can't pick T1 output from hand-written |
| 3 — Closed beta | 4 | 20–30 existing buyers running real traffic | ≥15 usable case studies with before/after numbers |
| 4 — Launch assets | 4 (overlaps 3) | Demo video, real-world landing mockup, sales page, JV kit | A-tier JV commitment secured |
Split screen. Left: live chat, WebRTC or phone conversation. Right: Mirror Profile and assets appearing progressively.
Then repeat quickly with an affiliate or local-service example.
| Decision | Recommendation |
|---|---|
| Which motion leads? | Launch on affiliate for acquisition, with the agency tier fully built and priced at launch. Simultaneous, not sequential. |
| Standalone or a tier inside the existing product? | Standalone, with the hybrid beta — beta free with existing buyers in exchange for case studies, then launch publicly with 30–50 in hand. Solves the day-one credibility problem that kills new launches. |
| Does phone ship? | Not in this funnel. Replace with Mirror Intelligence. Revisit as a separate product with its own compliance posture. |
| Is the Emotional Mirror out? | Yes — replaced by the Proof Mirror. Better commercially, better across verticals, removes most of the exposure. |
| Vault pack #2? | Local services. It's the audience the portfolio already owns and the doorway to Motion B pricing. |
| Memory on or off at launch? | On, derived-codes-only, with a visible clear control. Verbatim retention off and consent-gated. Off entirely for health-adjacent packs. |
| Launch quarter? | Q4 2026 or Q1 2027 — decided once Phase 0 returns a real latency number. |
| # | Action | Why it's in this position |
|---|---|---|
| 1 | Phase 0 latency spike | Highest-information action available. Two weeks. Everything else is contingent on it. |
| 2 | Build the real-world landing mockups | Cornerstone asset for JV pitches and Motion B validation. Doesn't wait on the build. |
| 3 | Hire the DR copywriter; freeze slot maps | Four weeks of authoring on the critical path. Starting late is the most likely cause of a slipped launch. |
| 4 | Counsel review | Model-vendor training terms, in-widget disclosure copy, retention default, agency-page claims. Cheap now, expensive after launch. |
| 5 | Open the beta list | 20–30 existing buyers, four weeks of real traffic, case studies as the price of entry. Must be running before the JV window opens. |
| 6 | JV shortlist and first pitches | 60–90 days out means now, on the strength of the mockup, before the build finishes. |
| 7 | Lock the launch quarter | Once #1 returns a number. |
| Area | v1 — Mirror Method | v2 — Adaptive Mirror 2 | v3 — this document |
|---|---|---|---|
| Scope | Personalised sales page | Conversation-to-Outcome Engine, 15 assets | Unchanged from v2, with the engine / vault / campaign split stated as an architectural rule |
| Channels | Browser chat, phone in OTO3 | Chat, WebRTC, phone, transcript | Same four. Transcript promoted to first; phone out of the launch funnel |
| Layers | 4 (Linguistic, Emotional, Goal, Objection) | 11 layers + reflection strength | 11 minus Emotional; Proof elevated; Budget hard-bounded to presentation only |
| Positioning lead | Headline mirroring | Multi-asset generation | Component re-composition — headline generation is a funded, crowded category |
| Memory | Not present | Persistent cross-session, verbatim | Derived codes only by default; verbatim consent-gated; off for health-adjacent packs |
| OTO 3 | Phone Call Mirror (BYOK) | — | Mirror Intelligence — novel, free to build, creates the switching cost |
| Business model | One launch ladder | Not addressed | Three motions: launch / agency recurring / SaaS |
| MRR projection | $200K–$500K MRR by year end | — | $9K–$36K from launch buyers. v1 conflated MRR with ARR |
| Timeline | 6–10 weeks | — | 13–16 weeks. Copywriting is the critical path, not code |
| Latency | ">3s and the magic dies" | "Split second" | Budgeted: ≤1.8s p90 per answer, as a kill criterion |
| Lift claims | Implied transformational | "Measure real lift" | +10% to +40%, plus a permanent holdout control shipped as a product feature |
| Risk register | 5 product risks | Not addressed | Full product, market and regulatory register (§15) |
| Verticals | Affiliate only | 17 industries | 17 retained; 4 reclassified as regulated markets needing their own workstream |
| Precedent | Not addressed | Not addressed | Two venture-backed teams shipped this mechanic and left. Their failure mode is now a design constraint |
Partner kit — features, benefits, angles, hooks, full use-case book.
v1 interactive demo — four scenarios, dual mode.
v2 realtime demo — channels, sources, tool calls, routing.
Real-world landing mockups. Five-email promo sequence per angle. Pack authoring guide. Holdout measurement spec. Counsel memo.
Whether the 1.8-second loop holds at p90 on real infrastructure. Two weeks of work answers it, and it changes everything downstream.
Adaptive Mirror v3 — master product document. Supersedes the original Mirror Method thread and the Adaptive Mirror 2 expansion; both are preserved in full within it. Prices, tiers, timelines and vertical priorities are working assumptions, not commitments. Figures cited for prior launches are historical and are not projections. Nothing in this document is legal advice; §15 requires counsel review before launch.