Operations & FinanceNew Angle
Every runs 44 agents, and the thing that made them specialists was a folder
Every republished Kieran Klaassen's account of running 44 agents across its Cora email product ahead of a new follow-up next week. He spent three months building agent swarms and abandoned them. What worked was ordinary project folders carrying conventions, runbooks, postmortems and incident history, plus a Ruby daemon doing file-based dispatch on a 60-second poll. Point the same model at one folder and it is a Rails engineer; point it at another and it is an ops engineer who knows the incident history. He cites Anthropic research showing multi-agent setups beat single agents by 90% on research tasks while burning 15 times the tokens.
So what
The asset that compounds is your accumulated operating context, not your orchestration platform, which means the build-versus-buy question is smaller than vendors would like. His sequencing rule is the transferable part: build it, use it, trust it, then orchestrate it, because teams that skip to orchestration get agents duplicating finished work. Pick your single most repeated internal process, write down the conventions and the last three things that went wrong, and run it manually against an agent for two weeks before automating anything. Budget for waste, since he still prunes stalled agents by hand.
Confidence: Informed perspective — a single practitioner's account, first published in April and republished September 4, with no independent measurement of the productivity claim.
Go deeper Every · Anthropic multi-agent research
Go-to-Market
A YC founder sold six slides before writing code, and his ARR number changes depending on who tells it
The GojiberryAI founding team published a widely shared account of its first year. The mechanics are specific and worth borrowing: a six-slide deck covering problem, solution, outcome and price, $10,000 collected before any code existed, a customer defined narrowly as founders at twenty-person SaaS companies about to hire a first sales rep, and outbound restricted to people showing intent through competitor engagement, role changes, fundraising or public complaints. They report reply rates of 25% to 40% against a 1% to 2% baseline, one channel at a time, at $99 per month. The company is a YC participant selling intent detection and automated demo booking.
So what
The transferable claim is that reply rate is a targeting problem rather than a copywriting problem, and that is testable in two weeks without buying anything. Have your team define one intent trigger you can observe reliably, restrict a 200-contact sequence to people who fired it, and compare reply rate against your current list-based send. The second lesson is cheaper still: sell the deck before you build the product, because a signed $10,000 commitment is better product validation than any amount of discovery. Treat the revenue figures as marketing.
Hype check
The identical post circulates under at least three different founder accounts citing $2.5 million, $3.5 million and $4 million ARR, with other write-ups saying $1.4 million in nine months. The tactics may be sound; the growth number is not a fact.
Confidence: Watch this — self-reported founder marketing with inconsistent revenue figures across versions, though the company and its YC participation are verifiable.
Go deeper Y Combinator launch page · TLDR Founders