Ten surfaces.
One workspace.
Each surface below is its own deep workspace — content, planning, brand assets, automation. They share a status set, a brand-switcher, and an encrypted secret vault. Use the ones that match your week; ignore the ones that don't.
Product Development
SolidA relational workspace for the actual entities your product consists of — solutions, features, models, controllers, lifecycles, events. Status rolls up; visualize as a graph; attach artifacts to any node. The shared spec workspace GitHub Projects can't be.
Whiteboards
SolidPersistent infinite boards where you drop your real m18t entities (solutions, features, content, events) as live nodes — not just labelled stickies. Use for event storming, process flows, mindmaps, brainstorming.
Content workspace
SolidOne table for blog posts, news posts, web pages, help articles, social posts, video posts — plus user-defined custom types per brand. One rich-text editor. One status workflow. One SEO model. No more copy-pasting across five tools.
Canvas — AI image gen
SolidChat-style brand-aware image generation. 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. Bring your own AI key.
Publish anywhere
SolidNative Facebook + Instagram with carousels, link-back URLs, container polling. Strapi push per brand per environment with multi-locale handling. Per-channel publish state, engagement counters, sync log.
Prompt library
SolidYour AI prompts are first-class records you edit by slug, not strings hard-coded in source. SEO prompts auto-inject the resolved canonical URL so the model literally cannot hallucinate it. Multi-provider, BYOK.
News manager
PolishingScout RSS sources, extract article bodies, AI-evaluate relevance, AI-draft. Four-stage pipeline in-app. Dedup by URL hash. Drafts land in the content table. For niche content creators, small news teams, or competitive-intel monitoring.
Email repository
SolidPer-brand spec and approval workspace for transactional emails. Draft, version, preview, send-as-test. Link each email to the analytics events that should trigger it. NOT a campaign send tool — that's a different category of product.
Analytics events
SolidThe named-event registry tied to PD controllers and to emails. Name your analytics events here before instrumenting them in PostHog or GA. The event-storming layer.
Multi-brand workspace
SolidEverything described above, scoped to a brand. Switching brands re-shards the whole workspace. Encrypted per-brand secret vault. Per-brand integrations across production and staging environments. Same architecture for one brand or thirty.
The point isn't the surfaces. The point is the integration.
Each of the ten surfaces above is real software, used daily. But the wedge — the reason m18t exists at all — is what happens when you connect them. The product spec in PD is structurally adjacent to the blog post in Content. The blog post auto-generates its SEO from the brand-and-type defaults in SEO Indices. The analytics event the blog post tracks is named in the Events registry. The lifecycle email that event triggers is drafted in the Email repository. The cover image was generated in Canvas using the brand record's colors.
That's m18t. Not a bundle of features; a workspace where features know about each other.
Pick the one that feels like your week.
Or just sign up and let your daily work show you which surfaces matter to you.