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.
three.ws marketing operating plan
Operating window: 2026-09-15 through 2026-12-15
North star: turn shipped proof into partner-owned distribution, community participation,
and repeated use of three.ws and $THREE.
This is the control page for the marketing push. It does not replace the detailed work already in the repository. It puts that work in an execution order, names the scorecard, and makes clear which actions require the owner.
The central decision is to spend the next 90 days distributing what already exists. The product has 409 audited surfaces; only 47 have received a dedicated announcement and 285 have never been mentioned on X. Eleven long-form articles, multiple partner announcement packs, two event plans, and several listing submissions are already written. More undirected drafting would increase the inventory without increasing reach.
The strategy in one loop
shipping proof
-> a useful story on a partner or community surface
-> official listing, reply, guest, or co-marketing support
-> community creates, contributes, or uses a $THREE utility
-> the result becomes the next proof asset
Every campaign must complete the loop. A partner logo without a user action is not a campaign. A product post without a distribution partner or community follow-up is an isolated post. A token post without a utility someone can use is speculation, not marketing.
What wins, based on our own archive
The account-level evidence is in the announcement voice, measured from 158 posts with usable metrics:
| Signal | Median lift over the account median | Operating consequence |
|---|---|---|
$THREE or token utility |
13.3x | Lead with $THREE when the demonstrated action genuinely uses it |
| A truthful partner mention | 4.5x | Build campaigns with partners, then tag only the partner involved |
| 100 to 179 characters | 3.0x | Default X post length |
| A real product image | 2.3x | No finished X pack without a current screenshot |
| A destination link | 1.5x | Give every post one action and one link |
The two largest avoidable losses were one-line posts and text-only posts. The house rules remain: one checkable claim, real media, one destination, no hashtags, no emoji, no generic launch copy.
The four programs
1. Partner proof, 35% of output
Turn existing relationships into things hosted, listed, replied to, or distributed by the partner. The order is:
- official catalog or directory listing;
- partner-domain article, event page, or showcase;
- partner social acknowledgement;
- our announcement of that external proof;
- a follow-up case study with measured use.
The current action queue is canonical in Partnership and listing pipeline. The most valuable immediate asks are the IBM Agent Connect application id, the OpenAI directory and Showcase submissions, the NVIDIA catalog follow-up, IBM marketing-program access, and the second IBM community event date.
Every partner request should arrive as a forwardable packet: one-sentence pitch, 100-word abstract, working link, screenshot, speaker bio if relevant, two proposed dates, exact requested action, and approved relationship wording. Do not ask a partner to invent the campaign for us.
2. $THREE utility, 25% of output
The editorial rule is show the action, not the ticker. Each utility post must answer all three:
- What can a holder do now?
- Where does
$THREEenter the action? - What verifiable result comes out?
Run the series as five chapters, each anchored to a live surface and current proof:
| Chapter | Story | Call to action |
|---|---|---|
| Access | $THREE changes the price or access path for a real service |
Complete the action on the relevant live page |
| Agent work | Agents hire, earn, or settle work using the platform economy | Inspect a real receipt or task lifecycle |
| Creation | Community creation becomes an event entry, asset, or reward | Make and publish one creation |
| Community | The token connects a shared world, contest, or commemorative reward | Attend, vote, or claim through the event flow |
| Transparency | Supply, holders, buybacks, burns, and activity are shown from live sources | Verify the figures on /three-token |
Never lead a utility campaign with price. Re-read every number from the live surface on posting day,
and link to the action rather than a generic home page. The long-form foundation is
The $THREE thesis.
3. Shipped-product proof, 25% of output
Work down the announcement backlog in clusters rather than spraying 285 unrelated features. One cluster supplies a hero demo, three to five follow-up posts, a community challenge, and a technical article. Prioritize capabilities that are visible in under ten seconds:
- Forge Max, Motion Swap, Mocap Studio, and the creation loop;
- Rig Doctor, retargeting, animation, and Open Source Friday;
- Guardian, receipts, labor, and the agent economy;
- Wardrobe, Fits, worlds, and community identity;
- developer tooling: the MCP fleet, SDKs, packages, and embeddable agents.
The full inventory, strongest candidates, and per-surface "announced on X" state are in Announcement coverage. Do not announce a route merely because it is unannounced. It must support one of the four programs and a measurable action.
4. Community participation, 15% of output
The community should be making the proof, not only reacting to it. Maintain three rhythms:
- a daily or weekly creation prompt that takes less than three minutes;
- one live show, demo, office hour, or contributor session each month;
- one headline event each quarter.
The recommended headline event is the Forge-Off Open: five daily creation themes, a community vote, and a finale in the three.ws world. IBM participation is upside, not a launch dependency. The event can run on our surfaces, our date, and our stream if no partner slot arrives.
The next 14 days
This is the launch order as of 2026-09-15. External posts, submissions, email, bookings, and event commitments are owner actions. Everything linked in the Asset column is already prepared.
| Due | Action | Owner | Asset | Done when |
|---|---|---|---|---|
| Sep 15 | Book a GitHub Open Source Friday slot and reply to approved issue #254 | Owner | Stream plan | Date is visible in the issue and calendar |
| Sep 15 | Publish the approval beat after the booking reply | Owner | Announcement pack | Post URL is recorded in the pack |
| Sep 16 | Send the IBM Agent Connect application-id request | Owner | Submission pack | Request exists in the partner thread |
| Sep 16 | Bundle the IBM directory, social, marketing-kit, and event asks into that thread | Owner | IBM visibility map | Each ask has an owner or IBM response state |
| Sep 17 | Submit the OpenAI Showcase and directory packets | Owner | Channel map | Confirmation links or receipts are recorded |
| Sep 18 | Choose the second IBM community-event kickoff date and prize pool | Owner | Event proposal | The event has a real date and budget |
| Sep 18 | Decide whether a local Hacktoberfest venue is viable | Owner | Tentpole brief | Venue, city, capacity, and host are named, or the idea is closed |
| Sep 19 | Publish the first prepared partner-domain article | Owner | Publishing program | Canonical URL is recorded and answered |
| Sep 20 | Submit the Hacktoberfest Fest application if a venue exists | Owner | Tentpole brief | Application receipt is recorded |
| Sep 22 | Publish $THREE utility chapter 1 with current live proof |
Owner + marketing | Token thesis | Post drives one instrumented utility action |
| Sep 23 | Publish the next prepared technical-community article | Owner | Publishing program | Canonical URL is recorded and discussion answered |
| Sep 25 | Follow up on the NVIDIA catalog request if still unanswered | Owner | Visibility map | Response or next follow-up date is logged |
| Sep 26 | Announce the Forge-Off Open save-the-date | Owner | Event proposal | Landing page and registration/action URL are live |
| Sep 29 | Review the scorecard and choose the next two-week slate | Owner + marketing | Scorecard | Stop, continue, and double-down decisions are written |
If a date slips, do not compress two partner articles or two major announcements into one day. Move the later item. The goal is sustained proof with room to answer people, not clearing a checklist.
Weekly publishing rhythm after the sprint
| Day | Primary beat | Community follow-through |
|---|---|---|
| Monday | $THREE utility demonstrated on a live surface |
Ask holders to complete or verify the action |
| Tuesday | Partner-domain or technical-community article | Answer every substantive reply |
| Wednesday | Creation prompt, user artifact, or contributor issue | Feature the strongest community result |
| Thursday | Partner listing, integration proof, or product cluster | Ask the named partner for a reply or repost only when pre-coordinated |
| Friday | Open-source build, livestream, or week-in-shipping proof | Direct people to one claimable issue or live demo |
Three strong primary posts per week is enough. Tuesday and Thursday can be the same beat when a partner article lands. Community replies, clips, and quote posts extend the beat without creating a second campaign.
Campaign tentpoles
Open Source Friday
State: approved, awaiting date.
Job: acquire contributors and earn GitHub-owned recognition.
Hero action: a newcomer claims a rig convention issue; the fix is reviewed and merged live.
Reuse: approval post, date post, contributor call, reminder, live clip, merged-PR proof, replay,
and a permanent first-contribution path.
Primary measure: first-time contributors who comment, open a PR, merge, and return within 30 days.
The date is the only blocker. Do not spend the approval news before the issue has the selected date.
Forge-Off Open with IBM
State: format complete, date unchosen.
Job: turn partner reach into first creation and next-day return.
Hero action: type one sentence, publish a real 3D creation, vote, then return for the next theme.
Reuse: IBM event page, five daily prompts, daily winner cards, finale stream, world screenshots,
winner gallery, and a responsible-AI case study.
Primary measure: unique creators, published creations, voters, day-two return, and finale attendance.
Hacktoberfest 2026 tentpole
State: applications are open on a rolling basis; venue is
the gate.
Job: put three.ws into an official open-source event directory and recruit local contributors.
Format: choose a one-day Hack Day if the team can support hands-on building, or a Meet Up if the
goal is talks and community. Both are in person. A Hack Day can qualify for event-expense support;
both formats receive organizer support and program promotion.
Hard requirements: a safe accessible venue, reliable Wi-Fi, power, seating, event check-in, and
post-event evidence under the official FAQ. Do not apply
until a real venue and accountable host exist.
three.ws angle: "Give an AI agent a body": a short prompt-to-avatar workshop followed by teams
improving a rig convention, animation, accessibility feature, or embed.
Primary measure: checked-in builders, first-time contributors, PRs opened, PRs merged, and
participants who return within 30 days.
The $THREE utility season
State: live product proof exists; editorial packaging is next.
Job: replace abstract token messaging with repeated, verifiable utility.
Format: five weekly chapters from the utility table above, each with a live action, screenshot,
and end-of-week receipt.
Primary measure: completed utility actions by unique wallets, repeat actions, and the share of
participants who also use a non-token product surface.
The content reuse rule
One real event or release should yield a complete asset stack:
| Moment | Asset |
|---|---|
| Before | Partner pitch, event/listing page, save-the-date, community prompt |
| During | One wide screenshot, one vertical clip, one quote, one live metric, one participant artifact |
| Within 24 hours | Result post with a verifiable number and destination link |
| Within 72 hours | Partner/community recap and winner or contributor profile |
| Within two weeks | Technical case study, searchable docs update, and next-action invitation |
| One month later | Outcome update with retention, usage, or merged-contribution evidence |
Never repost the same body across venues. Reuse the proof and media while rewriting the opening for the audience. The detailed venue rules and eleven finished drafts are in the publishing program.
Weekly scorecard
Record this every Monday for the previous Monday through Sunday. Use raw counts and conversion rates, not a blended "engagement" score.
| Funnel | Required measures | Decision it supports |
|---|---|---|
| Partner distribution | submissions sent, official listings live, partner-domain posts, partner replies/reposts | Which partner relationship produces durable reach |
| Community | unique creators, creations published, voters, live attendees, seven-day return | Which programs create participation rather than applause |
$THREE utility |
unique wallets completing the named action, total actions, repeat rate | Which utility is understood and repeatedly used |
| Open source | issue claimants, first-time PR authors, PRs opened, PRs merged, 30-day return | Whether recognition becomes a contributor pipeline |
| Content | impressions, destination clicks, click-through rate, action completions, completion rate | Which story and channel create product use |
Attach a campaign id and UTM source, medium, and campaign to every controllable link. Record the baseline before launch. A result without a baseline can still be interesting, but it cannot prove lift.
Stop, continue, double down
- Stop a recurring format after three runs with no attributable product action or useful partner/community conversation.
- Continue a format that produces the target action even when raw impressions are modest.
- Double down when a partner-owned surface or community artifact converts at twice the account's four-week baseline. Reuse that mechanism with a new proof point within seven days.
Ownership and gates
| Work | Default owner |
|---|---|
| Research, briefs, drafts, screenshots, tracking, analytics | Marketing/engineering |
| External booking, submission, email, post, publication, or promise | Owner |
| Partner claim and badge review | Owner against the relevant partner guide |
$THREE figures |
Marketing, refreshed from the live surface immediately before publication |
| Event prize transfers | Owner with explicit transaction confirmation |
Marketing can prepare everything up to the external boundary. It must never silently turn an approved relationship into an endorsement claim, announce an unbooked date, publish stale token figures, or automate a prize transfer.
Source map
- Partnership and listing pipeline: single next action and owner for every active relationship or listing.
- OpenAI, IBM, and NVIDIA growth plan: detailed partner-specific routes and prepared assets.
- Publishing program: eleven long-form drafts, short-form venue kit, order, and per-venue rules.
- Announcement coverage: every shipped surface versus its public coverage.
- Announcement voice: measured format rules and content QA.
- Open Source Friday plan: application, run of show, and campaign.
- Second IBM event: Forge-Off Open proposal and engineering scope.
- Listings: public status record.