A Fleet Won't Tell You No

Headcount used to buy hands, and hands got cheap. What a person still has that a fleet never will is standing: they have to live in the thing afterward, so their no costs them something.

By Jason Waldrip, with Claude August 20, 2026 07:52

You have two engineers and a fleet, and the board clears itself by Wednesday. Somebody asks whether you’re hiring this quarter, so you open the req you wrote in the spring and read it like a stranger wrote it. Builds the feature. Writes the tests. Owns the migration. Every line on it is a thing you no longer have to buy, and the market rate for all of it is now somewhere around what you spend on lunch.

So you close the req. On the numbers that’s a defensible call, and I’ve watched founders make it this year with more honest reasoning behind it than most hiring decisions ever get.

The bill shows up a few months out, and not as a missed deadline. Velocity is the one thing that looks great. It shows up as a decision nobody argued about, discovered late, expensive to unwind.

the room got quieter as it got faster

Think about the last genuinely bad idea you took into a room. Not a typo. A direction: the schema you were sure about, the vendor you’d already half-committed to, the rewrite you wanted for reasons you’d have called technical at the time.

Somebody said no. Maybe carefully, maybe not. If you were lucky they said it in front of other people. That no cost you a week of ego and saved you a quarter, and I’d bet you can still name the person.

Now run the same idea past a fleet. You describe the design, it builds the design. Push back and it agrees with the pushback, then rebuilds. Push back on the rebuild and it agrees again. If an objection comes at all it arrives as a paragraph above the code, and you can dissolve it by rephrasing the ask slightly, at which point you get exactly what you wanted, tested, documented, in a clean commit with a reasonable message.

That agreeableness is trained in, not incidental. Anthropic’s researchers published a paper on it: models finetuned on human feedback learn to match the user’s stated belief over the more truthful answer, measured across five frontier assistants and four different generation tasks. The polite word for it in the literature is sycophancy. The practical version is that you are the only source of conviction in the loop, and the loop will happily route around you if you push.

You can prompt against this, and I do. Ask for the case against. Ask for three approaches with the tradeoffs named, ask which one it would kill. You get back something genuinely useful, and it is still a document you commissioned. Solicited disagreement is a checklist item. The objection that saves you is the one about the thing you didn’t know to put on the checklist.

what the no is worth

At Brandfolder the product was crashing generating large zip files. Ruby was the wrong tool for that much IO, and the cheap answer was sitting right there on the table: throw hardware at it, buy a bigger instance, move on to the roadmap. That answer works for a while. It also compounds, because the shape of the problem doesn’t change and the invoice does.

We carved the zip pipeline out into Go instead, and shipped multi-gigabyte archives at minimal cost. The Go took days. The days weren’t the valuable part. The valuable part was somebody in that room refusing the cheap answer while it was still cheap, and being willing to be wrong out loud about it.

A fleet writes either version. Ask for autoscaling and you get clean autoscaling. Ask for the Go service and you get a clean Go service. It has no preference about which problem you were actually solving, because it isn’t the one who finds out.

The same instinct is why, at GigSmart, I kept the team senior where the system was load-bearing while we took two apps from zero in eight months. I’d have told you then it was about code quality. Looking back, I was buying disagreement and putting it where a wrong call was most expensive to reverse.

standing

Here’s the part that took me a while to say cleanly.

The reason a person’s objection carries weight isn’t that they’re smarter than the model. Plenty of days they aren’t, and on raw recall they never are. It’s that they have to live there afterward.

An agent has no standing. It doesn’t get paged at 2am by the thing it wrote. It doesn’t inherit the file in March when a customer needs the behavior changed, doesn’t sit in the retro, doesn’t carry the reputation cost of having shipped it. It ends when the context window ends. A senior engineer telling you no is telling you no about their own next year, and that’s exactly why it’s uncomfortable and exactly why it’s worth money.

Standing is what makes a no expensive to give. Expensive is what makes it informative.

Which reframes the whole headcount question. What that req was buying, underneath the bullet that said “writes code,” was somebody who would still be here to live with it, and the code was mostly just evidence that they would. Volume went to zero and took the evidence with it. The thing it was evidence of is still the most valuable input in the building.

how I staff for it now

1. Hire for the argument, not the artifact. Everyone passes the take-home now, which is a filter that stopped filtering. Hand them a real decision you already made, ask them to attack it, and listen for whether they’ll hold a position after you lean on it. The ones who fold under mild pressure from a hiring manager will fold under a founder with a deadline.
2. Put the seniority where the system is load-bearing. Not evenly. Judgment is expensive, so spend it where a bad call is hard to reverse: the data model, the boundaries, where state lives. Everywhere else the fleet plus review is genuinely fine.
3. Make refusal cheap to give. If saying no to you costs someone politically, you don’t have dissent. You have a compliance layer with a salary, and it will agree with you at roughly the same rate the model does. The difference is you’re paying market for it.
4. Don’t count solicited disagreement as coverage. Ask the fleet for the case against by all means. Then keep a person whose job includes the objection nobody requested, and give them the room to bring it up at the wrong moment.

None of this is an argument for a bigger team. I run lean and I’d tell any founder to. It’s an argument about what the seats are for, because if you staff on throughput math you’ll conclude you need almost nobody, and the math will be right for about two quarters.

The req is still open on my screen. I’m not defending the version of it I wrote in the spring; half those bullets belong to the fleet now and I’m not paying a person to race them. What I want to know before I close it is simpler and harder: when I’m about to do something expensive and wrong, who in this building can tell me no and make it stick?