For founders, operators and team leads

One shared memory for your team and their agents.

Mensara gives your team its own Mind: one place for your decisions, customers and ways of working that your people and the AI agents they already use read together. You decide what each person can see and change, and their agents work within the same access.

Join the waitlist

We're bringing on a small founding group and setting up each team personally.

  1. Checks your Mind before it answers
  2. Change held, then approved
  3. The next read gets the update
Ines · Support leadClaude
Do we answer support at weekends?
Read decisions/support-hours.md
Not at weekends yet. Support runs Monday to Friday, 8am to 6pm, and weekend messages get a reply first thing Monday.
Source decisions/support-hours.md
Theo · COOChatGPT
From 1 June we're open Saturdays, 9am to 1pm. Update the policy.
Proposed a change to decisions/support-hours.md
Proposed. Policy changes wait for the owner's approval.
Kai · EngineerCursor
What hours should the help page footer show?
Read decisions/support-hours.md
Monday to Friday, 8am to 6pm, and Saturday 9am to 1pm from 1 June.
Source decisions/support-hours.md
Your Minddecisions/support-hours.md
Current Proposed Held for review Now current Waiting for a question Being read Read, and cited as the source A change is proposed Policy changes wait for the owner's approval. Approved. The next read returns the updated file.
− Weekends: closed + Saturday: 9am to 1pm Held for review Approved by Sam, owner

Your team got faster. The handoffs didn't.

Each person's agent knows only what they paste in. You can't hand AI real work until you know what it sees and changes. And connecting people, agents and knowledge is a project nobody has time for.

What it is

Your Mind is one shared memory your team and your AI agents read together.

It holds decisions, customers and commitments, pricing and policies, and how work gets done, kept as plain files your team can copy and keep. Each person's agents see only what that person is allowed to.

When something changes, the update is proposed where the work happens. You can require approval before it goes live, and the history is kept.

Your Mind

  • decisions
  • support-hours.md
  • annual-pricing.md
  • customers
  • halden-foods.md
  • policies
  • refunds.md
  • how-we-work
  • onboarding.md
decisions/support-hours.md

Support hours

Monday to Friday, 8am to 6pm. Saturday 9am to 1pm from 1 June. Weekend messages outside those hours get a reply on the next working morning.

Who can read
Everyone, and their agents
Changes
Can wait for the owner's approval
History
Approved Saturday hours, by Sam, owner. Earlier wording kept.

How you use it

Bring the agent you already use. It becomes the way in.

There's no new app for your team to learn. Connect the AI tool each person already works in, once. From then on it's set up to check your Mind before it answers, and it can propose updates when something changes.

  1. Connect your tools.

    Claude, Codex, Cursor or ChatGPT on the web, with a one-time setup and sign-in. Other compatible AI tools may connect too.

  2. Work as usual.

    Ask, draft and plan in the tool you're in. It can answer using the records that person is allowed to read.

  3. Keep it current.

    When a price, policy or commitment changes, the agent proposes the update, the right person can approve it, and the next time any agent reads it, it gets the current version.

ClaudeInes · Support lead
ChatGPTTheo · COO
CursorKai · Engineer
Your Minddecisions/support-hours.md, the same file for all three

A customer asks about weekend support

Without the Mind · Ines in Claude

A customer asks if we answer support at weekends. What do I tell them?
I don't have your support hours. If you paste your support policy, I can draft a reply.

With the Mind · Ines in Claude

A customer asks if we answer support at weekends. What do I tell them?
Read decisions/support-hours.md
Not at weekends yet. Support runs Monday to Friday, 8am to 6pm, and weekend messages get a reply first thing Monday.
Source decisions/support-hours.md
  1. Proposed

    Theo, the COO, tells his agent that support opens on Saturdays from 1 June. It proposes the change to support-hours.md.

  2. Held for review

    The change waits for the owner's approval. Until then, the file still says weekends are closed.

  3. Approved

    Sam, the owner, approves it once. The next read returns the updated file, with Saturday hours.

Today, every question routes through you.

In most teams the context lives in a few heads, so the meetings, messages and handoffs all pass through the founder, COO or team lead. When it lives in your Mind, each person's agent reads what that person is allowed to, and far less has to pass through you.

YC partner Tom Blomfield describes the same shift: the context lives in the system, and people work at the edge. YC, May 2026

