Blog · 16 November 2026 · 8 minute read
From vibe coding to production: the twelve things your AI does not do for you
An AI can build your app in an evening. The twelve jobs between that and a product people can pay for, why they are still manual, and how to do them fast.
The gap nobody mentions
The demo is always the same: someone describes an app, and a few minutes later it runs. What the demo leaves out is that it runs on one laptop. A product is something a stranger can find, open, sign up for and pay for, and none of that is code.
The work in between is not difficult. It is a long list of small jobs spread over half a dozen websites, each with its own dashboard and its own vocabulary. Your AI cannot do them, because they are clicks in accounts that belong to you.
The twelve jobs
- A domain name, bought and renewed.
- A DNS zone, with the right records pointing to the right places.
- A private repository with a production branch.
- A hosting project that deploys when you push.
- A database, with its connection string in the right variable.
- An HTTPS certificate on your own domain.
- A sending domain that mail providers trust, so sign-up emails arrive.
- An address where replies reach you.
- A payment product, a price and a webhook, tested end to end.
- Every key stored where the app reads it, and nowhere else.
- Analytics and error tracking, so you know what happens after launch.
- A check that all of it works together on the live address.
Why your AI cannot do them
Three reasons. First, they happen in your accounts, behind your logins, and often involve a purchase or an agreement only a person may accept. Second, they depend on each other in a strict order, with waits in between that have nothing to do with code. Third, a mistake is invisible: a wrong DNS record or a missing email record produces no error message, only customers who never hear from you.
Coding tools are good at text they can see and test. This work is state in other companies' systems, and the feedback arrives minutes later, if at all.
What it costs you
Each job is ten or twenty minutes when you know the dashboard, and an hour when you do not. Add the waiting and the one thing that goes wrong, and a first launch takes a day or two. That would be fine once. The trouble is that it is the same day or two for every idea you try.
Building in volume only works when each attempt is cheap. If shipping costs two days, you ship a handful of things a year, and you become attached to each one because it was expensive. If it costs an hour, you can let the market choose.
How to get through it faster
- Do the jobs in dependency order, domain first. Out of order, you redo them.
- Use as few providers as you can. One for the domain and DNS, one for hosting and the database.
- Keep a list of the exact variable names your app expects, and fill it in as you go.
- Create a separate, narrowly scoped key for each product.
- Test with a real purchase in test mode before you call it done.
- Write down what you did. The second launch should not require remembering.
Or have it done for you
The list is the same every time, which makes it a job for a program. Shipyard connects to your own accounts once, then runs all twelve jobs for each new product in the right order, asks before the one step that costs money, and finishes by handing your coding tool a brief that names exactly what now exists. The AI builds, and it builds on something live.
Launch in an hour, not a weekend
Shipyard connects your accounts once, then sets up the domain, hosting, database, email and payments for every new product.
See how it works