What finished means for your app
Finished means a stranger can use the app without you standing beside them. Most stuck apps have a long feature list and no agreed finish line, so the work never ends.
Pick the first customer you want and write their journey as numbered steps. Anything outside that journey can wait until after launch.
Then check the journey against the short list below. Each line is something that must work before you invite anyone.
- A new person can sign up, sign in, sign out and reset a password.
- They can do the main job the app exists for, from start to finish.
- Each account sees its own records and nobody else's.
- If you charge, a payment unlocks what was paid for, and a failed payment unlocks nothing.
- Emails from the app arrive at an address on a different email service from yours.
- The live app runs on your domain, with accounts you own behind it.
- When something breaks, you find out before a customer has to tell you.
Why the last part is harder than the first
The first part of an app is screens, and AI tools are quick at screens. You describe a page, it appears, and you can see at once whether it is right.
The last part is made of rules that do not show on a screen, such as who may read which record and what happens when a card is declined. A wrong rule looks fine until a second person signs up.
The app has also grown. In a large project the tool commonly works from part of the code at a time, so a fix in one place can undo something in another.
Slow progress near the end is normal for an app built this way. The early work needed a prompt and a look. The remaining work needs a written list and testing with more than one account.
What you can finish alone, and how
You can finish a job alone when you can see the fault, repeat it, and undo your change if it goes wrong. Wording, layout, a broken link and a missing form field all fit.
Keep a plain list of what is left and cross items off as you go. If the list gets shorter each week, you can probably finish alone.
If the list stays the same length, something underneath needs a different approach, and more prompts will not shorten it.
For each item on the list, work in this order.
- Save the current version somewhere you can return to, such as a code repository.
- Write the fault as one sentence: what you did, what you expected and what happened.
- Ask the tool for that one fix and nothing else.
- Click through the whole customer journey afterwards, in a fresh account.
- If the journey still works, save again. If it broke, go back and try a smaller change.
What is worth handing to a developer
Hand over the jobs where a mistake costs you a customer's trust or their money, and where you cannot tell from the screen whether the fix worked.
The table sorts the usual leftover jobs. Use it as a starting point, and move a row if your own skills say otherwise.
- Users can see each other's data
- Payments are not working in your AI-built app
- What it costs to finish an AI-built app
| Job that is left | Finish it yourself when | Hand it over when |
|---|---|---|
| Wording, layout and small screen faults | You can see the fault and check the fix by looking | Each fix keeps breaking a different screen |
| Sign-in and password reset | It fails the same way for everyone and the cause is a setting you can find | It works for you and fails for some of the people you invite |
| Who can see which records | A test with two accounts already passes | One account can see or change what belongs to another |
| Payments | All that remains is switching from test keys to live keys | A payment goes through and the account stays locked, or a cancellation changes nothing |
| Messages arrive and only the wording needs work | Messages land in spam, or stop arriving as sign-ups grow | |
| Going live on your domain | The published app already behaves like the preview | It works inside the builder and fails once published |
| Finding out when it breaks | Nobody is paying yet and you are willing to check by hand | Customers are paying and you would only hear about a fault from them |
How to hand it over, and what stays yours
A good handover lets a developer start reading on the first day and leaves every account in your name. Add them as a member of each account, and keep your own password to yourself.
What stays yours: the repository, the domain, the database, the payment account and every login. If someone proposes moving the code into their own account, ask why, and ask how you would get it back.
Ask for the work to arrive as small saved changes, each with a note on what it fixed. You should be able to remove the developer's access on any day and still have a working app.
Here is what to give them at the start.
- Access to the code repository, or an export of the project if no repository exists yet.
- The address of the live app, and of the preview if the two differ.
- Member access to the database, the hosting, the payment account and the email service.
- The customer journey written as steps, with the step where it fails marked.
- Your list of what is left, in the order you care about.
- Two test accounts, with a note on what each one should be able to see.
A leftover list, sorted in one sitting
Finish it or rebuild it
Most almost-done apps are worth finishing. In the apps we see, the screens and the idea usually hold up, and the missing work sits underneath them.
Lean towards finishing when the main journey mostly works and a repair in one place stays in that place.
Lean towards rebuilding a part when the way records are stored cannot support the product, or when every change breaks something unrelated.
Rebuilding one part while keeping the screens is common, and it is a smaller job than starting over. Ask anyone who recommends a full rebuild to name what they would keep.
Nobody can make this call from the outside. It takes someone reading the code and the database, then writing down what stays and what goes, with reasons you can follow.
When to get help
Get help when your list of what is left has stopped getting shorter, or when the items on it touch private data or money. Those are the places where guessing costs the most.
Get help sooner if real people have already signed up, because a fault you could ignore in a test app now has to be explained to customers.
Start with a free consultation. Tell us what the app does and where it stops, and we will say whether you need us at all.
If you do, our Diagnostic is a fixed-price written plan. We read the code and the database, list what blocks launch in order, and quote the next phase.
The fee is credited to the build if you go ahead with us, and your repo and accounts stay yours whether you do or not.
Before you ask anyone to finish it
Write these five things down first. They make the remaining work smaller, whoever does it.
0 of 5 done
We can help you finish it.
Tell us what the app does and where it stops. On a free consultation we will say what you can finish yourself and what is worth handing over. If we do the work, it happens in your accounts and everything is handed back to you.
Book a free consultationOn the project call, we’ll discuss the problem, your existing tools and what TDAT should take off your hands. Then we can define the scope and next steps.
Or call (919) 289-1231
Questions before we start
Can someone finish my AI-built app without starting over?
Usually, yes. In the apps we see, most of the screens are worth keeping and the remaining work sits underneath them. Whoever does it should read the code and the database first, then tell you in writing which parts stay.
How do I know how much of my app is really done?
Count working steps in the customer journey, because a screen can look done with nothing behind it. Use a fresh account and go through sign-up, the main job, payment and coming back the next day. Each step that fails is part of what is left.
Can I finish my vibe coded app with the same AI tool?
Often you can finish the visible parts that way. Save a version first, ask for one change at a time, and test the whole journey after each one. Bring in a person for access rules and payments, and for anything you cannot check by looking.
Will a developer want to rewrite everything?
Some prefer to, since reading another author's code takes time. Ask them to name what they would keep and why. A developer who has read your code can point to specific files and tables when they answer.
What should I keep control of when I hand it over?
The code repository, the domain, the database, the payment account and the email service should all stay in accounts you own. Add the developer as a member. You should be able to remove them and still have everything.
How long will finishing take?
Nobody can say honestly before reading the code, because the remaining work is the part you cannot see on a screen. A written plan, made after a read of the code and the database, is the first point where a schedule means anything.
What does TDAT do first with an almost-finished app?
We start with a free consultation about what the app does and where it stops. If a deeper look is needed, the Diagnostic gives you a written plan and a fixed quote for the next phase. Its price and turnaround are on the pricing page.