Before and after

Before: every role routes through the founder or COO, with meetings, messages and handoffs queuing there. After: the same roles sit around your Mind, each reading its own allowed part, and the founder or COO is free at the edge.

What small teams report publicly.

From public YC videos; these companies are not Mensara customers:

  • AnswerThis said in May 2026 that it had passed $2M in ARR largely with two full-time employees, and that its internal agent had built more than 45 of its own tools. (video)
  • Legion Health said in February 2026 that patient numbers had grown 4x in a year while its care-operations team stayed the same size. (video)
  • YC partner Diana Hu said in April 2026 that teams she has seen cut their engineering sprint time in half and got close to 10x more done. (video)

What changes

The support hours changed without a meeting.

Theo decided to open on Saturdays. He told his agent, and it proposed the change. Sam approved it once. When Kai asked what the help page footer should show, his agent read the new hours from your Mind, with Sam's approval in the history. Pricing, policy and what was promised work the same way: one current answer for everyone who can read it, and changes that wait for the right person.

Recent activity
customers/halden-foods.mdHeldRenewal terms, proposed by Ines's agent. Waiting for the owner's approval.
decisions/support-hours.mdApprovedSaturday hours, proposed by Theo's agent. Approved by Sam, owner.
decisions/annual-pricing.mdApprovedAnnual plan wording, proposed by Mira. Approved by Sam, owner.
policies/refunds.mdRefusedKai can read policies but can't propose changes to them.

Who it's for

For the person everyone routes through.

Built first for founders, CEOs and COOs of small companies, where the context sits with one or two people. It works the same way for a solo founder running the business with agents, or a team inside a larger company that wants its own Mind with its own access rules. Your team uses AI, but each person's tool knows only what they paste in. You want AI doing real work across the team without losing track of what it sees or changes.

It isn't for teams who want AI they never have to look at. You stay in charge of what goes in and what changes.

Ines9:12
Sam, do we answer support at weekends now?
Mira10:40
What did we agree with Halden Foods on renewal?
Kai11:05
Is the old refund rule still the one we use?

From the founder

“I ran a company from my own head for years, and I know what that weighs. Mensara is what I built to put it down. I've run my own work on this system every day since January 2026. Today I run Mensara on it. I'm still one person, and I move faster than that should allow.”
Antony Evans, founder. Six years as COO of Wild Earth: zero to $50M+ lifetime revenue, profitable, acquired in 2025. Bain and Oliver Wyman, INSEAD MBA, Cambridge maths, Y Combinator (S14).

How to get started

  1. Join the waitlist.

    Tell us a little about your team. We're bringing on a small founding group and setting up each team personally.

  2. Start with one job.

    We work with you on one recurring job and check the result against your own records.

  3. Bring the team.

    Connect each person's agent, then add the next job.

Join the waitlist

We'll only use your details to contact you about Mensara. Privacy

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Mensara: one shared memory for your team and their agents. A Mind of your own.

For founders, operators and team leads

## One shared memory for your team and their agents.

Mensara gives your team its own Mind: one place for your decisions, customers and ways of working that your people and the AI agents they already use read together. You decide what each person can see and change, and their agents work within the same access.

