A Pair of Scissors in the Gap

A while back I wrote The Ignored Continent. I said the biggest market isn't inside the big tech companies. It's on every industrial belt you can't see. In Shenzhen alone there are 8,000-plus companies doing ocean freight forwarding, and their workflows are roughly the same — orders come in over WeChat, the paperwork gets done in Excel, files get passed around as PDFs, everything reconciled by hand, keyed in by hand, chased for payment by hand. I said big tech can't get in, VCs won't touch it, outsourcing does it badly, and the bosses can't do it themselves. That's the gap. And HA7CH was going to crawl into it.

So I actually crawled in. Headfirst into freight forwarding — a real company, real shipments, real operators.

Now I'm going to be honest with you about what I hit in that gap.

I hit a pair of scissors.

Let me spell out what these scissors look like.

A freight forwarder with thirty or forty people spends maybe twenty thousand RMB a year on software. I can help him. I can take the work he's been doing by piling up human labor and rewrite it with AI, and genuinely cut headcount. That part I've verified — the boss grabbed my hand and said you have to come help us cut costs and boost efficiency.

But I can't collect the money. Because his price ceiling is welded to a line below twenty thousand. The labor I pour in costs more than that twenty thousand. Low-ACV customers: I can do the work, but I can't make money.

So I go upmarket. Bigger customers, higher ACV.

And here's the problem. The moment the ACV is high enough to be worth my time, the customer is big enough and complex enough that one guy with a MacBook simply can't carry it. He wants security, compliance, SLAs, someone who picks up the phone at 3 a.m. when something breaks, a whole delivery org and a chain of accountability.

And that is exactly what big-tech FDE has and I don't. What I have is individual capability. What he wants is organizational capability.

So you see it, right? ACV and a builder's capability point in opposite directions.

The higher the ACV, the bigger and more complex the customer, the more org they need. The lower the ACV, the more I can actually do it, but the less money there is. The two blades of these scissors are joined together. I try to save my margin by raising the price, and the instant I raise it, the customer starts demanding the one thing I can't give.

That narrow band in the middle — ACV high enough to make money, simple enough for one person to deliver — is so thin it barely exists.

What sent a chill down my back wasn't "freight forwarding doesn't work." It was something else.

In The Ignored Continent I said big tech can't get in, because they'd never send a team for a thirty-person logistics company. I treated that as the opportunity.

But now I get it: the reason it isn't worth a team for big tech is the same reason it isn't worth my people either — this company can't afford FDE labor.

That gap is empty not because everyone else is stupid. It's empty because "delivery by humans" doesn't close the math at either end. I saw the gold. I just never put a price on the scissors that were locking it up.

I sat with it for a long time and almost gave up. But one thing saves this — and only one.

These scissors only cut when delivery runs on people.

The moment what I distill out of a company turns into software that runs on its own, without me — both blades open at once.

Low ACV becomes profitable: marginal cost approaches zero, and I can carry an entire long tail.

High ACV becomes serviceable: what carries the complexity is the product, not my body sitting in a chair.

Software is the only thing that can touch both blades of the scissors at the same time.

I used to hold up Palantir as the model FDE. But Palantir never made its money from FDE. It made it from Foundry.

FDE is the land — the act of walking in. The product is the business. The FDE labor is subsidized by the product's margin, and in the end it gets replaced by the product.

My mistake was treating "walking in" as the business itself. The scissors are the punishment for that confusion.

Honestly, these past few weeks I argued with myself round after round.

I said, AI parsing of shipping instructions — that's a moat, right? No. Anyone who wires up a model can copy it in a week.

Okay, the two-sided parsing of a whole reconciliation email? Also copyable. And right now it still gets things wrong all the time.

Fine, then I just take over the work entirely and run it for the customer (OPC)? The trust won't hold. When something breaks, who pays for it.

Then volume? The ACV is twenty thousand. Capped.

Then replicate to competitor number two, number three? Every single one makes you re-learn the whole workflow from scratch. It doesn't save you anything.

And now, another pair of scissors.

Five different angles, all slamming into the same wall. And the wall is one sentence: can the knowledge I distill out of a company become software that delivers itself — and gets more accurate the more it's used.

And then I have to admit the most embarrassing thing.

In HA7CH Is a FDE Accelerator I wrote the sexiest line of all: every traditional company can be distilled exactly once, and after that all the knowledge lives inside this AI system, so it's very hard for anyone to re-distill, and the boss won't want to switch.

That line — I've never verified it. Not once.

The product I built does quietly record every human correction: what the AI filled in, what the human changed it to in the end, stored in the database pair by pair. That's the hardest half of distillation, and I built it.

But the other half — feeding those corrections back so it gets better next time, so it actually gets thicker the more it's used — I haven't written a single line of. That table only takes in. Nothing comes out.

The load-bearing brick of my whole theory — I laid half of it, and I've never once put weight on it to see if it holds.

So I've decided to stop.

Stop writing theory. Stop finding new reasons it won't work — I've already found five, and every one of them ends at the same wall I've never pressed on.

No argument, however clever, will pry those scissors open. Only one thing will: build the other half of that wall, and put weight on it once.

This takes a week to settle. I feed back those "AI got it wrong, human got it right" pairs, and I watch whether — for the same customer, the same overseas agent's invoices — the human correction rate stays flat, or bends down.

If it stays flat — then I'll accept it. This is a service business capped by the scissors. It can earn a few people their first bucket of gold, but it isn't the thing I wanted. Accepting it early is worth more than accepting it late.

If it bends down — then the scissors are pried open. And the ignored continent is real again.

When I wrote MVP as Research, I said: drop the food on the ground first and see if anyone eats it. If someone eats it, then you give them a plate.

Freight forwarding is the food I dropped on the ground. Someone took a bite. The research has come back now — it's not that no one's hungry. It's that there's a pair of scissors on this patch of ground.

I'm not going to argue my way onto that continent with my mouth anymore. I'm going to walk over, put weight on that wall, and find out whether it holds.

That's it.