The whole business ran on a spreadsheet nobody could open on a truck: 470 job records, 337 hidden fields, no real search, and no mobile at all. The people who needed it most, the crews in the sun, never opened it. Lotline replaces that spreadsheet with one record per lot and six screens that each serve one job.
This is part eight of our series on the AI work we have shipped this year. Lotline was built for a production irrigation contractor whose engagement is still in progress, so the client is not named; the screens run as Caddo Ridge Irrigation, a demonstration brand with fully invented data, and the public demo signs in with demo / demo.
The Work
Residential irrigation for production builders is a relay race: intake, design, permit, schedule, install, backflow, inspection, billing. The reference tool in the trade answers six different jobs with one giant table filtered six ways.
Lotline's answer is one shared record and six purpose-built screens over it. The Lotline case study walks every screen as it runs today.
What We Built
1. The record
One lot, nine stages, from intake through design, permit, schedule, install, backflow, and inspection to billing. Documents, readiness gates, crew, and serial numbers all hang off the same record.
2. Six screens, six jobs
The crew lead gets a single run card with one green button sized for a gloved thumb. The superintendent gets gates and counts. The office gets a permit tracker. The owner gets throughput bars. The outside designer gets document rows and never sees payroll.
3. A whole street at once
Designers finish streets, not lots. Drop a batch of plans and each file's address is read from the filename and matched to its lot with the reason stated. In a real batch, sixteen of seventeen filed themselves.
4. The gates
Fence posts, electric, final grade: the three answers that decide whether a crew rolls or burns a day, on the record before the truck leaves the yard.
What Worked
The design argument lives on the crew screen: the person doing the work does not get a dashboard. They get the next lot, three readiness icons, and one green button.
stages per lot, dirt to green on one record
role-built screens over the same shared data
plan files from a real batch that filed themselves
Meanwhile the owner, reading the same record at the same moment, sees throughput bars. Same lot, same truth, six different products.
What It Means for Field Service Trades
Every trade that serves production builders runs some version of this relay, and most run it on a spreadsheet that punishes the field. The failure is not data; it is that one interface cannot serve six jobs.
The pattern that fixes it is role-first design over a shared record: give each role only what its day needs, and let the record keep everyone honest.
What this means for you: if your crews will not open your system in the field, the system is the problem. Build for the gloved thumb first and the dashboard second.
Where the AI Does the Lifting
AI shows up where reading is the bottleneck: batch plan filing reads each filename, matches it to a lot, and states its reason in plain English, with the uncertain file flagged for a human instead of guessed at. Confidence with an explanation, or a handoff.
The spreadsheet base
- - 470 rows, 337 hidden fields
- - No mobile, no real search
- - Six jobs share one filtered table
- - Crews never open it
One record, six screens
- - Nine stages on one lot record
- - Built for phones in the sun
- - Each role sees only its own day
- - The crew screen is one green button
What It Does for the Business
For the contractor, the wins are burned days avoided at the gates, permits that stop living in someone's head, and an owner who can see throughput without calling anyone.
For Agentify AI, Lotline is the field-operations pattern: white-label by design, one token set in light and dark, ready to carry another trade's brand next.
Final Takeaway: Build for the Gloved Thumb
Software for the trades fails at the truck, not the office. Lotline starts from the crew lead's hand and works backward to the owner's charts, which is the opposite of how field software is usually built.
One record, honestly shared, beats six copies of the truth in six inboxes.
The crew lead gets one green button. Everything else in the product exists to make that button safe to press.
