You write the product, 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 a doc tool for the product definition, a table tool for the content calendar, a scheduler for social, a design tool for graphics, and a board for engineering, m18t is the rebuild you would have done if you'd had time.
[founder before/after: 12 tabs → one m18t workspace]
Tuesday, with and without m18t.
Before
You spend 45 minutes drafting a blog post in a doc, paste it into your CMS, realize the cover is wrong, open your design tool, design a cover, download it, re-upload to the CMS, then remember you wanted a social post about this, switch to your scheduler, paste the headline, retype because its character limit cut it, attach the image, schedule.
Before social goes live you remember the launch email. Open your newsletter tool, 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 your docs, 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 your project board to mark the feature shipped. Switch the card from "In progress" to "Done." Don't have time to update the product doc, the wiki, or the walkthrough video 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, and the rich-text editor knows your SEO defaults for blog-post and pre-fills the meta-title template.
You open the graphics generator, pick a brand template, and the cover renders in your colors, lands in your asset library, attaches to the blog post.
You click "publish," or schedule it for Tuesday 9 AM and walk away. Goes to your CMS for the blog and to Facebook, Instagram, and LinkedIn 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 wrote the feature up in PD. Preview, send-as-test, approve.
You open PD, find the feature, click the status pill, set it to "Production." The parent shows the spread of statuses across everything attached to it, so where the release stands is visible at a glance. The analytics events for this feature are already named, so you don't have to remember.
Tab count: one.
The surfaces founders actually live in.
Product Development workspace
You're the only person holding the product definition. m18t is where it lives so it doesn't only live in your head. Solutions, features, models, controllers and 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 wiki page.
Content + Canvas + Publish
You write the marketing yourself. m18t's content table covers blog, web, social and help, with the same editor, one status, one SEO model. The graphics generator turns brand-aware templates into the covers that would otherwise be a design-tool tab and 20 minutes. Publish handles the FB / IG / LinkedIn / CMS push in one click, or on a schedule.
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 and approve, before you wire them into code or an outside email service. The events registry holds the named analytics events your product emits, tied to the controllers in PD they belong to. 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. It's just you today. The team layer (invites, roles, per-brand member scoping, assignment) is live and waiting for your first hire; until then, you simply won't open it.
- News manager. Unless your product is niche content, the news scout pipeline is for someone else. Skip.
- Whiteboards. Useful for occasional event-storming, but founders working alone 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 |
|---|---|---|
| A doc tool holding the product definition | PD workspace + artifacts + content table | Generic page-nesting / personal wiki |
| A table tool for content calendars | Content + calendar + status set | Custom database flexibility |
| A social scheduler | Native FB + IG + LinkedIn publishing, scheduling + calendar | TikTok / X / Threads (not covered yet) |
| A drag-and-drop design tool | Brand-aware templated graphics for covers and social cards | Pixel-perfect multi-page layouts |
| A newsletter tool (for drafting) | Email repository, preview, test-send | Actual delivery (use your existing sender) |
| A project board for engineering | PD workspace with structural depth | Issue tracking and sprint cadence |
| Scattered docs and 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.
What's next that moves the needle for you.
- Onboarding articles for bring-your-own-key setup. The hardest part of m18t today is connecting your own AI, social, and CMS keys for the first time. Thorough how-to articles with screenshots for each provider, in active drafting.
- More native social channels. Facebook, Instagram, and LinkedIn publish natively today, including video and scheduled publishing that runs unattended. TikTok, X, and Threads are next, prioritized by where users actually publish.
- 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 free.
Free to start. Bring your own keys. Support comes from the founder directly.