I built m18t so I could stop juggling twelve tabs.
Then a few friends asked to use it. Then they asked their friends. Now it's a beta product, and you're on its about page.
What m18t actually does
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 CMS and social, generate brand-aware imagery, register the analytics events and emails it emits, and keep multiple brands separate without context-switching between twelve tabs.
That's a long sentence on purpose. m18t doesn't fit one bucket. The point is the integration between the buckets — the brand-switcher in the sidebar is the same one whether you're editing a blog post or describing a controller method, and that's the wedge.
If you want the structured list of what's in the platform today and what isn't, see the roadmap.
Why it exists
For about a decade, working across startups as a product person who could also write the marketing and ship some of the code, I kept running into the same failure mode at every company I touched.
The marketing team pushed a story about features the engineering team was deprecating. The new content hire didn't know the scope of the product they were writing about. Sales promised capabilities the roadmap dropped last sprint. The founder was the only nervous system holding the picture together — which meant the founder was also the bottleneck.
We called it many things over the years. Most of the time we just called it "another Monday." The real name for it is silo drift, and no amount of process documentation, all-hands meetings, or Slack alignment threads makes it go away. The tools cause it. Marketing's tool isn't engineering's tool isn't sales's tool, and the only thing keeping them in sync is the human flipping between tabs.
I tried fixing this with Notion. Then with Coda. Then with a Notion-and-Coda-together stack glued by Zapier. Then I wrote scripts. Then I built mini-tools per business. Eventually I realized I was rebuilding the same underlying workspace every time, just differently shaped per business, and I was tired.
m18t is the rebuild that doesn't need to happen again.
How it got here
I started building m18t for myself in late 2024. The first version was opinionated to a fault — it only spoke vet-industry vocabulary, because the business I was running at the time was a vet startup. It was fast, it was useful, and it was completely useless to anyone else.
Around early 2026, after using it daily for months, I started ripping out the vet-specific assumptions and generalizing. The status set, the artifact types, the SEO conventions, the publishing pipeline — they're all there because I used them in anger for one business first and then realized the shape of each was generic even if the values were specific.
Most features in m18t exist because I was tired of doing something a particular way somewhere else:
- The product development workspace exists because GitHub Projects can only track issues, and I needed to track entities — solutions, features, models, the things the product actually consists of.
- The whiteboard exists because I was paying for Figma Jam and noticed it was a separate silo from everything else I worked on.
- The canvas image generator exists because Canva and Photoshop felt like overkill for blog covers I generated weekly.
- The news pipeline exists because I was reading 30 RSS sources by hand to publish two articles a week.
- The email repository exists because I kept drafting transactional emails in Google Docs and then re-typing them into whatever provider was sending them.
- The events registry exists because every team I ever worked with had a Notion page named some variant of "analytics events we should be tracking" that nobody updated.
m18t is, in short, what I made because I got tired of working around the absence of m18t.
What I believe about software like this
Every decision in m18t passes through these seven. If you disagree strongly with several of them, m18t is probably the wrong tool for you — and that's a healthier signal than discovering it after you've signed up.
- 1
Silos kill products.
One workspace beats five connected by integrations. Marketing, product, content, and lifecycle all live in the same brand-switcher because the alternative is a founder who is the only person who knows what is shipping this week.
- 2
Multi-brand is the unit, not the upgrade.
Same architecture for one brand or thirty. A solo founder with three side projects and an agency with thirty client brands run the same m18t — different scale, no tier-locked features.
- 3
AI is your account, not ours.
Bring your own OpenAI / Gemini / Anthropic key. The platform routes calls; you pay providers directly at provider rates. No markup, no bundled credits, no incentive to push you toward generating more.
- 4
Opinions ship. Configuration drowns.
Ten statuses, in a fixed order, refined over a decade of running real teams. A sensible default set you learn once, with surgical override where it actually matters. You don't get to add a forty-seventh status. You also don't need to.
- 5
The product spec lives where the marketing happens.
The feature page in PD is structurally adjacent to the blog post that announces it and the lifecycle email a controller fires. Silo drift becomes structurally impossible when the silos share a workspace.
- 6
Dogfood, then generalize.
Every feature in m18t was used by the founder in anger before it was generalized for others. A feature that's clearly useful and visibly rough beats a feature that's beautifully consistent and quietly useless.
- 7
Beta is not an apology.
The roadmap tells you what works, what's rough, what's coming, and what we're choosing not to build. No "enterprise-ready" theatre. If you're allergic to beta, m18t isn't for you yet — and we'd rather you know now than after a contract.
The full manifesto is the founder's worldview, made explicit so it survives the founder leaving the room. It will be published as its own page when the time is right.
Where I am with all this right now
m18t is in beta. It is live. I use it every day to run my own work and to develop m18t itself. A handful of friends use it for theirs. The marketing pages are getting written now because — until they existed — I had no honest way to invite a stranger to try the platform.
I'm a solo founder. No team yet. I'm running two other businesses in parallel and looking for seed funding. Support during beta comes from me, directly, on email or a quick call. If you find a bug, I'll probably fix it the same week.
Free during beta
No paid plans yet. You bring your own provider keys; you pay providers directly at provider rates. m18t takes no markup.
Pricing being worked out
Likely meter on brands per account — solo with three side projects pays less than agency with thirty clients, same product underneath. Not committed.
Some things are rough
The roadmap lists what works solidly, what's polishing, what's coming, and what we're choosing not to do.
If beta-honest is the right trade for you, start here. If you need enterprise-ready, m18t isn't there yet — and we'd both rather you know now.
About me
I'm Khalid Zamer. A product and engineering generalist who's spent a decade across startups in the MENA region — building things, running marketing for things, shipping code for things, and occasionally founding things. m18t is the tool I always wanted to use, now made available for other people who probably wanted the same.
If you want to talk — about m18t, about working together, about anything you'd say to another founder over coffee — email [email protected] or use the contact form.
Frequently Asked Questions
Want to give m18t a try?
Free during beta. You bring your own keys. Support comes from a real person.