The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
Insights
Every rebuild gets the same advice: switch frameworks. The real question comes first — is the output identical for everyone who asks? One answer prerenders the page, the other renders it per request.
One brief, several quotes that refuse to line up, and no document saying which quote priced which job. The three lines a brief tends to leave open, and the one sentence that closes each of them.
Moving a catalogue or menu from print to software is not a file upload. We show how paper's job survives the move: opening instantly, installing nothing, asking the reader for nothing.
If the fingerprint reader is questioned, which field of a timekeeping record is tied to a body? The identity field takes a reissuable identifier; the record model stays. A lawyer answers the rest.
Silence gets read as satisfaction. In fact the question leaves the customer, reaches an address and is answered there. Four fault patterns name where it goes and who answers it.
A field app earns its keep where the signal dies: where data is first written, how the phone's queue empties in order and how conflicts merge, drawn from our service-management work.
Seven separate installs, or one core? When the tenant boundary is a property of the data rather than a UI filter, adding an institution becomes a record instead of a deployment. Vipkurum shows how.
Asking the new system to print invoices gets you a PDF template. We cover who ends up retyping invoice numbers, what a work order does when nobody answers, and how to retry without sending twice.
If there is a system you want built, the quote form is the place to describe it.
