The 7 a.m. Test

Every AI-built system passes the demo test. The screen fills, the data flows, the room nods. The test that decides whether a business can actually depend on that system comes later—at 7 a.m. on a Tuesday, when something breaks and customers are already waiting.

The demo test is over.

Watching working software appear in an afternoon has permanently changed what buyers expect. That is genuine progress, and it is worth celebrating: ideas that once waited in queues for quarters can now be seen, touched, and improved in days.

It also means the demo no longer separates anyone from anyone. When every vendor can produce a convincing prototype, the deciding question moves somewhere the demo cannot reach: what happens to this system on its worst morning?

What actually breaks at 7 a.m.

Not exotic failures. Ordinary ones. A security certificate expires. A dependency ships a breaking patch. A disk quietly fills. A query that was fast at one thousand records is slow at one million. An upstream API changes shape over the weekend.

None of these are rare, and none of them are anyone’s fault. They are what production means. Every system that lives long enough meets all of them—the only variable is who is standing next to it when it does.

An SLA is a promise with a spine.

“Operated to an SLA” is easy to say and demanding to mean. It means monitoring is watching before the first user arrives. It means a named owner whose obligations survive the invoice. It means backups that have actually been restored in a drill, not assumed to work. It means a patch cadence, an incident record, and response times written into a contract a buyer can hold.

The distinction is simple: a support plan answers when you call. An operating agreement notices before you do.

Four questions for any AI software vendor.

1. 01
   Who notices?

   Ask to see the monitoring that watches the system overnight—and who receives the alert.

2. 02
   What is promised?

   Ask for the SLA: response times, uptime targets, and the name attached to them.

3. 03
   Can you show me a restore?

   Not a backup policy—an actual restore, performed and timed. Confidence lives in the drill.

4. 04
   Where is the incident log?

   A vendor proud of its 7 a.m. record will show it to you. That log is the résumé that matters.

The next decade of software will be won by the teams still answering at 7 a.m.—because the businesses that depend on software remember exactly who picked up.