The shared product record a task board 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 what engineering builds and what marketing promises stay aligned. PD entities, whiteboards, events, emails. Same workspace. No drift.
Sprint kickoff, with and without m18t.
Before
The PM writes the sprint plan in a doc. Engineers open the task tracker and create cards for each task. The designer opens the design tool and starts mockups. Marketing waits to be told what's being built. Plan changes don't reach the tracker; tracker updates don't reach the doc; design flows reference doc 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.
The written product, the tracking, the design, and the 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. Every surface shares the same brand-switcher and the same status pill.
The surfaces that align engineering and marketing.
Product Development workspace
Every feature, model, controller and event documented relationally, each parent showing the spread of statuses of the entries attached to it. One shared record: when marketing reads a Feature in PD, they're reading the same thing engineering reads.
Product DevelopmentWhiteboards with entity nodes
Event storming, architecture diagrams and retros, with your actual m18t entities as nodes, not labelled stickies that go stale. Boards stay synced with the product.
WhiteboardsAnalytics events + email repository
The events your controllers emit are named here. The emails that belong to those moments live here too. The full feature → event → email chain sits in one place. Engineers and marketers see the same registry.
Analytics eventsContent workspace tied to PD
Release notes, feature announcements and help articles, each linked to the PD Feature it describes. Marketing can't accidentally promise something engineering deprecated.
Content workspaceMulti-user is live, with one honest caveat.
m18t is multi-user today. Invite teammates, give them roles, scope members to specific brands, assign work with assigned-to fields, and mention people to notify them. No shared login required; everyone works under their own account.
The caveat: roles come from a fixed system set, and creating custom roles isn't built yet. For a founder plus a few engineers and a marketer, the roles that exist cover the week.