The Schlep Is the Only Moat Agents Can't Cross

TL;DR: In 2012 Paul Graham argued that founders unconsciously avoid ideas made of tedious work, and that this is why so few people built Stripe. Fourteen years later the avoidance costs more. Coding agents collapsed the price of the part everyone was running toward — the demo, the CRUD, the auth scaffold, the marketing site — to something close to zero. That half of your product is now copyable by anyone with a prompt and a weekend. The schlep half is not, because a schlep isn’t hard code. It’s work that requires a counterparty, an accountable human, and usually a signature: bank onboarding, a customer’s security review, dirty-data migration, the support escalation that ends in a refund. Graham’s question was “what problem do I wish someone else would solve for me?” The 2026 version is narrower: which half of my idea survives a competitor pointing an agent at it?

What Graham noticed in 2012

Schlep Blindness is a short essay from January 2012 with one idea in it. “Schlep was originally a Yiddish word but has passed into general use in the US. It means a tedious, unpleasant task.” Founders avoid ideas built out of schleps, and — this is the part that makes the essay good — they don’t know they’re doing it. “Your unconscious won’t even let you see ideas that involve painful schleps.”

His example was payments. “For over a decade, every hacker who’d ever had to process payments online knew how painful the experience was. Thousands of people must have known about this problem. And yet when they started startups, they decided to build recipe sites, or aggregators for local events.”

The Collison brothers took the schlep instead. Banks, underwriting, fraud, chargebacks, PCI scope, a different regulator in every country they expanded into. Graham’s summary line is the one worth keeping: “A company is defined by the schleps it will undertake.”

In 2012 that was a claim about opportunity cost. If you skipped the schlep, you skipped a big business and built a small one. Fine — plenty of people are happy running small ones.

The cost of skipping changed, and only in one direction

Here’s what’s different now. Take any product idea and cut it in half.

The first half is the part you can picture: the UI, the data model, the CRUD endpoints, auth, billing wiring, a landing page, onboarding email. In 2012 that half was most of the work. It was six months of two people’s lives and it was a real barrier to a competitor.

That half is now a weekend. I don’t think this is controversial anymore for anyone who has actually shipped with agents in the loop — it’s the observation underneath why estimating client work changed. The typing stopped being the constraint.

The second half is the schlep: getting a bank to onboard you, passing a Fortune 500 customer’s security review, migrating fifteen years of someone’s malformed CSVs, staffing the phone number on the invoice, being the name on the incident report.

Agents made the first half nearly free. They did approximately nothing to the second half. So the ratio between them inverted, and the strategic consequence is blunt: the half you were unconsciously running toward is now the half that provides no defense at all.

If your product is entirely first-half, you don’t have a company, you have a head start measured in weeks. Somebody with a similar idea and a similar agent budget arrives shortly. This is the actual mechanism behind the “it’s just a wrapper” complaint, which is usually stated as an insult when it’s really a structural observation. A wrapper is a product made only of the cheap half.

Why an agent can’t eat a schlep

The tempting counter is that agents will eventually eat the schlep too. Some of it, yes — I’ll get to that. But most schleps aren’t hard because the code is hard. They’re hard because of three properties that have nothing to do with code generation.

A schlep has a counterparty who moves at their own speed. A bank’s onboarding team, an auditor, a customer’s procurement department, a state regulator. You cannot prompt your way to the other side of that table. When a prospect’s security team sends you a 200-question vendor questionnaire, the bottleneck was never writing the answers — an agent drafts those fine. The bottleneck is that the questionnaire is a gate someone on the other side controls, and clearing it takes weeks of their calendar, not yours.

A schlep requires an accountable human. SOC 2 doesn’t ask whether the access review happened, it asks who ran it and produces their signature on the evidence. An agent can generate the policy document, and honestly it writes a better first draft than most people do. It cannot be the party who attests. This is the whole reason SOC 2 works as a revenue tool instead of a security artifact — the buyer is purchasing someone to blame, and a model can’t be blamed.

A schlep is where the mess is, and the mess is undocumented. Every migration I’ve watched go sideways went sideways in the same place: not the transform logic, but the eleven years of exceptions nobody wrote down. The customer who was manually invoiced because of a 2019 dispute. The three states where the tax rule is stored in a spreadsheet on someone’s laptop. An agent is excellent at the transform and blind to the exceptions, because the exceptions aren’t in the repo. They’re in a person’s head, and getting them out is a series of uncomfortable meetings.

