Seven Signs Your AI-Built App Needs an Engineer

It started as a demo. Customers or staff are running their day on it.

Now: a short review finds the risks. Later: an outage during a busy week.

The person who built it has moved on, or the process is a set of steps someone remembers.

Now: write the deploy path and automate it. Later: every change is a gamble and you stop making changes.

Anyone with the link can see everything, or everyone shares one account.

Now: add roles and least-privilege access, usually in place. Later: a data exposure, and a difficult conversation with a customer.

API keys and passwords sit in the repository or in the browser.

Now: move secrets out and rotate them. Later: anyone who has ever seen the code has the keys.

It came back. Nobody can say whether it will happen again, because there is no monitoring.

Now: add alerts so you hear from a monitor, not a customer. Later: downtime you learn about from customers.

Every change risks silently breaking something else, so changes get slower and scarier.

Now: add tests around the parts that make money. Later: you stop shipping.

Someone with authority, a customer, an investor or a board member, has started asking.

Now: an independent review you can hand them. Later: a deal or a customer waiting on an answer you cannot give.