Hey YC community! What does a normal workflow at a startup look like?

Probably like this:

> One founder talks to customers

> Another founder builds

> A customer asks for something. The first founder explains it to the second. The second founder explains it to Claude

> Two weeks any one of the founders asks one of the following questions:

• Why are we building it this way?
• What happened here?
• What did we promise ACME we’d do?
• How far along are we on X?

> Then you scream on the inside because you have to figure out what happened…

Before agents, the person who did one part of the work usually held a mental map. They could share the context with other people. Increasingly, they can’t.

Small teams can run far more work in parallel than ever before thanks to AI, but someone now has to connect all that context manually. The reasoning behind one product change might now be scattered across a customer call, two emails, a Slack thread, and four Claude conversations.

Soheil Sadabadi and I have been obsessed with solving these problems for a long, long time now.

Praxos is a team messaging app. 

It has channels, groups and threads like you’d expect. However, places where work happens—Github, harnesses, email, calls—get linked and converted into a living record of your company. This means everyone is always up to date with the latest developments.

Agents can join conversations and inherit the same context humans do.

Here are examples we’ve seen in production:

1. You talk to a customer. Later, when an engineer or coding agent works on the feature, your conversation and the customer’s information are already in context.
2. A new engineer picks up an existing project. They have immediate access to info about who worked on what part of the code base, the deltas across changes, and a granular view of their conversations with coding agents. There’s no need to interrogate the CTO.
3. Three weeks later, someone asks why the engineer made a certain decision about the feature. Praxos fetches the engineer’s convos, the original feature request and call logs between the founder and the engineer. Then it contextualizes the work.

We’re early, but the core product already works and is in use. You get messaging, search, memory and connectors. You can bring your own agents, use ours, or both.

A desktop app is going live next week. We’re building native calls and mobile apps, so that all the communications that go into a company’s history can happen on Praxos.

Our ask: if you’re a 2 to 10 person team where one person is spending all day with customers while the rest of the team is shipping with Claude/Codex, we’d love to personally onboard you.

Especially if you’ve already caught yourself asking “what did the customer want?” or “what’s going on with X?” last week.

The first 10 teams get

Praxos for free for 6 months ;)

Email me at lucas@praxos.ai.