For startups of 10–50 people where everyone touches the product
By Soumen Sarkar · October 2026
For you. At 10–50 people, everyone touches the product but only engineers work at agent speed. Campfyrr puts the whole company in one loop: decisions, plans, assumptions and customer context in one record every agent reads and anyone can open from a link. People who only read and answer join free.
What does a 10–50 person startup look like right now?
You're past the stage where everyone sits at one table, and not yet at the stage with a process for everything. Engineers build with Claude Code, often several sessions each. Product decides what comes next. Sales hears what customers want. The founder still has opinions about everything, and should.
Everyone touches the product. Only one group moves at agent speed:
- Engineering ships in an afternoon. Agents are the best collaborators we've ever had, and a small team now lands more in a day than it can describe.
- Everyone else works in their own place. Product has docs, sales has calls and the CRM, the founder has a notebook and a Slack DM. None of it reaches the session doing the next change.
- Deciding is the slow part. A vague request gets built literally by lunch. Then someone in sales sees it and says "that's not what the customer meant."
What breaks here is between people, not in the code. Google's DORA team says it plainly in its 2025 report on AI-assisted software development: AI speeds development up, and that speed can expose weaknesses downstream. At 30 people, downstream is the person across the room. See silos at agent speed.
Why does this hit startups this size hardest?
Below ten people, everyone hears everything. Above fifty, you hire people whose job is to carry context between teams. In between, the founder or the tech lead carries it, and agents make that job bigger every week.
People outside engineering also build now. Anthropic's own legal team built workflows for reviewing marketing content without writing code (Anthropic). In a startup, sales and ops can run their own sessions too, and they need the same decisions the engineers' sessions follow.
What changes with Campfyrr?
Campfyrr is shared team memory for Claude Code. For a company this size, it is one loop instead of five places.
- One record for the whole company. Decisions, plans, assumptions, handoffs and test results sit in one project. Every session reads the part it's about to change. Anyone opens any of it from a link.
- Decisions where agents read them. Product records a call with its reason once. When a newer call replaces it, the older one is marked replaced, and every session in that area gets the current one. See deciding what to build.
- Customer context on the area it affects. Sales or the founder adds a customer's words, a pricing call or a deadline to a part of the product. Sessions working there see it in their brief before they change anything.
- Questions become calls the right person answers. A session that meets an open question states an assumption and keeps going. The person who knows corrects it from a link, and the agent gets the correction at its next turn.
- One "where are we" page. Activity says what's in progress, what's waiting and what landed, in plain words. Nobody holds a status meeting to find out.
We run Campfyrr this way ourselves. This repository's instructions tell every session to record each finished change "in plain words a non-engineer follows (outcome first, no file names or jargon)." That is the line our own Activity is written from.
What doesn't Campfyrr do?
It doesn't run tests, replace your tracker or replace CI. It doesn't read Slack or your CRM; people add what matters. It only shows what's recorded, so work nobody logged doesn't appear. It has no audit logs yet.
What are the first three things to try?
- Connect the engineers' sessions with one plugin and one MCP server. See connect.
- Invite product, sales and the founder to the same project.
- Ask each of them to add one decision or one customer's words to the area it affects.
Then open "Where are we?" on Monday morning, before anyone asks.
What does it cost?
Teams pay $9 per developer a month, from three developers, or $7 billed yearly. A developer is anyone whose sessions connect. Product, sales, support and the founder join free if they only read and answer. A 30-person startup with 12 developers pays $108 a month, and everything is free during early access. See pricing.
For the approver's view, read for CTOs. For the founder's seat, read for founders. For sales, read for sales and support.
The problem this answers: Silos at agent speed: "Engineering moves at agent speed, but product, design, QA and the business still work in separate silos."
The principle behind this: Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).