Welcome to m18t

m18t is a multi-brand operations workspace that fixes silo drift: plan your product, publish content to your CMS and social, and keep every brand cleanly

What you'll learn

  • What m18t is, and the "silo drift" problem it exists to fix.
  • How the multi-brand workspace re-shards everything when you switch brands.
  • Where to start, in order.

m18t is an operations workspace for people building and running brands. In one tool you plan the product you're building, write and publish its content across your CMS and social channels, generate brand-aware imagery, register the analytics events and emails your product emits, and keep multiple brands separate without juggling twelve browser tabs.

It was built by a founder who got tired of stringing Notion, Coda, Buffer, Canva, and GitHub Projects together, then generalized it for other operators. It's in beta. It's real, used daily. It's missing things, and this help center will tell you which.

The name follows the i18n idiom: a letter, the count of letters between, the final letter. m-(18 letters)-t spells minimum viable producT. A nerdy footnote, not a marketing angle.

The problem: silo drift

The pain of a disconnected tool stack isn't the subscriptions. It's silo drift — the truth in one tool quietly stops matching the truth in another:

  • Marketing publishes content about a feature engineering already deprecated.
  • A new content hire doesn't know the scope of the product they're writing about.
  • Analytics events get added in PostHog ad-hoc, emails get drafted in Mailchimp ad-hoc, and the spec for what should fire when lives in a Loom nobody rewatches.
  • An agency running five client brands can't tell, at a glance, which client's blog needs an SEO pass this week.

m18t collapses the workspace where product, content, brand assets, and the operating glue between them all live. When the spec and the content calendar sit in the same database, they can't drift apart without someone noticing.

Multi-brand is the whole shape

The one architectural fact to internalize before anything else: every operational entity is brand-scoped. Content, assets, integrations, channels, product specs, AI prompts, news sources, cron jobs, Canvas sessions, whiteboards — all carry a brand.

A dropdown in the sidebar — the Brand Switcher — filters the entire workspace at once. Switch from one brand to another and the content table, the asset library, the integration credentials, the AI prompt library, and the PD spec all re-shard to the brand you picked. Same UI, different world.

This is what makes m18t serve a solo founder with three side projects and an agency with thirty client brands using the exact same product — see Brand vs. Business for how the layers stack.

Who uses it, and how

There's no single ideal user; the platform has surface area on purpose.

What's in the platform today

Each of these maps to live code, not aspiration:

  • Unified content workspace — one table for blog posts, news posts, web pages, help articles, social posts, and your own custom types, with SEO defaults per type.
  • Product Manager (PD) — a relational spec of what you're building, with status that rolls up from leaves to roots and a dependency graph view.
  • Graphics Generator — chat-style, brand-aware AI image generation. In beta.
  • Whiteboards — persistent canvases where your real m18t entities become live nodes.
  • News Manager — a four-stage pipeline: scout RSS, extract, AI-evaluate, AI-draft.
  • Emails & Events — a workspace to spec transactional emails and the analytics events that trigger them.
  • Multi-channel publishing — native to Facebook and Instagram, plus push to your Strapi CMS.

What it isn't

Honesty is the trade for your patience with rough edges. m18t is not a CRM, an e-commerce platform, or a bulk/campaign email tool — none of those exist here. Native publishing covers Facebook and Instagram today; TikTok, X, LinkedIn, and Threads are roadmap. The only headless CMS it pushes to natively is Strapi. And AI is bring-your-own-key — m18t routes your OpenAI, Google, or Anthropic calls; it never resells tokens. See Why m18t uses BYOK.

One more thing to set expectations: team features are live but young. You can invite members from Business → Team, give each a role that governs what they can do, and optionally restrict a member to specific brands with a brand scope. A member with no brand scope set can access every brand in the account — unrestricted is the default until you set it, so scope members at invite time when they shouldn't see everything.

FAQ

Is m18t free? It's free to use during beta. You pay your AI and social providers directly, because m18t doesn't mark up tokens or take a cut. See Why m18t uses BYOK.

Do I need to know how to code to use m18t? No. The content, publishing, news, and graphics surfaces need no code. Product Manager (PD) is denser — it's a relational way to spec software — but you can ignore it entirely and still get full value from the rest.

Why is the AI button greyed out? You haven't added an AI key yet. AI features (SEO generation, Graphics Generator, News evaluate/draft) are BYOK-gated and stay disabled with a tooltip until you add a key. Fix it in the Secret Vault.

Can I invite my team or my clients? Yes. Invite members from Business → Team, pick a role for each, and set a brand scope if a member should only see certain brands. New members are unrestricted until you set that scope — set it at invite time. For the client-facing considerations, see Agency Mode.

What does m18t replace? For most users, some combination of Notion + Buffer + Canva + an RSS reader + scattered spec docs. It does not replace a real CRM, a real email-sending platform, or your CMS's hosting — it pushes content to your CMS.

What's next

Set up your workspace in this order:

  1. Why m18t uses BYOK — the billing model in one read.
  2. Get an OpenAI API Key — generate a key and store it in the vault.
  3. Your First Brand — create a brand and set its identity.
  4. The Studio Dashboard — get oriented.
  5. Your First Content Piece — draft and publish, end to end.

Was this article helpful?