Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(marketing): add growth plan and campaign measurement framework

nirholas9697faa299ef
diff --git a/HSN-rLOWcAAbJxu-1.jpg b/HSN-rLOWcAAbJxu-1.jpg
new file mode 100644
index 000000000..69f362ff1
Binary files /dev/null and b/HSN-rLOWcAAbJxu-1.jpg differ
diff --git a/marketing/README.md b/marketing/README.md
index 78f30f66c..2b9faf4e9 100644
--- a/marketing/README.md
+++ b/marketing/README.md
@@ -4,6 +4,7 @@ Campaign assets for three.ws announcements and distribution: video scripts and r
| Campaign | Description |
| --- | --- |
+| [growth](growth/README.md) | The 90-day marketing command center: channel and content audit, partner and listing pipeline, $THREE utility series, community-event system, campaign calendar, outreach templates, and measurement rules. |
| [huggingface-article](huggingface-article/post.md) | The X thread announcing the second Hugging Face community article and thanking every program and partner named in it, with the tagging rules each one requires. |
| [ibm-partner-plus](ibm-partner-plus/README.md) | The IBM Partner Plus kit: the Agent Connect BYOL submission pack for listing the 3D Studio MCP server in the watsonx Orchestrate Agent Catalog, the catalog icon, the claims we may and may not make, and held announcement copy. |
| [imessage-video](imessage-video/README.md) | A 9:16 vertical video of a fake iMessage thread that lands the AR Forge and OpenAI collaboration beats, built for X, TikTok, and Reels. |
diff --git a/marketing/growth/README.md b/marketing/growth/README.md
new file mode 100644
index 000000000..ed55b38bd
--- /dev/null
+++ b/marketing/growth/README.md
@@ -0,0 +1,236 @@
+# three.ws marketing command center
+
+This is the operating plan for the 90-day growth push beginning **2026-09-15**. It turns
+the existing partner relationships, $THREE utility, community, product surface, and
+finished campaign assets into a measured publishing and co-marketing system.
+
+The strategy in one sentence:
+
+> Put a working three.ws proof on a partner-owned surface, connect it to one real $THREE
+> utility or community action, give the partner a small and explicit amplification ask,
+> and turn the response into the next event, listing, or customer story.
+
+This directory is the operational layer above the repo's deeper source material:
+
+- [Channel and content audit](./channel-audit.md): where three.ws already publishes, what
+ performed, and what can be pushed again.
+- [Opportunity register](./opportunities.md): partner-by-partner asks, new relationship
+ targets, official intake paths, and the big-brand engagement ladder.
+- [90-day campaigns](./campaigns.csv): one row per campaign, with channel, CTA, partner ask,
+ KPI, date, and status.
+- [Opportunity tracker](./opportunities.csv): the machine-readable pipeline. This is where
+ a status or next action changes first.
+- [Measurement](./measurement.md): the UTM convention, campaign scorecard, and weekly review.
+- [Co-marketing templates](./templates.md): a one-page partner brief, social amplification
+ request, event invitation, and post-campaign proof note.
+
+The existing [partnership pipeline](../../docs/partners/opportunities.md) remains the source
+of truth for the state of a listing or partner program. The existing
+[publishing program](../../docs/publishing-program-2026-09.md) remains the source of truth
+for long-form drafts. This command center sequences and measures both.
+
+## What the evidence says
+
+The best available quantitative baseline is the repository's
+[@trythreews X analysis](../../docs/x-archive/trythreews-engagement.md), covering 158 usable
+original posts from a 214-post archive through 2026-08-12:
+
+| Signal | Median engagement | Lift over the 12-engagement corpus median |
+| ------------------------ | ----------------: | ----------------------------------------: |
+| Token / $THREE | 160 | **13.33x** |
+| Partner / ecosystem | 76 | **6.33x** |
+| Mentions another account | 54 | **4.50x** |
+| Multi-paragraph | 33 | **2.75x** |
+| Shipped / changelog | 30 | **2.50x** |
+| Has an image | 28 | **2.33x** |
+| Text only | 11 | 0.88x |
+
+The samples for token and partner subjects are small, so they are a direction, not a
+forecast. The direction is nevertheless decisive: community response is strongest when
+$THREE utility and a recognizable partner are attached to visible proof. The best post in
+the corpus was the IBM in-world meetup announcement: 359 engagements and 41 replies.
+
+The content supply is not the constraint. The
+[announcement coverage ledger](../../docs/announcement-coverage.md) records at least **166
+unannounced product surfaces** across its main product, build, labs, and agent-economy
+sections. The repo also holds eleven unposted long-form drafts and multiple finished partner
+campaign kits. The constraint is selection, dispatch, and follow-through.
+
+## Ninety-day outcomes
+
+By **2026-12-14**, the program aims to produce:
+
+1. **Four partner amplifications**: a comment, repost, newsletter mention, or partner-authored
+ post from four distinct partner or ecosystem accounts.
+2. **Three new partner-owned listings**: priority order is IBM Agent Connect, the OpenAI
+ directory/showcase surfaces, and Google Cloud's AI-agent discovery path. A marketplace
+ listing counts; a three.ws-owned partner page does not.
+3. **Three live community events**: one per month, beginning with the existing IBM Community
+ user group. Each event gets an announcement, live moment, replay clip, and 24-hour recap.
+4. **Twelve anchor campaigns**: one meaningful story each week, not a daily stream of
+ disconnected feature announcements.
+5. **Twelve $THREE utility proofs**: each demonstrates one shipped action and sends people to
+ a place where they can use or verify it. No price prediction or guaranteed-return framing.
+6. **A complete measurement loop**: every anchor link uses a campaign ID, every partner ask
+ is logged, and every campaign receives a seven-day result row.
+
+These are output and relationship targets for the first cycle. Conversion baselines are set
+during the first four weeks; percentage-growth targets should only be added after that data
+exists.
+
+## The four audiences
+
+| Audience | What they care about | Message | Primary action |
+| ----------------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------ | -------------------------------------------------------- |
+| Community and $THREE holders | Proof the platform keeps building and the token does useful work | “Here is the utility that shipped, and here is how to use or verify it.” | Try, hold-check, pay, unlock, attend, or share |
+| Open-source and AI builders | Useful code, a live demo, and a tractable way to contribute | “Give an agent a body on any page, then inspect the implementation.” | Run demo, install, star, open an issue or PR |
+| Partner product and community teams | A credible story that makes their technology look useful | “Here is a measured, visual implementation your audience can reproduce.” | Comment, repost, list, provide a speaker, or co-publish |
+| Enterprise buyers and integrators | Governance, procurement, deployment, and a business outcome | “Deploy an embodied agent through infrastructure you already trust.” | Request demo, install from catalog, or begin procurement |
+
+One post should not try to speak to all four. Every campaign row in
+[`campaigns.csv`](./campaigns.csv) names its audience and one primary action.
+
+## The campaign format
+
+Every anchor campaign has five parts:
+
+1. **Visible proof.** A 10 to 30 second clip, interactive page, partner-domain article, public
+ receipt, benchmark, or source diff. Never lead with a logo wall.
+2. **One claim.** One product outcome that the linked proof verifies.
+3. **One partner.** Tag the team whose technology is genuinely used and tell their part of
+ the story in their vocabulary.
+4. **One $THREE action.** When relevant, show a shipped utility: access, discount, payment,
+ marketplace use, event access, or transparent treasury data. Do not force the token into
+ a technical venue whose rules exclude it.
+5. **One ask.** For the audience, one CTA. For the partner, one request: comment, repost,
+ listing, speaker, newsletter, or case-study introduction.
+
+The content atomization pattern is:
+
+```text
+working proof
+ -> partner-domain technical post
+ -> 15-second social clip
+ -> X anchor post + community discussion
+ -> live event or office hours
+ -> recap with metrics
+ -> directory, showcase, or customer-story pitch
+```
+
+Reusing an idea is encouraged. Reposting the same body is not. Every version needs a new
+opening, current proof, and a venue-native CTA.
+
+## The three pillars
+
+### 1. Partner proof before partner promotion
+
+Big brands are most likely to engage with content they can safely stand behind. Publish the
+implementation on their developer or community surface first, then ask the social team to
+amplify that link. The partner-domain page is both proof and permission.
+
+The first sequence is IBM Community, GitHub Open Source Friday, NVIDIA Developer Forums,
+OpenAI Showcase, and AWS Builder Center. All have an existing relationship or accepted
+route, and all have prepared material in the repo.
+
+### 2. $THREE utility as a weekly product series
+
+Run **“What $THREE does this week”** once a week. Each edition contains:
+
+- a single live utility;
+- a screen recording or verifiable public response;
+- the exact action the user can take;
+- the canonical contract address;
+- a plain statement of what is live versus planned;
+- no price target, urgency, or return language.
+
+The first eight editions are hold-to-access tiers, plan discounts, marketplace settlement,
+agent labor, token-gated embeds, on-chain agent deployment discounts, in-world purchases,
+and x402 acceptance. The underlying claims are already audited in
+[the $THREE thesis](../../docs/three-thesis.md).
+
+### 3. The community becomes the stage
+
+Run a monthly **Three World Session** inside `three.ws/play`. The event itself demonstrates
+the product: attendees arrive as avatars, use spatial voice, and leave with a shareable
+artifact or attendance souvenir.
+
+The repeatable event package:
+
+| Timing | Action |
+| -------- | ---------------------------------------------------------------------------------- |
+| T-21 | Confirm topic, date, guest, approval wording, and partner amplification commitment |
+| T-14 | Publish partner/community event page and open registration |
+| T-7 | Release the 20-second demo clip and community challenge |
+| T-1 | Post one reminder with exact UTC and local times |
+| Live | Demo first, guest discussion second, community showcase third, Q&A last |
+| T+1 day | Publish the replay clip, metrics, links, and next date |
+| T+7 days | Send the partner a concise proof note and ask for the next-level placement |
+
+Only IBM is a confirmed partner venue for the first event. Other companies may be invited
+as speakers, but their names and logos do not appear as co-hosts until they approve that
+wording.
+
+## First 14 days
+
+The execution order is deliberately narrow:
+
+1. Book the approved [GitHub Open Source Friday issue #254](https://github.com/githubevents/open-source-friday/issues/254),
+ then activate the existing announcement and stream plan.
+2. Send one IBM relationship note covering the second event, the promised IBM-domain page,
+ the promised social co-promotion, and Partner Plus marketing access. Send the Agent Connect
+ `APP_ID` request separately to its program inbox.
+3. Submit the prepared OpenAI Showcase packet and request that three.ws be made visible in the
+ OpenAI Partner Locator if it is absent from the authenticated partner record.
+4. Publish one finished NVIDIA technical post, then use the live NVIDIA-domain URL as the
+ amplification asset. Continue the existing Inception email thread; do not start another.
+5. Create the AWS Marketplace product. Once it is live, submit the launch assets for AWS
+ review before posting; AWS explicitly says it may repost approved seller announcements.
+6. Establish the measurement baseline using the campaign IDs and scorecard in
+ [measurement.md](./measurement.md).
+
+## Weekly operating rhythm
+
+| Day | Work |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| Monday | Reconcile opportunity statuses; choose one anchor story; send the partner brief |
+| Tuesday | Capture proof and publish the partner/domain version |
+| Wednesday | Publish the X anchor and Telegram/community version; answer every substantive reply |
+| Thursday | Run a live demo, office hour, or build-in-public follow-up |
+| Friday | Publish the $THREE utility edition; prepare next week's partner asset |
+| Following Monday | Record seven-day outcomes, partner response, and the next earned placement |
+
+No campaign is “done” when the post is published. It is done when its seven-day result and
+partner response are recorded.
+
+## Editorial and brand guardrails
+
+- Name the precise relationship. “Member of NVIDIA Inception,” “OpenAI Select Partner,” and
+ “IBM Business Partner” are not interchangeable with endorsement.
+- Use partner marks only under the applicable kit and approval rules. The existing
+ [press kit](../../docs/press-kit.md) and partner campaign folders hold the approved assets.
+- $THREE is marketed through shipped utility and verifiable economics, never a promised
+ return. Distinguish live, enabled-but-off, and planned functionality.
+- Use the canonical $THREE address everywhere:
+ `FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`.
+- Do not describe a partner invitation as a co-host, listing, or partnership before the
+ partner confirms it.
+- Do not manufacture engagement. Ask the community to try, build, contribute, or attend;
+ never ask for empty replies or coordinated spam.
+- External publishing remains owner-gated. Drafting, scheduling, and preparing submissions
+ in this repo does not authorize a post or form submission by itself.
+
+## Source-of-truth map
+
+| Question | Source |
+| ----------------------------------------- | ---------------------------------------------------------------------- |
+| What relationships may we claim? | [Partner ecosystem](../../docs/partners.md) |
+| What listing is blocked, and by whom? | [Partnership pipeline](../../docs/partners/opportunities.md) |
+| What long-form content is ready? | [Publishing program](../../docs/publishing-program-2026-09.md) |
+| What product pages were never announced? | [Announcement coverage](../../docs/announcement-coverage.md) |
+| What has performed on X? | [X engagement analysis](../../docs/x-archive/trythreews-engagement.md) |
+| What is published in the IBM group? | [IBM Community catalog](../../docs/ibm-community.md) |
+| What exists on Hugging Face? | [Hugging Face index](../../docs/huggingface.md) |
+| What can be claimed about $THREE utility? | [$THREE thesis](../../docs/three-thesis.md) |
+| What is the Open Source Friday state? | [Stream plan](../../docs/open-source-friday-plan.md) |
+
+Last verified: **2026-09-15**.
diff --git a/marketing/growth/campaigns.csv b/marketing/growth/campaigns.csv
new file mode 100644
index 000000000..39d4408ad
--- /dev/null
+++ b/marketing/growth/campaigns.csv
@@ -0,0 +1,25 @@
+"campaign_id","publish_date","type","audience","theme","anchor_proof","partner","primary_channel","secondary_channels","audience_cta","partner_ask","primary_kpi","owner","status"
+"MKT-2026-09-OSF","2026-09-17","anchor","open-source builders","Open Source Friday is approved and the community can shape the live contribution","https://github.com/githubevents/open-source-friday/issues/254","GitHub","X","GitHub Discussions|Telegram community","Claim or propose a good-first issue before the stream","Confirm the date and include the visual demo in official promotion","claimed issues and confirmed stream date","Owner","ready_after_booking"
+"MKT-2026-09-THREE-ACCESS","2026-09-18","utility","community and holders","What $THREE does this week: hold-to-access tiers","https://three.ws/three-token","$THREE","X","Telegram community|three.ws news","Check a wallet tier and use one live benefit","None","tier checks and benefit uses","Growth","planned"
+"MKT-2026-09-IBM-EVENT","2026-09-22","anchor","enterprise builders and community","A user-group event where the 3D world is the venue and the demo","https://three.ws/play","IBM","IBM Community","X|Telegram community|three.ws news","Register and bring an avatar or build to show","Provide one product speaker and amplify the IBM event page","registrations and live attendees","Owner","awaiting_date"
+"MKT-2026-09-THREE-DISCOUNT","2026-09-25","utility","community and creators","What $THREE does this week: lower-cost platform access","https://three.ws/pricing","$THREE","X","Telegram community|three.ws news","Compare the live quote and choose the lower-cost rail","None","THREE quote views and completed checkouts","Growth","planned"
+"MKT-2026-09-OPENAI-STUDIO","2026-09-29","anchor","AI builders","Create a real 3D object inside an AI conversation","https://three.ws/openai","OpenAI","OpenAI Developer Community","X|LinkedIn|Telegram community|three.ws news","Try the keyless 3D Studio and share the result","Showcase or directory placement and partner-GTM introduction","tool calls and completed generations","Owner","awaiting_submission"
+"MKT-2026-10-THREE-MARKET","2026-10-02","utility","creators and agents","What $THREE does this week: marketplace settlement","https://three.ws/marketplace","$THREE","X","Telegram community|three.ws news","List or buy one useful asset or skill","None","marketplace listings and settlements","Growth","planned"
+"MKT-2026-10-NVIDIA-DH","2026-10-06","anchor","GPU AI and 3D developers","Audio drives a visitor-generated 3D face in the browser","https://three.ws/demos/audio2face","NVIDIA","NVIDIA Developer Forums","X|LinkedIn|Telegram community|three.ws news","Run the demo and inspect the implementation","Inception reshare and Startup Showcase consideration","demo starts and partner amplification","Owner","draft_ready"
+"MKT-2026-10-THREE-LABOR","2026-10-09","utility","agent builders and community","What $THREE does this week: agent labor and escrow","https://three.ws/labor-market","$THREE","X","Telegram community|GitHub Discussions|three.ws news","Post or inspect a real task flow","None","tasks posted claimed or completed","Growth","planned"
+"MKT-2026-10-CDP-X402","2026-10-13","anchor","agent and payments builders","An AI agent discovers and purchases 3D work over HTTP 402","https://three.ws/bazaar","Coinbase Developer Platform","X","Coinbase builder channels|GitHub Discussions|Telegram community|three.ws news","Run one paid call and inspect its receipt","Founders Fuel Launch Spotlight and Builder Showcase review","settled CDP calls and partner response","Owner","awaiting_application"
+"MKT-2026-10-THREE-GATE","2026-10-16","utility","creators and community","What $THREE does this week: token-gated 3D content","https://three.ws/studio","$THREE","X","Telegram community|three.ws news","Create or unlock one gated embed","None","gates created and verified unlocks","Growth","planned"
+"MKT-2026-10-AWS-MARKET","2026-10-20","anchor","enterprise buyers and cloud builders","Enterprise procurement in front of agent-native pay-per-call usage","https://three.ws/aws","AWS","AWS Marketplace launch","AWS Builder Center|LinkedIn|X|three.ws news","Open the listing or request a demo","Review the launch assets and repost the live announcement","listing visits agreements and AWS amplification","Owner","awaiting_listing"
+"MKT-2026-10-THREE-DEPLOY","2026-10-23","utility","agent developers and holders","What $THREE does this week: holder deployment benefits","https://three.ws/deploy","$THREE","X","Telegram community|GitHub Discussions|three.ws news","Price a deploy from a real wallet","None","deploy quotes and completed deployments","Growth","planned"
+"MKT-2026-10-ELEVEN-BODY","2026-10-27","anchor","voice AI builders","A voice agent becomes a speaking expressive 3D body","https://three.ws/voice","ElevenLabs","X","LinkedIn|Telegram community|three.ws news","Create a voice-enabled agent and share the clip","Startup Grant review and Demo Day consideration","voice setup completions and partner response","Owner","awaiting_eligibility"
+"MKT-2026-10-THREE-WORLD","2026-10-30","utility","community and holders","What $THREE does this week: live world access and purchases","https://three.ws/play","$THREE","X","Telegram community|three.ws news","Enter the world and join the scheduled community session","None","world entrants and event registrations","Growth","planned"
+"MKT-2026-11-HF-LOOP","2026-11-03","anchor","ML and open-source developers","An agent inspects and corrects its own 3D output","https://huggingface.co/three-ws","Hugging Face","Hugging Face Community","X|GitHub Discussions|three.ws news","Open the Space and reproduce one correction loop","Community feature or Space GPU grant review","Space sessions article reads and partner response","Growth+Engineering","draft_ready"
+"MKT-2026-11-THREE-X402","2026-11-06","utility","agent and API builders","What $THREE does this week: pay for agent tools over x402","https://three.ws/x402","$THREE","X","Telegram community|GitHub Discussions|three.ws news","Call one compatible paid endpoint","None","THREE-denominated challenges and settlements","Growth","planned"
+"MKT-2026-11-GCP-AGENT","2026-11-10","anchor","enterprise agent builders","A production A2A agent with a browser-native 3D interface","https://three.ws/.well-known/agent-card.json","Google Cloud","Google Cloud Marketplace or agent finder","LinkedIn|X|three.ws news","Inspect the Agent Card and run the live agent","AI Agents validation and finder placement","agent calls listing visits and placement","Owner","awaiting_enrollment"
+"MKT-2026-11-THREE-RECEIPTS","2026-11-13","utility","community and technical evaluators","What $THREE does this week: public utility receipts","https://three.ws/three-token","$THREE","X","Telegram community|three.ws news","Verify a live public metric or receipt","None","stats endpoint reads and linked utility actions","Growth","planned"
+"MKT-2026-11-QUICKNODE","2026-11-17","anchor","Solana developers","How the production RPC path fails over without losing the user","https://three.ws/docs/solana","QuickNode","QuickNode community or blog","X|GitHub Discussions|three.ws news","Read the field note and test the open implementation","Founder spotlight or co-authored technical post","doc reads repo visits and partner placement","Owner","awaiting_outreach"
+"MKT-2026-11-THREE-CREATOR","2026-11-20","utility","3D creators and community","What $THREE does this week: creator earnings and royalties","https://three.ws/marketplace","$THREE","X","Telegram community|three.ws news","Publish one reusable 3D asset or skill","None","new creator listings and paid reuse","Growth","planned"
+"MKT-2026-11-IBM-WORLD-2","2026-11-24","anchor","enterprise AI builders and community","An agent buys a tool and returns with a verifiable result","https://three.ws/play","IBM","IBM Community event","X|LinkedIn|Telegram community|three.ws news","Attend and inspect the live transaction flow","IBM event amplification and partner-authored recap","registrations attendance and recap placement","Owner","awaiting_first_event"
+"MKT-2026-11-THREE-BUILD","2026-11-27","utility","community and open-source builders","What $THREE does this week: utility built in public","https://github.com/nirholas/three.ws","$THREE","GitHub Discussions","X|Telegram community|three.ws news","Audit the implementation or open an issue","None","repo visits discussions and issues","Growth","planned"
+"MKT-2026-12-OPEN-SOURCE","2026-12-01","anchor","open-source builders and partner teams","The quarter's community contributions and partner-owned proof","https://github.com/nirholas/three.ws","GitHub","GitHub Discussions","X|LinkedIn|Telegram community|partner communities|three.ws news","Choose the next contribution or event","Include the best community artifact in a GitHub roundup","contributors PRs and partner amplification","Growth","planned"
+"MKT-2026-12-THREE-QUARTER","2026-12-04","utility","community and holders","What $THREE did this quarter: verified utility outcomes","https://three.ws/three-token","$THREE","X","Telegram community|three.ws news","Use the most relevant live utility and vote on the next walkthrough","None","utility actions across the series","Growth","planned"
diff --git a/marketing/growth/channel-audit.md b/marketing/growth/channel-audit.md
new file mode 100644
index 000000000..2809a3c38
--- /dev/null
+++ b/marketing/growth/channel-audit.md
@@ -0,0 +1,136 @@
+# Channel and content audit
+
+This audit separates **published**, **automatic**, **prepared**, and **unclaimed** surfaces.
+That distinction matters: a finished draft is inventory, not reach; a shipped manifest is a
+technical prerequisite, not a listing; a three.ws-owned partner page is not partner validation.
+
+## Current distribution system
+
+| Surface | Control | Current evidence | Best use | Next move |
+| ------------------------------------------------------- | ------------------------------------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------- | -------------------------------------------------------------------------------- |
+| `three.ws/news`, blog, timeline, and press pages | Owned | Live site and repo-backed content | Canonical campaign pages and durable proof | Give every anchor campaign one canonical URL |
+| Changelog, JSON/XML feeds, and Telegram release channel | Owned, automated | 3,000+ changelog entries; deploy-driven Telegram publishing | Shipping velocity and holder confidence | Summarize into one weekly digest; do not make followers parse every change |
+| `@trythreews` on X | Owned | 214 original archived posts through 2026-08-12; 158 have usable engagement counts | Anchor posts, partner tags, clips, fast community feedback | Refresh the archive, then measure each new campaign at seven days |
+| three.ws X Community | Owned | Listed in `docs/community.md` | Creations, event coordination, community prompts | Give members an artifact or challenge, not a duplicate corporate post |
+| Telegram community | Owned | Listed in `docs/community.md` | Real-time event and product discussion | Pin one weekly roundup with links and next actions |
+| GitHub repo, Discussions, Issues, Releases | Owned on GitHub | Public Apache-2.0 repo, curated issues, seeded Discussions | Contributors, technical authority, release proof | Use Open Source Friday to convert viewers into claimed issues and PRs |
+| RSS | Owned, automatic | Curated feed at `/rss/announcements.xml` | Syndication and canonical distribution | Add every externally published partner article to the curated feed |
+| HackerNoon | Partner/media, automatic draft import | RSS import and live editorial coverage documented | Searchable founder/developer reach | Turn only proven anchor stories into HackerNoon drafts; preserve canonical links |
+| IBM Community user group | Partner-owned, team-operated | 17 members, 5 blogs, 8 catalogued threads, 2 past events at 2026-09-10 snapshot | Enterprise discussion, events, IBM employee participation | Schedule the second event and publish the finished governed-agents post |
+| NVIDIA Developer Forums | Partner-owned, self-serve | Two published technical posts | GPU/AI developer proof that NVIDIA teams can safely amplify | Publish the finished browser-digital-human post, then the fleet post |
+| AWS Builder Center | Partner-owned, self-serve | Two team articles plus one AWS-authored piece documented in the repo | Practical cloud engineering | Publish article three; reserve launch copy for the Marketplace announcement |
+| OpenAI Developer Community | Partner-owned, self-serve | Two complete drafts in the repo | Apps SDK, MCP, and spatial-tool implementation | Publish on a measured cadence around Showcase/directory submission |
+| Hugging Face organization | Ecosystem-owned | Two articles, an avatar model repo, and an interactive Space | Inspectable AI/3D proof | Publish the feedback-loop article and apply for a Space GPU grant if needed |
+| Alibaba Cloud Marketplace/blog | Partner-owned | Marketplace listing, storefront, and editorial feature documented | APAC distribution and Qwen story | Pitch a technical follow-up with usage proof rather than another launch post |
+| pump.fun project page | Ecosystem-owned | Verified $THREE page and feature article | Canonical token identity and utility education | Refresh only for a material new utility milestone |
+| Directories and catalogs | Third-party | Mixed: some live, some prepared, some only have manifests | Search/discovery and procurement | Work from `opportunities.csv`; record a live URL, not “submitted” |
+
+## What actually worked
+
+The X archive is the only cross-post quantitative dataset currently in the repo. Its
+strongest repeatable patterns are:
+
+1. **Partner plus community plus visible event.** The IBM in-world meetup announcement was
+ the best measured post: 359 engagements and 41 replies.
+2. **Third-party verification.** A verification announcement with a partner tag reached 266
+ engagements.
+3. **Official ecosystem placement.** The official MCP Registry announcement reached 241.
+4. **A concrete payment demo with links.** The x402 proof post reached 197.
+5. **Explicit anticipation of co-marketing.** “More co-marketing with IBM coming” reached 168
+ despite containing no media, showing how strongly the community values the relationship.
+6. **A tangible developer inventory.** The npm package roundup reached 111.
+
+The lesson is not “post about partners constantly.” It is that outside validation makes a
+technical claim legible. A partner logo without proof will decay quickly; a partner-domain
+link, a working demo, and a community event compound.
+
+## What underperformed
+
+- Text-only posts had a median of 11 engagements, below the corpus median.
+- Replies had a median of 5; use replies to deepen a live conversation, not as the main
+ distribution format.
+- Generic questions did not create engagement in the sample. Ask for an action tied to a
+ real artifact instead.
+- Video as a category did not outperform in the historical sample, but the sample was only
+ six posts. The correct response is better first frames and shorter standalone proof, not
+ abandoning video.
+- The account published heavily: 64 original posts in June and 56 in July. But the top 10% of
+ posts produced 49.4% of engagement. Fewer anchor stories with coordinated distribution are
+ a better use of the inventory.
+
+## Reusable campaign inventory
+
+Priority is based on proven audience fit, partner amplification potential, readiness, and
+whether the story can carry a real $THREE or community action.
+
+| Priority | Story to push again | Existing proof/assets | New angle | Partner ask |
+| -------: | -------------------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------- |
+| 1 | GitHub Open Source Friday approval | Approved issue, full stream plan, announcement pack, curated first issues | “Claim the convention we will implement and review live” | Book date; request official social card and live/replay posts |
+| 2 | Second IBM in-world community event | First event recap, world, spatial voice, event readiness suite, IBM group | “A user group meeting where the venue is the demo” | IBM speaker, event-calendar listing, announcement comment/repost |
+| 3 | OpenAI 3D Studio | Select Partner kit, press release, two community drafts, live keyless connector | “Create and manipulate a real 3D object inside the conversation” | Showcase/directory placement and partner-portal GTM contact |
+| 4 | NVIDIA browser-native digital human | Finished forum draft, Audio2Face demo, Inception assets | “Facial animation streamed to a visitor-generated rig in a browser” | Forum visibility, Inception reshare, Startup Showcase consideration |
+| 5 | $THREE utility series | `$THREE` thesis, token page, live utility endpoints | One shipped utility and one action each week | Applicable integration partner comments on the technical primitive |
+| 6 | AWS procurement launch | Marketplace backend, listing kit, three Builder Center articles | “Enterprise procurement in front of agent-native pay-per-call usage” | Pre-publication brand review and post-launch AWS repost |
+| 7 | x402 economy proof | Milestone videos, public stats, endpoint catalog, receipts | “What autonomous agents actually paid for this week” | Coinbase Developer Platform showcase / Founders Fuel amplification |
+| 8 | Hugging Face open 3D stack | Two published articles, model repo, live Space, finished feedback-loop draft | “Inspect the model, rig, demo, and code in one tab” | Community feature or Space GPU-grant review |
+| 9 | NVIDIA Inception membership | Complete announcement copy and graphics; never posted | Membership as the start of a GPU engineering series | Inception social reshare after asset approval |
+| 10 | Android / Solana Mobile product | Signed app, launch kit, device captures | “Make an avatar from a phone and take it into a live world” | Store feature or ecosystem roundup |
+| 11 | First 19 weeks / open-source ecosystem | 40+ visual assets, product map, GitHub proof | Quarterly “what shipped” with a contributor call, not a feature dump | GitHub/open-source community amplification |
+| 12 | Agent embed and 3D utility | Product demo, `<agent-3d>` examples, Rig Doctor | A partner-specific embedded avatar built live | Partner showcases the result on its own site or docs |
+
+## The unannounced backlog
+
+The [announcement coverage ledger](../../docs/announcement-coverage.md) already did the hard
+inventory work. Its snapshot includes:
+
+| Section | Pages | Never announced |
+| --------------------- | ------: | --------------: |
+| Main product surfaces | 51 | 33 |
+| Creation/build tools | 59 | 34 |
+| Labs | 20 | 16 |
+| Agent economy | 134 | 83 |
+| **Total** | **264** | **166** |
+
+Do not publish 166 feature posts. Bundle them into twelve audience-shaped stories:
+
+- one avatar from prompt to website;
+- the browser-native digital-human pipeline;
+- inspect, validate, repair, and animate any rig;
+- build a 3D scene with an agent;
+- a live world as a community venue;
+- accessibility through signed 3D communication;
+- agents that discover and pay for tools;
+- verifiable agent identity and reputation;
+- the $THREE utility stack;
+- mobile creation and AR;
+- the open-source contributor path;
+- the production infrastructure behind free creation.
+
+Each bundle can support a partner-domain article, a demo clip, an event segment, a community
+challenge, and an evergreen page without repeating the same body.
+
+## Republish rules
+
+Before reusing any existing piece:
+
+1. Re-run the live proof and update every number and status.
+2. Pick a new audience and rewrite the opening for that audience.
+3. Preserve one canonical URL and use canonical tags where the venue supports them.
+4. Replace “we launched” with the result, lesson, or next capability.
+5. Use a new visual cut or current screenshot.
+6. Give the partner 48 hours to review any co-branded claim or asset.
+7. Record the final live URL and seven-day result in the trackers.
+
+## Gaps to close
+
+- The X dataset ends on 2026-08-12. Refresh it before using absolute engagement targets.
+- Several timeline milestones lack `source_url` values, including high-value partner social
+ interactions. Recover and archive those links.
+- Partner announcements are tracked across several docs, but partner **responses** are not.
+ `opportunities.csv` now carries the success evidence for that purpose.
+- Telegram has reach but no structured campaign-level measurement. Use tracked links and one
+ weekly roundup.
+- The IBM catalog snapshot contains a partial fifth blog entry. Complete the URL, author,
+ date, and activity record before citing it in outreach.
+
+Last audited: **2026-09-15**.
diff --git a/marketing/growth/measurement.md b/marketing/growth/measurement.md
new file mode 100644
index 000000000..831511f5f
--- /dev/null
+++ b/marketing/growth/measurement.md
@@ -0,0 +1,137 @@
+# Marketing measurement system
+
+The measurement goal is to connect **partner validation and community attention** to a real
+three.ws action. Views and likes are useful diagnostics; they are not the outcome by
+themselves.
+
+## Campaign IDs and links
+
+Every anchor and utility campaign has an immutable ID in
+[`campaigns.csv`](./campaigns.csv):
+
+```text
+MKT-YYYY-MM-SHORT-NAME
+```
+
+Every link under our control uses:
+
+```text
+utm_source=<venue-or-account>
+utm_medium=<social|community|partner|event|email|directory>
+utm_campaign=<campaign_id in lowercase>
+utm_content=<asset-or-post-variant>
+```
+
+Example for the Open Source Friday X anchor:
+
+```text
+https://three.ws/rig-doctor?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-osf&utm_content=anchor-video
+```
+
+Example for an IBM Community event page:
+
+```text
+https://three.ws/play?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-09-ibm-event&utm_content=event-page
+```
+
+Use lowercase ASCII and hyphens. Do not rename a campaign after links are live. A repost by a
+partner gets its own `utm_source` and `utm_content=partner-repost` while preserving the
+campaign ID.
+
+## Funnel
+
+Measure each campaign through five layers:
+
+| Layer | Definition | Examples |
+| ------------------------- | --------------------------------------- | --------------------------------------------------------------------------- |
+| Distribution | The content was actually delivered | impressions, partner newsletter sends, event-page views |
+| Engagement | A person chose to interact | substantive replies, reposts, saves, article reads, registrations |
+| Product action | The visitor used the proof | generation completed, demo started, Agent Card fetched, listing opened |
+| Community/economic action | The visitor joined the ecosystem | event attendance, issue claimed, PR opened, utility used, paid call settled |
+| Earned escalation | A third party deepened the relationship | partner comment, repost, listing, speaker, newsletter, case-study intro |
+
+The north-star count is **qualified actions**: product actions, community/economic actions,
+and earned escalations attributed to a campaign. Report distribution and engagement beside
+it so a weak conversion can be diagnosed.
+
+## Required campaign result
+
+Record this at 24 hours and again at seven days:
+
+| Field | Meaning |
+| ------------------------ | ------------------------------------------------------------------------ |
+| Campaign ID | Immutable ID from `campaigns.csv` |
+| Live URLs | Canonical page and every published post |
+| Spend | Cash cost; organic time is recorded separately in hours |
+| Impressions / views | Per channel, not summed when audiences overlap |
+| Engagements | Likes, reposts, comments, saves, and partner interactions split out |
+| Landing sessions | Sessions carrying the campaign UTM |
+| Primary product action | Campaign-specific action and count |
+| Utility/community action | Campaign-specific deeper action and count |
+| Partner response | None, acknowledged, commented, reposted, listed, speaker, editorial lead |
+| Reusable learning | One sentence about what to repeat or stop |
+| Next escalation | The one ask earned by this result |
+
+## Weekly scorecard
+
+The Monday review answers seven questions:
+
+1. Did last week's anchor ship on its primary channel?
+2. Did the partner receive the brief before publication?
+3. Did it produce a qualified action?
+4. Did the partner respond, and at which engagement-ladder level?
+5. Which content format and opening beat the four-week median?
+6. Which channel produced the highest action rate, not the most impressions?
+7. What single earned placement does the proof justify asking for next?
+
+Track these rollups:
+
+| Metric | 90-day goal | Notes |
+| --------------------------------- | ------------------------: | ----------------------------------------------------- |
+| Anchor campaigns shipped | 12 | One per week |
+| $THREE utility proofs shipped | 12 | One per week |
+| Partner amplifications | 4 distinct brands | Comment, repost, newsletter, or partner-authored post |
+| New partner-owned live listings | 3 | Live URL required |
+| Community events held | 3 | Live event plus recap |
+| Partner briefs sent before launch | 100% of partner campaigns | Minimum 48 hours before publication |
+| Campaigns with seven-day result | 100% | No result means campaign remains open |
+
+## Decision rules after four weeks
+
+- Repeat a format when its qualified-action rate beats the rolling four-week median and the
+ campaign produced at least one substantive community or partner response.
+- Rewrite the landing path when engagement is healthy but product-action conversion is below
+ the median.
+- Stop a channel-specific format after three comparable attempts below the median. Keep the
+ story and move it to a better-fit venue.
+- Escalate a partner ask only after giving the partner a result it can reuse: a working demo,
+ useful article, attendance, customer outcome, or measured community response.
+- Do not compare the small historical token and partner samples as if they were stable
+ forecasts. Recalculate lift after each four-week block.
+
+## Data sources
+
+| Source | What it supplies | Cadence |
+| ----------------------------------------- | ------------------------------------------------------------- | -------------------------------------------- |
+| `data/x-archive/` | X post content and engagement | Refresh weekly and after large partner posts |
+| `docs/x-archive/trythreews-engagement.md` | Format and topic baselines | Regenerate after archive refresh |
+| Web analytics | UTM sessions and conversion events | 24 hours and 7 days |
+| `data/changelog.json` | Shipping volume and story discovery | Weekly editorial review |
+| IBM Community catalog | Members, articles, discussions, events | Monthly and after each event |
+| Partner dashboards/portals | Listing traffic, leads, installs, marketplace activity | Weekly while launching, monthly after |
+| Public product/stat endpoints | Utility usage and transaction proof | Capture at publication and seven days |
+| GitHub | Stars, clones, issues, PRs, contributors, discussion activity | Seven days after builder campaigns |
+
+## Integrity rules
+
+- Preserve raw counts and their capture times. Never overwrite a result with a newer count
+ without retaining the date.
+- Separate organic, partner-amplified, and paid delivery.
+- Do not sum impressions from channels with overlapping audiences into “people reached.”
+- Mark bot traffic, unreliable counters, and missing data as excluded rather than zero.
+- Attribute $THREE utility only to a verifiable action; do not infer a token purchase from a
+ page view.
+- Never report a submission as a listing or a partner acknowledgement as endorsement.
+
+The initial baseline window is **2026-09-15 through 2026-10-12**. Add rate targets only after
+that window closes.
diff --git a/marketing/growth/opportunities.csv b/marketing/growth/opportunities.csv
new file mode 100644
index 000000000..7141e740b
--- /dev/null
+++ b/marketing/growth/opportunities.csv
@@ -0,0 +1,21 @@
+"priority","score","opportunity","relationship","status","next_action","owner","target_date","three_ws_asset","partner_value","success_evidence","official_source","last_verified"
+"P0","20","GitHub Open Source Friday","existing-approved","approved_unbooked","Book a Friday and post the confirmed date on issue 254","Owner","2026-09-17","docs/open-source-friday-plan.md","A visual open-source episode with a real contribution merged live","Confirmed stream date and issue comment","https://github.com/githubevents/open-source-friday/issues/254","2026-09-15"
+"P0","20","IBM Agent Connect catalog","existing-partner","prepared","Email the program inbox for the BYOL APP_ID and enter Concierge","Owner","2026-09-18","marketing/ibm-partner-plus/agent-connect-listing.md","A production external 3D agent for the governed catalog","Live IBM catalog URL","https://www.ibm.com/products/watsonx-orchestrate/agent-catalog","2026-09-15"
+"P0","20","IBM Community event two","existing-partner","proposal_ready","Confirm date and request an IBM product speaker plus calendar promotion","Owner","2026-09-18","docs/ibm-next-event.md","A moderated hands-on user-group event where the venue is the demo","Live IBM event page and named speaker","https://www.ibm.com/community/user-groups-program/","2026-09-15"
+"P0","19","OpenAI Developer Showcase","existing-partner","ready_to_submit","Submit the prepared public 3D Studio project","Owner","2026-09-19","prompts/store-submissions/_generated/openai-submission.md","An open-source interactive Three.js project for developer inspiration","Submission receipt then live showcase URL","https://developers.openai.com/showcase/apps","2026-09-15"
+"P0","19","OpenAI Plugin Directory","existing-partner","ready_to_submit","Run the current production verification and complete partner-portal submission","Owner","2026-09-19","prompts/store-submissions/_generated/openai-submission.md","A tightly scoped production 3D creation plugin","Submission ID then live directory URL","https://developers.openai.com/plugins","2026-09-15"
+"P0","18","NVIDIA technical amplification","existing-member","draft_ready","Publish the browser digital-human forum post then send its URL in the existing Inception thread","Owner","2026-09-22","docs/nvidia-forum-browser-digital-human.md","A reproducible browser-native Audio2Face and Riva implementation","Live forum URL plus program repost or response","https://forums.developer.nvidia.com/","2026-09-15"
+"P0","18","AWS Marketplace launch amplification","existing-partner","backend_ready_listing_missing","Create the Marketplace product then submit launch assets for AWS review","Owner","2026-09-23","docs/aws-marketplace-listing-kit.md","A production SaaS listing and practical procurement story","Live listing URL and AWS repost","https://docs.aws.amazon.com/marketplace/latest/userguide/product-marketing.html","2026-09-15"
+"P1","19","Google Cloud AI Agents program and finder","existing-program_new_partner_path","not_started","Enroll through Partner Network and submit the public Agent Card and Marketplace business case","Owner","2026-09-25","public/.well-known/agent-card.json","A production Cloud Run and A2A agent with a visual 3D interface","Program ID and live finder or Marketplace URL","https://cloud.google.com/marketplace/sell","2026-09-15"
+"P1","19","Coinbase CDP Founders Fuel","new-target","not_started","Apply with the production x402 facilitator and Bazaar integration plus a 90-day launch plan","Owner","2026-09-23","docs/x402-distribution.md","A working x402 agent-commerce implementation with public receipts","Acceptance and CDP Builder Showcase or social URL","https://www.coinbase.com/developer-platform/discover/launches/founders-fuel","2026-09-15"
+"P1","18","ElevenLabs Startup Grants and Demo Day","new-target","eligibility_check","Confirm employee-count and account eligibility then apply with the embodied-voice demo","Owner","2026-09-24","api/_lib/elevenlabs.js","A monetized production voice experience where audio drives a visible 3D body","Grant acceptance and Demo Day consideration","https://elevenlabs.io/startup-grants","2026-09-15"
+"P1","17","NVIDIA Inception Startup Showcase","existing-member","requested_in_existing_thread","Attach one live technical proof and request a concrete spotlight window in the current thread","Owner","2026-09-25","marketing/nvidia-inception/README.md","A measured startup implementation built on NVIDIA technology","Published NVIDIA spotlight URL","https://www.nvidia.com/en-us/startups/","2026-09-15"
+"P1","17","Hugging Face Space feature and GPU grant","existing-channel","live_needs_upgrade","Turn the existing viewer into a focused prompt-to-rig proof and apply from Space settings if GPU is needed","Growth+Engineering","2026-10-02","docs/huggingface-agent-feedback-loop.md","An inspectable model rig demo and open implementation","Grant decision or featured Space URL","https://huggingface.co/docs/hub/spaces-overview","2026-09-15"
+"P1","16","OpenAI Partner Locator profile","existing-partner","public_presence_unverified","Check the authenticated partner record and request public discoverability if absent","Owner","2026-09-19","marketing/openai-select-partner/README.md","A complete and accurate Select Partner profile","Live partner locator URL","https://openai.com/business/partners/locator/","2026-09-15"
+"P1","16","Solana ecosystem directory","existing-ecosystem","listing_unverified","Search the live directory and submit current product screenshots if absent","Owner","2026-10-02","marketing/seeker-launch/README.md","A mature open-source Solana-native agent platform","Live ecosystem profile URL","https://solana.com/news/new-solana-ecosystem-directory","2026-09-15"
+"P1","16","IBM My Digital Marketing and co-marketing funds","existing-partner","entitlement_unused","Request access and the Build-track marketing kit in the existing relationship note","Owner","2026-09-18","marketing/ibm-partner-plus/README.md","A ready campaign and recurring user-group event series","Portal access and approved campaign or fund ID","https://www.ibm.com/partnerplus/marketing","2026-09-15"
+"P2","16","Solana Foundation public-good grant","existing-ecosystem","scope_needed","Define one narrow open-source identity payment or 3D public good with milestones and budget","Owner+Engineering","2026-10-16","docs/open-source-footprint.md","Reusable public infrastructure and documented learning for the ecosystem","Application ID then grant decision","https://solana.org/grants-funding","2026-09-15"
+"P2","15","GitHub Stars nomination","new-recognition-path","evidence_building","Complete Open Source Friday and two contributor workshops then assemble an education-first nomination","Community","2026-11-30","docs/first-contribution.md","Sustained open-source education and community growth","Nomination confirmation","https://stars.github.com/","2026-09-15"
+"P2","15","OpenAI share-your-story","existing-partner","not_started","Submit a founder story after Showcase submission with measurable product outcomes","Owner","2026-10-09","marketing/openai-select-partner/partnership-and-gpt-briefing.md","A human story about making 3D creation accessible through OpenAI products","Submission confirmation or editorial contact","https://openai.com/form/share-your-story/","2026-09-15"
+"P2","15","NVIDIA GTC 2027 startup route","existing-member","watching","Monitor registration and CFP weekly and ask Inception about pavilion and startup-pitch intake","Owner","2026-10-01","docs/nvidia-visibility-map.md","A browser digital-human demo for agentic AI and media audiences","Submission ID or pavilion acceptance","https://www.nvidia.com/gtc/","2026-09-15"
+"P2","14","QuickNode startup spotlight","existing-program","not_started","Send a one-page RPC failover field note and request a founder spotlight","Owner","2026-10-09","docs/solana.md","A practical reliability story with a production QuickNode integration","Published QuickNode-domain story or social post","https://www.quicknode.com/startup-program","2026-09-15"
diff --git a/marketing/growth/opportunities.md b/marketing/growth/opportunities.md
new file mode 100644
index 000000000..70d00a108
--- /dev/null
+++ b/marketing/growth/opportunities.md
@@ -0,0 +1,196 @@
+# Co-marketing and partnership opportunity register
+
+This is the human-readable strategy behind [`opportunities.csv`](./opportunities.csv). The
+CSV is the status ledger; this page explains why the opportunities are ranked, what three.ws
+can offer, and what to ask for.
+
+## How opportunities are scored
+
+Score each route from 1 to 5 on four dimensions:
+
+- **Brand:** how much third-party credibility or relevant reach a win creates.
+- **Fit:** how directly the shipping product uses the partner technology or serves its
+ audience.
+- **Readiness:** whether the proof, copy, integration, and relationship already exist.
+- **Access:** how direct the intake route is, where 5 is self-serve or an existing contact.
+
+`priority_score = brand + fit + readiness + access`. Work the highest score first, but a
+closing date overrides the score. An opportunity does not enter the register without an
+official source, a concrete next action, an owner, and evidence that would prove completion.
+
+## The big-brand engagement ladder
+
+Do not lead with “Can we partner?” Lead with the smallest useful action and earn the next
+one.
+
+| Level | Ask | What we give the brand | Proof of success |
+| ----: | ------------------------------------------------------ | ---------------------------------------------------------------------- | --------------------------------------------- |
+| 1 | Employee or program account comments on a working demo | A safe, accurate post and a reply-ready summary | Public comment URL |
+| 2 | Program handle reposts or includes it in a roundup | Approved assets, native copy, and a partner-domain proof link | Repost or newsletter URL |
+| 3 | Technical article or community event on its property | Reproducible implementation, moderation, recording, and recap | Partner-domain article/event URL |
+| 4 | Directory, catalog, marketplace, or showcase placement | Production integration, support process, screenshots, and metrics | Live listing URL |
+| 5 | Joint case study, event series, or formal GTM motion | Customer outcome, named spokesperson, legal-ready claims, and pipeline | Published case study or signed program motion |
+
+Each successful campaign should ask for only the next level. IBM has already demonstrated
+the sequence: official social engagement led into partner content and a dedicated community
+group, and the group led into an in-world event.
+
+## Existing relationships: activate what is already earned
+
+| Partner | Best next placement | Exact ask | What we offer | Source/status |
+| ------------- | -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| IBM | watsonx Orchestrate Agent Catalog and recurring user-group events | Issue the BYOL `APP_ID`; confirm event two; restore the promised IBM-domain page and social co-promotion; activate My Digital Marketing | Governed 3D agent demo, existing user group, event world, written listing pack | [IBM Agent Catalog](https://www.ibm.com/products/watsonx-orchestrate/agent-catalog), [Partner Plus marketing](https://www.ibm.com/partnerplus/marketing), [user-group benefits](https://www.ibm.com/community/user-groups-program/) |
+| OpenAI | Developer Showcase, Plugin Directory, and Partner Locator | Publish the prepared submission; make the Select Partner profile discoverable; route a measured story to partner GTM | Keyless 3D Studio connector, interactive Three.js output, open-source implementation | [Developer community](https://developers.openai.com/community), [Apps showcase](https://developers.openai.com/showcase/apps), [Partner Network](https://openai.com/business/partners/) |
+| NVIDIA | Developer Forums, Inception Startup Showcase, Accelerated Apps, and GTC startup routes | Continue the open Inception thread with one live technical URL and one requested placement; request approved co-marketing assets | Browser-native Audio2Face/Riva demo, GPU fleet story, measured implementation | [NVIDIA startups](https://www.nvidia.com/en-us/startups/), [GTC](https://www.nvidia.com/gtc/), [existing visibility map](../../docs/nvidia-visibility-map.md) |
+| AWS | Marketplace listing followed by reviewed launch amplification | Create the product; submit launch copy for AWS review; notify AWS when live and request the stated repost support | Production SaaS integration, procurement story, existing Builder Center audience | [AWS Marketplace marketing guide](https://docs.aws.amazon.com/marketplace/latest/userguide/product-marketing.html), [Partner Central](https://aws.amazon.com/partners/partner-central/) |
+| Google Cloud | AI Agents program, AI agent finder, and Cloud Marketplace | Enroll through Partner Network; submit the production Agent Card and Marketplace business case | Production Cloud Run/Vertex workload, public Agent Cards, A2A and MCP support | [Sell on Cloud Marketplace](https://cloud.google.com/marketplace/sell), [Marketplace requirements](https://docs.cloud.google.com/marketplace/docs/partners/get-started) |
+| Alibaba Cloud | Technical follow-up on the live Marketplace relationship | Pitch a measured Qwen/router implementation and APAC workshop rather than another partnership announcement | Live listing, Qwen lane, reproducible routing story | [Current listing record](../../docs/listings.md) |
+| HackerNoon | Recurring canonical syndication and a flagship founder story | Keep RSS healthy; pitch only the strongest quarterly proof as an editorial package | Automatic clean feed, original technical reporting, canonical URLs | [Syndication runbook](../../docs/syndication.md) |
+| QuickNode | Startup-program spotlight and technical reliability story | Ask the program contact for a founder spotlight or co-authored RPC failover post | Real Solana RPC failover implementation and operational lessons | [Partner record](../../docs/partners.md) |
+
+### The IBM event series
+
+The IBM Community user-group route is the fastest repeatable partner-owned channel because
+three.ws already moderates the group, has held a successful in-world event, and can create
+the venue at will. IBM's official user-group program says it can support events with IBM
+product experts, content, promotion, and branded giveaways.
+
+Proposed next three events:
+
+| Month | Event | Partner role | Community artifact |
+| ----------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
+| September/October | **Give an enterprise agent a 3D body, live** | IBM Community host; invite an IBM product expert for governance discussion | A rigged avatar and replay clip |
+| October/November | **An AI agent pays for its own tool** | IBM remains the confirmed venue; invite the relevant payments ecosystem team only after acceptance | Public x402 receipt and $THREE utility walkthrough |
+| November/December | **Browser-native digital humans** | IBM venue; invite NVIDIA and ElevenLabs as speakers, not co-hosts, until approved | A live speaking avatar and technical recap |
+
+Each event ends with one partner escalation: event one asks for the IBM Agent Catalog
+listing, event two asks for a partner-authored recap, event three asks for a multi-company
+technical session at a larger event.
+
+## New relationships with unusually strong fit
+
+### 1. Coinbase Developer Platform Founders Fuel
+
+**Why it fits.** The repository has a production Coinbase Developer Platform x402
+facilitator integration, Bazaar discovery, an official SDK dependency, live endpoints, and a
+large evidence base around agent payments. Founders Fuel explicitly accepts working products
+integrating x402 and offers a Launch Spotlight, social amplification, Builder Showcase
+placement, GTM support, and partner introductions.
+
+**Ask.** Apply with the x402 agent-economy proof, a live product link, and a 90-day launch
+plan centered on agents discovering and purchasing 3D work. Do not pitch $THREE price or a
+generic platform; pitch a specific CDP integration with measurable settlement volume.
+
+**Official source:** [CDP Founders Fuel](https://www.coinbase.com/developer-platform/discover/launches/founders-fuel).
+
+### 2. ElevenLabs Startup Grants and Demo Day
+
+**Why it fits.** ElevenLabs voice synthesis and cloning are integrated in the live agent
+product. The grant program is designed for monetized, long-term voice products at companies
+with fewer than 25 employees, offers 12 months of product access and founder programming,
+and feeds the ElevenLabs Demo Day. Demo Day winners receive an invitation to present at the
+ElevenLabs Summit, creating exactly the brand-owned event and social loop sought here.
+
+**Ask.** If three.ws meets the employee-count and account-status eligibility rules, apply
+with the “voice becomes a face and body” demo. Request Demo Day consideration after the
+grant is accepted. The application is rolling; do not claim participation before acceptance.
+
+**Official sources:** [Startup Grants](https://elevenlabs.io/startup-grants),
+[Demo Day](https://demoday.elevenlabs.io/).
+
+### 3. Google Cloud AI Agents program and agent finder
+
+**Why it fits.** Google now publishes a specific Marketplace path for agent builders,
+including an AI Agents program, A2A and Gemini Enterprise validations, Agent Cards, and an AI
+agent finder. three.ws already runs in Google Cloud production, ships public Agent Cards,
+and supports A2A. This is a substantially stronger fit than a generic SaaS Marketplace
+application.
+
+**Ask.** Enroll in the Google Cloud Partner Network, apply for the AI Agents program, and ask
+the assigned partner manager to route three.ws into the agent finder and Gemini Enterprise
+validation path. Use production Agent Card and A2A evidence in the first message.
+
+**Official source:** [Google Cloud Marketplace for agent builders](https://cloud.google.com/marketplace/sell).
+
+### 4. GitHub open-source programs
+
+**Why it fits.** Open Source Friday is already approved. The next relationship is not a cold
+application; it is a strong episode that generates a real merged contribution. GitHub Stars
+is an individual recognition path for people who educate and grow developer communities,
+which becomes credible after repeated public contributor onboarding.
+
+**Ask.** Book the Open Source Friday date now, co-produce the episode assets, and make the
+on-air PR the result. After the episode and two additional community workshops, assemble a
+GitHub Stars nomination around open-source education, not company promotion.
+
+**Official sources:** [approved issue #254](https://github.com/githubevents/open-source-friday/issues/254),
+[GitHub Stars](https://stars.github.com/).
+
+### 5. Hugging Face Space and community feature
+
+**Why it fits.** The organization already has published models, two community articles, and
+a working Space. Hugging Face invites innovative Spaces to apply for a community GPU grant
+from the Space settings page. A stronger Space creates a visual destination Hugging Face can
+feature and every partner can link.
+
+**Ask.** Upgrade the existing Space into a prompt-to-rig-to-view demo or a focused rig
+inspector, apply for the community GPU grant if compute is required, and publish the finished
+feedback-loop article alongside it.
+
+**Official source:** [Hugging Face Spaces overview](https://huggingface.co/docs/hub/spaces-overview).
+
+### 6. Solana ecosystem directory and Foundation public-good funding
+
+**Why it fits.** Solana is the home chain, the project is Apache-2.0, and the repo includes
+free developer tools and public infrastructure. The Foundation evaluates rolling grant
+applications on public-good value, open source, why the work is only possible on Solana, and
+clear milestones. The ecosystem directory offers another partner-owned discovery surface.
+
+**Ask.** First verify whether three.ws is already in the current ecosystem directory. If
+absent, submit the product with current screenshots. Separately scope a grant around a narrow
+public good, such as open agent identity/payment/3D tooling, not general company marketing.
+
+**Official sources:** [Foundation grants](https://solana.org/grants-funding),
+[ecosystem directory process](https://solana.com/news/new-solana-ecosystem-directory).
+
+## High-value editorial routes
+
+These are earned after a measurable launch, not submitted as generic company profiles:
+
+| Route | Trigger required before pitching | Pitch |
+| ---------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------- |
+| OpenAI customer story | Directory listing plus meaningful tool-call or user outcome | Interactive 3D creation inside ChatGPT with measured completion and reuse |
+| Google Cloud startup success story | Marketplace/AI Agents acceptance plus Cloud Run/Vertex metrics | A free browser 3D service kept reliable by an elastic GPU and model fleet |
+| AWS Partner Success | Marketplace live plus a customer or procurement outcome | Agent-native metering behind enterprise procurement |
+| NVIDIA Technical Blog / Startup Showcase | High-performing forum post plus benchmark | Browser-native digital human on NVIDIA infrastructure |
+| ElevenLabs customer story | Grant/Demo Day acceptance plus voice usage | Voice that drives a visible 3D body rather than an audio-only agent |
+| Coinbase Builder Showcase | Founders Fuel acceptance plus settlement proof | Agents buying creative work over x402 |
+
+## First ten business days
+
+| By | Action | Completion evidence |
+| ---------- | -------------------------------------------------------------------- | ------------------------------------------------------- |
+| 2026-09-17 | Book GitHub Open Source Friday and reply on issue #254 | Confirmed date and public issue comment |
+| 2026-09-18 | Send IBM relationship note; send Agent Connect request separately | Sent-thread IDs and next checkpoint |
+| 2026-09-19 | Submit OpenAI Showcase packet and check Partner Locator profile | Submission confirmation and profile URL or support case |
+| 2026-09-22 | Publish one prepared NVIDIA forum post | Live NVIDIA-domain URL |
+| 2026-09-23 | Apply to Coinbase Founders Fuel | Application confirmation |
+| 2026-09-24 | Confirm ElevenLabs eligibility and apply if eligible | Application confirmation or recorded ineligibility |
+| 2026-09-25 | Follow up once in the existing NVIDIA Inception thread if unanswered | Reply or next checkpoint |
+| 2026-09-25 | Begin Google Cloud AI Agents/Marketplace enrollment | Partner/application ID |
+| 2026-09-28 | Lock date and speaker for IBM event two | Live event URL |
+
+External sends, submissions, posts, and event publication remain owner-gated. The material
+can be prepared completely in advance; the actual dispatch is recorded only after it occurs.
+
+## Research rules
+
+- Prefer official program, documentation, or owned community sources.
+- Record `last_verified` for every row; re-check any intake older than 30 days before using it.
+- “Applied” and “submitted” are not wins. A live URL or explicit acceptance is the win.
+- A manifest in `public/.well-known` is not a directory listing.
+- If a program is membership-based, state the eligibility dependency in the row.
+- Never imply a partner endorsed three.ws because an employee replied. Preserve the exact
+ public action and exact relationship wording.
+
+Last verified: **2026-09-15**.
diff --git a/marketing/growth/templates.md b/marketing/growth/templates.md
new file mode 100644
index 000000000..568e39ff5
--- /dev/null
+++ b/marketing/growth/templates.md
@@ -0,0 +1,136 @@
+# Co-marketing dispatch templates
+
+These templates use current three.ws facts and active opportunities. Re-verify the linked
+proof immediately before sending. Relationship wording and logo use still follow the
+partner-specific kits.
+
+## The one-page partner brief
+
+Every partner receives the same six-part brief, tailored to its audience:
+
+| Part | Required content |
+| ------------ | ------------------------------------------------------------------------------------ |
+| Outcome | One sentence describing what the user can now do |
+| Partner role | The exact production technology or program involved |
+| Proof | One public URL that works without private access |
+| Evidence | Three current metrics or test results with capture dates |
+| Assets | One 16:9 image, one square image, one 15 to 30 second clip, exact alt text |
+| Ask | One action: comment, repost, speaker, listing, newsletter, or editorial introduction |
+
+Send the brief at least 48 hours before a social post and at least ten business days before
+anything requiring brand review.
+
+## IBM relationship note
+
+Subject: `Three.ws user group: event two, Agent Connect, and the open June follow-ups`
+
+> We are ready to schedule the second Three.ws User Group event inside the live three.ws
+> world. The first event proved the format: attendees joined as avatars, used spatial voice,
+> and the venue itself demonstrated the product. The next session is a live build: give an
+> enterprise agent a rigged 3D body, connect its governed tools, and publish the result.
+>
+> Could you help with one product speaker and list the event on the IBM Community calendar?
+> We will provide the event page, moderation, live environment, recording, visual assets, and
+> a recap within 24 hours.
+>
+> In the same thread, could you confirm the next step for the dedicated three.ws page and IBM
+> social co-promotion discussed on June 18, and enable our My Digital Marketing access and the
+> Build-track Partner Marketing Kit? The full public implementation and relationship wording
+> are documented at https://three.ws/ibm/hello.
+
+Send the Agent Connect `APP_ID` request separately using the existing
+[submission pack](../ibm-partner-plus/agent-connect-listing.md); combining a technical unblock
+with the marketing note makes both harder to route.
+
+## NVIDIA partner amplification note
+
+Subject: `Live NVIDIA Audio2Face proof for your developer community`
+
+> We published a working implementation of NVIDIA Audio2Face-3D in production:
+> https://three.ws/demos/audio2face.
+>
+> The story is one claim, one live proof, and a reproducible technical explanation. We have
+> included approved relationship wording, current screenshots, a 20-second clip, and alt text.
+> Would your team be comfortable commenting on or reposting the live post? If a partner-owned
+> technical or community channel is a better fit, we can provide the same proof in that
+> channel's format.
+
+Adapt this structure for another partner only after its public proof URL and approved
+relationship wording are verified.
+
+## GitHub Open Source Friday booking follow-through
+
+Post on [issue #254](https://github.com/githubevents/open-source-friday/issues/254) immediately
+after booking:
+
+> Booked for the confirmed Friday. We will demo prompt-to-rigged-avatar-to-one-tag embed, then
+> take one of the open rig conventions through implementation, test, review, and merge live.
+> The stream plan and fallback assets are ready; happy to send the 16:9 card and 20-second demo
+> clip in advance for the official announcement.
+
+Do not use this reply until the booking is confirmed; the current issue has no date.
+
+## Coinbase Founders Fuel application core
+
+> three.ws is a production platform where AI agents create, inspect, and pay for 3D work. Its
+> paid-service layer integrates the Coinbase Developer Platform x402 facilitator, the official
+> x402 SDK, and Bazaar discovery: an agent finds a priced capability, receives an HTTP 402,
+> settles the payment, retries the request, and receives both the result and an on-chain
+> receipt. The same product has a public endpoint catalog and working buyer flow.
+>
+> Over the next 90 days we will package that implementation into a repeatable builder demo,
+> publish the integration guide, and run a live community session where an agent purchases a
+> 3D capability end to end. Founders Fuel is a strong fit because the remaining challenge is
+> distribution rather than prototype risk. A Launch Spotlight or Builder Showcase placement
+> would let other agent builders reproduce the pattern from working code.
+
+Attach current settlement and usage metrics at submission time; do not paste numbers from an
+old article.
+
+## ElevenLabs Startup Grants application core
+
+> three.ws turns a text prompt or photo into a rigged 3D AI agent that can speak, gesture, and
+> react on any web page. ElevenLabs voice synthesis and voice cloning are integrated into the
+> production agent flow, so speech is not an audio layer beside the character: it drives the
+> visible performance of the face and body. A user can build the avatar, give it a voice, and
+> publish the result without a game engine or native application.
+>
+> The product has a long-term monetization path through paid generation, voice-enabled agents,
+> and pay-per-call tools. The grant would support sustained production voice usage and a public
+> browser-native embodied-voice demo. If accepted, we would also like to be considered for a
+> future Demo Day session centered on the jump from voice agent to visible digital human.
+
+Send only after verifying that the company meets the program's employee-count and account
+eligibility requirements.
+
+## Event speaker invitation
+
+Subject: `Invitation: demonstrate browser-native embodied agents inside a live 3D world`
+
+> Three.ws runs its community sessions inside the product rather than on a webinar page:
+> guests arrive as avatars, use spatial voice, and watch the implementation run in the same
+> browser world. We are preparing a technical session on browser-native embodied agents and
+> would value a 15-minute practitioner segment from your team.
+>
+> We provide the venue, rehearsal, moderation, recording, accessibility notes, visual assets,
+> and 24-hour recap. Your team controls the wording of its role and may review every branded
+> asset before publication. The session remains a three.ws community event unless and until
+> your team approves co-host wording.
+
+Tailor the practitioner segment only after the named speaker and technical fit are known.
+
+## Seven-day proof note
+
+Subject: `Results from the three.ws campaign and the next useful placement`
+
+> Thank you for supporting the three.ws campaign. At seven days, the partner-owned and
+> three.ws posts produced the attached channel-level delivery, qualified product actions, and
+> community responses. The strongest reusable result is included first, with its live URL and
+> capture date.
+>
+> The result supports one next step: placing the same working proof in the relevant directory,
+> showcase, newsletter, or technical program. We will supply the copy, current evidence,
+> approved assets, and owner for the submission.
+
+Attach the completed fields from [measurement.md](./measurement.md). Do not send a proof note
+that contains only impressions.