About
One workspace, because the alternative kept failing.
m18t is an operations workspace for building a product and running the brand around it. The planning, the content, the graphics, the channels, the analytics events and the mail your product sends all live in one place, with every brand kept apart from the others.
The problem
Silo drift, and why process never fixes it.
Marketing writes about a feature the build already dropped. A new writer describes a product they have never been shown. Someone promises a capability the plan let go of last month. One person ends up holding the whole picture in their head, which makes that person the only reliable source and also the bottleneck.
Nothing about that is a discipline failure, and no amount of meetings or written process removes it. The tools cause it. The planning tool is not the writing tool is not the publishing tool, and the only thing keeping them in agreement is a person moving between tabs and remembering. Put the plan, the words and the record of what went out in one workspace and the drift has nowhere to start.
How it gets built
Nothing here was offered before it was used.
Every part of m18t ran real work before it was generalised for anyone else, which is why the pieces are shaped the way they are rather than the way a feature list would suggest.
- The product workspace exists because issue trackers track issues, and the thing that actually needed tracking was the product itself: its solutions, features, models and the fields underneath them.
- The whiteboards exist because a board full of labelled rectangles is a drawing of your work, not your work. These ones hold the real records.
- The graphics templates exist because a full design suite is a heavy way to make the weekly cover image, and the brand rules were already written down.
- The news pipeline exists because reading thirty sources by hand to publish twice a week is a job, and most of it is filtering.
- The email repository exists because the mail a product sends kept getting drafted in one place, approved in another and retyped into a third.
- The events registry exists because every team has a page called something like "events we should be tracking" that nobody has updated since it was made.
What we believe
The seven that decide everything else.
When a question is genuinely open, it gets settled against these. If you disagree with several of them, this is probably the wrong workspace for you, and that is better to know now.
- 1
Silos kill products.
One workspace beats five joined by integrations. The plan, the words about it and the record of what went out belong to the same switcher.
- 2
Multi brand is the unit, not the upgrade.
One brand and thirty run the same architecture. Nothing worth having is locked behind a tier for the people running one.
- 3
The AI account is yours.
You bring the key and pay your provider directly, so nobody here earns anything by nudging you to generate more.
- 4
Opinions ship. Configuration drowns.
A sensible set you learn once, in a fixed order, with override where it earns its place. You do not get a forty-seventh status. You also do not need one.
- 5
The plan lives where the writing happens.
A feature sits next to the post that announces it and the mail it triggers, so drift is structurally awkward rather than merely discouraged.
- 6
Used before it is offered.
Every part of this ran real work first. Clearly useful and visibly rough beats beautifully consistent and quietly useless.
- 7
Say what is thin.
The roadmap names what works, what is rough and what we have decided not to build. Nothing is served by finding that out later.
Who is behind it
The people who build it are the people who answer you.
There is no support tier between you and the workspace. A bug you report is read by someone who can fix it, and usually is, in the same week. That is a deliberate choice about how close the people making decisions stay to the people living with them, and it is the part of working this way we would keep at any size.
m18t is led by Khalid Zamer, a product and engineering generalist who spent a decade across startups in the region building products, running the marketing around them, and shipping the code underneath. m18t is the workspace that job kept needing and never had.
Talk to us about the product, about working together, or about anything you would ask another operator. [email protected], or the contact form.
Questions
Questions people ask about m18t.
What does the name m18t mean?
It is a numeronym, the same idiom as i18n: the first letter, the count of letters between, and the last. m18t spells "minimum viable product". The workspace outgrew that scope a long time ago, but the name stuck. It is a footnote, not a positioning.
Who is m18t for?
Founders running one or more products, small product teams, marketers and content operators, and agencies running many client brands. If you have been moving between one tool for the plan, another for the writing, another for the graphics and another for the mail, that is the shape m18t replaces.
What does it cost?
Free to start. Everything that costs money per call is your own key, so you pay your provider at their rate and there is nothing here to mark up. When pricing arrives it will meter on what the workspace is worth, most likely the number of brands you run, and you will be told before anything changes.
Is m18t a CRM?
No. Contacts here are a pipeline with stages, an activity log and the people who subscribed to you. If you need a real CRM, run one alongside. m18t is good at the line from planning a product to publishing about it and recording what happened.
Does m18t host my website?
No, and it is not trying to. m18t publishes into whatever you already run, so there is nothing new to keep alive at midnight. Your site stays where it is.
Can I self-host m18t?
Not today. m18t runs as a managed service. Your data is yours and exportable, and your AI, publishing and email credentials are yours throughout, so the parts that would usually make you want to self-host are already on your side of the line.
Start free. Bring your own agent.
Give yourself a key that cannot write, let your agent look around, and widen it when you are ready.