The 7 a.m. Test

Every tool looks brilliant in a demo. The data is clean, the path is happy, the room is rooting for you. Demos are designed to be passed.

The real exam is quieter, and it starts the morning after launch.

7 a.m.

A batch job from your billing provider ran long overnight. Traffic is climbing toward the morning peak. A dependency you don't control just returned a 500 for the third time in a minute. Somewhere, a customer is staring at a spinner.

Here is the only question that matters: who is accountable in that moment, and what happens next?

For a prototype builder, the answer is: you are. The demo ended at the repository. Production — the uptime, the incident, the patch, the 3 a.m. page — was always going to be your problem. The tool made the first mile faster and left you the marathon.

Passing the test

Software that passes the 7 a.m. test is built to be operated, not just shipped. It watches itself. When something breaks, it diagnoses the failure, proposes a fix, and — with your approval — deploys it through the same governed pipeline that built it. The incident closes with a timeline: detected, acted, resolved, impact.

The honest version of “it just works” is not “nothing ever breaks.” It's “when it broke, no one was paged, and you approved the fix over coffee.”

That's what an SLA is for. Not a marketing badge — a named commitment: this much uptime, this fast a response, this quick a restore, in writing. A demo makes a promise for the length of the meeting. An SLA makes one you can hold someone to at 7 a.m.

Anyone can pass the demo. Ask what happens the morning after.