The shared spec workspace GitHub Projects can't be.
If you're a founder plus one to three engineers, maybe a designer, shipping faster than the marketing site catches up — m18t is where engineering's spec and marketing's promise stay aligned. PD entities, whiteboards, events, emails. Same workspace. No drift.
[small team view: PD graph + whiteboard + linked release-note]
Sprint kickoff, with and without m18t.
Before
PM writes the sprint spec in Notion. Engineers open Linear and create cards for each task. Designer opens Figma and starts mockups. Marketing waits to be told what's being built. Spec changes don't propagate to Linear; Linear updates don't propagate to Notion; Figma flows reference Notion pages that have been edited since.
Midway through the sprint, marketing asks "is feature X shipping this week?" and nobody can answer without checking three tools.
Spec, tracking, design, and announcement all live in different workspaces.
After
PM opens PD, creates the Feature, links the Models it depends on, sets the status to Planning. Engineers open the same Feature in m18t, see the models, set status as work progresses (Doing → Testing → Production).
Marketing drafts the launch blog post in the content workspace, links it to the PD Feature. When the feature hits Production, marketing sees it without asking. The release-note artifact is attached to the Feature, the email tied to the launch event is in the email repo.
One workspace. The four surfaces share the same brand-switcher and the same status pill.
The four surfaces that align engineering and marketing.
Product Development workspace
Every feature, model, controller, event documented relationally with status that rolls up. The shared spec — when marketing reads a Feature in PD, they're reading the same thing engineering reads.
Product DevelopmentWhiteboards with entity nodes
Event storming, architecture diagrams, retros — with your actual m18t entities as nodes, not labelled stickies that go stale. Boards stay synced with the product.
WhiteboardsAnalytics events + email repository
Events emitted by your controllers are named here. Emails fired by those events live here. The full feature → event → email chain lives in one place. Engineers and marketers see the same registry.
Analytics eventsContent workspace tied to PD
Release notes, feature announcements, help articles — link each to the PD Feature it describes. Marketing can't accidentally promise something engineering deprecated.
Content workspaceTeam features are imminent, not live today.
m18t today is single-operator-shaped with multi-brand awareness. Multi-user-per-tenant with assigned-to fields, ownership, and roles ships in Q3 2026. You can use m18t now with a small team by sharing an account — the surfaces work for collaborative use even though formal ownership / permissions aren't there yet.
If formal team support is a hard requirement, wait for the team-features release. If you can work around it for now (one shared login, informal ownership), m18t is useful today.