// FOUNDER LETTER · APRIL 17 2026

Why we're
building this.

// MAYA REYES · CO-FOUNDER, CEO · ~9 MIN READ · LAST UPDATED 8 DAYS AGO

The most expensive moment in any company is the one where you re-decide a thing you already decided. Maybe four months earlier. Maybe with the same people in the same room. The decision was made, the trade-offs were weighed, the call was good — and then the artifact got buried in a Slack thread, and now four engineers are spending a week re-litigating it. Multiply by a thousand decisions, by a hundred companies, by every quarter. That cost is not theoretical.

I joined a 60-person company in 2022 as the third engineering manager. Within six weeks I'd watched two senior people give the same architectural recommendation to my CTO that another engineer had given nineteen months earlier and that we'd already implemented and rolled back. Nobody had any idea it had happened before. The doc was buried in Notion. The Slack discussion was archived. The two engineers who built and rolled back the original system had both left.

It wasn't a process problem. They had wikis. They had retros. They had OKR docs. The problem was that the human capacity to find and synthesize prior reasoning across thousands of disconnected artifacts is essentially zero. You can search Slack for keywords. You cannot search Slack for "decisions we made in Q1 about X that we then revised in Q2." That requires reading.

// SECTION 02What changed

Three things changed in 2024-2025 that made this problem suddenly tractable: long-context retrieval that doesn't hallucinate, multi-source ingestion that actually works (Slack, Notion, GitHub, calendars all in one place), and reasoning models that can chase down a thread of evidence rather than just answer the question in front of them.

This was not true in 2022. We tried. The shortcut was to build "AI search" on top of what you already had. The result was a chatbot that confidently invented context. Nobody wanted that, and the trust collapsed within a quarter.

// We are not building an AI assistant. We are building the team's institutional memory — the thing that, in well-run companies, lives in the heads of two or three senior people who never leave.

Here is the real test. You join a new company. On day one, you can ask Your Business: what's the architecture of the auth system, who designed it, what alternatives were considered, what got rejected, and why? — and get an answer with citations to the actual decision documents, the actual Slack discussion, and the actual PR review where the call was made.

You should not need to find Theo on his second cup of coffee and beg him to tell you the story. Theo is busy. Theo is also going to leave eventually. The company should not lose its memory when Theo leaves.

// SECTION 03What we won't do

We will never train on your data. We will never co-mingle context across customers. Your Your Business is yours; we don't even see what's in it. The architecture is Bring-Your-Own-VPC for enterprise and SOC 2 Type II from day one.

We will never replace decisions with answers. Your Business does not tell you what to do. Your Business tells you what your team has already discussed, what they decided, and what they rejected. The decision is still yours. We just want to make sure you're making it with the full picture.

And we will never go horizontal. We are deeply committed to one job — institutional memory for technical teams between 25 and 500 people. If your team is two people, you don't need us. If your team is 5,000 people, you need a different shape of tool. We are building one thing for one shape of company, and we are going to be very good at it.

// SECTION 04Where we are

Today, April 17 2026, we are eight engineers in a building in Mission Bay. We have 32 design partners running the alpha across teams ranging from a 30-person Series A to a 240-person Series C. Two are public — Linear and Cresta — the rest are under NDA until launch.

We have a tier-one investor (Sequoia, seed) and a small handful of unusually thoughtful angels. We are not raising for some time. The product is what we focus on.

We open the public beta on May 14, 2026. The first thousand people in line get week-one access. The next nine thousand get rolled in over the following six weeks. After that, we open up to anyone who wants in.

If reading this made you nod three times, you are exactly the person we want to ship to first. The waitlist is on the home page. We will see you in May.

MR
Maya Reyes// CO-FOUNDER, CEO · YOUR BUSINESS
// previously: Stripe, two early-stage startups, Stanford '17

Want in first?

// 12,847 in line · launching May 14 · refer 3 friends to jump to top 1,000

▶ Join the waitlist