List what the demonstration leaves unproven
A form may show a success state without delivering an inquiry. A booking button may lead to a placeholder. A dashboard may display invented data. Ask which elements are functional, simulated or unfinished, and inspect the actual destinations. A good prototype makes those limits clear so the next phase can be priced instead of being mistaken for completed delivery.
Make production readiness an explicit milestone
Check public URLs, accurate content, mobile interaction, keyboard access and the services handling customer information. Identify who can publish changes and recover from a faulty release. Generated code still needs review in its deployed environment. The right decision may be to retain the prototype’s design direction while rebuilding an integration or simplifying an unsafe interaction.
A practical check before you buy
Follow the primary customer journey with controlled test information and verify its final destination. Then repeat one failed-input path and one mobile path. Record anything that works only in the demonstration.
| Decision | What to consider | What to check |
|---|---|---|
| Appearance | Direction and layout | Use real content |
| Interaction | Working end-to-end path | Check destination and failure |
| Release | Operating responsibility | Verify publishing and recovery |
An illustrative business scenario
A US lead-generation team can require proof of receipt at the intended sales destination before treating a generated form as complete.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.