What I decide in the first hour of an AI-built app, and what I never let the model touch

Most of the work I do now starts with someone else's app. It runs on their laptop, it demos well, and it has been sitting at "almost done" for three weeks. So before I ever open an editor on a client build, there are a few decisions I make in the first hour, and a few things I never hand to the model.

What I decide before I open the editor

Who is the first person allowed in, and how do they prove who they are? What is the smallest payment that has to succeed on day one? And where does the data live if the machine dies? Those three answers decide the shape of the build. If a client can't answer them yet, that conversation is the first day of work, not a formality before it.

What I give the model, and what I keep

I hand over boilerplate, forms, tables, API wrappers, migration scripts — the boring seventy percent. It is genuinely fast there, and charging a client for typing it by hand would be dishonest. What I keep is the wiring between services: auth domains, redirect URLs, webhooks, storage permissions, environment variables. The model writes those plausibly and wrong, and the wrongness only shows when a real phone hits a real domain.

Where it still breaks, every time

Sign-in returns to a blank page because the redirect domain isn't allow-listed. Payment succeeds in the UI and no webhook arrives, so nobody ships what was paid for. File upload dies on mobile at the size limit, the MIME check, or the bucket's CORS rule. A table can be read without a session. Nobody has an error log, so the first bug report comes from the customer. The list is short, and it is the same list every time.

The order I finish in

Entry, then money, then data in, then data safe, then someone gets told when it breaks. Every step tested on a phone, not on my laptop. For a project that already has its screens, that is two to four days, and the screens stay as they are.

If you are sitting at eighty percent right now, send me the repo and I will tell you what is missing before you pay anything. English or Korean, whichever you prefer: yyhak12345@gmail.com, and a little more about the studio at https://cpcai-studio.netlify.app/en/

Comments

Popular posts from this blog

From 80% to shipped: what a 3-5 day finish of an AI-built app actually looks like

An Australian app build in AUD: GST, ABN and the three decisions to settle on day one

A five-day build is not the impressive part. The handover is.