You're the spec, the marketing, the analytics, and the email copy. m18t is the workspace that knows it.
If you're building one product (or two side projects) and your week disappears into context-switching between Notion for the spec, Coda for the content calendar, Buffer for social, Canva for graphics, and GitHub Projects for engineering — m18t is the rebuild you would have done if you'd had time.
[solo founder before/after: 12 tabs → one m18t workspace]
Tuesday, with and without m18t.
Before
You spend 45 minutes drafting a blog post in a Google Doc, paste it into WordPress, realize the cover is wrong, open Canva, design a cover, download it, re-upload to WordPress, then remember you wanted a social post about this, switch to Buffer, paste the headline, retype because Buffer's character limit cut it, attach the image, schedule.
Before social goes live you remember the launch email — open Mailchimp, find last month's template, copy it, paste the new copy, fix the subject line, save the draft, mark a reminder to come back.
Open the analytics tool. Realize you never named the event for "user clicks the new feature button" — open Notion, find the page named some variant of "events to track," realize it's three months stale, give up, type the event name straight into the dashboard, hope you remember it next week.
Open GitHub Projects to mark the feature shipped. Switch the card from "In progress" to "Done." Don't have time to update the spec doc in Notion, the wiki in Coda, or the Loom you recorded.
Tab count at end of day: fourteen.
After
You're in m18t. The brand-switcher in the sidebar already shows the right brand. You draft the blog post — the rich-text editor knows your SEO defaults for blog-post and pre-fills the meta-title template.
You hit a button to generate the cover image. AI Canvas rewrites your two-line brief using your brand colors and the article's excerpt, generates, lands in your asset library, attaches to the blog post.
You click "publish." Goes to your Strapi CMS for the blog and to Facebook + Instagram for the social. Per-channel state shows green. Sync log captures the receipts.
You open the email tied to this launch — drafted two weeks ago when you specced the feature in PD. Preview, send-as-test, approve.
You open PD, find the feature, click the status pill, set it to "Production." The status rolls up to its parent feature, then to the solution. The analytics events the feature emits are already named — you don't have to remember.
Tab count: one.
The surfaces solo founders actually live in.
Product Development workspace
You're the only person holding the product spec. m18t is where it lives so it doesn't only live in your head. Solutions, features, models, controllers, events — documented relationally, status-tracked, attachable to artifacts (decision logs, design notes, half-baked drafts). When you talk to a developer (yours or contracted), you point them at PD, not at a stale Notion page.
Content + Canvas + Publish
You write the marketing yourself. m18t's content table covers blog, web, social, help — same editor, one status, one SEO model. Canvas generates the cover graphics that would otherwise be a Canva tab and 20 minutes. Publish handles the FB / IG / CMS push in one click.
Email repository + Events registry
You're the one drafting the transactional emails your product sends. m18t's email repo lets you draft, version, preview, send-as-test, approve — before you wire them into code or a third-party email service. The events registry holds the named analytics events your product emits, tied to the controllers in PD that fire them. When a developer adds the instrumentation, they read the catalogue here.
Multi-brand workspace (if you have side projects)
If you're running your main product and a side project (or two, or three), the brand-switcher re-shards every surface. Each brand has its own colors, integrations, SEO defaults, content, analytics events. Same UI, different world. Pricing will likely meter on brands, not seats — so multi-brand is treated as core, not as an agency upgrade.
m18t has surfaces you won't touch. That's fine.
- Team features. You're solo today. When you hire your first person, the team layer (Q3 2026) becomes relevant. Until then, you don't think about ownership, assignment, permissions.
- News manager. Unless your product is niche content, the news scout pipeline is for someone else. Skip.
- Whiteboards. Useful for occasional event-storming, but solo founders mostly think with code and prose, not stickies. Open when you need it; ignore otherwise.
The point isn't that you use every feature — it's that the features you do use are integrated. The brand-switcher in the sidebar is the same one whether you're editing a blog post or describing a controller.
Tools you can stop or downgrade.
| If you use… | m18t covers… | What stays separate |
|---|---|---|
| Notion (for product specs) | PD workspace + artifacts + content table | Generic page-nesting / personal wiki |
| Coda (for content calendars + tables) | Content + calendar + status set | Custom database flexibility |
| Buffer / Hootsuite / Later | Native FB + IG publishing + calendar | TikTok / X / LinkedIn (today routes elsewhere) |
| Canva | Brand-aware AI cover and social-graphic generation | Pixel-perfect multi-page layouts |
| Mailchimp / Resend (for drafting) | Email repository, preview, test-send | Actual delivery (use your existing sender) |
| GitHub Projects | PD workspace with structural depth | Issue tracking and sprint cadence |
| Scattered Notion + Drive folders | Artifacts attached to the work they describe | Generic file storage |
You don't replace your AI provider, your email sender, your CMS, or your hosting. m18t is the workspace; those are the runtime.
The roadmap items that move the needle for you.
- Onboarding articles for BYOK setup. The hardest part of m18t today is getting your own OpenAI / Gemini / Meta / Strapi keys connected for the first time. Thorough how-to articles with screenshots for each provider — in active drafting.
- Scheduled auto-publish. Today every publish is a click. Coming: cron + status + due-date → push without click. Big quality-of-life for solo operators who can't be at the keyboard at 9 AM Tuesday.
- Shared starter prompt library. So you don't have to build your AI prompt library from zero.
See full roadmap → /roadmap
Frequently Asked Questions
Stop juggling. Start in beta.
Free during beta. Bring your own keys. Support comes from the founder directly.