Phronesis,
as a process.
Four movements. The same discipline Aristotle described, applied to a system instead of a soul. None of the four can be skipped. Most builders skip the first two.
The diagnostic
Perceive
We sit together. I watch how work actually happens, not how the SOP says it does. I ask the questions nobody has asked: why does this take three days? Why does nobody trust this number? Why are you paying for software that doesn't do the one thing you need? The gap reveals itself in the silence after each question.
The question
What is actually broken, that you have stopped noticing?
The anatomy
Diagnose
A gap is not a feature request. I map the actors, the incentives, the failure modes, the compliance envelope, the data flows. I write a one-page diagnosis you can take to your board. I refuse to build on a misdiagnosis. Most failed software projects die here, killed by builders who never diagnosed.
The question
What is the smallest system that closes this gap, and no more?
The build
Close
Production-grade from day one. Encrypted backups. Role-based access. Audit trails. Mobile-responsive. Multi-language when you need it. No 'we'll add that in v2'. If it's needed, it ships in v1. I work in two-week cycles so you see real software every fourteen days, not slideware.
The question
What can I ship in fourteen days that proves the diagnosis was right?
The partnership
Refine
Software that ships and is forgotten is software that decays. I stay, not as a vendor, as a partner. Annual license includes updates, security patches, and the next gap I notice before you do. The contract is structured so my incentives stay aligned with yours: I only win when the system keeps closing the gap.
The question
What is the next gap this system is now ready to absorb?