[Join the waitlist](https://app.mensara.ai/#waitlist)

We're bringing on a small founding group and setting up each team personally.

## Your team got faster. The handoffs didn't.

Each person's agent knows only what they paste in. You can't hand AI real work until you know what it sees and changes. And connecting people, agents and knowledge is a project nobody has time for.

## What it is

Your Mind is one shared memory your team and your AI agents read together.

It holds decisions, customers and commitments, pricing and policies, and how work gets done, kept as plain files your team can copy and keep. Each person's agents see only what that person is allowed to.

When something changes, the update is proposed where the work happens. You can require approval before it goes live, and the history is kept.

## How you use it

Bring the agent you already use. It becomes the way in.

There's no new app for your team to learn. Connect the AI tool each person already works in, once. From then on it's set up to check your Mind before it answers, and it can propose updates when something changes.

1. **Connect your tools.** Claude, Codex, Cursor or ChatGPT on the web, with a one-time setup and sign-in. Other compatible AI tools may connect too.
2. **Work as usual.** Ask, draft and plan in the tool you're in. It can answer using the records that person is allowed to read.
3. **Keep it current.** When a price, policy or commitment changes, the agent proposes the update, the right person can approve it, and the next time any agent reads it, it gets the current version.

### A customer asks about weekend support

- **Without the Mind** (Ines in Claude): "I don't have your support hours. If you paste your support policy, I can draft a reply."
- **With the Mind** (Ines in Claude): the agent reads `decisions/support-hours.md` and answers, "Not at weekends yet. Support runs Monday to Friday, 8am to 6pm, and weekend messages get a reply first thing Monday." Source: `decisions/support-hours.md`.

Then the policy changes:

1. **Proposed.** Theo, the COO, tells his agent that support opens on Saturdays from 1 June. It proposes the change to `support-hours.md`.
2. **Held for review.** The change waits for the owner's approval. Until then, the file still says weekends are closed.
3. **Approved.** Sam, the owner, approves it once. The next read returns the updated file, with Saturday hours.

## Today, every question routes through you.

In most teams the context lives in a few heads, so the meetings, messages and handoffs all pass through the founder, COO or team lead. When it lives in your Mind, each person's agent reads what that person is allowed to, and far less has to pass through you.

Before: every role routes through the founder or COO, with meetings, messages and handoffs queuing there. After: the same roles sit around your Mind, each reading its own allowed part, and the founder or COO is free at the edge.

YC partner Tom Blomfield describes the same shift: the context lives in the system, and people work at the edge. [YC, May 2026](https://www.youtube.com/watch?v=X_JsIHUfUjc)

### What small teams report publicly.

From public YC videos; these companies are not Mensara customers:

- **AnswerThis** said in May 2026 that it had passed $2M in ARR largely with two full-time employees, and that its internal agent had built more than 45 of its own tools. ([video](https://www.youtube.com/watch?v=DGD9b8K42lk))
- **Legion Health** said in February 2026 that patient numbers had grown 4x in a year while its care-operations team stayed the same size. ([video](https://www.youtube.com/watch?v=rWUWfj_PqmM))
- **YC partner Diana Hu** said in April 2026 that teams she has seen cut their engineering sprint time in half and got close to 10x more done. ([video](https://www.youtube.com/watch?v=EN7frwQIbKc))

## What changes

The support hours changed without a meeting.

Theo decided to open on Saturdays. He told his agent, and it proposed the change. Sam approved it once. When Kai asked what the help page footer should show, his agent read the new hours from your Mind, with Sam's approval in the history. Pricing, policy and what was promised work the same way: one current answer for everyone who can read it, and changes that wait for the right person.

## Who it's for

For the person everyone routes through.

Built first for founders, CEOs and COOs of small companies, where the context sits with one or two people. It works the same way for a solo founder running the business with agents, or a team inside a larger company that wants its own Mind with its own access rules. Your team uses AI, but each person's tool knows only what they paste in. You want AI doing real work across the team without losing track of what it sees or changes.

It isn't for teams who want AI they never have to look at. You stay in charge of what goes in and what changes.

## From the founder

> "I ran a company from my own head for years, and I know what that weighs. Mensara is what I built to put it down. I've run my own work on this system every day since January 2026. Today I run Mensara on it. I'm still one person, and I move faster than that should allow."

**Antony Evans, founder.** Six years as COO of Wild Earth: zero to $50M+ lifetime revenue, profitable, acquired in 2025. Bain and Oliver Wyman, INSEAD MBA, Cambridge maths, Y Combinator (S14).

## How to get started

1. **Join the waitlist.** Tell us a little about your team. We're bringing on a small founding group and setting up each team personally.
2. **Start with one job.** We work with you on one recurring job and check the result against your own records.
3. **Bring the team.** Connect each person's agent, then add the next job.

**[Join the waitlist](https://app.mensara.ai/#waitlist)**

We'll only use your details to contact you about Mensara. [Privacy](https://app.mensara.ai/privacy)

---

A Mind of your own. One shared memory for your team and their agents.

[How it works](https://app.mensara.ai/how-it-works) · [Docs](https://app.mensara.ai/docs) · [About](https://app.mensara.ai/about) · [Contact](mailto:[email protected]) · [Privacy](https://app.mensara.ai/privacy) · [Terms](https://app.mensara.ai/terms)

© 2026 Xanadu Labs LLC