The Signup Form

On April 3 my Kindle pipeline went green. The EPUBs passed epubcheck, the print PDFs matched KDP's trim spec, and the covers came out with spine widths computed from the page counts. Zero to green in one day. It is the middle of July now, and that pipeline has not published a single book, because the only thing between it and a live listing is a signup form that wants a Social Security number and a bank account. The code took a day. The form has taken a quarter.

The same wall

I told myself this was a publishing problem. Then it happened again in professional services. Speckles is an RFP agent I built. You hand it a request for proposal and it answers from the source decks, with citations back to the exact slides it drew from. Empty repo to verified, cited answers in one day. It is still not live. Going live needs a BotFather token from Telegram and three decks that sit behind a Canva login. Not a line of code. A token and a login.

Then I remembered I had seen this wall before and misread it. In medical billing, the software to work a denial comes together in days. Getting credentialed on a payer portal takes months. For years I filed that under healthcare being healthcare. It was the same wall. I just could not see it, because back then the code was slow too, and the paperwork hid behind it.

Publishing books, answering RFPs, appealing denials. Three businesses with nothing in common, and the same wall in all of them. The wall is me.

The machine was ready in a day. I was the part that took a quarter.

• 
  1 day zero to a green Kindle pipeline


• 
  1 day zero to a verified, cited RFP agent


• 
  3 months the green pipeline waiting on one signup form


• 
  3 decks stuck behind a single Canva login

What only a person can produce

Look at what is actually blocking. A tax ID. A bank account. An OAuth login. A messaging token tied to an account tied to a phone number tied to a person. None of it is hard. All of it needs a legal human identity, and a venture only gets the identities its founder brings.

Why can't the machine do this part? Because these systems exist to prove a person is behind the button. The form that wants my SSN is not badly designed. It is doing exactly what it was built to do. It marks the line where the economy stops trusting machines and asks for a human it can tax, sue, or pay. AI moved every other line. It cannot move this one, and it should not.

So the critical path of a new venture has quietly changed shape. It used to be months of engineering with paperwork sprinkled through, and the paperwork got done while the code was still being written. Now the engineering compresses into days, and the paperwork stands alone, exposed, as the thing everything else waits on.

Key insight: Once AI does the building, the critical path of a new venture is no longer engineering. It is the short list of artifacts only a legal human identity can produce.

Build to the boundary

Here is the discipline I landed on. Build everything up to the auth boundary, then stop. Every project now ends the same way: a green machine, parked and verified, plus a short list titled PENDING (user). The list holds only things a machine cannot do. Sign up for the account. Enter the SSN. Approve the OAuth grant. Export the decks.

The point of the list is not organization. The point is honesty. When the human blockers stay buried inside a project, they look like engineering, and I respond by engineering more.

What broke: The Kindle toolchain sat green for three months while I kept finding code to polish. It was done on April 3. I was improving the part of the project that was no longer the bottleneck, because polishing code feels like progress and typing my SSN into a form does not.

The result: Speckles went from an empty repo to an RFP agent with verified, cited answers in one day. Everything a machine could produce, it produced. Its pending list has two entries, and both of them are mine.

What I do now

1. Build to the auth boundary, then stop. Once the machine is green, more engineering is avoidance.


2. End every project with a green machine and a written PENDING (user) list. Blockers that stay unwritten disguise themselves as work.


3. Schedule the paperwork like the critical path it is. Right now a form is worth more than a feature.


4. Find the wall before you start. If a venture is going to stall at a signup form, better to know on day one than on day ninety.

For most of my working life, the scarce thing was working software. I have a Master's in Language and Theology and I ran a 32-rig mining farm before I wrote production code, so I never assumed software would be the easy part. Now it is. Green machines stack up at the boundary like planes waiting on one runway, and the runway is one person with a Social Security number. The constraint is not intelligence anymore, and it is not code. It is the number of hands that can sign. If your machines are parked at the same wall, compare notes with me. The builders need to find each other.

Originally published at nabbilkhan.com.