Example: Carter Irrigation, six vans, Apex NC
1. The problem, in your words
"The schedule for tomorrow is on a whiteboard in the shop. I photograph it about six every evening and text the picture to the crew leads. If a job moves after that, I call three people and hope. Twice this month two vans went to the same address and nobody went to the third."
2. What it costs you today
About forty minutes an evening, five nights a week. Roughly 160 hours a year. The two double-bookings this month cost a wasted morning each and one customer who has not called back. The larger cost is the one you did not mention: nobody except you can answer "where is Danny" without calling Danny.
3. What I will build
One screen the crew leads open on their phones: today and tomorrow, their jobs only, in order, with the address and the gate code. One screen you open in the shop: all six vans on one page, where you move a job between vans by dragging it. A move you make is on their phones inside a second. Nothing to install, and it works on the two-year-old Android in the yard.
4. What I will not build
No invoicing, no payments, no customer portal, no route optimization, no GPS tracking. Each is a real thing you may want one day and none is the job you described. I am also not replacing the whiteboard. It stays.
5. How you will know it worked
Three things, checked six weeks in. You stop photographing the whiteboard. Zero double-booked addresses in a month, counted off the schedule itself. A crew lead can answer "what is my third job" without calling you.
6. What changes for you beyond the obvious
The schedule stops being something only you can read. When you are out for a day, somebody else can move a job without your handwriting in front of them.
7. What I need from you
An hour at the start to watch the evening routine. The list of your six crews and who leads them. One crew lead willing to try it for a week and tell me it is wrong.
8. Timeline
Three weeks to the first working version, with the shop screen in week two. A week running it beside the whiteboard. Live in the fifth week.
9. Investment
A single fixed number inside the published build range, quoted in writing before anything is built. A deposit to start and the balance before it goes live. Then a monthly care plan for hosting, backups and fixes.