MENO / About
Grow without
fragmenting.
Meno is building the shared company environment for teams that want their work, context, and AI teammates to grow together.
Growing a company should not make it harder to run.
WHY MENO
A company should not be scattered across tools.
Strategy lives in one place, customer feedback in another, work in another, and the reason behind a decision can disappear between them. The founder becomes the bridge between it all.
Meno is being built as the new home. It brings the company’s work and context together so people and AI teammates can understand the business and move it forward.
A project should have one living record.
Version 1.0 is our foundation: a shared home for the team’s current work. Outcomes, discussions, designs, files, and tasks live next to one another—so the reason behind a decision never gets separated from the decision itself.
Collaboration should feel present, even when the team is not in the same room.
In 1.1, Meno begins to make collaboration visible. You can see who is shaping a design, reviewing a decision, building a file, or moving an outcome forward. The workspace feels alive because the work is actually happening there.
AI teammates are part of the team—not a black box.
They work from the same project record, show what they are doing, and return their work to people who can judge it.That means agents do not begin every task cold, and people do not have to guess what an agent changed or why. Everyone starts from the same shared context.
The project should remember what the team learns.
Meno 1.2 turns the shared workspace into a living company brain. The vision, users, requirements, decisions, design direction, and project history become an evolving understanding of what the team is building—not a pile of documents that goes stale.
The handoff from design to build should not lose its meaning.
1.3 brings collaborative design and build closer together. A team can shape a product direction, discuss it where it lives, turn it into a buildable starting point, and keep the decisions attached all the way through implementation.
Design is not a static file. Code is not a black box.
Both are part of one project conversation that the whole team can understand and move forward.The goal is not to recreate every specialist tool feature-for-feature. It is to make the most important transitions in product work feel continuous.
Autonomy is useful only when the team can see and shape it.
By 1.4, teammates can give an agent a role, a goal, the relevant project context, and clear boundaries. The workspace shows what it is investigating, building, or waiting on—then makes the result understandable before anything important moves forward.
One place for a company to understand, make, and improve.
Meno 1.5 connects the full loop: the company’s shared memory, live collaboration, product direction, design, technical activity, and agent work. It is not an attempt to mash every existing tool into one screen. It is the operating system that makes the work between them coherent.
The system gets more valuable as the company grows.
It holds the reasoning behind the work, makes progress legible, and gives people and agents a shared place to begin the next useful thing.CHAPTER II
A team should be able to create together in real time.
The product does not stop at a better project record. Meno is designed to make the team’s work feel live and shared: who is present, what is changing, where a decision is being made, and what needs a response.
That feeling matters even more when a team is distributed. Great collaboration is not a stream of notifications. It is the confidence that everyone can find the current state of the work and participate without asking someone else to translate it.
People and agents should meet inside the work—not in a separate chat window.
The project gives both sides the context to make a useful contribution, and the team keeps the judgment.See the team in the work, not just in a status update.
Meno 2.1 makes presence useful. A teammate can see who is shaping a flow, reviewing a proposal, building a file, or waiting for a decision—without a noisy feed trying to narrate every movement.
The right conversation should be easy to find when it matters.
2.2 gives every important outcome, design, change, and review a home for its discussion. The record stays attached to the object it changes, so a new teammate can understand the decision without hunting through a channel archive.
A decision is more useful when its reasoning travels with it.
Chat becomes part of the product record—clear enough to return to, specific enough to act on.A design review should bring the product team closer to the decision.
In 2.3, the design space becomes a live shared surface. People can shape a flow together, see one another’s presence, capture feedback in place, and connect the chosen direction to the outcome it is meant to serve.
Building software should not disappear behind a technical wall.
2.4 brings the build process into the shared project. Code, files, changes, and technical activity remain connected to product intent, while an explainer layer helps nontechnical teammates understand what changed, why it matters, and what needs a decision.
Technical depth stays intact. The understanding becomes shared.
Engineers keep their craft; everyone else gains a clear way to participate in the work around it.The project can coordinate itself without becoming project-management theater.
By 2.5, Meno connects tasks, calendars, notifications, and daily intelligence to the work already in motion. It surfaces the next useful thing, the decisions that need attention, and the risks worth seeing—without creating another system the team has to keep up to date.
See how a project stays coordinated →CHAPTER III
Build a company that gets wiser as it grows.
Tools usually preserve artifacts and lose the reasoning around them. Meno is built around the opposite idea: the project’s history, decisions, and outcomes should compound into a usable memory for the people and agents who join next.
That is how Meno can eventually become more than a workspace. It becomes the place where a company understands itself well enough to move quickly without becoming careless.
Our long view is simple: a person should be able to enter a project and understand what the company is building, what changed, what matters now, and what an AI teammate is doing. An agent should arrive with the same clarity, scope, and guardrails.
Every completed project should make the next one easier to understand.
Meno 3.1 turns project history into an asset rather than an archive. The system carries forward decisions, outcomes, tradeoffs, and learned patterns so the team can begin the next chapter with more clarity than the last.
An agent should understand its role before it starts working.
3.2 gives agents durable roles: researcher, product manager, designer, engineer, QA reviewer, or operations partner. Each role begins from the company brain, receives a clear goal and scope, and contributes to the same project record as the rest of the team.
Useful agency begins with a clear remit.
Agents gain enough context to help without gaining vague authority to act beyond the team’s intent.The more consequential the work, the clearer the review path should be.
In 3.3, proposals arrive with their reasoning, affected work, and tradeoffs. The team can approve, reject, or request changes in the same place that holds the context. Permissions and budgets become visible boundaries, not hidden settings.
The technical system should be part of the company’s shared understanding.
3.4 deepens the build environment: a repository experience where changes, pull requests, tests, and deployments stay connected to the work that motivated them. Agents can operate safely, and the entire team can follow what is happening without needing to become an engineer.
Explore the build space →A company can finally work from one shared, living picture of itself.
Meno 3.5 is the full expression of the idea: shared memory, live collaboration, product direction, design, build activity, review, and AI teammates working as one connected system. The surface stays calm; the underlying understanding grows deeper over time.
One place to make the next thing real.
Not by replacing every tool on day one, but by making the work between people, systems, and agents finally hold together.WHAT COMES NEXT
Build the place your team grows into.
We are starting with the moments where a small team loses the thread. The rest of Meno grows from there—one useful branch at a time.
Join early access →