{ "schema": "armalo.portfolio.marketing.v1", "generatedBy": "portfolio", "instructions": [ "Drafts only: verify status, proof, legal, platform, and customer-specific claims before publication.", "Do not imitate the named research references or imply affiliation, endorsement, or quoted language.", "Do not publish, send, buy media, or run commands without explicit human approval." ], "mechanics": [ { "lens": "outcome-installation", "label": "Outcome installation", "researchReference": "Jordan Lee / AI Acquisition", "principle": "Package one repeatable business outcome as a scoped installation, then earn recurring work through transparent operation and optimization.", "adaptation": "Original Armalo adaptation: narrow the workflow, specify what is installed, define acceptance tests, and keep customer authority explicit.", "sourceUrl": "https://www.aiacquisition.com/blog/top-5-most-profitable-ai-services-our-clients-are-selling", "disclosure": "Research reference only. Armalo is not affiliated with AI Acquisition, and this is not an endorsement." }, { "lens": "constraint-offer", "label": "Constraint offer", "researchReference": "Alex Hormozi / Acquisition.com", "principle": "Lead with the costly constraint, make the path to value legible, and surround the tool with diagnosis, implementation, and proof.", "adaptation": "Original Armalo adaptation: name one measurable bottleneck and offer the smallest credible intervention that can change it.", "sourceUrl": "https://ai.acquisition.com/", "disclosure": "Research reference only. Armalo is not affiliated with Acquisition.com, and this is not an endorsement." }, { "lens": "expertise-product", "label": "Expertise product", "researchReference": "Iman Gadzhi / Monetise", "principle": "Turn owned expertise into a coherent offer ladder that connects education, product, delivery, and continued support.", "adaptation": "Original Armalo adaptation: use owned or licensed knowledge, preserve the expert's authorship, and validate demand before scaling distribution.", "sourceUrl": "https://www.monetise.com/policy/terms", "disclosure": "Research reference only. Armalo is not affiliated with Monetise or Iman Gadzhi, and this is not an endorsement." }, { "lens": "encoded-playbook", "label": "Encoded playbook", "researchReference": "Serge Gatari / Cook.ai", "principle": "Encode the best operator's judgment into reusable infrastructure so delivery compounds instead of restarting from prompts and memory.", "adaptation": "Original Armalo adaptation: make the playbook inspectable, tenant-isolated, versioned, and accountable to real acceptance tests.", "sourceUrl": "https://webby.trycook.ai/", "disclosure": "Research reference only. Armalo is not affiliated with Cook.ai or Serge Gatari, and this is not an endorsement." }, { "lens": "evidence-loop", "label": "Evidence loop", "researchReference": "Alex Becker / HYROS", "principle": "Instrument the journey from action to revenue so the system can learn which work deserves more investment and which does not.", "adaptation": "Original Armalo adaptation: distinguish observed signals, modeled attribution, verified outcomes, and genuine incrementality.", "sourceUrl": "https://hyros.ai/", "disclosure": "Research reference only. Armalo is not affiliated with HYROS or Alex Becker, and this is not an endorsement." } ], "products": [ { "slug": "armalo-app", "name": "Armalo App", "category": "Multiplayer business operations platform", "status": "live", "proof": "public-live", "audience": "Founders", "claimBoundary": "Armalo App is live, but campaign claims must still match its public-live proof and the evidence available for the buyer's exact workflow.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Armalo App: the installed outcome", "headline": "Armalo App, installed around one working outcome—not another AI subscription.", "offer": "For Founders: a hosted pilot that starts with “No sign-up wall — visiting mints a live shared workspace with the agent already present,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current multiplayer business operations platform workflow, install the minimum Armalo App capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Armalo App pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Armalo App is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Armalo App installation worth proving.", "emailSubject": "Armalo App: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Armalo App installed around one job, one owner, and one acceptance test.", "landingLead": "A multiplayer AI workspace for planning, designing, building, monitoring, and scaling a business alongside agents that code, browse, and run commerce. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Armalo App: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Armalo App can make measurable.", "offer": "Armalo App begins with a diagnostic for Founders, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where multiplayer business operations platform work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Armalo App only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Armalo App offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Armalo App should remove.", "emailSubject": "Where is Armalo App worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Armalo App one measurable job.", "landingLead": "The collaborative workspace that learns your business and gets out of the way — vibe coding, agentic browser automation, and a Compass that turns your decisions into autonomy. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Armalo App: expertise into an offer", "headline": "Turn the way your best people handle this work into a Armalo App offer the whole team can use.", "offer": "For Founders, Armalo App packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for multiplayer business operations platform, structure their decisions into a guided Armalo App workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Armalo App workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Armalo App should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Armalo App should productize.", "emailSubject": "Package your best operating knowledge with Armalo App", "socialHook": "Your best operator already has a product in their head. Armalo App can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A multiplayer AI workspace for planning, designing, building, monitoring, and scaling a business alongside agents that code, browse, and run commerce. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Armalo App: the compounding playbook", "headline": "Stop rebuilding Armalo App from prompts. Encode the playbook your operation can improve.", "offer": "Armalo App becomes a reusable operating layer for Founders: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “No sign-up wall — visiting mints a live shared workspace with the agent already present,” encode the stable decisions, isolate customer data and permissions, and improve the Armalo App playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Armalo App release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Armalo App separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Armalo App should encode first.", "emailSubject": "Make Armalo App improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Armalo App playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "The collaborative workspace that learns your business and gets out of the way — vibe coding, agentic browser automation, and a Compass that turns your decisions into autonomy. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Armalo App: prove what compounds", "headline": "If Armalo App cannot connect its work to an observable result, it does not get credit.", "offer": "Give Founders a Armalo App deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Armalo App input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Armalo App should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Armalo App pilot.", "emailSubject": "What evidence would make Armalo App worth expanding?", "socialHook": "The useful question is not whether Armalo App ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A multiplayer AI workspace for planning, designing, building, monitoring, and scaling a business alongside agents that code, browse, and run commerce. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "autonomous-business", "name": "Autonomous Business", "category": "Business operations", "status": "planned", "proof": "not-yet-proven", "audience": "Solo founders", "claimBoundary": "Autonomous Business is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Autonomous Business: the installed outcome", "headline": "Autonomous Business, installed around one working outcome—not another AI subscription.", "offer": "For Solo founders: a hosted pilot that starts with “Turns company goals into owned missions and measurable outcomes,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current business operations workflow, install the minimum Autonomous Business capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Autonomous Business pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Autonomous Business is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Autonomous Business installation worth proving.", "emailSubject": "Autonomous Business: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Autonomous Business installed around one job, one owner, and one acceptance test.", "landingLead": "A governed company operating system that plans, builds, markets, sells, supports, and learns around an owner's goals. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Autonomous Business: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Autonomous Business can make measurable.", "offer": "Autonomous Business begins with a diagnostic for Solo founders, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where business operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Autonomous Business only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Autonomous Business offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Autonomous Business should remove.", "emailSubject": "Where is Autonomous Business worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Autonomous Business one measurable job.", "landingLead": "Run more of the company through one accountable agent system: durable context, bounded authority, action receipts, and learning from real outcomes. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Autonomous Business: expertise into an offer", "headline": "Turn the way your best people handle this work into a Autonomous Business offer the whole team can use.", "offer": "For Solo founders, Autonomous Business packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for business operations, structure their decisions into a guided Autonomous Business workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Autonomous Business workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Autonomous Business should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Autonomous Business should productize.", "emailSubject": "Package your best operating knowledge with Autonomous Business", "socialHook": "Your best operator already has a product in their head. Autonomous Business can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A governed company operating system that plans, builds, markets, sells, supports, and learns around an owner's goals. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Autonomous Business: the compounding playbook", "headline": "Stop rebuilding Autonomous Business from prompts. Encode the playbook your operation can improve.", "offer": "Autonomous Business becomes a reusable operating layer for Solo founders: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Turns company goals into owned missions and measurable outcomes,” encode the stable decisions, isolate customer data and permissions, and improve the Autonomous Business playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Autonomous Business release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Autonomous Business separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Autonomous Business should encode first.", "emailSubject": "Make Autonomous Business improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Autonomous Business playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Run more of the company through one accountable agent system: durable context, bounded authority, action receipts, and learning from real outcomes. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Autonomous Business: prove what compounds", "headline": "If Autonomous Business cannot connect its work to an observable result, it does not get credit.", "offer": "Give Solo founders a Autonomous Business deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Autonomous Business input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Autonomous Business should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Autonomous Business pilot.", "emailSubject": "What evidence would make Autonomous Business worth expanding?", "socialHook": "The useful question is not whether Autonomous Business ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A governed company operating system that plans, builds, markets, sells, supports, and learns around an owner's goals. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "managed-agent-workspaces", "name": "Managed Agent Workspaces", "category": "Managed agent infrastructure", "status": "planned", "proof": "not-yet-proven", "audience": "Small businesses", "claimBoundary": "Managed Agent Workspaces is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Managed Agent Workspaces: the installed outcome", "headline": "Managed Agent Workspaces, installed around one working outcome—not another AI subscription.", "offer": "For Small businesses: a hosted pilot that starts with “Create role-specific agents from centrally governed workspace templates,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current managed agent infrastructure workflow, install the minimum Managed Agent Workspaces capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Managed Agent Workspaces pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Managed Agent Workspaces is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Managed Agent Workspaces installation worth proving.", "emailSubject": "Managed Agent Workspaces: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Managed Agent Workspaces installed around one job, one owner, and one acceptance test.", "landingLead": "A governed team workspace for deploying specialized AI agents without making every employee manage infrastructure, keys, or billing. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Managed Agent Workspaces: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Managed Agent Workspaces can make measurable.", "offer": "Managed Agent Workspaces begins with a diagnostic for Small businesses, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where managed agent infrastructure work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Managed Agent Workspaces only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Managed Agent Workspaces offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Managed Agent Workspaces should remove.", "emailSubject": "Where is Managed Agent Workspaces worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Managed Agent Workspaces one measurable job.", "landingLead": "Give a team one managed place to deploy role-specific agents, set authority, monitor work, and pay one clean invoice instead of operating a fleet of VPS instances. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Managed Agent Workspaces: expertise into an offer", "headline": "Turn the way your best people handle this work into a Managed Agent Workspaces offer the whole team can use.", "offer": "For Small businesses, Managed Agent Workspaces packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for managed agent infrastructure, structure their decisions into a guided Managed Agent Workspaces workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Managed Agent Workspaces workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Managed Agent Workspaces should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Managed Agent Workspaces should productize.", "emailSubject": "Package your best operating knowledge with Managed Agent Workspaces", "socialHook": "Your best operator already has a product in their head. Managed Agent Workspaces can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A governed team workspace for deploying specialized AI agents without making every employee manage infrastructure, keys, or billing. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Managed Agent Workspaces: the compounding playbook", "headline": "Stop rebuilding Managed Agent Workspaces from prompts. Encode the playbook your operation can improve.", "offer": "Managed Agent Workspaces becomes a reusable operating layer for Small businesses: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Create role-specific agents from centrally governed workspace templates,” encode the stable decisions, isolate customer data and permissions, and improve the Managed Agent Workspaces playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Managed Agent Workspaces release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Managed Agent Workspaces separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Managed Agent Workspaces should encode first.", "emailSubject": "Make Managed Agent Workspaces improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Managed Agent Workspaces playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Give a team one managed place to deploy role-specific agents, set authority, monitor work, and pay one clean invoice instead of operating a fleet of VPS instances. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Managed Agent Workspaces: prove what compounds", "headline": "If Managed Agent Workspaces cannot connect its work to an observable result, it does not get credit.", "offer": "Give Small businesses a Managed Agent Workspaces deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Managed Agent Workspaces input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Managed Agent Workspaces should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Managed Agent Workspaces pilot.", "emailSubject": "What evidence would make Managed Agent Workspaces worth expanding?", "socialHook": "The useful question is not whether Managed Agent Workspaces ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A governed team workspace for deploying specialized AI agents without making every employee manage infrastructure, keys, or billing. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "business-constraint-finder", "name": "Business Constraint Finder", "category": "Business strategy", "status": "planned", "proof": "not-yet-proven", "audience": "Founders", "claimBoundary": "Business Constraint Finder is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Business Constraint Finder: the installed outcome", "headline": "Business Constraint Finder, installed around one working outcome—not another AI subscription.", "offer": "For Founders: a hosted pilot that starts with “Links each diagnosis to the evidence behind it,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current business strategy workflow, install the minimum Business Constraint Finder capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Business Constraint Finder pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Business Constraint Finder is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Business Constraint Finder installation worth proving.", "emailSubject": "Business Constraint Finder: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Business Constraint Finder installed around one job, one owner, and one acceptance test.", "landingLead": "An evidence-linked diagnostic that helps teams identify the operating constraint most worth testing next. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Business Constraint Finder: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Business Constraint Finder can make measurable.", "offer": "Business Constraint Finder begins with a diagnostic for Founders, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where business strategy work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Business Constraint Finder only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Business Constraint Finder offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Business Constraint Finder should remove.", "emailSubject": "Where is Business Constraint Finder worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Business Constraint Finder one measurable job.", "landingLead": "Replace generic advice with a focused diagnosis, visible evidence, and a testable next-step hypothesis. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Business Constraint Finder: expertise into an offer", "headline": "Turn the way your best people handle this work into a Business Constraint Finder offer the whole team can use.", "offer": "For Founders, Business Constraint Finder packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for business strategy, structure their decisions into a guided Business Constraint Finder workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Business Constraint Finder workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Business Constraint Finder should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Business Constraint Finder should productize.", "emailSubject": "Package your best operating knowledge with Business Constraint Finder", "socialHook": "Your best operator already has a product in their head. Business Constraint Finder can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "An evidence-linked diagnostic that helps teams identify the operating constraint most worth testing next. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Business Constraint Finder: the compounding playbook", "headline": "Stop rebuilding Business Constraint Finder from prompts. Encode the playbook your operation can improve.", "offer": "Business Constraint Finder becomes a reusable operating layer for Founders: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Links each diagnosis to the evidence behind it,” encode the stable decisions, isolate customer data and permissions, and improve the Business Constraint Finder playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Business Constraint Finder release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Business Constraint Finder separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Business Constraint Finder should encode first.", "emailSubject": "Make Business Constraint Finder improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Business Constraint Finder playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Replace generic advice with a focused diagnosis, visible evidence, and a testable next-step hypothesis. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Business Constraint Finder: prove what compounds", "headline": "If Business Constraint Finder cannot connect its work to an observable result, it does not get credit.", "offer": "Give Founders a Business Constraint Finder deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Business Constraint Finder input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Business Constraint Finder should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Business Constraint Finder pilot.", "emailSubject": "What evidence would make Business Constraint Finder worth expanding?", "socialHook": "The useful question is not whether Business Constraint Finder ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "An evidence-linked diagnostic that helps teams identify the operating constraint most worth testing next. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-forward-deployed-engineer", "name": "AI Forward Deployed Engineer", "category": "AI engineering services", "status": "planned", "proof": "not-yet-proven", "audience": "AI startups", "claimBoundary": "AI Forward Deployed Engineer is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Forward Deployed Engineer: the installed outcome", "headline": "AI Forward Deployed Engineer, installed around one working outcome—not another AI subscription.", "offer": "For AI startups: a custom build pilot that starts with “Starts with one measurable workflow, not an open-ended AI transformation,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current ai engineering services workflow, install the minimum AI Forward Deployed Engineer capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Forward Deployed Engineer pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Forward Deployed Engineer is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Forward Deployed Engineer installation worth proving.", "emailSubject": "AI Forward Deployed Engineer: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Forward Deployed Engineer installed around one job, one owner, and one acceptance test.", "landingLead": "A human-accountable AI engineering partner that embeds with your team to turn one valuable workflow into a reliable production system. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Forward Deployed Engineer: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Forward Deployed Engineer can make measurable.", "offer": "AI Forward Deployed Engineer begins with a diagnostic for AI startups, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where ai engineering services work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Forward Deployed Engineer only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Forward Deployed Engineer offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Forward Deployed Engineer should remove.", "emailSubject": "Where is AI Forward Deployed Engineer worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Forward Deployed Engineer one measurable job.", "landingLead": "One accountable delivery team combines an embedded human engineer with bounded AI agents to find, build, prove, and transfer a production workflow. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Forward Deployed Engineer: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Forward Deployed Engineer offer the whole team can use.", "offer": "For AI startups, AI Forward Deployed Engineer packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for ai engineering services, structure their decisions into a guided AI Forward Deployed Engineer workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Forward Deployed Engineer workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Forward Deployed Engineer should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Forward Deployed Engineer should productize.", "emailSubject": "Package your best operating knowledge with AI Forward Deployed Engineer", "socialHook": "Your best operator already has a product in their head. AI Forward Deployed Engineer can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A human-accountable AI engineering partner that embeds with your team to turn one valuable workflow into a reliable production system. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Forward Deployed Engineer: the compounding playbook", "headline": "Stop rebuilding AI Forward Deployed Engineer from prompts. Encode the playbook your operation can improve.", "offer": "AI Forward Deployed Engineer becomes a reusable operating layer for AI startups: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Starts with one measurable workflow, not an open-ended AI transformation,” encode the stable decisions, isolate customer data and permissions, and improve the AI Forward Deployed Engineer playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Forward Deployed Engineer release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Forward Deployed Engineer separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Forward Deployed Engineer should encode first.", "emailSubject": "Make AI Forward Deployed Engineer improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Forward Deployed Engineer playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "One accountable delivery team combines an embedded human engineer with bounded AI agents to find, build, prove, and transfer a production workflow. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Forward Deployed Engineer: prove what compounds", "headline": "If AI Forward Deployed Engineer cannot connect its work to an observable result, it does not get credit.", "offer": "Give AI startups a AI Forward Deployed Engineer deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Forward Deployed Engineer input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Forward Deployed Engineer should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Forward Deployed Engineer pilot.", "emailSubject": "What evidence would make AI Forward Deployed Engineer worth expanding?", "socialHook": "The useful question is not whether AI Forward Deployed Engineer ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A human-accountable AI engineering partner that embeds with your team to turn one valuable workflow into a reliable production system. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "software-engineering-copilot", "name": "Software Engineering Copilot", "category": "AI engineering services", "status": "planned", "proof": "not-yet-proven", "audience": "Software teams", "claimBoundary": "Software Engineering Copilot is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Software Engineering Copilot: the installed outcome", "headline": "Software Engineering Copilot, installed around one working outcome—not another AI subscription.", "offer": "For Software teams: a custom build pilot that starts with “Works inside explicit repository and task boundaries,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current ai engineering services workflow, install the minimum Software Engineering Copilot capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Software Engineering Copilot pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Software Engineering Copilot is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Software Engineering Copilot installation worth proving.", "emailSubject": "Software Engineering Copilot: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Software Engineering Copilot installed around one job, one owner, and one acceptance test.", "landingLead": "A repository-scoped engineering copilot for planning, implementing, and validating bounded software changes. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Software Engineering Copilot: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Software Engineering Copilot can make measurable.", "offer": "Software Engineering Copilot begins with a diagnostic for Software teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where ai engineering services work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Software Engineering Copilot only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Software Engineering Copilot offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Software Engineering Copilot should remove.", "emailSubject": "Where is Software Engineering Copilot worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Software Engineering Copilot one measurable job.", "landingLead": "Accelerate bounded engineering work while keeping repository context, tests, review, and promotion evidence legible. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Software Engineering Copilot: expertise into an offer", "headline": "Turn the way your best people handle this work into a Software Engineering Copilot offer the whole team can use.", "offer": "For Software teams, Software Engineering Copilot packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for ai engineering services, structure their decisions into a guided Software Engineering Copilot workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Software Engineering Copilot workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Software Engineering Copilot should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Software Engineering Copilot should productize.", "emailSubject": "Package your best operating knowledge with Software Engineering Copilot", "socialHook": "Your best operator already has a product in their head. Software Engineering Copilot can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A repository-scoped engineering copilot for planning, implementing, and validating bounded software changes. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Software Engineering Copilot: the compounding playbook", "headline": "Stop rebuilding Software Engineering Copilot from prompts. Encode the playbook your operation can improve.", "offer": "Software Engineering Copilot becomes a reusable operating layer for Software teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Works inside explicit repository and task boundaries,” encode the stable decisions, isolate customer data and permissions, and improve the Software Engineering Copilot playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Software Engineering Copilot release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Software Engineering Copilot separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Software Engineering Copilot should encode first.", "emailSubject": "Make Software Engineering Copilot improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Software Engineering Copilot playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Accelerate bounded engineering work while keeping repository context, tests, review, and promotion evidence legible. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Software Engineering Copilot: prove what compounds", "headline": "If Software Engineering Copilot cannot connect its work to an observable result, it does not get credit.", "offer": "Give Software teams a Software Engineering Copilot deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Software Engineering Copilot input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Software Engineering Copilot should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Software Engineering Copilot pilot.", "emailSubject": "What evidence would make Software Engineering Copilot worth expanding?", "socialHook": "The useful question is not whether Software Engineering Copilot ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A repository-scoped engineering copilot for planning, implementing, and validating bounded software changes. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "agent-skill-library", "name": "Agent Skill Library", "category": "Managed agent infrastructure", "status": "planned", "proof": "not-yet-proven", "audience": "Businesses", "claimBoundary": "Agent Skill Library is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Agent Skill Library: the installed outcome", "headline": "Agent Skill Library, installed around one working outcome—not another AI subscription.", "offer": "For Businesses: a hosted pilot that starts with “Package domain expertise as inspectable, versioned agent skills,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current managed agent infrastructure workflow, install the minimum Agent Skill Library capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Agent Skill Library pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Agent Skill Library is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Agent Skill Library installation worth proving.", "emailSubject": "Agent Skill Library: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Agent Skill Library installed around one job, one owner, and one acceptance test.", "landingLead": "Versioned, evaluated agent skills that package domain expertise, operating steps, safety boundaries, and proof requirements for repeatable work. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Agent Skill Library: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Agent Skill Library can make measurable.", "offer": "Agent Skill Library begins with a diagnostic for Businesses, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where managed agent infrastructure work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Agent Skill Library only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Agent Skill Library offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Agent Skill Library should remove.", "emailSubject": "Where is Agent Skill Library worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Agent Skill Library one measurable job.", "landingLead": "Buy the operating knowledge and tested workflow—not a blank agent—through reusable skill packages tuned for a specific job and evidence standard. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Agent Skill Library: expertise into an offer", "headline": "Turn the way your best people handle this work into a Agent Skill Library offer the whole team can use.", "offer": "For Businesses, Agent Skill Library packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for managed agent infrastructure, structure their decisions into a guided Agent Skill Library workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Agent Skill Library workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Agent Skill Library should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Agent Skill Library should productize.", "emailSubject": "Package your best operating knowledge with Agent Skill Library", "socialHook": "Your best operator already has a product in their head. Agent Skill Library can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "Versioned, evaluated agent skills that package domain expertise, operating steps, safety boundaries, and proof requirements for repeatable work. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Agent Skill Library: the compounding playbook", "headline": "Stop rebuilding Agent Skill Library from prompts. Encode the playbook your operation can improve.", "offer": "Agent Skill Library becomes a reusable operating layer for Businesses: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Package domain expertise as inspectable, versioned agent skills,” encode the stable decisions, isolate customer data and permissions, and improve the Agent Skill Library playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Agent Skill Library release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Agent Skill Library separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Agent Skill Library should encode first.", "emailSubject": "Make Agent Skill Library improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Agent Skill Library playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Buy the operating knowledge and tested workflow—not a blank agent—through reusable skill packages tuned for a specific job and evidence standard. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Agent Skill Library: prove what compounds", "headline": "If Agent Skill Library cannot connect its work to an observable result, it does not get credit.", "offer": "Give Businesses a Agent Skill Library deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Agent Skill Library input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Agent Skill Library should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Agent Skill Library pilot.", "emailSubject": "What evidence would make Agent Skill Library worth expanding?", "socialHook": "The useful question is not whether Agent Skill Library ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "Versioned, evaluated agent skills that package domain expertise, operating steps, safety boundaries, and proof requirements for repeatable work. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "girl-math", "name": "Girl Math", "category": "Travel", "status": "beta", "proof": "public-live", "audience": "Travel teams", "claimBoundary": "Girl Math is a beta product. Market the verified workflow and its public-live proof only; do not imply broad availability or business outcomes.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Girl Math: the installed outcome", "headline": "Girl Math, installed around one working outcome—not another AI subscription.", "offer": "For Travel teams: a hosted pilot that starts with “Browse reference sweet spots without an account,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current travel workflow, install the minimum Girl Math capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Girl Math pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Girl Math is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Girl Math installation worth proving.", "emailSubject": "Girl Math: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Girl Math installed around one job, one owner, and one acceptance test.", "landingLead": "An award-travel reference board for comparing points redemptions, transfer routes, and premium-cabin value. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Girl Math: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Girl Math can make measurable.", "offer": "Girl Math begins with a diagnostic for Travel teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where travel work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Girl Math only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Girl Math offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Girl Math should remove.", "emailSubject": "Where is Girl Math worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Girl Math one measurable job.", "landingLead": "A focused research surface that turns complicated award-travel decisions into a clearer buying conversation. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Girl Math: expertise into an offer", "headline": "Turn the way your best people handle this work into a Girl Math offer the whole team can use.", "offer": "For Travel teams, Girl Math packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for travel, structure their decisions into a guided Girl Math workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Girl Math workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Girl Math should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Girl Math should productize.", "emailSubject": "Package your best operating knowledge with Girl Math", "socialHook": "Your best operator already has a product in their head. Girl Math can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "An award-travel reference board for comparing points redemptions, transfer routes, and premium-cabin value. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Girl Math: the compounding playbook", "headline": "Stop rebuilding Girl Math from prompts. Encode the playbook your operation can improve.", "offer": "Girl Math becomes a reusable operating layer for Travel teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Browse reference sweet spots without an account,” encode the stable decisions, isolate customer data and permissions, and improve the Girl Math playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Girl Math release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Girl Math separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Girl Math should encode first.", "emailSubject": "Make Girl Math improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Girl Math playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "A focused research surface that turns complicated award-travel decisions into a clearer buying conversation. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Girl Math: prove what compounds", "headline": "If Girl Math cannot connect its work to an observable result, it does not get credit.", "offer": "Give Travel teams a Girl Math deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Girl Math input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Girl Math should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Girl Math pilot.", "emailSubject": "What evidence would make Girl Math worth expanding?", "socialHook": "The useful question is not whether Girl Math ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "An award-travel reference board for comparing points redemptions, transfer routes, and premium-cabin value. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "byok-agent-cloud", "name": "BYOK Agent Cloud", "category": "Managed agent infrastructure", "status": "planned", "proof": "not-yet-proven", "audience": "Agent operators", "claimBoundary": "BYOK Agent Cloud is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "BYOK Agent Cloud: the installed outcome", "headline": "BYOK Agent Cloud, installed around one working outcome—not another AI subscription.", "offer": "For Agent operators: a hosted pilot that starts with “Keep model usage on a customer-controlled model account,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current managed agent infrastructure workflow, install the minimum BYOK Agent Cloud capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the BYOK Agent Cloud pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "BYOK Agent Cloud is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest BYOK Agent Cloud installation worth proving.", "emailSubject": "BYOK Agent Cloud: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need BYOK Agent Cloud installed around one job, one owner, and one acceptance test.", "landingLead": "A managed agent control plane with customer-supplied model keys, predictable platform pricing, backups, and messaging gateway integrations. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "BYOK Agent Cloud: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work BYOK Agent Cloud can make measurable.", "offer": "BYOK Agent Cloud begins with a diagnostic for Agent operators, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where managed agent infrastructure work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure BYOK Agent Cloud only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The BYOK Agent Cloud offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint BYOK Agent Cloud should remove.", "emailSubject": "Where is BYOK Agent Cloud worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give BYOK Agent Cloud one measurable job.", "landingLead": "Separate the managed platform fee from volatile model spend: customers bring their own model API key while Armalo manages orchestration, recovery, and gateway connections. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "BYOK Agent Cloud: expertise into an offer", "headline": "Turn the way your best people handle this work into a BYOK Agent Cloud offer the whole team can use.", "offer": "For Agent operators, BYOK Agent Cloud packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for managed agent infrastructure, structure their decisions into a guided BYOK Agent Cloud workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the BYOK Agent Cloud workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "BYOK Agent Cloud should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise BYOK Agent Cloud should productize.", "emailSubject": "Package your best operating knowledge with BYOK Agent Cloud", "socialHook": "Your best operator already has a product in their head. BYOK Agent Cloud can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A managed agent control plane with customer-supplied model keys, predictable platform pricing, backups, and messaging gateway integrations. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "BYOK Agent Cloud: the compounding playbook", "headline": "Stop rebuilding BYOK Agent Cloud from prompts. Encode the playbook your operation can improve.", "offer": "BYOK Agent Cloud becomes a reusable operating layer for Agent operators: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Keep model usage on a customer-controlled model account,” encode the stable decisions, isolate customer data and permissions, and improve the BYOK Agent Cloud playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each BYOK Agent Cloud release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "BYOK Agent Cloud separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook BYOK Agent Cloud should encode first.", "emailSubject": "Make BYOK Agent Cloud improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned BYOK Agent Cloud playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Separate the managed platform fee from volatile model spend: customers bring their own model API key while Armalo manages orchestration, recovery, and gateway connections. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "BYOK Agent Cloud: prove what compounds", "headline": "If BYOK Agent Cloud cannot connect its work to an observable result, it does not get credit.", "offer": "Give Agent operators a BYOK Agent Cloud deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from BYOK Agent Cloud input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "BYOK Agent Cloud should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first BYOK Agent Cloud pilot.", "emailSubject": "What evidence would make BYOK Agent Cloud worth expanding?", "socialHook": "The useful question is not whether BYOK Agent Cloud ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A managed agent control plane with customer-supplied model keys, predictable platform pricing, backups, and messaging gateway integrations. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "hermes-revenue-agents", "name": "Hermes Revenue Agents", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "High-ticket teams", "claimBoundary": "Hermes Revenue Agents is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Hermes Revenue Agents: the installed outcome", "headline": "Hermes Revenue Agents, installed around one working outcome—not another AI subscription.", "offer": "For High-ticket teams: a custom build pilot that starts with “Qualify high-intent leads against a defined buying rubric,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum Hermes Revenue Agents capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Hermes Revenue Agents pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Hermes Revenue Agents is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Hermes Revenue Agents installation worth proving.", "emailSubject": "Hermes Revenue Agents: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Hermes Revenue Agents installed around one job, one owner, and one acceptance test.", "landingLead": "Dedicated Hermes agents for high-ticket lead qualification, appointment setting, calendar coordination, dialing, and sales handoff. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Hermes Revenue Agents: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Hermes Revenue Agents can make measurable.", "offer": "Hermes Revenue Agents begins with a diagnostic for High-ticket teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Hermes Revenue Agents only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Hermes Revenue Agents offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Hermes Revenue Agents should remove.", "emailSubject": "Where is Hermes Revenue Agents worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Hermes Revenue Agents one measurable job.", "landingLead": "A reliable revenue-agent layer for businesses that need more qualified conversations without paying human labor rates for every repetitive touch. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Hermes Revenue Agents: expertise into an offer", "headline": "Turn the way your best people handle this work into a Hermes Revenue Agents offer the whole team can use.", "offer": "For High-ticket teams, Hermes Revenue Agents packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided Hermes Revenue Agents workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Hermes Revenue Agents workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Hermes Revenue Agents should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Hermes Revenue Agents should productize.", "emailSubject": "Package your best operating knowledge with Hermes Revenue Agents", "socialHook": "Your best operator already has a product in their head. Hermes Revenue Agents can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "Dedicated Hermes agents for high-ticket lead qualification, appointment setting, calendar coordination, dialing, and sales handoff. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Hermes Revenue Agents: the compounding playbook", "headline": "Stop rebuilding Hermes Revenue Agents from prompts. Encode the playbook your operation can improve.", "offer": "Hermes Revenue Agents becomes a reusable operating layer for High-ticket teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Qualify high-intent leads against a defined buying rubric,” encode the stable decisions, isolate customer data and permissions, and improve the Hermes Revenue Agents playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Hermes Revenue Agents release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Hermes Revenue Agents separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Hermes Revenue Agents should encode first.", "emailSubject": "Make Hermes Revenue Agents improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Hermes Revenue Agents playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "A reliable revenue-agent layer for businesses that need more qualified conversations without paying human labor rates for every repetitive touch. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Hermes Revenue Agents: prove what compounds", "headline": "If Hermes Revenue Agents cannot connect its work to an observable result, it does not get credit.", "offer": "Give High-ticket teams a Hermes Revenue Agents deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Hermes Revenue Agents input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Hermes Revenue Agents should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Hermes Revenue Agents pilot.", "emailSubject": "What evidence would make Hermes Revenue Agents worth expanding?", "socialHook": "The useful question is not whether Hermes Revenue Agents ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "Dedicated Hermes agents for high-ticket lead qualification, appointment setting, calendar coordination, dialing, and sales handoff. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "voice-customer-service", "name": "Voice Customer Service Assistant", "category": "Customer service", "status": "planned", "proof": "not-yet-proven", "audience": "Service businesses", "claimBoundary": "Voice Customer Service Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Voice Customer Service Assistant: the installed outcome", "headline": "Voice Customer Service Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Service businesses: a hosted pilot that starts with “Answers recurring customer questions in a natural voice,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current customer service workflow, install the minimum Voice Customer Service Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Voice Customer Service Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Voice Customer Service Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Voice Customer Service Assistant installation worth proving.", "emailSubject": "Voice Customer Service Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Voice Customer Service Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A voice-first service desk assistant for answering routine questions, routing intent, and escalating the moments that need a human. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Voice Customer Service Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Voice Customer Service Assistant can make measurable.", "offer": "Voice Customer Service Assistant begins with a diagnostic for Service businesses, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where customer service work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Voice Customer Service Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Voice Customer Service Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Voice Customer Service Assistant should remove.", "emailSubject": "Where is Voice Customer Service Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Voice Customer Service Assistant one measurable job.", "landingLead": "Sell the outcome: fewer repetitive calls, faster response, and a service experience that still knows when to hand off. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Voice Customer Service Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Voice Customer Service Assistant offer the whole team can use.", "offer": "For Service businesses, Voice Customer Service Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for customer service, structure their decisions into a guided Voice Customer Service Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Voice Customer Service Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Voice Customer Service Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Voice Customer Service Assistant should productize.", "emailSubject": "Package your best operating knowledge with Voice Customer Service Assistant", "socialHook": "Your best operator already has a product in their head. Voice Customer Service Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A voice-first service desk assistant for answering routine questions, routing intent, and escalating the moments that need a human. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Voice Customer Service Assistant: the compounding playbook", "headline": "Stop rebuilding Voice Customer Service Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Voice Customer Service Assistant becomes a reusable operating layer for Service businesses: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Answers recurring customer questions in a natural voice,” encode the stable decisions, isolate customer data and permissions, and improve the Voice Customer Service Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Voice Customer Service Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Voice Customer Service Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Voice Customer Service Assistant should encode first.", "emailSubject": "Make Voice Customer Service Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Voice Customer Service Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Sell the outcome: fewer repetitive calls, faster response, and a service experience that still knows when to hand off. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Voice Customer Service Assistant: prove what compounds", "headline": "If Voice Customer Service Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Service businesses a Voice Customer Service Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Voice Customer Service Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Voice Customer Service Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Voice Customer Service Assistant pilot.", "emailSubject": "What evidence would make Voice Customer Service Assistant worth expanding?", "socialHook": "The useful question is not whether Voice Customer Service Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A voice-first service desk assistant for answering routine questions, routing intent, and escalating the moments that need a human. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-customer-service-desk", "name": "AI Customer Service Desk", "category": "Customer service", "status": "planned", "proof": "not-yet-proven", "audience": "Support teams", "claimBoundary": "AI Customer Service Desk is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Customer Service Desk: the installed outcome", "headline": "AI Customer Service Desk, installed around one working outcome—not another AI subscription.", "offer": "For Support teams: a hosted pilot that starts with “Answers routine questions from approved company sources,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current customer service workflow, install the minimum AI Customer Service Desk capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Customer Service Desk pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Customer Service Desk is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Customer Service Desk installation worth proving.", "emailSubject": "AI Customer Service Desk: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Customer Service Desk installed around one job, one owner, and one acceptance test.", "landingLead": "One governed service desk for answering, routing, drafting, and escalating customer demand across approved channels. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Customer Service Desk: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Customer Service Desk can make measurable.", "offer": "AI Customer Service Desk begins with a diagnostic for Support teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where customer service work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Customer Service Desk only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Customer Service Desk offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Customer Service Desk should remove.", "emailSubject": "Where is AI Customer Service Desk worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Customer Service Desk one measurable job.", "landingLead": "Buy one policy, knowledge, routing, and reporting layer across service channels, or start with a single channel module and expand after proof. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Customer Service Desk: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Customer Service Desk offer the whole team can use.", "offer": "For Support teams, AI Customer Service Desk packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for customer service, structure their decisions into a guided AI Customer Service Desk workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Customer Service Desk workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Customer Service Desk should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Customer Service Desk should productize.", "emailSubject": "Package your best operating knowledge with AI Customer Service Desk", "socialHook": "Your best operator already has a product in their head. AI Customer Service Desk can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "One governed service desk for answering, routing, drafting, and escalating customer demand across approved channels. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Customer Service Desk: the compounding playbook", "headline": "Stop rebuilding AI Customer Service Desk from prompts. Encode the playbook your operation can improve.", "offer": "AI Customer Service Desk becomes a reusable operating layer for Support teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Answers routine questions from approved company sources,” encode the stable decisions, isolate customer data and permissions, and improve the AI Customer Service Desk playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Customer Service Desk release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Customer Service Desk separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Customer Service Desk should encode first.", "emailSubject": "Make AI Customer Service Desk improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Customer Service Desk playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Buy one policy, knowledge, routing, and reporting layer across service channels, or start with a single channel module and expand after proof. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Customer Service Desk: prove what compounds", "headline": "If AI Customer Service Desk cannot connect its work to an observable result, it does not get credit.", "offer": "Give Support teams a AI Customer Service Desk deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Customer Service Desk input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Customer Service Desk should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Customer Service Desk pilot.", "emailSubject": "What evidence would make AI Customer Service Desk worth expanding?", "socialHook": "The useful question is not whether AI Customer Service Desk ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "One governed service desk for answering, routing, drafting, and escalating customer demand across approved channels. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "sms-customer-service", "name": "SMS Customer Service Assistant", "category": "Customer service", "status": "planned", "proof": "not-yet-proven", "audience": "Local businesses", "claimBoundary": "SMS Customer Service Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "SMS Customer Service Assistant: the installed outcome", "headline": "SMS Customer Service Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Local businesses: a hosted pilot that starts with “Handles common questions and status updates by text,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current customer service workflow, install the minimum SMS Customer Service Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the SMS Customer Service Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "SMS Customer Service Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest SMS Customer Service Assistant installation worth proving.", "emailSubject": "SMS Customer Service Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need SMS Customer Service Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A text-message assistant for updates, reminders, triage, and lightweight customer support that meets people in the channel they already use. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "SMS Customer Service Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work SMS Customer Service Assistant can make measurable.", "offer": "SMS Customer Service Assistant begins with a diagnostic for Local businesses, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where customer service work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure SMS Customer Service Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The SMS Customer Service Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint SMS Customer Service Assistant should remove.", "emailSubject": "Where is SMS Customer Service Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give SMS Customer Service Assistant one measurable job.", "landingLead": "A simple wedge for teams that need faster follow-up without asking customers to learn another app. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "SMS Customer Service Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a SMS Customer Service Assistant offer the whole team can use.", "offer": "For Local businesses, SMS Customer Service Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for customer service, structure their decisions into a guided SMS Customer Service Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the SMS Customer Service Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "SMS Customer Service Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise SMS Customer Service Assistant should productize.", "emailSubject": "Package your best operating knowledge with SMS Customer Service Assistant", "socialHook": "Your best operator already has a product in their head. SMS Customer Service Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A text-message assistant for updates, reminders, triage, and lightweight customer support that meets people in the channel they already use. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "SMS Customer Service Assistant: the compounding playbook", "headline": "Stop rebuilding SMS Customer Service Assistant from prompts. Encode the playbook your operation can improve.", "offer": "SMS Customer Service Assistant becomes a reusable operating layer for Local businesses: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Handles common questions and status updates by text,” encode the stable decisions, isolate customer data and permissions, and improve the SMS Customer Service Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each SMS Customer Service Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "SMS Customer Service Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook SMS Customer Service Assistant should encode first.", "emailSubject": "Make SMS Customer Service Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned SMS Customer Service Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "A simple wedge for teams that need faster follow-up without asking customers to learn another app. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "SMS Customer Service Assistant: prove what compounds", "headline": "If SMS Customer Service Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Local businesses a SMS Customer Service Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from SMS Customer Service Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "SMS Customer Service Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first SMS Customer Service Assistant pilot.", "emailSubject": "What evidence would make SMS Customer Service Assistant worth expanding?", "socialHook": "The useful question is not whether SMS Customer Service Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A text-message assistant for updates, reminders, triage, and lightweight customer support that meets people in the channel they already use. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "whatsapp-customer-service", "name": "WhatsApp Customer Service Assistant", "category": "Customer service", "status": "planned", "proof": "not-yet-proven", "audience": "International teams", "claimBoundary": "WhatsApp Customer Service Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "WhatsApp Customer Service Assistant: the installed outcome", "headline": "WhatsApp Customer Service Assistant, installed around one working outcome—not another AI subscription.", "offer": "For International teams: a hosted pilot that starts with “Supports conversational service and lead qualification,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current customer service workflow, install the minimum WhatsApp Customer Service Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the WhatsApp Customer Service Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "WhatsApp Customer Service Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest WhatsApp Customer Service Assistant installation worth proving.", "emailSubject": "WhatsApp Customer Service Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need WhatsApp Customer Service Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A WhatsApp-native assistant for customer questions, qualification, scheduling, and human handoff in high-context conversations. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "WhatsApp Customer Service Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work WhatsApp Customer Service Assistant can make measurable.", "offer": "WhatsApp Customer Service Assistant begins with a diagnostic for International teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where customer service work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure WhatsApp Customer Service Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The WhatsApp Customer Service Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint WhatsApp Customer Service Assistant should remove.", "emailSubject": "Where is WhatsApp Customer Service Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give WhatsApp Customer Service Assistant one measurable job.", "landingLead": "Use the channel customers already trust, then make the operational handoff visible and manageable. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "WhatsApp Customer Service Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a WhatsApp Customer Service Assistant offer the whole team can use.", "offer": "For International teams, WhatsApp Customer Service Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for customer service, structure their decisions into a guided WhatsApp Customer Service Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the WhatsApp Customer Service Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "WhatsApp Customer Service Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise WhatsApp Customer Service Assistant should productize.", "emailSubject": "Package your best operating knowledge with WhatsApp Customer Service Assistant", "socialHook": "Your best operator already has a product in their head. WhatsApp Customer Service Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A WhatsApp-native assistant for customer questions, qualification, scheduling, and human handoff in high-context conversations. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "WhatsApp Customer Service Assistant: the compounding playbook", "headline": "Stop rebuilding WhatsApp Customer Service Assistant from prompts. Encode the playbook your operation can improve.", "offer": "WhatsApp Customer Service Assistant becomes a reusable operating layer for International teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Supports conversational service and lead qualification,” encode the stable decisions, isolate customer data and permissions, and improve the WhatsApp Customer Service Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each WhatsApp Customer Service Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "WhatsApp Customer Service Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook WhatsApp Customer Service Assistant should encode first.", "emailSubject": "Make WhatsApp Customer Service Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned WhatsApp Customer Service Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Use the channel customers already trust, then make the operational handoff visible and manageable. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "WhatsApp Customer Service Assistant: prove what compounds", "headline": "If WhatsApp Customer Service Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give International teams a WhatsApp Customer Service Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from WhatsApp Customer Service Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "WhatsApp Customer Service Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first WhatsApp Customer Service Assistant pilot.", "emailSubject": "What evidence would make WhatsApp Customer Service Assistant worth expanding?", "socialHook": "The useful question is not whether WhatsApp Customer Service Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A WhatsApp-native assistant for customer questions, qualification, scheduling, and human handoff in high-context conversations. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "email-customer-service", "name": "Email Customer Service Assistant", "category": "Customer service", "status": "planned", "proof": "not-yet-proven", "audience": "Support teams", "claimBoundary": "Email Customer Service Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Email Customer Service Assistant: the installed outcome", "headline": "Email Customer Service Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Support teams: a hosted pilot that starts with “Groups recurring requests and surfaces the next action,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current customer service workflow, install the minimum Email Customer Service Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Email Customer Service Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Email Customer Service Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Email Customer Service Assistant installation worth proving.", "emailSubject": "Email Customer Service Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Email Customer Service Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "An email operations assistant for drafting, classifying, summarizing, and routing customer conversations with a clear review boundary. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Email Customer Service Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Email Customer Service Assistant can make measurable.", "offer": "Email Customer Service Assistant begins with a diagnostic for Support teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where customer service work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Email Customer Service Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Email Customer Service Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Email Customer Service Assistant should remove.", "emailSubject": "Where is Email Customer Service Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Email Customer Service Assistant one measurable job.", "landingLead": "Turn a crowded support inbox into a calmer queue without pretending every reply should be automated. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Email Customer Service Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Email Customer Service Assistant offer the whole team can use.", "offer": "For Support teams, Email Customer Service Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for customer service, structure their decisions into a guided Email Customer Service Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Email Customer Service Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Email Customer Service Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Email Customer Service Assistant should productize.", "emailSubject": "Package your best operating knowledge with Email Customer Service Assistant", "socialHook": "Your best operator already has a product in their head. Email Customer Service Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "An email operations assistant for drafting, classifying, summarizing, and routing customer conversations with a clear review boundary. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Email Customer Service Assistant: the compounding playbook", "headline": "Stop rebuilding Email Customer Service Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Email Customer Service Assistant becomes a reusable operating layer for Support teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Groups recurring requests and surfaces the next action,” encode the stable decisions, isolate customer data and permissions, and improve the Email Customer Service Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Email Customer Service Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Email Customer Service Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Email Customer Service Assistant should encode first.", "emailSubject": "Make Email Customer Service Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Email Customer Service Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Turn a crowded support inbox into a calmer queue without pretending every reply should be automated. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Email Customer Service Assistant: prove what compounds", "headline": "If Email Customer Service Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Support teams a Email Customer Service Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Email Customer Service Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Email Customer Service Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Email Customer Service Assistant pilot.", "emailSubject": "What evidence would make Email Customer Service Assistant worth expanding?", "socialHook": "The useful question is not whether Email Customer Service Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "An email operations assistant for drafting, classifying, summarizing, and routing customer conversations with a clear review boundary. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "hermes-ai-crm", "name": "Hermes AI CRM", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "Sales teams", "claimBoundary": "Hermes AI CRM is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Hermes AI CRM: the installed outcome", "headline": "Hermes AI CRM, installed around one working outcome—not another AI subscription.", "offer": "For Sales teams: a hosted pilot that starts with “Keep lead identity, status, assignment, and activity connected,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum Hermes AI CRM capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Hermes AI CRM pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Hermes AI CRM is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Hermes AI CRM installation worth proving.", "emailSubject": "Hermes AI CRM: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Hermes AI CRM installed around one job, one owner, and one acceptance test.", "landingLead": "An AI CRM layer that keeps lead context, pipeline state, outreach approvals, follow-ups, and revenue evidence in one operating loop. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Hermes AI CRM: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Hermes AI CRM can make measurable.", "offer": "Hermes AI CRM begins with a diagnostic for Sales teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Hermes AI CRM only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Hermes AI CRM offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Hermes AI CRM should remove.", "emailSubject": "Where is Hermes AI CRM worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Hermes AI CRM one measurable job.", "landingLead": "A CRM built around agent work and accountable state changes, so automation produces a usable operating record instead of a pile of untracked messages. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Hermes AI CRM: expertise into an offer", "headline": "Turn the way your best people handle this work into a Hermes AI CRM offer the whole team can use.", "offer": "For Sales teams, Hermes AI CRM packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided Hermes AI CRM workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Hermes AI CRM workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Hermes AI CRM should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Hermes AI CRM should productize.", "emailSubject": "Package your best operating knowledge with Hermes AI CRM", "socialHook": "Your best operator already has a product in their head. Hermes AI CRM can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "An AI CRM layer that keeps lead context, pipeline state, outreach approvals, follow-ups, and revenue evidence in one operating loop. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Hermes AI CRM: the compounding playbook", "headline": "Stop rebuilding Hermes AI CRM from prompts. Encode the playbook your operation can improve.", "offer": "Hermes AI CRM becomes a reusable operating layer for Sales teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Keep lead identity, status, assignment, and activity connected,” encode the stable decisions, isolate customer data and permissions, and improve the Hermes AI CRM playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Hermes AI CRM release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Hermes AI CRM separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Hermes AI CRM should encode first.", "emailSubject": "Make Hermes AI CRM improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Hermes AI CRM playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "A CRM built around agent work and accountable state changes, so automation produces a usable operating record instead of a pile of untracked messages. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Hermes AI CRM: prove what compounds", "headline": "If Hermes AI CRM cannot connect its work to an observable result, it does not get credit.", "offer": "Give Sales teams a Hermes AI CRM deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Hermes AI CRM input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Hermes AI CRM should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Hermes AI CRM pilot.", "emailSubject": "What evidence would make Hermes AI CRM worth expanding?", "socialHook": "The useful question is not whether Hermes AI CRM ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "An AI CRM layer that keeps lead context, pipeline state, outreach approvals, follow-ups, and revenue evidence in one operating loop. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "personal-finance-assistant", "name": "Personal Finance AI Assistant", "category": "Personal finance", "status": "planned", "proof": "not-yet-proven", "audience": "Consumers", "claimBoundary": "Personal Finance AI Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Personal Finance AI Assistant: the installed outcome", "headline": "Personal Finance AI Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Consumers: a hosted pilot that starts with “Explains financial concepts in plain language,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current personal finance workflow, install the minimum Personal Finance AI Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Personal Finance AI Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Personal Finance AI Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Personal Finance AI Assistant installation worth proving.", "emailSubject": "Personal Finance AI Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Personal Finance AI Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A personal finance assistant for organizing questions, explaining trade-offs, and turning a messy money picture into a clearer next step. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Personal Finance AI Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Personal Finance AI Assistant can make measurable.", "offer": "Personal Finance AI Assistant begins with a diagnostic for Consumers, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where personal finance work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Personal Finance AI Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Personal Finance AI Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Personal Finance AI Assistant should remove.", "emailSubject": "Where is Personal Finance AI Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Personal Finance AI Assistant one measurable job.", "landingLead": "Position clarity and education first; personalized financial actions require explicit product and compliance boundaries. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Personal Finance AI Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Personal Finance AI Assistant offer the whole team can use.", "offer": "For Consumers, Personal Finance AI Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for personal finance, structure their decisions into a guided Personal Finance AI Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Personal Finance AI Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Personal Finance AI Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Personal Finance AI Assistant should productize.", "emailSubject": "Package your best operating knowledge with Personal Finance AI Assistant", "socialHook": "Your best operator already has a product in their head. Personal Finance AI Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A personal finance assistant for organizing questions, explaining trade-offs, and turning a messy money picture into a clearer next step. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Personal Finance AI Assistant: the compounding playbook", "headline": "Stop rebuilding Personal Finance AI Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Personal Finance AI Assistant becomes a reusable operating layer for Consumers: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Explains financial concepts in plain language,” encode the stable decisions, isolate customer data and permissions, and improve the Personal Finance AI Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Personal Finance AI Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Personal Finance AI Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Personal Finance AI Assistant should encode first.", "emailSubject": "Make Personal Finance AI Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Personal Finance AI Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Position clarity and education first; personalized financial actions require explicit product and compliance boundaries. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Personal Finance AI Assistant: prove what compounds", "headline": "If Personal Finance AI Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Consumers a Personal Finance AI Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Personal Finance AI Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Personal Finance AI Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Personal Finance AI Assistant pilot.", "emailSubject": "What evidence would make Personal Finance AI Assistant worth expanding?", "socialHook": "The useful question is not whether Personal Finance AI Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A personal finance assistant for organizing questions, explaining trade-offs, and turning a messy money picture into a clearer next step. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "proposal-generator", "name": "Proposal Generator", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "Agencies", "claimBoundary": "Proposal Generator is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Proposal Generator: the installed outcome", "headline": "Proposal Generator, installed around one working outcome—not another AI subscription.", "offer": "For Agencies: a hosted pilot that starts with “Builds drafts from approved CRM, discovery, offer, and proof sources,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum Proposal Generator capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Proposal Generator pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Proposal Generator is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Proposal Generator installation worth proving.", "emailSubject": "Proposal Generator: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Proposal Generator installed around one job, one owner, and one acceptance test.", "landingLead": "A proposal workflow agent that turns approved deal context into reviewable scope, pricing, proof, and next steps without inventing commercial terms. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Proposal Generator: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Proposal Generator can make measurable.", "offer": "Proposal Generator begins with a diagnostic for Agencies, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Proposal Generator only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Proposal Generator offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Proposal Generator should remove.", "emailSubject": "Where is Proposal Generator worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Proposal Generator one measurable job.", "landingLead": "Move from discovery to a buyer-ready proposal faster while keeping scope, pricing, claims, and acceptance under accountable review. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Proposal Generator: expertise into an offer", "headline": "Turn the way your best people handle this work into a Proposal Generator offer the whole team can use.", "offer": "For Agencies, Proposal Generator packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided Proposal Generator workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Proposal Generator workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Proposal Generator should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Proposal Generator should productize.", "emailSubject": "Package your best operating knowledge with Proposal Generator", "socialHook": "Your best operator already has a product in their head. Proposal Generator can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A proposal workflow agent that turns approved deal context into reviewable scope, pricing, proof, and next steps without inventing commercial terms. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Proposal Generator: the compounding playbook", "headline": "Stop rebuilding Proposal Generator from prompts. Encode the playbook your operation can improve.", "offer": "Proposal Generator becomes a reusable operating layer for Agencies: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Builds drafts from approved CRM, discovery, offer, and proof sources,” encode the stable decisions, isolate customer data and permissions, and improve the Proposal Generator playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Proposal Generator release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Proposal Generator separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Proposal Generator should encode first.", "emailSubject": "Make Proposal Generator improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Proposal Generator playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Move from discovery to a buyer-ready proposal faster while keeping scope, pricing, claims, and acceptance under accountable review. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Proposal Generator: prove what compounds", "headline": "If Proposal Generator cannot connect its work to an observable result, it does not get credit.", "offer": "Give Agencies a Proposal Generator deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Proposal Generator input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Proposal Generator should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Proposal Generator pilot.", "emailSubject": "What evidence would make Proposal Generator worth expanding?", "socialHook": "The useful question is not whether Proposal Generator ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A proposal workflow agent that turns approved deal context into reviewable scope, pricing, proof, and next steps without inventing commercial terms. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "invoice-chaser", "name": "Invoice Chaser", "category": "Accounts receivable", "status": "planned", "proof": "not-yet-proven", "audience": "Freelancers", "claimBoundary": "Invoice Chaser is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Invoice Chaser: the installed outcome", "headline": "Invoice Chaser, installed around one working outcome—not another AI subscription.", "offer": "For Freelancers: a hosted pilot that starts with “Prioritizes overdue work from approved invoice and customer state,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current accounts receivable workflow, install the minimum Invoice Chaser capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Invoice Chaser pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Invoice Chaser is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Invoice Chaser installation worth proving.", "emailSubject": "Invoice Chaser: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Invoice Chaser installed around one job, one owner, and one acceptance test.", "landingLead": "A policy-aware receivables agent that follows up on overdue invoices, preserves customer context, and escalates disputes or sensitive cases for review. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Invoice Chaser: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Invoice Chaser can make measurable.", "offer": "Invoice Chaser begins with a diagnostic for Freelancers, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where accounts receivable work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Invoice Chaser only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Invoice Chaser offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Invoice Chaser should remove.", "emailSubject": "Where is Invoice Chaser worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Invoice Chaser one measurable job.", "landingLead": "Recover time and cash without turning every overdue invoice into an awkward manual chase or an unreviewed automated threat. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Invoice Chaser: expertise into an offer", "headline": "Turn the way your best people handle this work into a Invoice Chaser offer the whole team can use.", "offer": "For Freelancers, Invoice Chaser packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for accounts receivable, structure their decisions into a guided Invoice Chaser workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Invoice Chaser workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Invoice Chaser should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Invoice Chaser should productize.", "emailSubject": "Package your best operating knowledge with Invoice Chaser", "socialHook": "Your best operator already has a product in their head. Invoice Chaser can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A policy-aware receivables agent that follows up on overdue invoices, preserves customer context, and escalates disputes or sensitive cases for review. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Invoice Chaser: the compounding playbook", "headline": "Stop rebuilding Invoice Chaser from prompts. Encode the playbook your operation can improve.", "offer": "Invoice Chaser becomes a reusable operating layer for Freelancers: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Prioritizes overdue work from approved invoice and customer state,” encode the stable decisions, isolate customer data and permissions, and improve the Invoice Chaser playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Invoice Chaser release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Invoice Chaser separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Invoice Chaser should encode first.", "emailSubject": "Make Invoice Chaser improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Invoice Chaser playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Recover time and cash without turning every overdue invoice into an awkward manual chase or an unreviewed automated threat. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Invoice Chaser: prove what compounds", "headline": "If Invoice Chaser cannot connect its work to an observable result, it does not get credit.", "offer": "Give Freelancers a Invoice Chaser deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Invoice Chaser input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Invoice Chaser should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Invoice Chaser pilot.", "emailSubject": "What evidence would make Invoice Chaser worth expanding?", "socialHook": "The useful question is not whether Invoice Chaser ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A policy-aware receivables agent that follows up on overdue invoices, preserves customer context, and escalates disputes or sensitive cases for review. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "finance-operations-assistant", "name": "Finance Operations Assistant", "category": "Finance operations", "status": "planned", "proof": "not-yet-proven", "audience": "Finance teams", "claimBoundary": "Finance Operations Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Finance Operations Assistant: the installed outcome", "headline": "Finance Operations Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Finance teams: a hosted pilot that starts with “Prepares and reconciles records for review,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current finance operations workflow, install the minimum Finance Operations Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Finance Operations Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Finance Operations Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Finance Operations Assistant installation worth proving.", "emailSubject": "Finance Operations Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Finance Operations Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A finance workflow assistant that prepares AP, AR, reconciliation, and close work for accountable human review. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Finance Operations Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Finance Operations Assistant can make measurable.", "offer": "Finance Operations Assistant begins with a diagnostic for Finance teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where finance operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Finance Operations Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Finance Operations Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Finance Operations Assistant should remove.", "emailSubject": "Where is Finance Operations Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Finance Operations Assistant one measurable job.", "landingLead": "Reduce repetitive finance preparation while keeping approvals, system authority, and segregation of duties explicit. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Finance Operations Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Finance Operations Assistant offer the whole team can use.", "offer": "For Finance teams, Finance Operations Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for finance operations, structure their decisions into a guided Finance Operations Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Finance Operations Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Finance Operations Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Finance Operations Assistant should productize.", "emailSubject": "Package your best operating knowledge with Finance Operations Assistant", "socialHook": "Your best operator already has a product in their head. Finance Operations Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A finance workflow assistant that prepares AP, AR, reconciliation, and close work for accountable human review. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Finance Operations Assistant: the compounding playbook", "headline": "Stop rebuilding Finance Operations Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Finance Operations Assistant becomes a reusable operating layer for Finance teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Prepares and reconciles records for review,” encode the stable decisions, isolate customer data and permissions, and improve the Finance Operations Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Finance Operations Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Finance Operations Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Finance Operations Assistant should encode first.", "emailSubject": "Make Finance Operations Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Finance Operations Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Reduce repetitive finance preparation while keeping approvals, system authority, and segregation of duties explicit. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Finance Operations Assistant: prove what compounds", "headline": "If Finance Operations Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Finance teams a Finance Operations Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Finance Operations Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Finance Operations Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Finance Operations Assistant pilot.", "emailSubject": "What evidence would make Finance Operations Assistant worth expanding?", "socialHook": "The useful question is not whether Finance Operations Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A finance workflow assistant that prepares AP, AR, reconciliation, and close work for accountable human review. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-attribution-remarketing", "name": "AI Attribution & Remarketing", "category": "Marketing intelligence", "status": "planned", "proof": "not-yet-proven", "audience": "Paid-growth teams", "claimBoundary": "AI Attribution & Remarketing is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Attribution & Remarketing: the installed outcome", "headline": "AI Attribution & Remarketing, installed around one working outcome—not another AI subscription.", "offer": "For Paid-growth teams: a hosted pilot that starts with “Connects campaign, journey, conversion, and customer-value evidence,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current marketing intelligence workflow, install the minimum AI Attribution & Remarketing capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Attribution & Remarketing pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Attribution & Remarketing is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Attribution & Remarketing installation worth proving.", "emailSubject": "AI Attribution & Remarketing: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Attribution & Remarketing installed around one job, one owner, and one acceptance test.", "landingLead": "A paid-growth intelligence layer that connects customer journeys to revenue and turns approved behavior into accountable follow-up. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Attribution & Remarketing: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Attribution & Remarketing can make measurable.", "offer": "AI Attribution & Remarketing begins with a diagnostic for Paid-growth teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where marketing intelligence work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Attribution & Remarketing only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Attribution & Remarketing offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Attribution & Remarketing should remove.", "emailSubject": "Where is AI Attribution & Remarketing worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Attribution & Remarketing one measurable job.", "landingLead": "Show which journeys create valuable customers, then use approved context to improve targeting and follow-up without inventing attribution certainty. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Attribution & Remarketing: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Attribution & Remarketing offer the whole team can use.", "offer": "For Paid-growth teams, AI Attribution & Remarketing packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for marketing intelligence, structure their decisions into a guided AI Attribution & Remarketing workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Attribution & Remarketing workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Attribution & Remarketing should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Attribution & Remarketing should productize.", "emailSubject": "Package your best operating knowledge with AI Attribution & Remarketing", "socialHook": "Your best operator already has a product in their head. AI Attribution & Remarketing can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A paid-growth intelligence layer that connects customer journeys to revenue and turns approved behavior into accountable follow-up. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Attribution & Remarketing: the compounding playbook", "headline": "Stop rebuilding AI Attribution & Remarketing from prompts. Encode the playbook your operation can improve.", "offer": "AI Attribution & Remarketing becomes a reusable operating layer for Paid-growth teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Connects campaign, journey, conversion, and customer-value evidence,” encode the stable decisions, isolate customer data and permissions, and improve the AI Attribution & Remarketing playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Attribution & Remarketing release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Attribution & Remarketing separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Attribution & Remarketing should encode first.", "emailSubject": "Make AI Attribution & Remarketing improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Attribution & Remarketing playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Show which journeys create valuable customers, then use approved context to improve targeting and follow-up without inventing attribution certainty. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Attribution & Remarketing: prove what compounds", "headline": "If AI Attribution & Remarketing cannot connect its work to an observable result, it does not get credit.", "offer": "Give Paid-growth teams a AI Attribution & Remarketing deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Attribution & Remarketing input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Attribution & Remarketing should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Attribution & Remarketing pilot.", "emailSubject": "What evidence would make AI Attribution & Remarketing worth expanding?", "socialHook": "The useful question is not whether AI Attribution & Remarketing ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A paid-growth intelligence layer that connects customer journeys to revenue and turns approved behavior into accountable follow-up. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "hermes-financial-adviser", "name": "Hermes Financial Adviser", "category": "Financial Intelligence", "status": "planned", "proof": "not-yet-proven", "audience": "Operators", "claimBoundary": "Hermes Financial Adviser is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Hermes Financial Adviser: the installed outcome", "headline": "Hermes Financial Adviser, installed around one working outcome—not another AI subscription.", "offer": "For Operators: a custom build pilot that starts with “Research markets, positions, and operating assumptions with cited inputs,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current financial intelligence workflow, install the minimum Hermes Financial Adviser capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Hermes Financial Adviser pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Hermes Financial Adviser is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Hermes Financial Adviser installation worth proving.", "emailSubject": "Hermes Financial Adviser: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Hermes Financial Adviser installed around one job, one owner, and one acceptance test.", "landingLead": "A dedicated Hermes financial decision-support agent for research, monitoring, scenario analysis, and disciplined human-reviewed action. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Hermes Financial Adviser: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Hermes Financial Adviser can make measurable.", "offer": "Hermes Financial Adviser begins with a diagnostic for Operators, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where financial intelligence work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Hermes Financial Adviser only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Hermes Financial Adviser offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Hermes Financial Adviser should remove.", "emailSubject": "Where is Hermes Financial Adviser worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Hermes Financial Adviser one measurable job.", "landingLead": "A disciplined financial intelligence layer that turns market and operating inputs into traceable scenarios and decisions, with suitability and execution boundaries kept explicit. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Hermes Financial Adviser: expertise into an offer", "headline": "Turn the way your best people handle this work into a Hermes Financial Adviser offer the whole team can use.", "offer": "For Operators, Hermes Financial Adviser packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for financial intelligence, structure their decisions into a guided Hermes Financial Adviser workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Hermes Financial Adviser workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Hermes Financial Adviser should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Hermes Financial Adviser should productize.", "emailSubject": "Package your best operating knowledge with Hermes Financial Adviser", "socialHook": "Your best operator already has a product in their head. Hermes Financial Adviser can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A dedicated Hermes financial decision-support agent for research, monitoring, scenario analysis, and disciplined human-reviewed action. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Hermes Financial Adviser: the compounding playbook", "headline": "Stop rebuilding Hermes Financial Adviser from prompts. Encode the playbook your operation can improve.", "offer": "Hermes Financial Adviser becomes a reusable operating layer for Operators: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Research markets, positions, and operating assumptions with cited inputs,” encode the stable decisions, isolate customer data and permissions, and improve the Hermes Financial Adviser playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Hermes Financial Adviser release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Hermes Financial Adviser separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Hermes Financial Adviser should encode first.", "emailSubject": "Make Hermes Financial Adviser improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Hermes Financial Adviser playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "A disciplined financial intelligence layer that turns market and operating inputs into traceable scenarios and decisions, with suitability and execution boundaries kept explicit. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Hermes Financial Adviser: prove what compounds", "headline": "If Hermes Financial Adviser cannot connect its work to an observable result, it does not get credit.", "offer": "Give Operators a Hermes Financial Adviser deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Hermes Financial Adviser input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Hermes Financial Adviser should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Hermes Financial Adviser pilot.", "emailSubject": "What evidence would make Hermes Financial Adviser worth expanding?", "socialHook": "The useful question is not whether Hermes Financial Adviser ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A dedicated Hermes financial decision-support agent for research, monitoring, scenario analysis, and disciplined human-reviewed action. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "personal-tutor", "name": "Personal Tutor Assistant", "category": "Learning", "status": "planned", "proof": "not-yet-proven", "audience": "Learners", "claimBoundary": "Personal Tutor Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Personal Tutor Assistant: the installed outcome", "headline": "Personal Tutor Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Learners: a hosted pilot that starts with “Adjusts explanations to a learner’s current context,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current learning workflow, install the minimum Personal Tutor Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Personal Tutor Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Personal Tutor Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Personal Tutor Assistant installation worth proving.", "emailSubject": "Personal Tutor Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Personal Tutor Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A patient tutor assistant that adapts explanations, practice, and feedback to the learner instead of serving the same lesson to everyone. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Personal Tutor Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Personal Tutor Assistant can make measurable.", "offer": "Personal Tutor Assistant begins with a diagnostic for Learners, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where learning work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Personal Tutor Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Personal Tutor Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Personal Tutor Assistant should remove.", "emailSubject": "Where is Personal Tutor Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Personal Tutor Assistant one measurable job.", "landingLead": "Sell the personalized learning loop: explain, practice, notice confusion, and try again. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Personal Tutor Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Personal Tutor Assistant offer the whole team can use.", "offer": "For Learners, Personal Tutor Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for learning, structure their decisions into a guided Personal Tutor Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Personal Tutor Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Personal Tutor Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Personal Tutor Assistant should productize.", "emailSubject": "Package your best operating knowledge with Personal Tutor Assistant", "socialHook": "Your best operator already has a product in their head. Personal Tutor Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A patient tutor assistant that adapts explanations, practice, and feedback to the learner instead of serving the same lesson to everyone. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Personal Tutor Assistant: the compounding playbook", "headline": "Stop rebuilding Personal Tutor Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Personal Tutor Assistant becomes a reusable operating layer for Learners: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Adjusts explanations to a learner’s current context,” encode the stable decisions, isolate customer data and permissions, and improve the Personal Tutor Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Personal Tutor Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Personal Tutor Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Personal Tutor Assistant should encode first.", "emailSubject": "Make Personal Tutor Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Personal Tutor Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Sell the personalized learning loop: explain, practice, notice confusion, and try again. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Personal Tutor Assistant: prove what compounds", "headline": "If Personal Tutor Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Learners a Personal Tutor Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Personal Tutor Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Personal Tutor Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Personal Tutor Assistant pilot.", "emailSubject": "What evidence would make Personal Tutor Assistant worth expanding?", "socialHook": "The useful question is not whether Personal Tutor Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A patient tutor assistant that adapts explanations, practice, and feedback to the learner instead of serving the same lesson to everyone. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-lead-generation", "name": "AI Lead Generation", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "B2B companies", "claimBoundary": "AI Lead Generation is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Lead Generation: the installed outcome", "headline": "AI Lead Generation, installed around one working outcome—not another AI subscription.", "offer": "For B2B companies: a hosted pilot that starts with “Builds prospect lists from an explicit ideal-customer profile,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum AI Lead Generation capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Lead Generation pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Lead Generation is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Lead Generation installation worth proving.", "emailSubject": "AI Lead Generation: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Lead Generation installed around one job, one owner, and one acceptance test.", "landingLead": "A research and prospecting agent that turns an ideal-customer profile into sourced, scored, and reviewable opportunities. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Lead Generation: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Lead Generation can make measurable.", "offer": "AI Lead Generation begins with a diagnostic for B2B companies, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Lead Generation only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Lead Generation offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Lead Generation should remove.", "emailSubject": "Where is AI Lead Generation worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Lead Generation one measurable job.", "landingLead": "Replace brittle list buying with an evidence-bearing prospecting loop that shows why each account fits and what should happen next. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Lead Generation: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Lead Generation offer the whole team can use.", "offer": "For B2B companies, AI Lead Generation packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided AI Lead Generation workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Lead Generation workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Lead Generation should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Lead Generation should productize.", "emailSubject": "Package your best operating knowledge with AI Lead Generation", "socialHook": "Your best operator already has a product in their head. AI Lead Generation can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A research and prospecting agent that turns an ideal-customer profile into sourced, scored, and reviewable opportunities. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Lead Generation: the compounding playbook", "headline": "Stop rebuilding AI Lead Generation from prompts. Encode the playbook your operation can improve.", "offer": "AI Lead Generation becomes a reusable operating layer for B2B companies: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Builds prospect lists from an explicit ideal-customer profile,” encode the stable decisions, isolate customer data and permissions, and improve the AI Lead Generation playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Lead Generation release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Lead Generation separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Lead Generation should encode first.", "emailSubject": "Make AI Lead Generation improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Lead Generation playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Replace brittle list buying with an evidence-bearing prospecting loop that shows why each account fits and what should happen next. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Lead Generation: prove what compounds", "headline": "If AI Lead Generation cannot connect its work to an observable result, it does not get credit.", "offer": "Give B2B companies a AI Lead Generation deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Lead Generation input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Lead Generation should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Lead Generation pilot.", "emailSubject": "What evidence would make AI Lead Generation worth expanding?", "socialHook": "The useful question is not whether AI Lead Generation ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A research and prospecting agent that turns an ideal-customer profile into sourced, scored, and reviewable opportunities. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-qualifier", "name": "AI Qualifier", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "B2B companies", "claimBoundary": "AI Qualifier is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Qualifier: the installed outcome", "headline": "AI Qualifier, installed around one working outcome—not another AI subscription.", "offer": "For B2B companies: a hosted pilot that starts with “Applies a buyer-owned fit and readiness rubric,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum AI Qualifier capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Qualifier pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Qualifier is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Qualifier installation worth proving.", "emailSubject": "AI Qualifier: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Qualifier installed around one job, one owner, and one acceptance test.", "landingLead": "A qualification agent that tests fit, urgency, authority, and next-step readiness against the seller's actual rubric. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Qualifier: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Qualifier can make measurable.", "offer": "AI Qualifier begins with a diagnostic for B2B companies, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Qualifier only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Qualifier offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Qualifier should remove.", "emailSubject": "Where is AI Qualifier worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Qualifier one measurable job.", "landingLead": "Give salespeople fewer dead-end conversations and a defensible reason each opportunity should advance, nurture, or stop. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Qualifier: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Qualifier offer the whole team can use.", "offer": "For B2B companies, AI Qualifier packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided AI Qualifier workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Qualifier workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Qualifier should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Qualifier should productize.", "emailSubject": "Package your best operating knowledge with AI Qualifier", "socialHook": "Your best operator already has a product in their head. AI Qualifier can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A qualification agent that tests fit, urgency, authority, and next-step readiness against the seller's actual rubric. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Qualifier: the compounding playbook", "headline": "Stop rebuilding AI Qualifier from prompts. Encode the playbook your operation can improve.", "offer": "AI Qualifier becomes a reusable operating layer for B2B companies: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Applies a buyer-owned fit and readiness rubric,” encode the stable decisions, isolate customer data and permissions, and improve the AI Qualifier playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Qualifier release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Qualifier separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Qualifier should encode first.", "emailSubject": "Make AI Qualifier improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Qualifier playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Give salespeople fewer dead-end conversations and a defensible reason each opportunity should advance, nurture, or stop. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Qualifier: prove what compounds", "headline": "If AI Qualifier cannot connect its work to an observable result, it does not get credit.", "offer": "Give B2B companies a AI Qualifier deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Qualifier input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Qualifier should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Qualifier pilot.", "emailSubject": "What evidence would make AI Qualifier worth expanding?", "socialHook": "The useful question is not whether AI Qualifier ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A qualification agent that tests fit, urgency, authority, and next-step readiness against the seller's actual rubric. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-setter", "name": "AI Setter", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "High-ticket teams", "claimBoundary": "AI Setter is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Setter: the installed outcome", "headline": "AI Setter, installed around one working outcome—not another AI subscription.", "offer": "For High-ticket teams: a hosted pilot that starts with “Works from qualified context and an approved outreach policy,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum AI Setter capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Setter pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Setter is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Setter installation worth proving.", "emailSubject": "AI Setter: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Setter installed around one job, one owner, and one acceptance test.", "landingLead": "An appointment-setting agent that follows up with qualified prospects, resolves scheduling friction, and records the handoff. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Setter: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Setter can make measurable.", "offer": "AI Setter begins with a diagnostic for High-ticket teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Setter only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Setter offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Setter should remove.", "emailSubject": "Where is AI Setter worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Setter one measurable job.", "landingLead": "Turn qualified interest into attended conversations through timely, contextual follow-up instead of generic calendar-link spam. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Setter: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Setter offer the whole team can use.", "offer": "For High-ticket teams, AI Setter packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided AI Setter workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Setter workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Setter should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Setter should productize.", "emailSubject": "Package your best operating knowledge with AI Setter", "socialHook": "Your best operator already has a product in their head. AI Setter can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "An appointment-setting agent that follows up with qualified prospects, resolves scheduling friction, and records the handoff. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Setter: the compounding playbook", "headline": "Stop rebuilding AI Setter from prompts. Encode the playbook your operation can improve.", "offer": "AI Setter becomes a reusable operating layer for High-ticket teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Works from qualified context and an approved outreach policy,” encode the stable decisions, isolate customer data and permissions, and improve the AI Setter playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Setter release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Setter separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Setter should encode first.", "emailSubject": "Make AI Setter improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Setter playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Turn qualified interest into attended conversations through timely, contextual follow-up instead of generic calendar-link spam. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Setter: prove what compounds", "headline": "If AI Setter cannot connect its work to an observable result, it does not get credit.", "offer": "Give High-ticket teams a AI Setter deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Setter input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Setter should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Setter pilot.", "emailSubject": "What evidence would make AI Setter worth expanding?", "socialHook": "The useful question is not whether AI Setter ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "An appointment-setting agent that follows up with qualified prospects, resolves scheduling friction, and records the handoff. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-dialer", "name": "AI Dialer", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "High-ticket teams", "claimBoundary": "AI Dialer is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Dialer: the installed outcome", "headline": "AI Dialer, installed around one working outcome—not another AI subscription.", "offer": "For High-ticket teams: a hosted pilot that starts with “Calls only within configured consent, timing, and jurisdiction rules,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum AI Dialer capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Dialer pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Dialer is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Dialer installation worth proving.", "emailSubject": "AI Dialer: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Dialer installed around one job, one owner, and one acceptance test.", "landingLead": "A voice agent for approved calls, fast lead response, structured discovery, disposition capture, and live human handoff. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Dialer: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Dialer can make measurable.", "offer": "AI Dialer begins with a diagnostic for High-ticket teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Dialer only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Dialer offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Dialer should remove.", "emailSubject": "Where is AI Dialer worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Dialer one measurable job.", "landingLead": "Make every permitted call timely and accountable, with a bounded script, clear escalation, and a complete disposition after the conversation. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Dialer: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Dialer offer the whole team can use.", "offer": "For High-ticket teams, AI Dialer packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided AI Dialer workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Dialer workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Dialer should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Dialer should productize.", "emailSubject": "Package your best operating knowledge with AI Dialer", "socialHook": "Your best operator already has a product in their head. AI Dialer can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A voice agent for approved calls, fast lead response, structured discovery, disposition capture, and live human handoff. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Dialer: the compounding playbook", "headline": "Stop rebuilding AI Dialer from prompts. Encode the playbook your operation can improve.", "offer": "AI Dialer becomes a reusable operating layer for High-ticket teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Calls only within configured consent, timing, and jurisdiction rules,” encode the stable decisions, isolate customer data and permissions, and improve the AI Dialer playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Dialer release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Dialer separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Dialer should encode first.", "emailSubject": "Make AI Dialer improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Dialer playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Make every permitted call timely and accountable, with a bounded script, clear escalation, and a complete disposition after the conversation. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Dialer: prove what compounds", "headline": "If AI Dialer cannot connect its work to an observable result, it does not get credit.", "offer": "Give High-ticket teams a AI Dialer deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Dialer input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Dialer should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Dialer pilot.", "emailSubject": "What evidence would make AI Dialer worth expanding?", "socialHook": "The useful question is not whether AI Dialer ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A voice agent for approved calls, fast lead response, structured discovery, disposition capture, and live human handoff. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-salesman", "name": "AI Salesman", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "High-ticket teams", "claimBoundary": "AI Salesman is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Salesman: the installed outcome", "headline": "AI Salesman, installed around one working outcome—not another AI subscription.", "offer": "For High-ticket teams: a hosted pilot that starts with “Maintains one evidence-backed opportunity brief across the cycle,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum AI Salesman capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Salesman pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Salesman is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Salesman installation worth proving.", "emailSubject": "AI Salesman: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Salesman installed around one job, one owner, and one acceptance test.", "landingLead": "A full-cycle sales agent that carries verified context from discovery through objection handling, proposal, and bounded close. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Salesman: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Salesman can make measurable.", "offer": "AI Salesman begins with a diagnostic for High-ticket teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Salesman only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Salesman offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Salesman should remove.", "emailSubject": "Where is AI Salesman worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Salesman one measurable job.", "landingLead": "Add selling capacity without surrendering control of claims, pricing, discounts, contracts, or the customer relationship. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Salesman: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Salesman offer the whole team can use.", "offer": "For High-ticket teams, AI Salesman packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided AI Salesman workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Salesman workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Salesman should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Salesman should productize.", "emailSubject": "Package your best operating knowledge with AI Salesman", "socialHook": "Your best operator already has a product in their head. AI Salesman can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A full-cycle sales agent that carries verified context from discovery through objection handling, proposal, and bounded close. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Salesman: the compounding playbook", "headline": "Stop rebuilding AI Salesman from prompts. Encode the playbook your operation can improve.", "offer": "AI Salesman becomes a reusable operating layer for High-ticket teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Maintains one evidence-backed opportunity brief across the cycle,” encode the stable decisions, isolate customer data and permissions, and improve the AI Salesman playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Salesman release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Salesman separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Salesman should encode first.", "emailSubject": "Make AI Salesman improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Salesman playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Add selling capacity without surrendering control of claims, pricing, discounts, contracts, or the customer relationship. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Salesman: prove what compounds", "headline": "If AI Salesman cannot connect its work to an observable result, it does not get credit.", "offer": "Give High-ticket teams a AI Salesman deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Salesman input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Salesman should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Salesman pilot.", "emailSubject": "What evidence would make AI Salesman worth expanding?", "socialHook": "The useful question is not whether AI Salesman ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A full-cycle sales agent that carries verified context from discovery through objection handling, proposal, and bounded close. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-stylist", "name": "AI Stylist", "category": "Personal style", "status": "planned", "proof": "not-yet-proven", "audience": "Consumers", "claimBoundary": "AI Stylist is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Stylist: the installed outcome", "headline": "AI Stylist, installed around one working outcome—not another AI subscription.", "offer": "For Consumers: a hosted pilot that starts with “Builds outfit ideas from wardrobe, occasion, and preference context,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current personal style workflow, install the minimum AI Stylist capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Stylist pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Stylist is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Stylist installation worth proving.", "emailSubject": "AI Stylist: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Stylist installed around one job, one owner, and one acceptance test.", "landingLead": "A personal style concierge that learns wardrobe context and preferences, assembles outfits, and narrows shopping choices without taking over the final decision. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Stylist: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Stylist can make measurable.", "offer": "AI Stylist begins with a diagnostic for Consumers, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where personal style work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Stylist only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Stylist offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Stylist should remove.", "emailSubject": "Where is AI Stylist worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Stylist one measurable job.", "landingLead": "Sell a clearer path from what someone owns and likes to what they can wear or buy next, with a white-label path for commerce partners. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Stylist: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Stylist offer the whole team can use.", "offer": "For Consumers, AI Stylist packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for personal style, structure their decisions into a guided AI Stylist workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Stylist workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Stylist should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Stylist should productize.", "emailSubject": "Package your best operating knowledge with AI Stylist", "socialHook": "Your best operator already has a product in their head. AI Stylist can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A personal style concierge that learns wardrobe context and preferences, assembles outfits, and narrows shopping choices without taking over the final decision. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Stylist: the compounding playbook", "headline": "Stop rebuilding AI Stylist from prompts. Encode the playbook your operation can improve.", "offer": "AI Stylist becomes a reusable operating layer for Consumers: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Builds outfit ideas from wardrobe, occasion, and preference context,” encode the stable decisions, isolate customer data and permissions, and improve the AI Stylist playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Stylist release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Stylist separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Stylist should encode first.", "emailSubject": "Make AI Stylist improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Stylist playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Sell a clearer path from what someone owns and likes to what they can wear or buy next, with a white-label path for commerce partners. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Stylist: prove what compounds", "headline": "If AI Stylist cannot connect its work to an observable result, it does not get credit.", "offer": "Give Consumers a AI Stylist deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Stylist input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Stylist should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Stylist pilot.", "emailSubject": "What evidence would make AI Stylist worth expanding?", "socialHook": "The useful question is not whether AI Stylist ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A personal style concierge that learns wardrobe context and preferences, assembles outfits, and narrows shopping choices without taking over the final decision. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "lead-recovery-operator", "name": "Lead Recovery Operator", "category": "Revenue operations", "status": "planned", "proof": "not-yet-proven", "audience": "Sales teams", "claimBoundary": "Lead Recovery Operator is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Lead Recovery Operator: the installed outcome", "headline": "Lead Recovery Operator, installed around one working outcome—not another AI subscription.", "offer": "For Sales teams: a hosted pilot that starts with “Works only with consented or authorized contacts,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current revenue operations workflow, install the minimum Lead Recovery Operator capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Lead Recovery Operator pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Lead Recovery Operator is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Lead Recovery Operator installation worth proving.", "emailSubject": "Lead Recovery Operator: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Lead Recovery Operator installed around one job, one owner, and one acceptance test.", "landingLead": "A governed follow-up operator for already-known leads whose conversations stalled before a clear next step. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Lead Recovery Operator: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Lead Recovery Operator can make measurable.", "offer": "Lead Recovery Operator begins with a diagnostic for Sales teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where revenue operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Lead Recovery Operator only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Lead Recovery Operator offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Lead Recovery Operator should remove.", "emailSubject": "Where is Lead Recovery Operator worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Lead Recovery Operator one measurable job.", "landingLead": "Recover value from consented, already-known leads with traceable follow-up and a firm boundary around contact authority. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Lead Recovery Operator: expertise into an offer", "headline": "Turn the way your best people handle this work into a Lead Recovery Operator offer the whole team can use.", "offer": "For Sales teams, Lead Recovery Operator packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for revenue operations, structure their decisions into a guided Lead Recovery Operator workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Lead Recovery Operator workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Lead Recovery Operator should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Lead Recovery Operator should productize.", "emailSubject": "Package your best operating knowledge with Lead Recovery Operator", "socialHook": "Your best operator already has a product in their head. Lead Recovery Operator can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A governed follow-up operator for already-known leads whose conversations stalled before a clear next step. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Lead Recovery Operator: the compounding playbook", "headline": "Stop rebuilding Lead Recovery Operator from prompts. Encode the playbook your operation can improve.", "offer": "Lead Recovery Operator becomes a reusable operating layer for Sales teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Works only with consented or authorized contacts,” encode the stable decisions, isolate customer data and permissions, and improve the Lead Recovery Operator playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Lead Recovery Operator release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Lead Recovery Operator separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Lead Recovery Operator should encode first.", "emailSubject": "Make Lead Recovery Operator improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Lead Recovery Operator playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Recover value from consented, already-known leads with traceable follow-up and a firm boundary around contact authority. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Lead Recovery Operator: prove what compounds", "headline": "If Lead Recovery Operator cannot connect its work to an observable result, it does not get credit.", "offer": "Give Sales teams a Lead Recovery Operator deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Lead Recovery Operator input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Lead Recovery Operator should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Lead Recovery Operator pilot.", "emailSubject": "What evidence would make Lead Recovery Operator worth expanding?", "socialHook": "The useful question is not whether Lead Recovery Operator ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A governed follow-up operator for already-known leads whose conversations stalled before a clear next step. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "legal-advice-assistant", "name": "Legal Advice Assistant", "category": "Legal workflows", "status": "planned", "proof": "not-yet-proven", "audience": "Legal teams", "claimBoundary": "Legal Advice Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Legal Advice Assistant: the installed outcome", "headline": "Legal Advice Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Legal teams: a custom build pilot that starts with “Summarizes and compares approved legal materials,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current legal workflows workflow, install the minimum Legal Advice Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Legal Advice Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Legal Advice Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Legal Advice Assistant installation worth proving.", "emailSubject": "Legal Advice Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Legal Advice Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A legal-workflow assistant for research, issue spotting, document explanation, and preparation with careful limits around professional advice. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Legal Advice Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Legal Advice Assistant can make measurable.", "offer": "Legal Advice Assistant begins with a diagnostic for Legal teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where legal workflows work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Legal Advice Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Legal Advice Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Legal Advice Assistant should remove.", "emailSubject": "Where is Legal Advice Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Legal Advice Assistant one measurable job.", "landingLead": "A Harvey-like workflow wedge: make legal work easier to prepare and review, never blur assistance into unauthorized practice. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Legal Advice Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Legal Advice Assistant offer the whole team can use.", "offer": "For Legal teams, Legal Advice Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for legal workflows, structure their decisions into a guided Legal Advice Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Legal Advice Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Legal Advice Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Legal Advice Assistant should productize.", "emailSubject": "Package your best operating knowledge with Legal Advice Assistant", "socialHook": "Your best operator already has a product in their head. Legal Advice Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A legal-workflow assistant for research, issue spotting, document explanation, and preparation with careful limits around professional advice. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Legal Advice Assistant: the compounding playbook", "headline": "Stop rebuilding Legal Advice Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Legal Advice Assistant becomes a reusable operating layer for Legal teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Summarizes and compares approved legal materials,” encode the stable decisions, isolate customer data and permissions, and improve the Legal Advice Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Legal Advice Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Legal Advice Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Legal Advice Assistant should encode first.", "emailSubject": "Make Legal Advice Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Legal Advice Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "A Harvey-like workflow wedge: make legal work easier to prepare and review, never blur assistance into unauthorized practice. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Legal Advice Assistant: prove what compounds", "headline": "If Legal Advice Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Legal teams a Legal Advice Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Legal Advice Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Legal Advice Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Legal Advice Assistant pilot.", "emailSubject": "What evidence would make Legal Advice Assistant worth expanding?", "socialHook": "The useful question is not whether Legal Advice Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A legal-workflow assistant for research, issue spotting, document explanation, and preparation with careful limits around professional advice. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "ai-digital-product-studio", "name": "AI Digital Product Studio", "category": "Creator commerce", "status": "planned", "proof": "not-yet-proven", "audience": "Creators", "claimBoundary": "AI Digital Product Studio is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Digital Product Studio: the installed outcome", "headline": "AI Digital Product Studio, installed around one working outcome—not another AI subscription.", "offer": "For Creators: a hosted pilot that starts with “Finds repeated audience problems in approved research and content,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current creator commerce workflow, install the minimum AI Digital Product Studio capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Digital Product Studio pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Digital Product Studio is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Digital Product Studio installation worth proving.", "emailSubject": "AI Digital Product Studio: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Digital Product Studio installed around one job, one owner, and one acceptance test.", "landingLead": "A product system for turning approved expertise and audience evidence into a course, guide, community, or coaching offer. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Digital Product Studio: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Digital Product Studio can make measurable.", "offer": "AI Digital Product Studio begins with a diagnostic for Creators, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where creator commerce work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Digital Product Studio only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Digital Product Studio offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Digital Product Studio should remove.", "emailSubject": "Where is AI Digital Product Studio worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Digital Product Studio one measurable job.", "landingLead": "Turn real expertise into a coherent product and launch system without replacing the expert, borrowing trust carelessly, or fabricating demand. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Digital Product Studio: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Digital Product Studio offer the whole team can use.", "offer": "For Creators, AI Digital Product Studio packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for creator commerce, structure their decisions into a guided AI Digital Product Studio workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Digital Product Studio workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Digital Product Studio should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Digital Product Studio should productize.", "emailSubject": "Package your best operating knowledge with AI Digital Product Studio", "socialHook": "Your best operator already has a product in their head. AI Digital Product Studio can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A product system for turning approved expertise and audience evidence into a course, guide, community, or coaching offer. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Digital Product Studio: the compounding playbook", "headline": "Stop rebuilding AI Digital Product Studio from prompts. Encode the playbook your operation can improve.", "offer": "AI Digital Product Studio becomes a reusable operating layer for Creators: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Finds repeated audience problems in approved research and content,” encode the stable decisions, isolate customer data and permissions, and improve the AI Digital Product Studio playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Digital Product Studio release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Digital Product Studio separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Digital Product Studio should encode first.", "emailSubject": "Make AI Digital Product Studio improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Digital Product Studio playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Turn real expertise into a coherent product and launch system without replacing the expert, borrowing trust carelessly, or fabricating demand. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Digital Product Studio: prove what compounds", "headline": "If AI Digital Product Studio cannot connect its work to an observable result, it does not get credit.", "offer": "Give Creators a AI Digital Product Studio deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Digital Product Studio input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Digital Product Studio should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Digital Product Studio pilot.", "emailSubject": "What evidence would make AI Digital Product Studio worth expanding?", "socialHook": "The useful question is not whether AI Digital Product Studio ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A product system for turning approved expertise and audience evidence into a course, guide, community, or coaching offer. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "marketing-campaign-studio", "name": "Marketing Campaign Studio", "category": "Marketing production", "status": "planned", "proof": "not-yet-proven", "audience": "Marketing teams", "claimBoundary": "Marketing Campaign Studio is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Marketing Campaign Studio: the installed outcome", "headline": "Marketing Campaign Studio, installed around one working outcome—not another AI subscription.", "offer": "For Marketing teams: a hosted pilot that starts with “Builds review-ready campaign variants from an approved brief,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current marketing production workflow, install the minimum Marketing Campaign Studio capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Marketing Campaign Studio pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Marketing Campaign Studio is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Marketing Campaign Studio installation worth proving.", "emailSubject": "Marketing Campaign Studio: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Marketing Campaign Studio installed around one job, one owner, and one acceptance test.", "landingLead": "A governed campaign studio for producing creative variants, launch assets, and review-ready marketing packages. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Marketing Campaign Studio: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Marketing Campaign Studio can make measurable.", "offer": "Marketing Campaign Studio begins with a diagnostic for Marketing teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where marketing production work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Marketing Campaign Studio only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Marketing Campaign Studio offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Marketing Campaign Studio should remove.", "emailSubject": "Where is Marketing Campaign Studio worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Marketing Campaign Studio one measurable job.", "landingLead": "Increase campaign production capacity while keeping claims, rights, publication, and spend under accountable control. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Marketing Campaign Studio: expertise into an offer", "headline": "Turn the way your best people handle this work into a Marketing Campaign Studio offer the whole team can use.", "offer": "For Marketing teams, Marketing Campaign Studio packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for marketing production, structure their decisions into a guided Marketing Campaign Studio workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Marketing Campaign Studio workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Marketing Campaign Studio should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Marketing Campaign Studio should productize.", "emailSubject": "Package your best operating knowledge with Marketing Campaign Studio", "socialHook": "Your best operator already has a product in their head. Marketing Campaign Studio can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A governed campaign studio for producing creative variants, launch assets, and review-ready marketing packages. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Marketing Campaign Studio: the compounding playbook", "headline": "Stop rebuilding Marketing Campaign Studio from prompts. Encode the playbook your operation can improve.", "offer": "Marketing Campaign Studio becomes a reusable operating layer for Marketing teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Builds review-ready campaign variants from an approved brief,” encode the stable decisions, isolate customer data and permissions, and improve the Marketing Campaign Studio playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Marketing Campaign Studio release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Marketing Campaign Studio separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Marketing Campaign Studio should encode first.", "emailSubject": "Make Marketing Campaign Studio improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Marketing Campaign Studio playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Increase campaign production capacity while keeping claims, rights, publication, and spend under accountable control. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Marketing Campaign Studio: prove what compounds", "headline": "If Marketing Campaign Studio cannot connect its work to an observable result, it does not get credit.", "offer": "Give Marketing teams a Marketing Campaign Studio deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Marketing Campaign Studio input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Marketing Campaign Studio should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Marketing Campaign Studio pilot.", "emailSubject": "What evidence would make Marketing Campaign Studio worth expanding?", "socialHook": "The useful question is not whether Marketing Campaign Studio ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A governed campaign studio for producing creative variants, launch assets, and review-ready marketing packages. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "expert-knowledge-assistant", "name": "Expert Knowledge Assistant", "category": "Knowledge products", "status": "planned", "proof": "not-yet-proven", "audience": "Experts", "claimBoundary": "Expert Knowledge Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Expert Knowledge Assistant: the installed outcome", "headline": "Expert Knowledge Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Experts: a hosted pilot that starts with “Answers from an approved, versioned source library,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current knowledge products workflow, install the minimum Expert Knowledge Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Expert Knowledge Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Expert Knowledge Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Expert Knowledge Assistant installation worth proving.", "emailSubject": "Expert Knowledge Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Expert Knowledge Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A source-grounded advisor that makes an expert's approved books, lessons, frameworks, and decisions available as an interactive product. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Expert Knowledge Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Expert Knowledge Assistant can make measurable.", "offer": "Expert Knowledge Assistant begins with a diagnostic for Experts, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where knowledge products work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Expert Knowledge Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Expert Knowledge Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Expert Knowledge Assistant should remove.", "emailSubject": "Where is Expert Knowledge Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Expert Knowledge Assistant one measurable job.", "landingLead": "Package a trusted body of work as a useful advisor with citations, identity boundaries, update ownership, and a clear route to the human expert. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Expert Knowledge Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Expert Knowledge Assistant offer the whole team can use.", "offer": "For Experts, Expert Knowledge Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for knowledge products, structure their decisions into a guided Expert Knowledge Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Expert Knowledge Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Expert Knowledge Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Expert Knowledge Assistant should productize.", "emailSubject": "Package your best operating knowledge with Expert Knowledge Assistant", "socialHook": "Your best operator already has a product in their head. Expert Knowledge Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A source-grounded advisor that makes an expert's approved books, lessons, frameworks, and decisions available as an interactive product. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Expert Knowledge Assistant: the compounding playbook", "headline": "Stop rebuilding Expert Knowledge Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Expert Knowledge Assistant becomes a reusable operating layer for Experts: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Answers from an approved, versioned source library,” encode the stable decisions, isolate customer data and permissions, and improve the Expert Knowledge Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Expert Knowledge Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Expert Knowledge Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Expert Knowledge Assistant should encode first.", "emailSubject": "Make Expert Knowledge Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Expert Knowledge Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Package a trusted body of work as a useful advisor with citations, identity boundaries, update ownership, and a clear route to the human expert. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Expert Knowledge Assistant: prove what compounds", "headline": "If Expert Knowledge Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Experts a Expert Knowledge Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Expert Knowledge Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Expert Knowledge Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Expert Knowledge Assistant pilot.", "emailSubject": "What evidence would make Expert Knowledge Assistant worth expanding?", "socialHook": "The useful question is not whether Expert Knowledge Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A source-grounded advisor that makes an expert's approved books, lessons, frameworks, and decisions available as an interactive product. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "document-operations-agent", "name": "Document Operations Agent", "category": "Business operations", "status": "planned", "proof": "not-yet-proven", "audience": "Operations teams", "claimBoundary": "Document Operations Agent is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Document Operations Agent: the installed outcome", "headline": "Document Operations Agent, installed around one working outcome—not another AI subscription.", "offer": "For Operations teams: a hosted pilot that starts with “Extracts fields only from authorized source documents,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current business operations workflow, install the minimum Document Operations Agent capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Document Operations Agent pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Document Operations Agent is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Document Operations Agent installation worth proving.", "emailSubject": "Document Operations Agent: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Document Operations Agent installed around one job, one owner, and one acceptance test.", "landingLead": "A document workflow agent that extracts, validates, and routes business data while making uncertainty and exceptions visible. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Document Operations Agent: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Document Operations Agent can make measurable.", "offer": "Document Operations Agent begins with a diagnostic for Operations teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where business operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Document Operations Agent only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Document Operations Agent offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Document Operations Agent should remove.", "emailSubject": "Where is Document Operations Agent worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Document Operations Agent one measurable job.", "landingLead": "Turn recurring document handling into a traceable workflow without hiding uncertainty or bypassing the people accountable for exceptions. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Document Operations Agent: expertise into an offer", "headline": "Turn the way your best people handle this work into a Document Operations Agent offer the whole team can use.", "offer": "For Operations teams, Document Operations Agent packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for business operations, structure their decisions into a guided Document Operations Agent workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Document Operations Agent workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Document Operations Agent should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Document Operations Agent should productize.", "emailSubject": "Package your best operating knowledge with Document Operations Agent", "socialHook": "Your best operator already has a product in their head. Document Operations Agent can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A document workflow agent that extracts, validates, and routes business data while making uncertainty and exceptions visible. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Document Operations Agent: the compounding playbook", "headline": "Stop rebuilding Document Operations Agent from prompts. Encode the playbook your operation can improve.", "offer": "Document Operations Agent becomes a reusable operating layer for Operations teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Extracts fields only from authorized source documents,” encode the stable decisions, isolate customer data and permissions, and improve the Document Operations Agent playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Document Operations Agent release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Document Operations Agent separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Document Operations Agent should encode first.", "emailSubject": "Make Document Operations Agent improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Document Operations Agent playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Turn recurring document handling into a traceable workflow without hiding uncertainty or bypassing the people accountable for exceptions. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Document Operations Agent: prove what compounds", "headline": "If Document Operations Agent cannot connect its work to an observable result, it does not get credit.", "offer": "Give Operations teams a Document Operations Agent deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Document Operations Agent input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Document Operations Agent should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Document Operations Agent pilot.", "emailSubject": "What evidence would make Document Operations Agent worth expanding?", "socialHook": "The useful question is not whether Document Operations Agent ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A document workflow agent that extracts, validates, and routes business data while making uncertainty and exceptions visible. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "internal-knowledge-assistant", "name": "Internal Knowledge Assistant", "category": "Business operations", "status": "planned", "proof": "not-yet-proven", "audience": "Companies", "claimBoundary": "Internal Knowledge Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Internal Knowledge Assistant: the installed outcome", "headline": "Internal Knowledge Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Companies: a hosted pilot that starts with “Answers from an organization’s approved source material,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current business operations workflow, install the minimum Internal Knowledge Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Internal Knowledge Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Internal Knowledge Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Internal Knowledge Assistant installation worth proving.", "emailSubject": "Internal Knowledge Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Internal Knowledge Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A private knowledge assistant that helps teams find answers, understand decisions, and work from the source material they already own. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Internal Knowledge Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Internal Knowledge Assistant can make measurable.", "offer": "Internal Knowledge Assistant begins with a diagnostic for Companies, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where business operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Internal Knowledge Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Internal Knowledge Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Internal Knowledge Assistant should remove.", "emailSubject": "Where is Internal Knowledge Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Internal Knowledge Assistant one measurable job.", "landingLead": "A practical first agent for organizations that need their own knowledge to become usable without becoming public. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Internal Knowledge Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Internal Knowledge Assistant offer the whole team can use.", "offer": "For Companies, Internal Knowledge Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for business operations, structure their decisions into a guided Internal Knowledge Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Internal Knowledge Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Internal Knowledge Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Internal Knowledge Assistant should productize.", "emailSubject": "Package your best operating knowledge with Internal Knowledge Assistant", "socialHook": "Your best operator already has a product in their head. Internal Knowledge Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A private knowledge assistant that helps teams find answers, understand decisions, and work from the source material they already own. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Internal Knowledge Assistant: the compounding playbook", "headline": "Stop rebuilding Internal Knowledge Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Internal Knowledge Assistant becomes a reusable operating layer for Companies: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Answers from an organization’s approved source material,” encode the stable decisions, isolate customer data and permissions, and improve the Internal Knowledge Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Internal Knowledge Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Internal Knowledge Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Internal Knowledge Assistant should encode first.", "emailSubject": "Make Internal Knowledge Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Internal Knowledge Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "A practical first agent for organizations that need their own knowledge to become usable without becoming public. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Internal Knowledge Assistant: prove what compounds", "headline": "If Internal Knowledge Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Companies a Internal Knowledge Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Internal Knowledge Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Internal Knowledge Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Internal Knowledge Assistant pilot.", "emailSubject": "What evidence would make Internal Knowledge Assistant worth expanding?", "socialHook": "The useful question is not whether Internal Knowledge Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A private knowledge assistant that helps teams find answers, understand decisions, and work from the source material they already own. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "clinical-documentation-assistant", "name": "Clinical Documentation Assistant", "category": "Healthcare operations", "status": "planned", "proof": "not-yet-proven", "audience": "Clinical teams", "claimBoundary": "Clinical Documentation Assistant is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Clinical Documentation Assistant: the installed outcome", "headline": "Clinical Documentation Assistant, installed around one working outcome—not another AI subscription.", "offer": "For Clinical teams: a custom build pilot that starts with “Prepares drafts for clinician review,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current healthcare operations workflow, install the minimum Clinical Documentation Assistant capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Clinical Documentation Assistant pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Clinical Documentation Assistant is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Clinical Documentation Assistant installation worth proving.", "emailSubject": "Clinical Documentation Assistant: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Clinical Documentation Assistant installed around one job, one owner, and one acceptance test.", "landingLead": "A privacy-bounded assistant that prepares clinical documentation for accountable clinician review. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Clinical Documentation Assistant: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Clinical Documentation Assistant can make measurable.", "offer": "Clinical Documentation Assistant begins with a diagnostic for Clinical teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where healthcare operations work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Clinical Documentation Assistant only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Clinical Documentation Assistant offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Clinical Documentation Assistant should remove.", "emailSubject": "Where is Clinical Documentation Assistant worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Clinical Documentation Assistant one measurable job.", "landingLead": "Reduce documentation burden without moving clinical judgment, patient privacy, or chart accountability away from qualified people. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Clinical Documentation Assistant: expertise into an offer", "headline": "Turn the way your best people handle this work into a Clinical Documentation Assistant offer the whole team can use.", "offer": "For Clinical teams, Clinical Documentation Assistant packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for healthcare operations, structure their decisions into a guided Clinical Documentation Assistant workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Clinical Documentation Assistant workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Clinical Documentation Assistant should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Clinical Documentation Assistant should productize.", "emailSubject": "Package your best operating knowledge with Clinical Documentation Assistant", "socialHook": "Your best operator already has a product in their head. Clinical Documentation Assistant can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A privacy-bounded assistant that prepares clinical documentation for accountable clinician review. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Clinical Documentation Assistant: the compounding playbook", "headline": "Stop rebuilding Clinical Documentation Assistant from prompts. Encode the playbook your operation can improve.", "offer": "Clinical Documentation Assistant becomes a reusable operating layer for Clinical teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Prepares drafts for clinician review,” encode the stable decisions, isolate customer data and permissions, and improve the Clinical Documentation Assistant playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Clinical Documentation Assistant release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Clinical Documentation Assistant separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Clinical Documentation Assistant should encode first.", "emailSubject": "Make Clinical Documentation Assistant improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Clinical Documentation Assistant playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Reduce documentation burden without moving clinical judgment, patient privacy, or chart accountability away from qualified people. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Clinical Documentation Assistant: prove what compounds", "headline": "If Clinical Documentation Assistant cannot connect its work to an observable result, it does not get credit.", "offer": "Give Clinical teams a Clinical Documentation Assistant deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Clinical Documentation Assistant input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Clinical Documentation Assistant should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Clinical Documentation Assistant pilot.", "emailSubject": "What evidence would make Clinical Documentation Assistant worth expanding?", "socialHook": "The useful question is not whether Clinical Documentation Assistant ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A privacy-bounded assistant that prepares clinical documentation for accountable clinician review. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "trading-agent", "name": "Automated Trading Agent", "category": "Capital intelligence", "status": "planned", "proof": "not-yet-proven", "audience": "Traders", "claimBoundary": "Automated Trading Agent is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Automated Trading Agent: the installed outcome", "headline": "Automated Trading Agent, installed around one working outcome—not another AI subscription.", "offer": "For Traders: a custom build pilot that starts with “Organizes market research and scenario analysis,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current capital intelligence workflow, install the minimum Automated Trading Agent capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Automated Trading Agent pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Automated Trading Agent is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Automated Trading Agent installation worth proving.", "emailSubject": "Automated Trading Agent: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Automated Trading Agent installed around one job, one owner, and one acceptance test.", "landingLead": "A trading-research and automation assistant for monitoring signals, testing hypotheses, and making decision context more legible. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Automated Trading Agent: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Automated Trading Agent can make measurable.", "offer": "Automated Trading Agent begins with a diagnostic for Traders, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where capital intelligence work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Automated Trading Agent only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Automated Trading Agent offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Automated Trading Agent should remove.", "emailSubject": "Where is Automated Trading Agent worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Automated Trading Agent one measurable job.", "landingLead": "Lead with research discipline and team visibility; live execution is a separate, authorization-heavy product decision. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Automated Trading Agent: expertise into an offer", "headline": "Turn the way your best people handle this work into a Automated Trading Agent offer the whole team can use.", "offer": "For Traders, Automated Trading Agent packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for capital intelligence, structure their decisions into a guided Automated Trading Agent workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Automated Trading Agent workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Automated Trading Agent should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Automated Trading Agent should productize.", "emailSubject": "Package your best operating knowledge with Automated Trading Agent", "socialHook": "Your best operator already has a product in their head. Automated Trading Agent can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A trading-research and automation assistant for monitoring signals, testing hypotheses, and making decision context more legible. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Automated Trading Agent: the compounding playbook", "headline": "Stop rebuilding Automated Trading Agent from prompts. Encode the playbook your operation can improve.", "offer": "Automated Trading Agent becomes a reusable operating layer for Traders: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Organizes market research and scenario analysis,” encode the stable decisions, isolate customer data and permissions, and improve the Automated Trading Agent playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Automated Trading Agent release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Automated Trading Agent separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Automated Trading Agent should encode first.", "emailSubject": "Make Automated Trading Agent improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Automated Trading Agent playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Lead with research discipline and team visibility; live execution is a separate, authorization-heavy product decision. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Automated Trading Agent: prove what compounds", "headline": "If Automated Trading Agent cannot connect its work to an observable result, it does not get credit.", "offer": "Give Traders a Automated Trading Agent deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Automated Trading Agent input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Automated Trading Agent should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Automated Trading Agent pilot.", "emailSubject": "What evidence would make Automated Trading Agent worth expanding?", "socialHook": "The useful question is not whether Automated Trading Agent ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A trading-research and automation assistant for monitoring signals, testing hypotheses, and making decision context more legible. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "revenue-intelligence-platform", "name": "Revenue Intelligence Platform", "category": "Data intelligence", "status": "planned", "proof": "not-yet-proven", "audience": "Revenue teams", "claimBoundary": "Revenue Intelligence Platform is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Revenue Intelligence Platform: the installed outcome", "headline": "Revenue Intelligence Platform, installed around one working outcome—not another AI subscription.", "offer": "For Revenue teams: a hosted pilot that starts with “Uses first-party or consented data,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current data intelligence workflow, install the minimum Revenue Intelligence Platform capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Revenue Intelligence Platform pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Revenue Intelligence Platform is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Revenue Intelligence Platform installation worth proving.", "emailSubject": "Revenue Intelligence Platform: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Revenue Intelligence Platform installed around one job, one owner, and one acceptance test.", "landingLead": "A revenue measurement layer that connects consented events, attribution, and outcome review without overstating causality. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Revenue Intelligence Platform: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Revenue Intelligence Platform can make measurable.", "offer": "Revenue Intelligence Platform begins with a diagnostic for Revenue teams, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where data intelligence work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Revenue Intelligence Platform only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Revenue Intelligence Platform offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Revenue Intelligence Platform should remove.", "emailSubject": "Where is Revenue Intelligence Platform worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Revenue Intelligence Platform one measurable job.", "landingLead": "Make revenue signals easier to inspect while separating directional attribution from experimentally verified incrementality. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Revenue Intelligence Platform: expertise into an offer", "headline": "Turn the way your best people handle this work into a Revenue Intelligence Platform offer the whole team can use.", "offer": "For Revenue teams, Revenue Intelligence Platform packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for data intelligence, structure their decisions into a guided Revenue Intelligence Platform workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Revenue Intelligence Platform workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Revenue Intelligence Platform should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Revenue Intelligence Platform should productize.", "emailSubject": "Package your best operating knowledge with Revenue Intelligence Platform", "socialHook": "Your best operator already has a product in their head. Revenue Intelligence Platform can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A revenue measurement layer that connects consented events, attribution, and outcome review without overstating causality. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Revenue Intelligence Platform: the compounding playbook", "headline": "Stop rebuilding Revenue Intelligence Platform from prompts. Encode the playbook your operation can improve.", "offer": "Revenue Intelligence Platform becomes a reusable operating layer for Revenue teams: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Uses first-party or consented data,” encode the stable decisions, isolate customer data and permissions, and improve the Revenue Intelligence Platform playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Revenue Intelligence Platform release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Revenue Intelligence Platform separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Revenue Intelligence Platform should encode first.", "emailSubject": "Make Revenue Intelligence Platform improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Revenue Intelligence Platform playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Make revenue signals easier to inspect while separating directional attribution from experimentally verified incrementality. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Revenue Intelligence Platform: prove what compounds", "headline": "If Revenue Intelligence Platform cannot connect its work to an observable result, it does not get credit.", "offer": "Give Revenue teams a Revenue Intelligence Platform deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Revenue Intelligence Platform input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Revenue Intelligence Platform should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Revenue Intelligence Platform pilot.", "emailSubject": "What evidence would make Revenue Intelligence Platform worth expanding?", "socialHook": "The useful question is not whether Revenue Intelligence Platform ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A revenue measurement layer that connects consented events, attribution, and outcome review without overstating causality. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "sports-betting-agent", "name": "Sports Betting Intelligence Agent", "category": "Sports intelligence", "status": "planned", "proof": "not-yet-proven", "audience": "Sports fans", "claimBoundary": "Sports Betting Intelligence Agent is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "Sports Betting Intelligence Agent: the installed outcome", "headline": "Sports Betting Intelligence Agent, installed around one working outcome—not another AI subscription.", "offer": "For Sports fans: a hosted pilot that starts with “Compares evidence and assumptions around a sports thesis,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current sports intelligence workflow, install the minimum Sports Betting Intelligence Agent capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the Sports Betting Intelligence Agent pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "Sports Betting Intelligence Agent is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest Sports Betting Intelligence Agent installation worth proving.", "emailSubject": "Sports Betting Intelligence Agent: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need Sports Betting Intelligence Agent installed around one job, one owner, and one acceptance test.", "landingLead": "A sports research assistant for comparing information, tracking assumptions, and making a betting thesis easier to inspect. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "Sports Betting Intelligence Agent: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work Sports Betting Intelligence Agent can make measurable.", "offer": "Sports Betting Intelligence Agent begins with a diagnostic for Sports fans, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where sports intelligence work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure Sports Betting Intelligence Agent only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The Sports Betting Intelligence Agent offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint Sports Betting Intelligence Agent should remove.", "emailSubject": "Where is Sports Betting Intelligence Agent worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give Sports Betting Intelligence Agent one measurable job.", "landingLead": "Sell the quality of the research loop and the visibility of assumptions, not certainty or guaranteed outcomes. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "Sports Betting Intelligence Agent: expertise into an offer", "headline": "Turn the way your best people handle this work into a Sports Betting Intelligence Agent offer the whole team can use.", "offer": "For Sports fans, Sports Betting Intelligence Agent packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for sports intelligence, structure their decisions into a guided Sports Betting Intelligence Agent workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the Sports Betting Intelligence Agent workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "Sports Betting Intelligence Agent should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise Sports Betting Intelligence Agent should productize.", "emailSubject": "Package your best operating knowledge with Sports Betting Intelligence Agent", "socialHook": "Your best operator already has a product in their head. Sports Betting Intelligence Agent can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "A sports research assistant for comparing information, tracking assumptions, and making a betting thesis easier to inspect. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "Sports Betting Intelligence Agent: the compounding playbook", "headline": "Stop rebuilding Sports Betting Intelligence Agent from prompts. Encode the playbook your operation can improve.", "offer": "Sports Betting Intelligence Agent becomes a reusable operating layer for Sports fans: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Compares evidence and assumptions around a sports thesis,” encode the stable decisions, isolate customer data and permissions, and improve the Sports Betting Intelligence Agent playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each Sports Betting Intelligence Agent release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "Sports Betting Intelligence Agent separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook Sports Betting Intelligence Agent should encode first.", "emailSubject": "Make Sports Betting Intelligence Agent improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned Sports Betting Intelligence Agent playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Sell the quality of the research loop and the visibility of assumptions, not certainty or guaranteed outcomes. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "Sports Betting Intelligence Agent: prove what compounds", "headline": "If Sports Betting Intelligence Agent cannot connect its work to an observable result, it does not get credit.", "offer": "Give Sports fans a Sports Betting Intelligence Agent deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from Sports Betting Intelligence Agent input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "Sports Betting Intelligence Agent should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first Sports Betting Intelligence Agent pilot.", "emailSubject": "What evidence would make Sports Betting Intelligence Agent worth expanding?", "socialHook": "The useful question is not whether Sports Betting Intelligence Agent ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "A sports research assistant for comparing information, tracking assumptions, and making a betting thesis easier to inspect. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] }, { "slug": "agency-ai-workbench", "name": "AI Agency Operating System", "category": "Agency infrastructure", "status": "planned", "proof": "not-yet-proven", "audience": "Agencies", "claimBoundary": "AI Agency Operating System is planned catalogue inventory and not yet proven live. The copy below is a campaign starter, not a claim of availability, customer results, or verified demand.", "campaigns": [ { "lens": "outcome-installation", "campaignName": "AI Agency Operating System: the installed outcome", "headline": "AI Agency Operating System, installed around one working outcome—not another AI subscription.", "offer": "For Agencies: a hosted pilot that starts with “Supports reusable software and fixed installation packages,” then configures the workflow, permissions, handoffs, and operating owner around it.", "mechanism": "Map the current agency infrastructure workflow, install the minimum AI Agency Operating System capability, test representative cases, train the owner, and separate the fixed installation from any optional managed operation.", "proofPlan": "Baseline cycle time, backlog, error rate, or conversion before the AI Agency Operating System pilot; verify the same measure after a bounded acceptance test and retain the receipts.", "objection": "“We do not need another platform that creates more work for the team.”", "response": "AI Agency Operating System is positioned as an installed workflow with a named owner and acceptance test. If it cannot remove a specific burden, the scope does not expand.", "cta": "Scope the smallest AI Agency Operating System installation worth proving.", "emailSubject": "AI Agency Operating System: one workflow, installed and measured", "socialHook": "Most teams do not need more AI access. They need AI Agency Operating System installed around one job, one owner, and one acceptance test.", "landingLead": "Reusable software for agencies to install, configure, and operate governed AI services across client accounts. Start with a bounded installation, prove the operating result, then decide whether continued optimization deserves a retainer." }, { "lens": "constraint-offer", "campaignName": "AI Agency Operating System: remove the constraint", "headline": "The constraint is not “we need AI.” It is the work AI Agency Operating System can make measurable.", "offer": "AI Agency Operating System begins with a diagnostic for Agencies, isolates the most expensive repeatable constraint, and packages the intervention around a result the buyer can inspect.", "mechanism": "Identify where agency infrastructure work queues, stalls, leaks, or depends on memory; choose one constraint, define the authority boundary, and configure AI Agency Operating System only around that point.", "proofPlan": "Record the constraint's baseline cost, volume, delay, or loss; measure the pilot against a pre-agreed threshold and verify exceptions instead of hiding them in an average.", "objection": "“This sounds broad, expensive, and difficult to adopt.”", "response": "The AI Agency Operating System offer is intentionally narrow: one constraint, one accountable owner, one measurement window, and a stop decision before broader rollout.", "cta": "Diagnose the first constraint AI Agency Operating System should remove.", "emailSubject": "Where is AI Agency Operating System worth deploying first?", "socialHook": "“Add AI” is not a strategy. Find the operating constraint, price the drag, and give AI Agency Operating System one measurable job.", "landingLead": "Package reusable software as a fixed installation or managed operation while keeping every client's authority and delivery evidence separate. The offer is strongest when the buyer can point to the before state, the intervention, and the evidence required to continue." }, { "lens": "expertise-product", "campaignName": "AI Agency Operating System: expertise into an offer", "headline": "Turn the way your best people handle this work into a AI Agency Operating System offer the whole team can use.", "offer": "For Agencies, AI Agency Operating System packages approved knowledge, operating guidance, reusable assets, and supported delivery into a ladder that can start small and deepen after proof.", "mechanism": "Collect owned source material, interview the people responsible for agency infrastructure, structure their decisions into a guided AI Agency Operating System workflow, and keep expert review visible at consequential steps.", "proofPlan": "Test the AI Agency Operating System workflow with real representative users; measure task completion, correction rate, time saved, and whether users return without being pushed.", "objection": "“Our expertise is too nuanced to flatten into templates or generic AI copy.”", "response": "AI Agency Operating System should preserve source attribution, uncertainty, and expert approval. The product distributes judgment; it does not borrow an identity or erase the author.", "cta": "Choose the first piece of expertise AI Agency Operating System should productize.", "emailSubject": "Package your best operating knowledge with AI Agency Operating System", "socialHook": "Your best operator already has a product in their head. AI Agency Operating System can turn the repeatable parts into an offer without pretending nuance disappeared.", "landingLead": "Reusable software for agencies to install, configure, and operate governed AI services across client accounts. Build the first version from owned knowledge, test whether it helps a real audience, and earn the right to add education, service, licensing, or support." }, { "lens": "encoded-playbook", "campaignName": "AI Agency Operating System: the compounding playbook", "headline": "Stop rebuilding AI Agency Operating System from prompts. Encode the playbook your operation can improve.", "offer": "AI Agency Operating System becomes a reusable operating layer for Agencies: versioned instructions, approved data, integrations, decision rules, evaluation cases, and explicit escalation paths.", "mechanism": "Observe how the best operator performs “Supports reusable software and fixed installation packages,” encode the stable decisions, isolate customer data and permissions, and improve the AI Agency Operating System playbook from reviewed exceptions.", "proofPlan": "Run a fixed evaluation set before each AI Agency Operating System release; compare accuracy, escalation quality, latency, cost, and operator corrections with versioned evidence.", "objection": "“A reusable system will become rigid or leak context between clients and teams.”", "response": "AI Agency Operating System separates the reusable playbook from tenant-specific data, credentials, policy, and authority. Reuse compounds the method—not private context.", "cta": "Map the playbook AI Agency Operating System should encode first.", "emailSubject": "Make AI Agency Operating System improve with every reviewed case", "socialHook": "Prompts are disposable. A versioned AI Agency Operating System playbook—rules, cases, boundaries, receipts—can become operating leverage.", "landingLead": "Package reusable software as a fixed installation or managed operation while keeping every client's authority and delivery evidence separate. The durable asset is not a clever prompt; it is a governed playbook that survives staff changes and gets better from evidence." }, { "lens": "evidence-loop", "campaignName": "AI Agency Operating System: prove what compounds", "headline": "If AI Agency Operating System cannot connect its work to an observable result, it does not get credit.", "offer": "Give Agencies a AI Agency Operating System deployment with measurement designed in: consented events, workflow receipts, outcome definitions, review queues, and a decision rule for what happens next.", "mechanism": "Instrument the path from AI Agency Operating System input to action to outcome; distinguish direct observations from modeled influence, preserve failed cases, and feed verified findings into the next operating decision.", "proofPlan": "Define the baseline and attribution limits before launch, measure leading and lagging indicators, verify data coverage, and use a holdout or comparable check when causality matters.", "objection": "“Attribution will overstate the system's impact and turn noisy activity into a success story.”", "response": "AI Agency Operating System should label what was observed, inferred, and independently verified. Uncertain attribution is a reason to improve the test—not manufacture certainty.", "cta": "Design the evidence loop for the first AI Agency Operating System pilot.", "emailSubject": "What evidence would make AI Agency Operating System worth expanding?", "socialHook": "The useful question is not whether AI Agency Operating System ran. It is what changed, what evidence connects the change, and what decision that evidence supports.", "landingLead": "Reusable software for agencies to install, configure, and operate governed AI services across client accounts. Instrument the journey before scaling so the buyer can protect what works, stop what does not, and separate activity from verified value." } ] } ] }