Before you begin
Make a copy or preserve a known working version before introducing production data or major changes.
Identify the person who will review uncertain, exceptional, or incorrect results.
Prepare the application
A preview proves the idea can exist. Production means people can rely on it.
The path from preview to production usually has four steps
1. Use realistic data
Replace sample content with the information the app will actually receive.
2. Define what good looks like
Write one sentence describing a correct result.
3. Test the uncomfortable cases
Try missing fields, unusual inputs, conflicting information, and cases that should require human review.
4. Choose where it will run
Deploy with Empromptu AI, connect your code through GitHub, or prepare the application for your own infrastructure.
You do not need to complete everything at once. Choose the next production risk, then solve that one risk.
For your project, the recommended next step is
the next production milestone
Common mistakes
Treating a clickable preview as production ready.
Using only happy-path test data.
Trying to solve every production risk in one release.
Frequently asked questions
What is the difference between a preview and production?
A preview proves that the workflow can exist. Production adds realistic data, tests, permissions, monitoring, deployment, support, and a defined response when the system is wrong.
Do I need to complete every production step at once?
No. Identify the next material risk and address it. Typical next risks are data, evaluation, edge cases, deployment, or human review.