04 / Trajectory
● Public roadmapThe four services are the first layer — not the destination.
A direction, spoken out loud
What we ship today is scoped to be usable this quarter. What comes after is scoped to be worth building for years.
Every website, every app, every content engine we hand over is a component of a longer arc — one that ends somewhere most community software refuses to go. We won't spoil the ending. But we're willing to mark the map.
Foundation. The instrument we're tuning first.
Four services, built to ship in weeks. Each one already works on its own — together they form the operating layer every community we work with needs before anything else can stand on top.
- 01Community Apps3–6 weeks
- 02Community Content Engine2–3 weeks
- 03Websites & Landing Pages3–6 weeks
- 04Growth Marketing4+ weeks
● Each service stands on its own
A connective layer for communities that already have surface — and still feel flat.
Once the foundation is live, the question changes. It stops being "do we have a website" and starts being "do our members actually meet each other through it." That's the layer we're designing next — software that treats a community as a living network, not a directory of seats.
Working title
The member graph.
A soft-edged layer that sits above every surface we ship — so a member who joined through a newsletter is the same member visible in the event feed, the directory, the dashboard. One thread, many rooms.
Shared identity across surfaces
Editorial & event rhythm, unified
Private spaces that feel personal
[ ████ not yet announced ]
The tools that exist today treat a community like a mailing list with a skin. We don't think that's good enough.
What this layer replaces
- Five disconnected SaaS subscriptions stitched by hand
- Copy-pasted member lists that age out the moment they’re exported
- Events no one remembers unless the person running them remembers to remind them
- “Community” platforms that optimize for retention, not recognition
Arriving / after the first wave of Phase 01 partners ship
A surface built for people to find each other — on purpose.
The layer after the layer. We're not going to describe it in detail yet, because the work to earn it hasn't shipped. But the direction is pointed: away from feeds, away from engagement traps, toward something closer to a meeting place than a platform.
Built around showing up, not scrolling.
████ ████████ — ██ ██████ ████ ██.
The communities we've worked with first.
Another feed. Another inbox. Another wall.
████ · after Phase 02 proves out.
Partners from Phase 01 get the earliest look.
“If the internet ever taught us to meet each other again, it won't look like what taught us to scroll.”
— Thermait, on where this is headed
Something that reaches further than a community ever could.
We're not describing this one. Not because we don't know what it is — but because the moment you name it, people stop imagining. What we'll say: it's the reason the first three phases exist. Not a feature. Not a product extension. The destination.
Social. But not like that.
████ ████ ████ ████ ████.
Everything before it.
The communities that trusted Phase 01.
[ ████████████████ ]
Phase 01 partners. No one else, first.
████████ · ████████████ · not yet announced
Working notes
What we're thinking through.
04 / Why this order
We could have started with the end. Most studios do. We think that's how you end up with software nobody asked for.
The four services pay for the right to build the second layer. The second layer earns the right to build the third. Each phase is a promise to the communities shipping with us now that the work they see is the same work the bigger thing will be built on — not abandoned for it.
If you want to be a Phase 01 partner, you'll be a Phase 02 and Phase 03 partner by default. That's the entire arc in one sentence.
05 / Step in early
The arc is short-listing its first partners.
No waiting list, no form theatre. A conversation, a scoped first layer, and a seat at the table when the next layers land.