What works. What's rough.
What's coming. What we're choosing not to build.
m18t is in beta. This page is the honest state of every surface, updated when the code is — not when we feel like saying we updated it.
If you want the marketing version, start at the home page. This page is for the kind of reader who'd rather see the rough edges before signing up.
What works solidly today
Surfaces the founder uses every day, and a handful of beta users use theirs. They have edges; they don't fall over.
Multi-brand workspace
Every entity is scoped by brand. Brand-switcher in the sidebar re-shards the entire workspace. Encrypted per-brand secret vault. Pricing axis sits here.
Product Development workspace
Relational planning across thirteen entity types — solutions, features, models, attributes, controllers, lifecycles, events, views, layouts, components, middleware, plus the role and policy junctions. Status rolls up from leaves to roots. Dependency graph visualization. Attach artifacts to any node.
Whiteboards with m18t entity nodes
Persistent infinite boards where you drop your real solutions, features, content, and events as live nodes — not just labelled stickies.
Unified content workspace
One rich-text editor, one table, all content types. Blog posts, news posts, web pages, help articles, social posts, video posts — plus user-defined custom types per brand.
SEO indices per brand × content type
Path prefix, schema.org type, robots default, OG image fallback, meta-title template. Defaults flow into every piece; per-piece override available.
Native publishing to Facebook + Instagram
Single images, multi-image carousels, link-back URLs, full container handling. Per-channel publish state tracked.
CMS push to Strapi
Per brand, per environment (production + staging), with multi-locale handling. Rich text and images convert and upload correctly.
Managed AI prompt library
Prompts are records you edit by slug, not strings hard-coded in source. The platform calls them by name. SEO prompts auto-inject the resolved canonical URL so the model cannot hallucinate it.
AI canvas (image generation)
Chat-style, brand-aware, two-stage. A prompt model rewrites your casual request using your brand colors and content context; an image model generates from the rewritten prompt. Output lands in your asset library.
Per-brand email repository
Draft, version, preview, send-as-test, link each email to the analytics events that should trigger it. A spec-and-approval workspace, not a campaign send tool.
Analytics event registry
Named-event catalogue tied to product-development controllers and to emails. The event-storming layer for what your product emits.
Artifacts
Rich-text docs, annotations, tasks, release notes that attach to any other entity. Same status set as everything else.
Opinionated status set
Ten statuses, fixed order, per-content-type display aliases. The same status reads as "Published" on a blog post and "Hired" on a vacancy.
Encrypted per-brand secret vault
Your provider keys (AI, social, CMS, storage) are encrypted at rest, scoped per brand, resolved at runtime. The platform never holds your keys in plain text and never returns them to the browser.
What's rough today
These work, but they have visible polish gaps. We're not hiding them.
News manager (4-stage pipeline)
Scout RSS sources, extract article bodies, AI-evaluate relevance, AI-draft. End-to-end works. The Generate step today is wired for one specific niche; making it locale-and-topic-generic is the polish step. Coming.
Cron + automation foundation
The scheduler runs and per-run telemetry is captured. The "auto-publish when status is ready and the publish date is due" loop is substrate-only — the wiring step (notification → confirmation → push) is not done yet. Coming.
External webhook workflow bridge
Exists in code, predates several of m18t's native features. Its current usefulness is being re-evaluated. We will either polish it into a real advanced-automation surface or retire it; either way, an honest answer is coming.
Voice across the product
Most of the UI uses opinionated, current vocabulary. A few corners still leak older phrasing from earlier product iterations. Rolling cleanup.
What's coming
Committed, with honest dates where we have them. Order is roughly by current priority.
Team features
Q3 2026Multi-user-per-tenant with assigned-to fields, ownership, and granular permissions. Multi-user-per-tenant is near-complete; ownership and permissions land in the next iteration. Unlocks the audience page for cross-functional team leads.
More social platforms beyond FB + IG
TBDTikTok, X, LinkedIn, Threads. Today they route through external webhook automation if configured at all; native publishing is real engineering work and the priority order will be set by where beta users actually publish.
More CMS vendors beyond Strapi
On requestWordPress, Sanity, Contentful, Payload as candidates. The adapter pattern exists, but today's CMS push assumes a specific schema (matching SEO component, multi-locale enabled on the collection). Onboarding a new CMS vendor means real adapter work and probably a config UI to map fields. Best path: if you are on a specific CMS and want m18t to support it natively, let us know and we will prioritize.
Scheduled auto-publish loop
TBDCron + content status `testing` + scheduled date due → publish without a click, with a pre-publish notification and a one-tap confirmation surface.
Shared starter prompt library
TBDFork-and-adjust starter prompts so brands do not have to build their AI prompt library from zero.
News-Generate genericized
TBDMaking the news drafting step work for any niche and any locale, not just the one it was first built for.
Onboarding & help articles
RollingHow-to coverage for setting up your own OpenAI / Gemini / Meta / Strapi keys end-to-end, plus deeper teach-the-concept-then-the-steps articles for each major surface. Friction reduction.
What we're choosing not to build
Not "haven't gotten to yet" — actively not building. Honest scope.
A CRM
Tried, dropped. m18t is not Pipedrive / HubSpot / Close. If you need one, integrate it separately and connect it to m18t's analytics event registry.
E-commerce, inventory, or orders
Was an experiment for one specific business; dropped. m18t is not Shopify.
Bulk or drip email sending
The email surface specs and approves the emails your product sends — it does not blast newsletters. Use Mailchimp / Resend / Postmark / Brevo for the actual send.
Hosted AI tokens
Strictly bring-your-own-key. We do not resell tokens or bundle credits. You pay providers directly at provider rates.
Hosting the website that serves your content
m18t pushes to your CMS. Your CMS or your own app (Nuxt / Next / Astro / whatever) serves the actual pages.
A real-time multiplayer surface
Live cursors, presence indicators, simultaneous editing. Not on the immediate horizon. Whiteboards are persistent and single-author-at-a-time.
Enterprise-grade certifications
SOC 2 audits, SSO, advanced audit logs, granular permission lattices. Not in beta. Some of these may arrive eventually; none are committed.
How updates land
When something ships, moves from rough to solid, or gets cut, this page changes the same week. The dated changelog lives at the blog under build-in-public posts. Major changes also go out via contact follow-ups if you've signed up.
If you spot something on this page that contradicts what the product actually does, that's a bug. Tell us and we'll fix the page or the product.
Frequently Asked Questions
Beta-honest sound like the right trade?
You bring your own keys, we route everything, the founder fixes bugs the same week.