{"description":"Structured conversion copy system for future agents, including source boundaries, principles, copy types, weak/strong examples, workflow, anti-patterns, QA gates, and pass criteria.","objective":"Give a future agent enough structure to start from the main URL and understand how to inspect, plan, build, validate, and improve a serious website without needing prior chat context.","conversion_copy":{"objective":"Teach future agents how to write clear, proof-aware, conversion-focused website copy without copying another creator's proprietary language.","why":"Strong site copy is not just tone. It clarifies the market, names the painful problem, makes the outcome concrete, explains the mechanism, reduces perceived risk, proves claims, and gives the next step. Agents need that sequence spelled out so they do not ship vague, clever, unsupported, or visually attractive copy that fails to convert.","studyDate":"2026-06-07","sourceStudy":{"name":"Alex Hormozi / Acquisition.com public conversion-copy pattern study","sourceBoundary":"Use these sources to learn principles and page patterns. Do not copy proprietary copy, income claims, testimonials, guarantees, course structures, or brand language into client work.","sources":[{"title":"Acquisition.com homepage","url":"https://www.acquisition.com/","usefulFor":"Offer-first page framing, founder proof, free training positioning, and direct CTA structure."},{"title":"Acquisition.com training library","url":"https://www.acquisition.com/training","usefulFor":"Lead magnet hierarchy, course naming, free-value positioning, and workshop escalation."},{"title":"Acquisition.com Alex Hormozi bio","url":"https://www.acquisition.com/bio-alex","usefulFor":"Credibility sequencing, business history, and expertise claims tied to specific accomplishments."},{"title":"Acquisition.com books page","url":"https://www.acquisition.com/books","usefulFor":"Authority positioning, book ecosystem, practical education promise, and proof stacking."},{"title":"Acquisition.com lead generation course","url":"https://www.acquisition.com/training/leads","usefulFor":"Ethical disclaimer language, outcome boundaries, education versus guarantee separation, and stepwise training structure."},{"title":"ACQ AI","url":"https://ai.acquisition.com/","usefulFor":"AI-assistant positioning, model/tool trust cues, grounded-answer claims, and advisor-in-your-pocket framing."},{"title":"ACQ Vantage","url":"https://vantage.acquisition.com/","usefulFor":"Ecosystem offer architecture across AI tools, founder network, workshops, playbooks, pricing tiers, referral economics, qualification, and disclaimers."},{"title":"Acquisition.com store and $100M book ecosystem","url":"https://shop.acquisition.com/","usefulFor":"Book-to-training-to-workshop ladder, proof stacking, implementation-plan framing, and productized education copy."},{"title":"The Lost Chapter: Your First Avatar","url":"https://acquisition.com/hubfs/The_Lost_Chapter-Your_First_Avatar.pdf","usefulFor":"Avatar selection, best-customer research, qualification, buyer-journey reverse engineering, and quality-over-volume messaging."}]},"supplementaryFrameworks":{"why":"A single source study breeds house-style monoculture. These public-domain copy frameworks give agents independent lenses to cross-check any draft against, so guidance never reduces to one creator's voice.","frameworks":[{"id":"aida","name":"AIDA (Attention, Interest, Desire, Action)","origin":"Classic advertising canon, public domain (attributed to E. St. Elmo Lewis, 1898).","agentUse":"Sequence check: does the page earn attention with relevance (not tricks), build interest with specifics, create desire with proof, and end with one unambiguous action?","failureSignal":"Pages that jump from attention to action with no proof in between."},{"id":"pas","name":"PAS (Problem, Agitate, Solve)","origin":"Direct-response canon, public domain.","agentUse":"Lead check: state the buyer's problem in their words, make its cost concrete without manufacturing fear, then present the mechanism that resolves it.","failureSignal":"Agitation that exaggerates beyond the source evidence, or solutions presented before the problem is established."},{"id":"four-u","name":"4U headlines (Useful, Urgent, Unique, Ultra-specific)","origin":"Direct-response canon (popularized by Michael Masterson), used here as a public scoring rubric.","agentUse":"Score every headline 1-4 on each U; rewrite anything that scores under 3 on Useful or Ultra-specific. Urgency only counts when real.","failureSignal":"Headlines that are clever before clear, or urgent without an operational reason."},{"id":"jtbd","name":"Jobs to Be Done framing","origin":"Public product-strategy literature (Christensen et al.).","agentUse":"Voice check: copy describes the job the buyer is hiring for and the progress they seek, not the vendor's feature taxonomy.","failureSignal":"Feature names doing the work that buyer outcomes should do."}]},"conversionPrinciples":[{"id":"specific-dream-outcome","name":"Make the desired outcome concrete","why":"People evaluate offers by the clarity and value of the future state. Vague outcomes force the reader to imagine the value themselves.","agentCheck":"Can a reader repeat the promised outcome in one sentence without guessing the audience, timeframe, or result type?","weakExample":"We help businesses grow with modern digital solutions.","strongerExample":"Turn your current website into a source-backed sales asset that explains your offer, answers buyer objections, and gives agents clean data to cite.","guardrail":"Do not promise specific revenue, rankings, traffic, or timelines unless source evidence and legal approval support the claim."},{"id":"pain-before-platform","name":"Name the painful problem before explaining the system","why":"Buyers care about the job they need solved before they care about tools, frameworks, or implementation details.","agentCheck":"Does the copy state the buyer's actual constraint before listing features?","weakExample":"Our platform includes dashboards, automation, AI, and analytics.","strongerExample":"When prospects cannot understand what you do, your team keeps re-explaining the same basics and your best proof stays buried.","guardrail":"Avoid fear-based exaggeration. The problem must match actual audience research or source material."},{"id":"value-equation","name":"Increase perceived value and reduce perceived cost","why":"Conversion copy should improve the ratio between desired outcome and likelihood of success while reducing time, effort, delay, and risk.","agentCheck":"Does each section either increase outcome clarity, increase confidence, reduce effort, reduce delay, or reduce risk?","weakExample":"We provide a comprehensive solution for your online presence.","strongerExample":"The starter gives agents a route map, machine endpoints, schemas, examples, and QA commands so they can understand the site before touching implementation.","guardrail":"Do not hide effort. If the offer requires client work, name it clearly and make the sequence manageable."},{"id":"offer-stack","name":"Show the offer as a bundle of outcomes, not a pile of features","why":"A strong offer makes the components feel inevitable because each one removes a buyer obstacle.","agentCheck":"Can every feature be translated into the obstacle it removes or the decision it helps the buyer make?","weakExample":"Includes strategy, design, development, SEO, AEO, and testing.","strongerExample":"You get a source ledger for claims, page patterns for build speed, SEO/AEO contracts for discovery, and QA evidence for handoff confidence.","guardrail":"Do not inflate the stack with filler bonuses. Every component must have a reason to exist."},{"id":"mechanism-clarity","name":"Explain why this approach works","why":"A specific mechanism makes the claim more believable than a broad promise because it gives the reader a causal path.","agentCheck":"Does the copy explain the method behind the outcome in plain language?","weakExample":"Our proven process gets results.","strongerExample":"The system starts by preserving source evidence, then turns approved facts into visible copy, schema, LLM summaries, and tests that catch unsupported claims.","guardrail":"Do not claim a proprietary mechanism unless the business actually owns one."},{"id":"proof-before-claim","name":"Attach proof to claims before asking for belief","why":"Strong conversion copy earns trust by pairing claims with evidence, examples, screenshots, crawl results, testimonials, or source-backed facts.","agentCheck":"Does every meaningful claim have a visible proof element or claim ID?","weakExample":"We are the best choice for serious businesses.","strongerExample":"The current build exposes QA reports, crawl evidence, browser screenshots, schema maps, and contract drift checks so readiness is inspectable.","guardrail":"Never fabricate testimonials, logos, statistics, or case studies."},{"id":"risk-reversal","name":"Reduce buyer risk honestly","why":"A reader who wants the outcome may still hesitate because of uncertainty, effort, budget, switching cost, or fear of a bad decision.","agentCheck":"Does the page answer what happens if this does not work, is not a fit, or requires more effort than expected?","weakExample":"Contact us today to get started.","strongerExample":"Start with a source and QA audit before implementation, so gaps are found while the cost of correction is low.","guardrail":"Do not add guarantees the business cannot operationally and legally honor."},{"id":"ethical-urgency","name":"Use urgency only when it is real","why":"Urgency can improve action, but fake scarcity damages trust and teaches agents the wrong habit.","agentCheck":"Is the urgency tied to a real capacity, date, price change, event, or operational constraint?","weakExample":"Spots are limited, act now.","strongerExample":"The next audit batch closes Friday because each review includes manual crawl and source-traceability checks.","guardrail":"If there is no real constraint, use clarity of next step instead of urgency."},{"id":"cta-specificity","name":"Make the next step specific and low-confusion","why":"A conversion path fails when the reader likes the idea but cannot tell what action starts the process.","agentCheck":"Does the CTA say exactly what happens next, who it is for, and what the reader should expect?","weakExample":"Learn more.","strongerExample":"Run the agent readiness audit.","guardrail":"The CTA must match the destination. Do not use high-commitment language for a low-commitment page or vice versa."},{"id":"qualified-who-before-what","name":"Define who this is for before explaining everything they get","why":"The newer Acquisition.com surfaces use fit boundaries, revenue thresholds, and operator language to make the offer feel more valuable to the right buyer while filtering poor-fit demand.","agentCheck":"Does the page state who qualifies, who does not, and why that boundary improves the outcome?","weakExample":"This is for any business that wants to grow.","strongerExample":"This is for teams that already have source material, proof, and a real offer, but need an agent-readable site system that keeps claims, schema, and QA evidence aligned.","guardrail":"Do not invent exclusivity. Qualification must reflect a real operational, pricing, legal, capacity, or value-delivery reason."},{"id":"ecosystem-offer-architecture","name":"Show the offer ecosystem, not just one asset","why":"Modern conversion pages often sell an integrated system: tool, training, community, live guidance, playbooks, and escalation paths. The bundle works when each layer has a distinct job.","agentCheck":"Can the reader tell what each layer does, what order to use it in, and why the layers are stronger together?","weakExample":"Members get AI, workshops, templates, calls, and a community.","strongerExample":"Agents start with the manifest, use copy and page contracts to draft, use traceability to prove claims, then run QA and handoff reports before implementation is called ready.","guardrail":"Do not stack unrelated bonuses. Ecosystem layers must connect to one customer journey."},{"id":"ai-tool-trust","name":"Position AI tools with boundaries and implementation use cases","why":"AI-tool copy converts better when it explains what the tool is trained to help with, how the user should apply outputs, and where human judgment or source evidence still controls the result.","agentCheck":"Does AI copy name the jobs the AI helps with, the evidence it should use, and the decisions humans must still verify?","weakExample":"Our AI writes everything for your business instantly.","strongerExample":"Use the copy endpoint to draft options, then validate each claim against source traceability, page context, and QA before it reaches a live site.","guardrail":"Do not imply AI outputs are inherently true, current, legal, or ready to publish without review."},{"id":"value-in-advance-journey","name":"Use value-in-advance content to shape the buyer journey","why":"The avatar material emphasizes studying how best customers bought and then recreating that journey with genuinely useful long-form content before a sales conversation.","agentCheck":"Does the site give a qualified buyer useful context before asking for a high-commitment action?","weakExample":"Book a call to find out how it works.","strongerExample":"Read the copy lab, inspect the endpoint, and run the stress report before deciding whether the starter is ready for implementation work.","guardrail":"Value-in-advance content must be genuinely useful, not a disguised pitch."},{"id":"pricing-and-path-choice","name":"Make tiers and paths easy to compare","why":"Tiered offers convert when each path explains who it is for, what changes, what stays the same, and why the higher commitment exists.","agentCheck":"Can a buyer compare options without reading every line twice?","weakExample":"Basic, Pro, and Elite plans are available.","strongerExample":"Use Standard for core access, Premium when implementation speed matters, and VIP when direct advisory support is the constraint.","guardrail":"Do not bury material constraints, cancellation rules, trial terms, or eligibility requirements."},{"id":"disclaimer-near-outcome","name":"Place outcome boundaries near ambitious claims","why":"Strong direct-response pages can use bold proof and ambitious outcomes, but trust improves when disclaimers and result boundaries live near the relevant promise.","agentCheck":"Are atypical results, earnings claims, investment-like claims, AI claims, and referral incentives paired with plain disclaimers?","weakExample":"Use our system and get the same results.","strongerExample":"The system can improve copy and QA discipline, but results depend on the offer, source quality, market, execution, traffic, and review process.","guardrail":"Never use disclaimers as permission to make reckless claims."}],"copyTypes":[{"id":"homepage-hero","name":"Homepage hero","purpose":"Clarify who the site is for, what outcome it creates, why it is credible, and what to do next.","structure":["Audience or category","Specific outcome","Mechanism","Proof cue","Primary CTA"],"agentPrompt":"Write a hero that a qualified buyer understands in five seconds without needing buzzwords."},{"id":"offer-section","name":"Offer section","purpose":"Turn the service or product into an obstacle-removal stack.","structure":["Problem","Offer component","Obstacle removed","Proof or example","Fit boundary"],"agentPrompt":"List each component only if it improves outcome, certainty, speed, effort, or risk."},{"id":"proof-section","name":"Proof section","purpose":"Let evidence carry belief instead of relying on adjectives.","structure":["Claim","Evidence type","Source","What it proves","Limitation"],"agentPrompt":"Pair every impressive statement with the proof source and state what it does not prove."},{"id":"objection-faq","name":"Objection FAQ","purpose":"Answer real buyer hesitation with direct, non-defensive copy.","structure":["Objection","Plain answer","Evidence or boundary","Next step"],"agentPrompt":"Write answers that reduce uncertainty without overpromising."},{"id":"lead-magnet","name":"Lead magnet page","purpose":"Make free value feel specific enough to justify attention and contact exchange.","structure":["Who it helps","Problem it solves","Asset delivered","Use case","CTA","Consent/disclaimer"],"agentPrompt":"Make the free asset concrete. Avoid vague newsletter language."},{"id":"service-page","name":"Service page","purpose":"Explain fit, scope, sequence, proof, and buying path for a concrete service.","structure":["Use case","Problem","Process","Deliverables","Proof","Boundaries","CTA"],"agentPrompt":"Make scope and decision criteria clear enough that the wrong buyer can opt out."},{"id":"ai-tool-page","name":"AI tool page","purpose":"Explain what the AI helps produce, what it is grounded in, how the user should apply it, and what must be verified before use.","structure":["User job","AI capability","Grounding source","Implementation use cases","Human review boundary","CTA"],"agentPrompt":"Write AI copy that is useful, specific, and bounded by source evidence."},{"id":"community-membership-page","name":"Community or membership page","purpose":"Show why the network, live guidance, tools, and playbooks are more valuable together than separately.","structure":["Qualified member","Core promise","Member layers","How it works","Pricing/path choice","Disclaimers","CTA"],"agentPrompt":"Make the membership feel filtered, operational, and outcome-oriented without fake exclusivity."},{"id":"qualification-gate","name":"Qualification gate","purpose":"Filter fit before high-commitment sales, workshops, or advisory paths.","structure":["Who qualifies","Why the gate exists","What is reviewed","What happens next","Alternative path"],"agentPrompt":"Explain qualification as value protection for both sides, not as status theater."},{"id":"pricing-tier-section","name":"Pricing tier section","purpose":"Help a buyer choose between access levels with minimal confusion.","structure":["Shared value","Tier-specific difference","Best-fit cue","Risk/cancellation boundary","CTA per tier"],"agentPrompt":"Make each tier's reason to exist obvious without pushing everyone to the highest price."}],"exampleTransformations":[{"id":"generic-agency-to-agent-operating-system","weakCopy":"We build beautiful, high-performing websites that help your business grow.","strongerCopy":"We build source-backed websites that agents, search engines, and buyers can understand: every core claim maps to evidence, every key page has schema, and every handoff includes QA proof.","whyStronger":"It names the mechanism, audience, proof model, and operational output instead of leaning on broad adjectives.","requiredChecks":["Source-backed claim","Specific audience","Mechanism stated","QA or proof cue present"]},{"id":"feature-list-to-offer-stack","weakCopy":"Includes design, SEO, content, schema, analytics, and testing.","strongerCopy":"Design gives buyers a clear path, SEO and schema make the offer discoverable, source traceability keeps claims defensible, and testing proves the site works before handoff.","whyStronger":"It translates each feature into the buyer or agent obstacle it removes.","requiredChecks":["Every feature has a job","No filler component","Benefit tied to system objective"]},{"id":"unsupported-proof-to-evidence-led","weakCopy":"Trusted by businesses that want the best results.","strongerCopy":"Use crawl reports, browser screenshots, schema maps, and source manifests as visible proof before calling a page launch-ready.","whyStronger":"It replaces a vague trust claim with inspectable evidence types.","requiredChecks":["No unverifiable superlative","Evidence type named","Launch criteria stated"]},{"id":"generic-ai-to-bounded-ai-tool","weakCopy":"Our AI will write all your website copy instantly.","strongerCopy":"Use the copy endpoint to draft conversion options, then check every claim against source traceability, page context, and QA before publishing.","whyStronger":"It names the AI job, the implementation path, and the human/source verification boundary.","requiredChecks":["AI use case named","Source boundary stated","No publish-ready claim","QA gate present"]},{"id":"open-to-everyone-to-qualified-fit","weakCopy":"Anyone who wants a better website should book a call.","strongerCopy":"Book implementation only after the source package, proof inventory, required pages, and launch constraints are clear enough for an agent to validate.","whyStronger":"It turns a broad CTA into a qualification gate that protects execution quality.","requiredChecks":["Fit criteria named","Next step is specific","Operational reason for gate is clear"]},{"id":"local-service-vague-trust-to-bounded-promise","vertical":"local service (see /demo/brightline/)","weakCopy":"Your trusted local gutter experts — satisfaction guaranteed!","strongerCopy":"Two crews, three named counties, photo documentation of every finished run, and a walk-through before any quote. Requests outside the service area are declined, not waitlisted.","whyStronger":"It replaces unverifiable trust language with operational facts a buyer can check, and the explicit boundary makes the in-area promise credible.","requiredChecks":["Every fact maps to a source claim","Service boundary stated","No guarantee the business cannot operationally honor"]},{"id":"saas-feature-dump-to-job-outcome","vertical":"B2B SaaS (see /demo/logpilot/)","weakCopy":"Powerful, flexible log management with enterprise-grade security and seamless integrations.","strongerCopy":"When a client's auditor asks for nine months of access logs, export them in one operation — retention is set per client at 30, 90, or 365 days with immutable locks, across six verified integrations.","whyStronger":"It anchors on the buyer's job (the audit request), states exact capability boundaries, and counts integrations instead of calling them seamless.","requiredChecks":["Job-to-be-done leads","Numbers replace adjectives","Integration claims match the verified list","No superiority language"]},{"id":"professional-services-credential-fog-to-sourced-scope","vertical":"professional services","weakCopy":"Our award-winning team of experts delivers world-class advisory services.","strongerCopy":"Two licensed practitioners (license numbers on the about page), three defined engagements with explicit exclusions, and anonymized case summaries published with written approval.","whyStronger":"Credential-heavy buyers verify; copy that points at checkable credentials and bounded scope converts the skeptics that adjectives repel.","requiredChecks":["Credentials visible and sourced","Scope exclusions stated","Proof carries permission status"]}],"agentWorkflow":["Identify the business model, audience, buying stage, and site type before writing.","Identify the best-fit buyer and the poor-fit buyer before writing the offer.","Map the buyer journey: value-in-advance content, low-commitment action, qualification gate, paid path, and implementation/handoff.","Extract source-backed facts, proof, constraints, and disallowed claims from the source ledger.","Write the plain-language problem in the buyer's words before naming the solution.","Define the dream outcome, likelihood proof, time-to-value, effort reduction, and risk reduction.","Build the offer stack by mapping each feature to the obstacle it removes.","If the offer includes AI, community, workshops, playbooks, referrals, or pricing tiers, write the role and boundary of each layer separately.","Draft hero, offer, proof, objection, and CTA copy separately before polishing tone.","Attach claim IDs, source notes, proof blocks, or disclaimers to meaningful claims.","Stress test for vague adjectives, fake urgency, unsupported outcomes, unclear audience, and missing next step.","Run SEO/AEO QA and verify LLM summaries do not overstate the visible page."],"antiPatterns":[{"id":"clever-before-clear","issue":"The headline is memorable but does not tell the reader what the offer does.","fix":"Lead with the concrete outcome, then add personality."},{"id":"feature-dump","issue":"The page lists capabilities without explaining the buyer obstacle each one removes.","fix":"Rewrite each feature as an outcome, confidence, speed, effort, or risk improvement."},{"id":"fake-scarcity","issue":"Urgency is invented because the page lacks a strong reason to act.","fix":"Use real capacity/date constraints or remove urgency entirely."},{"id":"proofless-superlatives","issue":"The copy says best, fastest, leading, trusted, or proven without evidence.","fix":"Replace with specific proof or remove the claim."},{"id":"ai-slop-generalities","issue":"The copy could apply to any business in any market.","fix":"Add audience, pain, mechanism, proof, and fit boundaries from source data."},{"id":"unbounded-ai-claims","issue":"The page implies AI can replace source evidence, expert review, legal review, or implementation judgment.","fix":"Name the AI job, the source material it should use, the review boundary, and the QA gate."},{"id":"ecosystem-confusion","issue":"The offer stacks tools, community, live help, playbooks, pricing, and referrals without a clear buyer journey.","fix":"Put each layer in order and state the job it performs."},{"id":"qualification-theater","issue":"The page uses exclusivity language without a real operational reason.","fix":"Tie qualification to fit, capacity, source readiness, value delivery, or risk reduction."},{"id":"buried-disclaimer","issue":"Ambitious results, referral incentives, or AI claims appear far away from the relevant boundary language.","fix":"Move plain disclaimers beside the claim or offer component they qualify."}],"qaGates":["npm run qa:aeo","npm run qa:seo","npm run qa:browser","npm run qa:all"],"stressTestSuite":{"command":"npm run qa:copy","fixturePath":"data/derived/copy-stress/copy-stress-fixtures.json","reportPath":"reports/copy-stress/copy-stress-report.json","why":"Copy guidance should be proven against weak prompts and bad examples, not only documented as principles."},"passCriteria":["Copy states a specific audience, problem, outcome, mechanism, proof model, and next step.","Every meaningful claim is source-backed, visible, or clearly framed as a process principle.","Offer sections explain why each component exists.","Bad examples and better examples are both available for agent training.","LLM summaries can describe the copy strategy without inventing unsupported claims."],"objectiveAlignment":"Adds conversion copy as a reusable operating layer so future agents can build sites that are not merely technically valid, but clear, believable, and action-oriented."}}