Sheet 2 — Autonomys Mainnet

D1.1 · Section A–A — engagement assembly · callouts read on the datum

Eighteen months, sequenced backward from mainnet.

M1 – M4

Rebrand

Foundation

One narrative spineVisual language, voice, and messaging architecture — every channel pulls from it.
M2 → continuous

Content engine

Production

Near-zero → four digits of growthDaily cadence, structured onboarding, feedback loops to product.
M6 – M13

Exchange pipeline

Partnerships

Binance · Bybit · KrakenUnique content, compliance docs, and community proofs per listing.
M9 – M14

Launch architecture

Orchestration

Whisper → Tease → ShoutOne storyline across every channel and KOL through launch week.
M14 – M18

Mainnet window

Delivery ✓

Shipped on scheduleListings landed, FOX & CNBC aired, Top 100 CMC held through Day 30.

SECTION A–A · ENGAGEMENT ASSEMBLY — READ LEFT TO RIGHT EVERY PHASE TIMED BACKWARD FROM MAINNET

D1.2 · Measured outcomes — the coverage above is the reference

FIG. 2.0 — 2024 WRAPPED · THE MAINNET YEAR IN NUMBERSPRODUCED BY THE CONTENT ENGINE · 1:53 · ▶ PRESS PLAY

FIG. 2.1

14,000%

Social growth · 12 monthsX + Discord, from a near-zero base

REF: platform analytics

FIG. 2.2

Tier-1 listingsBinance · Bybit · Kraken — all inside the launch window

REF: exchange announcements

FIG. 2.3

TOP 100

CMC visibilityHeld through Day 30 post-launch

REF: CoinMarketCap

FIG. 2.4

FOX·CNBC

National pressCoverage most pre-mainnet protocols never reach

REF: broadcast segments

D1.3 · Construction notes — read in order

How it was assembled.

N1.

A protocol with no story.

Autonomys Network is a decentralized AI infrastructure protocol — pre-mainnet when I joined, with strong technology but no brand presence, no distribution, and no GTM system. The challenge: build the marketing infrastructure from scratch while keeping pace with a fast-moving technical roadmap.

Everything on this sheet happened inside one mainnet year — the most compressed, highest-stakes window in a protocol's life.

N2.

Technical project → narrative ecosystem.

The rebrand wasn't cosmetic. New visual language, voice, and messaging architecture gave every downstream channel — exchange decks, KOL briefs, community content — a single spine to pull from. One narrative, every surface.

N3.

The launch plan, end to end.

Launch architecture: content calendar, community milestones, exchange sequencing, and press strategy — all timed backward from mainnet.
Whisper → Tease → Shout: a narrative escalation framework that kept every channel and KOL on one storyline through launch week.
Press execution: FOX and CNBC — visibility most pre-mainnet protocols never reach.
Cross-functional leadership: marketing aligned with engineering, BD, and community across multiple time zones through the protocol's most critical period.

N4.

Three Tier-1s in the launch window.

Led partnership conversations and coordinated deliverables for Binance, Bybit, and Kraken — each requiring unique content, compliance documentation, and community proofs. All three landed inside the mainnet window.

N5.

Near-zero to 14,000%.

A content system scaled the community from near-zero across X and Discord over 12 months — the engine that made the exchange and press motions credible. Daily cadence, structured onboarding, feedback loops back to product.

N6.

What this detail proves.

A pre-mainnet protocol doesn't need a bigger marketing team — it needs a system. One operator, one narrative spine, one production engine: rebrand, GTM, listings, and launch, all shipped inside a single mainnet year.

Eighteen months, sequenced backward from mainnet.

Rebrand

Content engine

Exchange pipeline

Launch architecture