Marketing engagement · Closing report
Three months of marketing work: what was delivered, and who runs each system from here. This page is the entry point to all of it.
The engagement opened with a deep GTM/Marketing audit: market landscape, competitor benchmarks, and a five-dimension review of the existing setup, closed by prioritised recommendations. The verdict: pre-launch, the marketing function was still to be built. Everything below follows from building it.
The main deliveries of the engagement, phase by phase. The list is not exhaustive: behind each line sit the sub-tasks, iterations and day-to-day support work that carried it.
| Deliverable | Status |
|---|---|
| Phase 1 · Diagnose · 22 May to 8 June | |
| Onboarding pack Welcome brief, access checklist, kickoff agenda, GTM intake form | Delivered |
| 30-60-90 plan and day-by-day retroplanning Plus two visual timelines | Delivered |
| GTM advisory: landscape, mapping, SWOT On-chain options competitive picture | Delivered |
| Week 1 quick wins Prioritised against the volume north star | Delivered |
| Message map Master message, two funnels, three pillars, persona cheat sheet. Three iterations to the CEO version | Delivered |
| Social activation stack v1 | Delivered |
| Marketing OS architecture proposal The structure the nine layers were later built on | Delivered |
| GTM roadmap Three phases against the launch sequence | Delivered |
| Marketing readiness review Recommendations sequenced by horizon, each backed by external evidence | Delivered |
| Core message and narrative For the content channel | Delivered |
| Martech content creation recommendation | Delivered |
| Brand Book v2 Design systems, tokens, agentic integration with visuals, videos, documents | Delivered |
| Phase 2 · Build · 9 June to 29 July | |
| Content database structure Recommended schema, six categories, channel and account fields | Delivered |
| Genesis Part I and II The founder's essays, reviewed and carried through the publication mechanics | Delivered |
| Outreach and sales tooling recommendation | Delivered |
| Academy v1 site Hub by track and level, article template with payoff diagrams, glossary, search, AI-readability layer | Delivered |
| Weekly marketing decks Four sessions, published as PDF | Delivered |
| CEO interview: key insights readout The founder's own answers, captured as the canonical narrative source | Delivered |
| Content Pipeline database Backlog, production and post log through views, with publication links | Delivered |
| Content Engine bundle First self-contained package | Delivered |
| Founder knowledge extraction | Delivered |
| Editorial system Angle engine across six lanes, scored topics, calendar gated to launch, review flow | Delivered |
| State of Volatility series specification Format, first three issues outlined, source check per issue | Delivered |
| NFT Collection: best use cases, benchmarking and planning Idea-stage strategy: collection model, utility ladder, milestone-gated distribution | Delivered |
| Foundation Layer: the Marketing OS The consolidated strategic foundation, from positioning and voice to playbooks, pipeline and research | Delivered |
| Media kit and brand guide | Delivered |
| Analytics recommendation | Delivered |
| Content Engine v2.19 Three-agent chain, seven commands, voice guide, anti-slop rules in two tiers, sourced claims whitelist, channel files, visual templates | Delivered |
| Marketing delivery tracker Epics, tasks, ownership and milestones, maintained across the engagement | Delivered |
| Social media playbooks Channel strategy and post templates for X and LinkedIn, carried into the Marketing OS and the Content Engine | Delivered |
| Team enablement Strategy walkthroughs, shared resources and Q&A across the weekly marketing calls, plus individual coaching and support sessions, about 26 hours total | Delivered |
| Phase 3 · Video production system · 30 July to 21 August | |
| Pilot episode and storyboard review gate First film, plus the voice audition page and the corrected storyboard | Delivered |
| Video framework reference page The chain, each stage contract, the rules applied, the automatic refusals | Delivered |
| Generation account: admin access and spend log | Delivered |
| Architecture report review A full pass checking the report against the system as it actually runs | Delivered |
| Creator landscape panorama Twenty verified profiles, with the finding that differentiates it from a list | Delivered |
| Video production system: mission report What the system does, what it cost, what it refuses | Delivered |
| Video production system V1.0, complete Four stages and the router, the shot library, the spend gate, 503 automated checks, installation and handover documentation | Delivered |
| Skills packages for video production Five skills: script, storyboard, produce, revise, and the academy router, packaged for Claude Cowork | Delivered |
| Video prompt engineering guide The prompt method behind every generated shot, shipped inside the system | Delivered |
Six systems, each carrying its own instructions and designed to be run without its author.
The nine-layer Marketing OS on Notion, the source any person or model reads before writing anything. The CEO owns positioning and locks copy.
A written lesson goes in; a voiced, captioned, on-brand film comes out. Only the produce stage spends, behind a written authorisation naming the exact amount.
A researcher, a writer and an editor, chained so the editor reviews in a fresh context rather than marking its own work, with a claims whitelist that refuses to publish an unsourced figure. The engine has continued to move since handover, which is the point: it is yours and it is being extended.
Backlog, production and post log in one database, and the angle engine that feeds it. The growth lead runs it day to day.
A static education site, readable by people and by language models alike, seeded with starter lessons and built to grow from the pipeline. The content reviewer owns it.
The design lead's Brand Book v2, extended into the AI layer, so every output, human or agent, stays coordinated and on brand.
Beyond the systems handed over, this is the map of what a token launch demands on the marketing and GTM side. Eighteen workstreams, each one buildable on the foundations above. Headlines only, by design.
| Pre-launch · September |
| Launch strategy grid One structured pass over the founding questions; every open gap surfaces at once |
| One-thesis narrative A single story, locked before launch, carried identically by every channel and announcement |
| Boilerplate and one-liner bank Approved descriptions at every length plus a tagline shortlist; every listing, partner page and press mention pulls from the same set |
| Listing and market-structure sequencing What unlocks what, in which order, before the token is live |
| Listing-risk guardrails The decision rule that keeps derivatives listings from forcing a cascade the market cannot absorb |
| Creator program, paid on performance Tiered compensation on verified metrics instead of flat fees; targeting the audience, not the influencer |
| Ambassador and community engine Quest tiers, role systems, reusable campaign briefs and announcement formats |
| Points and distribution design Points mechanics, anti-sybil thresholds, beneficiary tiers, and how the allocation is framed publicly |
| Partnership and ecosystem outreach A give-and-seek qualification per vertical, partner-audience activation, and treasury-level proposals |
| Referral program design A referral matrix built alongside the points system, and the discipline of switching it on only once the numbers earn it |
| AI search visibility How the protocol surfaces in AI-driven search; extends the readability layer already live on the Academy |
| Launch week |
| Launch-week comms guardrails What is said, by whom, and what is deliberately not said while the token finds its market |
| Launch war room One source of truth, one operational checklist, one owner per line |
| Crisis comms playbook Pre-approved scripts, tiered alerting and an incident banner path, ready before they are ever needed |
| Post-launch |
| Post-launch measurement On-chain volume, holder quality and campaign returns, read against the north star |
| Community listening system Community messages analysed at scale and turned into prioritised recommendations: explicit criteria, stated biases, a metric per horizon |
| User feedback sprints A recurring quant and qual ritual: satisfaction scored and segmented, and read against how long each user has been around |
| Competitive intelligence from public communities Reading competitors through their own channels; a maintained watchlist instead of one-off research |