01 · the problem
ADGI came to Protorix with a problem that was hurting operational speed directly. The verification process ran on paper, which means an agent leaves with a list, comes back with forms, and somebody re-enters the results. Every step of that is latency and every handoff is a chance to lose a case. In a business paid to turn checks around quickly, the paperwork was not an administrative cost sitting beside the work; it was the constraint on how much work could be done.
02 · what i built
A Flutter app built for the person doing the visits rather than for the office receiving them. An agent logs in and gets their own queue, with visits sorted by state: pending, rescheduled, completed. That structure is the point. A rescheduled visit is the case that quietly disappears in a paper process, so making it a first-class status rather than a note in a margin is what keeps the pipeline honest. Results are captured at the address, on the phone, which removes both the re-entry step and the gap where a form goes missing.
- An agent’s own queue
- Each agent logs in to the visits assigned to them, rather than working from a printed list that has to be reconciled with the office later.
- Visits with a state
- Pending, rescheduled and completed as explicit statuses. Rescheduled is the one that matters: it is the case a paper process loses.
- Capture at the address
- The check is recorded on the phone at the point of the visit, which removes the re-entry step and the window where a form can go astray.
