Client systems · VerdeOps · Signed · In delivery
Field operations out of spreadsheets and into one record
A custom operating system for a Triangle landscaping business, replacing scheduling, crew coordination and job records spread across spreadsheets, printed route sheets and group messaging.
Client system. A custom operating system built by isonew for LeAd's Landscaping. Signed and currently in delivery.
Service line: Custom Software Development
Context
What the operation looked like
A field services business coordinating crews, properties, schedules and job history across spreadsheets, printed route sheets and group messaging. Job status lived in whichever thread the crew lead happened to use, and office staff rebuilt the day's picture by phone.
Constraint
Crews work offline-ish in the field with phones and gloves. Any system that adds steps at the job site will be abandoned within a week, so the field surface had to be smaller than what it replaced, not larger.
Decisions
What was decided, and why
- 01
Make the office the first module, because the reconciliation cost was concentrated there and a field rollout without a clean back office would repeat the current mess.
- 02
Model properties and recurring service agreements as first-class records, since scheduling accuracy depends on them rather than on individual jobs.
- 03
Keep messaging in the workflow instead of banning it, so crews are not asked to abandon a tool that works for them.
- 04
Phase delivery so scheduling and job records ship before reporting and billing integration.
System built
What exists, module by module
Estimates
Quotes built from property scope, sent and tracked to acceptance.
Crews
Crew records, assignment and day-by-day workload across the team.
Routes
Route planning replacing the spreadsheet and the printed sheets.
Clients
One record per client and property with recurring scope, access notes and history.
Payments
Invoice state and payment status tied to the job that produced it.
Materials
Materials consumed per job so cost is visible against the estimate.
Built with
Shipped
What it looks like in use
The delivered surface, live. Open it and check.
Evidence
No figures published yet
Operations System Blueprint
Field capture, sync rules and the reporting path.
The artifact handed over on this engagement. Client figures are replaced with representative ones, the structure is unchanged.
No outcome figures are published for VerdeOps. The engagement is signed and in delivery, and measurement starts after the first module has run through a full service cycle. Anything we published now would be a projection.
Current state
Where it stands today
Signed and in delivery. Architecture and module map agreed, first modules in build with the client operating in parallel on the existing tools.
Next expansion
Billing and reporting integration, then field capture expansion once office operations run on the system without a parallel spreadsheet.
What this does not claim
No realized outcome is claimed for VerdeOps. The work is in delivery, and nothing here describes a measured result.
Written and reviewed by
Ronan Pinho
Founder of isonew and of ChatSac, co-founder and CRO of ChurnDefense. Over ten years building and operating technology companies. Based in Apex, North Carolina. Works in English, Portuguese and Spanish.
Last reviewed 2026-08-14
Keep going
Other write-ups and the commercials
Same format, different relationship — plus what work like this costs.
One next step, and it is a paid one on purpose
The AI Opportunity Diagnostic is a fixed-scope engagement. You leave with a ranked plan you can act on with us or without us.