acquisition-strategy
Acquisition Strategy & Campaigns
Reuse Growth Context
At the start, read .agents/growth-context.md when it exists. Reuse only product, customer, market, outcome, constraint, evidence, and routing fields whose scope, definition, source, and date remain compatible; state what is reused and surface conflicts or staleness before asking for decision-changing gaps. The file grants no system access or execution authority, and this Skill must not silently rewrite the primary diagnosis.
Integrated Capabilities
This Skill consolidates adjacent workflows behind one trigger. Use the main workflow for core requests. When a request matches a module below, read that module before executing it:
Design a portfolio that connects a defined customer problem and reachable intent to incremental customers who activate, retain, and create acceptable contribution. Reach, traffic, leads, signups, rankings, followers, attributed conversions, low historical CAC, and channel count are operating signals; none proves acquisition quality, incrementality, economics, or diversification.
Read acquisition-contract.md before accepting audience, source, attribution, cohort, cost, retention, contribution, saturation, or dependency evidence. Read channel-and-portfolio-methods.md before selecting, sequencing, scaling, diversifying, or stopping channels. Read measurement-and-economics.md before calculating CAC, payback, contribution, incrementality, or allocation. Read market-entry-and-risk.md for international, platform, partner, concentration, privacy, and operating boundaries. Read output-contract.md before delivery. Use playbook-sources.md to cite the pinned Growth Playbook basis.