One workspace for the
spec, the content, and the brand.
m18t is where you plan the product you're building, write and publish its content across CMS and social, generate brand-aware imagery, register the analytics events and emails it emits, and keep multiple brands separate — all without juggling twelve tabs.
Free during beta. Bring your own AI keys; you pay providers directly at provider rates. Here's what m18t doesn't do.
Silos kill products.
Marketing pitches features the product team is deprecating. Product ships features marketing doesn't know about. Sales promises capabilities the roadmap dropped last sprint. The founder is the only nervous system holding the picture together — which means the founder is also the bottleneck.
No amount of all-hands meetings, alignment Slack threads, or process documentation makes silo drift go away. The tools cause it. The marketing tool isn't the engineering tool isn't the brand-asset tool isn't the analytics tool, and the only thing keeping them in sync is a human flipping between tabs.
m18t collapses the workspace where product spec, content, brand assets, analytics events, and lifecycle emails all live, so the same brain — or the same team — sees them at once.
Three loops, one workspace
m18t doesn't fit one category. It runs three operational loops that usually live in separate tools. Pick the one that feels like your week:
Plan what you're building.
A relational workspace for the actual entities your product consists of — solutions, features, models, controllers, lifecycles, events. Status rolls up. Whiteboards drop your real entities onto a canvas, not labelled stickies.
Run the brand's content.
One content table covers blog, news, web, help, social, video. AI image generation knows your brand colors and logo. Push to Facebook + Instagram natively, push to your CMS, all on a shared calendar.
Keep multiple brands tidy.
One account, many brands. Brand-switcher re-shards every surface. Each brand carries its own colors, integrations, secrets, analytics events, and content. Works for a founder with side projects and an agency with thirty clients.
Most people use parts of all three. The brand-switcher in the sidebar is the same one across every loop.
What's actually inside
Ten surfaces that integrate with each other. Each is its own deep workspace; together they're m18t.
Product Development
The relational workspace where your product's entities — solutions, features, models, attributes, controllers — live with status rollups and a graph view.
Whiteboards
Persistent canvases that know about your real m18t entities. Drop solutions, features, content, events as live nodes for event storming, process flows, and mapping.
Content workspace
One table for blog posts, news posts, web pages, help articles, social posts, video posts. Plus user-defined content types per brand with their own SEO defaults.
Canvas — AI image gen
Chat-style brand-aware image generation. Your colors, your logo, your content context auto-injected. Output lands in your asset library.
Publish anywhere
Native Facebook + Instagram with carousels. Strapi push per brand per environment with multi-locale handling. Per-channel state and engagement tracking.
Prompt library
Your AI prompts are first-class records you edit by slug, not strings hard-coded in source. SEO prompts cannot hallucinate URLs.
News manager
Scout RSS sources, extract bodies, AI-evaluate relevance, AI-draft. The four-step pipeline a niche content operator runs every morning.
Email repository
Per-brand spec and approval workspace for transactional emails. Draft, version, preview, send-as-test. NOT a campaign send tool — that's a different category of product.
Analytics events
The named-event registry tied to PD controllers and to emails. The event-storming layer for what your product emits.
Multi-brand workspace
Everything described above, scoped to a brand. Switching brands re-shards the whole workspace. The unit, not the upgrade.
What works, what's rough, what's coming, what we're not building
m18t is in beta. The trade we offer is candor about every surface in exchange for your patience with rough edges. The short version below; full state on the roadmap.
Works solidly
- — Multi-brand workspace
- — Product Development
- — Whiteboards
- — Content + SEO indices
- — AI prompt library + Canvas
- — Native FB + IG publishing
- — Strapi CMS push
- — Email repo + events registry
- — Encrypted per-brand vault
Rough today
- — News-generate (currently single-niche)
- — Auto-publish loop (substrate-only)
- — External webhook workflow bridge
- — Older voice in a few UI corners
Coming
- — Team features (Q3 2026)
- — TikTok / X / LinkedIn native
- — More CMS adapters (on request)
- — Scheduled auto-publish
- — Starter prompt library
Not building
- — CRM / lead pipeline
- — E-commerce / inventory
- — Bulk email sending
- — Hosted AI tokens
- — Hosting your website
- — Real-time multiplayer
Built for one of these. Maybe several at once.
Each link below is a re-projection of m18t through one role's lens — the surfaces that role uses heavily, the ones they ignore, and the day it changes.
For solo founders
You write the spec, draft the marketing, fire the analytics events, design the OG image, and answer customer support — sometimes the same day. m18t collapses that into one workspace.
For small product teams
Founder, one to three engineers, maybe a designer. PD plus whiteboards plus the events-to-emails chain in one place. The shared spec workspace GitHub Projects can't be.
For marketers
Content, SEO, social, email-spec, canvas — every inbound pillar except paid ads. The brand-switcher cuts context-switching across however many brands you run.
For agencies
One account, one switcher, one workspace per client. The agency tier isn't a thing here. Multi-brand is the unit, not the upgrade.
For content creators
Read thirty sources, publish one piece. The news manager runs the four-step pipeline you'd otherwise do by hand. Canvas covers the cover graphics.
For cross-functional teams
Ownership and assignment across the work the team does, with status rollups by person and brand. Shipping with Q3 2026 team-features release.
What m18t is willing to stand on
Decision filters. When a question is unclear — add this feature? support this use case? phrase it this way? — pass it through these. The full version lives on the about page.
- 1
Silos kill products. One workspace beats five connected by integrations.
- 2
Multi-brand is the unit, not the upgrade. Same architecture for one brand or thirty.
- 3
AI is your account, not ours. Bring your own key. We don't resell tokens.
- 4
Opinions ship. Configuration drowns. Ten statuses, sensible defaults, learn it once.
- 5
The product spec lives where the marketing happens. Adjacent, not integrated.
- 6
Dogfood, then generalize. Clearly useful and visibly rough beats beautifully consistent and quietly useless.
- 7
Beta is not an apology. Honest about state, every surface, every week.
Frequently Asked Questions
Try m18t. Free during beta.
Bring your own keys. The founder fixes bugs the same week. If it's not the right tool for you, you'll know within an hour.