An Acquisition Growth Lever is a single, measurable action—such as a referral bonus or a new ad creative—designed to increase the rate at which new users join. It is scoped, tracked, and evaluated independently of broader campaigns.
An Acquisition Intent Note is a short written entry that records the observed signals (e.g., content viewed, referral source) indicating a prospect’s readiness to join. It is attached to the prospect’s profile for future outreach.
An Acquisition Loop outlines the full journey a potential user follows, including touchpoints, content, and conversion steps. It highlights where data passes between marketing, sales, and product teams.
An Acquisition Map is a visual representation that lists all inbound pathways—social, SEO, referrals, paid ads—and the specific assets (landing pages, forms) that guide prospects toward signup.
An Acquisition Matrix is a two‑dimensional planning sheet that aligns specific audience segments with chosen acquisition channels and the core message for each pairing, helping teams coordinate growth efforts.
An Acquisition Model is a documented strategy that specifies the steps a builder takes to bring new participants into a project and keep them engaged. It maps acquisition channels, conversion tactics, and retention indicators.
An Acquisition Path outlines the specific channels, touchpoints, and actions a builder uses to bring a prospect into the community. It serves as a reference for planning and improving outreach efforts.
Acquisition Proof is any verifiable record—such as a referral code usage, a tracked URL click, or a signed welcome email—that links a new member to a specific acquisition effort. It validates the effectiveness of that effort.
The Acquisition Quality Bar lists required traits—such as relevant skill set, commitment level, or alignment with community goals—that a new member should possess. It helps filter leads before onboarding.
The Acquisition Scorecard aggregates key performance indicators for a specific campaign into a single view. Scores guide decisions on scaling or adjusting tactics.
An Acquisition Signal is a recorded indicator—such as a click, form submission, or content view—that marks the initial point of contact between a potential builder and a marketing effort. It serves as the baseline for measuring subsequent engagement.
An Acquisition Snapshot captures the latest quantitative and qualitative state of member recruitment, typically refreshed weekly. It provides a quick reference for the team.
An Acquisition Strategy is a documented plan that identifies who you want to attract, what value you promise, and which outreach methods you will employ. It guides coordinated efforts across marketing, partnerships, and product touchpoints.
An Acquisition Tracker is a lightweight record that logs every inbound user acquisition event, capturing the origin, date, and resulting sign‑ups. It helps teams compare channel performance without requiring complex analytics tools.
An Ambassador Calendar is a shared timeline that outlines when each community ambassador will host events, post updates, or run campaigns. It helps prevent overlap and ensures continuous visibility for the community.
The Ambassador Engine comprises onboarding workflows, communication templates, and incentive mechanisms that streamline the lifecycle of an ambassador from sign‑up to active promotion.
An Ambassador Framework outlines the criteria for choosing community champions, the onboarding process, ongoing support mechanisms, and reward structures. It provides a repeatable method to keep ambassadors aligned with project values.
The Ambassador Loop is a closed feedback loop that gathers data from ambassador activities, distributes insights back to them, and refines outreach tactics based on real‑world results.
An Ambassador Map visualizes who the community’s ambassadors are, where they operate, and how they interact with each other and the core team. It helps coordinate outreach and support activities across regions.
An Ambassador Program is a coordinated set of activities that selects community members, equips them with resources, and recognises their contributions, all aimed at amplifying the builder’s mission.
API Architecture describes the macro‑level layout of an ecosystem’s APIs, including service boundaries, communication patterns, and shared standards. It guides scalability, security, and governance decisions across teams.
api architectureproduct & technologyapiarchitecturedescribes
An API Architecture Note records the high‑level structure of an application programming interface, including endpoint groups, authentication schemes, and versioning strategy. It serves as a quick reference for developers and integrators.
api architecture noteproduct & technologyapiarchitecturenote