Put together: the schlep is the part of the business that runs on trust, accountability, and other people’s institutions. That’s not a temporary gap in model capability. It’s the layer where somebody has to own the outcome, which is a claim I’ve made about professionals generally and which gets more load-bearing the cheaper generation gets.

Jason Fried made the demand-side version of this argument back in March: most people don’t want to build their own software no matter how cheap building gets — “a powerful excavator doesn’t turn a homeowner into a contractor.” That matches every client conversation I’ve had. Nobody asks me to help them build a system. They ask me to make a problem go away, and the system is an implementation detail they’d rather never think about again. Cheap generation didn’t mint a nation of builders. It lowered the price of hiring someone who already likes owning the outcome.

Where this argument is weakest

I’d rather say this myself than have you shout it at the screen: agents genuinely have shrunk some schleps, and I don’t want to pretend otherwise.

Integration glue used to be a schlep and mostly isn’t. Writing a client for a badly documented vendor API, parsing their inconsistent responses, mapping their enums to yours — that was weeks of grinding work and is now an afternoon. Document extraction is another. Turning ten thousand PDFs of purchase orders into structured records was a real business four years ago; now it’s a pipeline you stand up in a sprint. Backfill scripts, one-off data repairs, test fixtures for legacy code, first-line support triage — all cheaper.

So the honest version of my claim isn’t “agents can’t do tedious work.” They’re very good at tedious work. The claim is narrower: agents eat the tedium; they don’t eat the accountability. When a schlep is only tedious, expect it to get cheap and stop treating it as a moat. When a schlep is tedious and has a counterparty, a signature, or a liability attached, the tedium falls away and the hard part stands there untouched — now more visible, because everything around it got easier.

That’s a useful filter, actually. Look at any schlep in your business and ask what’s left after you delete the typing. If nothing’s left, it was never a moat. If what’s left is a relationship, an attestation, or a person who’s on the hook, that’s the thing you own.

The 2026 version of Graham’s question

Graham’s closing move was a reframe: “Instead of asking ‘what problem should I solve?’ ask ‘what problem do I wish someone else would solve for me?’” That question still works — it’s still the best trick I know for getting around your own blindness, because your annoyance is a signal your conscious mind can’t suppress.

But it’s no longer sufficient, because it selects for painful problems and says nothing about defensible ones. In 2012 those overlapped almost completely. Painful implied nobody had done it, which implied room. Today, “painful” includes a large category of problems that are painful right up until someone spends a weekend with an agent.

So run a second question after his: which half of this idea survives a competent stranger pointing an agent at it?

Be concrete. Write down the two halves. If the surviving column has entries — we’re the ones with the bank relationship, we hold the certification the buyer requires, we have the eleven years of exception rules encoded from customers who told us in person, we answer the phone at 2am and eat the refund — you have a business. If the surviving column is empty, you have a feature, and you should either go find a schlep to attach to it or accept that you’re building something with a short shelf life.

The failure mode I see most often in AI startups is a team that has done this exercise implicitly, found the surviving column empty, and responded by making the cheap half more impressive. Better UI. More models. A slicker demo. It’s the schlep blindness Graham described, with a new escape hatch: instead of building a recipe site, you build a very polished version of the copyable half and mistake the polish for a position. Proving the return is what breaks that spell, because a buyer who can measure your value doesn’t care how the sausage was generated.

The schlep is the company now

Graham’s line was that a company is defined by the schleps it will undertake. In 2012 that was mostly a statement about ambition. In 2026 it’s closer to a definition, because the schleps are what’s left after you subtract everything a competitor can regenerate.

Which means the calculus for founders inverted. The schleppy idea used to be the brave choice — bigger prize, worse odds, more suffering. Now it’s the conservative one. It’s the version of the plan where, eighteen months in, you still have something a stranger with a good agent can’t stand up next to you in a week.

For what it’s worth, the individual-career version of this is the same shape and I’ve written it separately: the career I built on work nobody wanted is one long argument that the unglamorous assignment teaches you the system, and that the same asymmetry applies to a person’s skills that applies to a company’s moat. Nobody competes with you for it, which is exactly why it’s worth having.

Pick the schlep. It’s the only part of the plan that’s still yours in a year.