Checklist

Before you trust your AI-built prototype: a checklist

You built something promising with AI tools, or a contractor did. It works in the demo. These eight plain questions show what stands between that demo and running the business on it.

It runs in your browser. Nothing you answer is sent or stored.

Eight questions

Is it ready for real customers, real data, and real money?

First, credit where it's due: a prototype captures what the business actually needs, and that's the hard part. These questions are about the foundation underneath it. Answer with what you know today; "Not sure" is a perfectly good answer.

1.Do you know where the data is stored, and who can get to it?

Why it matters: Customer and business information needs a known home, with access limited to the people and systems that need it. Prototypes often keep data in a demo service, a file, or someone's personal account.

2.Does everyone sign in with their own account, and see only what they should?

Why it matters: Shared logins make it impossible to know who did what. Real use needs individual sign-in, a way to remove someone who leaves, and permissions, so a customer sees only their own orders, for example.

3.Are passwords and keys kept out of the code?

Why it matters: Prototypes often have passwords or API keys (the codes that let one system use another, like a payment or AI service) typed right into the code. Anyone who sees the code can use them to run up bills or reach your data.

4.Is the data backed up, and has anyone tried restoring it?

Why it matters: A backup no one has ever restored is a hope, not a plan. Know how often it runs, where the copies go, and how long recovery would take.

5.Does it hold up when two people work in it at once?

Why it matters: A demo has one user. In daily use, two people edit the same order, or someone clicks Save twice. Without care, one change quietly overwrites another, or a record gets duplicated.

6.Does it check information as it's entered?

Why it matters: Prototypes tend to accept whatever is typed. Real use needs checks, like required fields, sensible dates, and no duplicate customers, so bad data doesn't spread into reports and invoices.

7.Could another developer read the code and pick it up?

Why it matters: Code written quickly, by an AI tool or in a hurry, is often inconsistent, and nobody has reviewed all of it. If only its creator can change it safely, every update is a risk. Maintainable code follows a clear, consistent structure.

8.Is it clear who looks after it once it's live?

Why it matters: Someone has to apply security updates, fix problems, make sure it's running, and change it as the business changes. Decide who that is, and what it costs, before customers depend on it.

What the gaps mean

A few gaps are normal. Starting over usually isn't.

Most prototypes were built to prove an idea, not to run a business, so gaps are expected. What matters is closing the ones that count for your situation.

  • ✓Keep what works. The screens, the workflow, and the business rules the prototype captures are worth keeping.
  • ✓Build the foundation underneath. Security, sign-in, and data checks don't have to be invented from scratch. Our platform already provides security, single sign-on, and organization management, so time goes to your product.
  • ✓Fix what matters first. Not every gap is urgent. We'll help you decide which ones protect the business and which can wait.
  • ✓Plan for after launch. Your team runs it day to day, and we're available to stay on for maintenance and updates.
Start with a conversation

Show us the prototype.

A 20-minute call, no deck and no pressure. Bring it as it is; it doesn't need to be finished or tidy. We'll tell you honestly what it would take to run the business on it.