Irrigation business software for small service teams
An irrigation company does not run at one speed. Six weeks of spring startups, a long stretch of one-off repairs, six weeks of fall winterization — and a book of properties that has to be worked twice a year whether or not anyone remembers to book it. Opsler is irrigation business software built for exactly that year: the seasonal round arrives on the board on its own, the technician pulls up already knowing the property, a sheared head gets priced at the valve box instead of after a callback, and the finished visit turns into an invoice before the truck is back at the yard.
Two people run all of that for nothing, permanently. Put a third pair of hands on for the spring push and you add the person you actually hired at $25 — no block of seats to buy into, no tier above the one you are on, and nothing your busiest month unlocks that your quietest month takes away.
Two very different products both answer to the word irrigation, and only one of them runs a business. Opsler is irrigation business management software — the customers, the schedule, the crew, the parts and the money. The design canvas and the controller programming stay in the specialist tools you already own. Everything between the phone ringing and the invoice clearing lives here, which is what people are actually looking for when they search for irrigation service software.
What the office gets
Every property with its own service history, the seasonal round scheduled once and repeating, technicians assigned with the clash flagged before it happens, and invoices that build themselves out of finished work.
What the truck gets
Today’s calls in the right driving order, the property’s history in hand before the knock, on-site pricing from your own catalog, and a full visit that closes out with no signal at the far end of a gravel road.
Here is what that looks like from the first call to a paid invoice.
A seasonal irrigation workflow from request to invoice
Every job starts the same way and ends the same way, and the money is made in how little friction sits between the two. A request comes in — a returning customer with a broken head, a spring-startup booking, a winterization that a recurring series has already placed on the board — and it opens against the property record you already hold. Assign it, and the technician has it that day with the property’s history attached: what was fixed last visit, what to check, what the last technician left a note about. On site they log what they find in photos and notes, and if repair or upgrade work turns up they price it right there from your own catalog rather than radioing in for a number. The visit closes with the photos and the signature, and the invoice is built out of what actually happened. Nobody writes it up that evening.
Spring startup
Charging systems back up and finding what winter broke, inside a six-week window. Win it by booking volume fast and quoting the repair at the valve box, not after a callback.
Mid-season repairs
A head sheared by a mower, a valve that has started weeping, a controller that lost its program. One at a time, and every one goes faster when the technician already knows the property.
Upgrades and additions
A new planting bed, a drip conversion, a controller swap. Quoted work — and the jobs where offering three price points earns you the bigger ticket.
Winterization
The second narrow window, and the one with a bill attached to missing it: a property skipped in October is a burst line in January.
See how scheduling and dispatch carry the rest of the board on an ordinary Tuesday.
Keep properties and service history together
The technician who has never been to a property should arrive as useful as the one who has. That is worth real money in April, when seasonal help is on the crew and the schedule has no slack in it. The customer record carries contact details, the service address, the notes and every visit ever made there, with its photos, its parts and its completion notes still attached — where the backflow assembly sits, which side of the garage the controller lives on, that the far zone was capped two summers ago, that the gate code changed in April.
In irrigation the natural unit of work is the zone: zone 7 head sheared, zone 3 valve weeping, controller lost its program. That detail lands exactly where a technician goes looking for it — the property’s notes, the job description, and the photographs attached to the visit. The controller face with its program on it. The valve box lid and what is under it. The backflow assembly and how it is plumbed. A photograph of the actual box beats a field in a form that somebody has to keep current, and the next technician to that address opens the call already knowing where everything is buried.
A record per property is the pattern that works, including for the property manager running six sites off one contact. Each address then keeps its own clean history, so the technician standing at the rental sees the rental’s story rather than a merged timeline of six — which is exactly what you want when a two-year gap sits between visits.
Schedule seasonal and recurring visits
Irrigation scheduling software has one job worth paying for: getting two narrow seasons booked without anyone rebuilding last year’s list by hand. On Pro, a property on a fixed annual pattern runs as a recurring series — an annual startup and a separate annual winterization on the same record, or a single series on a custom interval where a contract runs differently. Set it in March and next March it is already there: on the board, assigned, with the checklist attached. Every year after that, too.
Each occurrence still behaves like an ordinary job with the property’s history on it, so moving one visit is one edit and the rest of the series stays exactly where you put it. That is the difference between a customer who wants the second week of April and a customer who wants the second week of April except this year.
A wet week is one decision rather than a rebuild. Reschedule the visit, tag the reason — weather conditions is right there in the list — and the customer’s email and the technician’s phone both update from the same change. You decide which properties move and to when, which is the call an owner wants to keep anyway when half the book is on clay and half is on sand.
For a book you can hold in your head — a few hundred properties run by an owner and a couple of technicians — the recurring series carries the part that repeats every single year, and the board carries everything else. How recurring work is set up.
Assign field work with clear job context
A dispatcher assigns a job to a technician, and on Pro the day comes back in the right driving order. On eleven scattered service calls across a county, that is the difference between finishing at four and finishing at six — or between eleven calls and thirteen. Route optimisation is included on Pro at the same $25 a seat as everything else; there is no routing tier to be moved up into once your book grows.
What the technician opens is their own day, not everybody’s: today, what is coming, and the history behind it, with plain actions like marking a job on the way or opening its details. No wall of menus to dig through on a phone with wet hands.
And if an assignment lands on top of something already on that technician’s day — the same slot, an overlapping window, or simply the same afternoon — Opsler flags it the moment you make it, while there is still time to fix it rather than when two customers are standing outside. The dispatcher decides what happens next, because two properties five minutes apart are a good afternoon, not a conflict, and only the person holding the map knows which is which.
Capture notes, photos and customer evidence
Every visit you invoice arrives with the evidence already behind it. Closing a job takes at least one photo from before the work, at least one from after, and a signature — so the conversation about whether that head was already cracked is settled by a picture, not by two memories. A per-service checklist travels onto the job with it, which means the spring startup runs in the same order whoever is doing it, and the items that must not be missed are marked as such on the technician’s screen.
None of that needs a signal, and in this trade that is the whole ballgame. Half of an irrigation book is out past where coverage stops — acreage, back gardens, valve boxes behind a barn. Before the crew leaves, the device pulls down today’s jobs, the service and parts catalogs, tax settings, the van’s stock levels and recent customer history.
With that on board and no bars at all, the technician opens the job, reads the property’s history, adds photos and notes, works the checklist, moves the job through its statuses, captures the signature, completes the visit, finishes the invoice and records the payment. The truck comes back into range and all of it uploads on its own. A property at the end of a gravel road costs you exactly what a property in town costs you. What a technician can do with no signal.
Build estimates for repairs and upgrades
The repair you price at the valve box is the repair you win. When a technician finds a sheared head or a valve on its way out, the estimate is built there from your own catalog of services and parts, priced and in the customer’s hands before the truck moves — instead of a callback three days later, by which time somebody cheaper has been round.
Bigger work goes out as three price points rather than one take-it-or-leave-it number: patch the single head, replace the zone’s tired heads while the technician is already standing there, or repipe the zone properly. The customer picks a level instead of answering yes or no, and the middle option is where a $180 repair routinely becomes a $900 one.
Approval is a six-digit code sent to the customer and a signature on screen, so the yes is on the record with a time against it rather than remembered as something said over a valve box. An approved estimate converts straight into a scheduled job. How Good/Better/Best estimates work.
Track parts and complete invoices
Heads, nozzles, valves, fittings and controller spares sit in inventory across three kinds of place — warehouse, truck and van — so a technician’s van shows what is actually loaded on it rather than one shared company number. Whatever gets used on a job comes off the right location the moment the job is completed, and two separate stock thresholds raise the alert before a van runs dry in the middle of the busiest fortnight of your year. Budding covers 100 items in a single location; Pro opens up the rest.
The invoice is built out of what actually happened — the completed checklist, the parts used, the approved estimate if there was one. Whether it goes straight to the customer or waits for office review is set on the job itself rather than as one switch for the whole company, so the job a technician raised in the field can behave differently from the one the office booked. And because an invoice raised at the property syncs the moment the signal returns, the money starts moving from the driveway rather than from the desk. See invoicing end to end.
Where irrigation-specific tools fit alongside Opsler
Irrigation business software is the operations layer, and it sits happily next to the specialist tools an irrigation contractor already owns. Design and hydraulics stay where they are. Backflow certification keeps going through whatever you file with today — and the test visit itself schedules here like any other work, as a one-off or as a recurring annual job, with what the technician did recorded in notes and photos and the invoice raised from the same record. You keep the filing system; Opsler runs the round, the crew and the money around it.
On day one you build your service and parts catalog the way you sell it — startups, winterizations, head and valve replacements, controller swaps, zone repairs — or start from the general service catalog and edit it into your own line items. Your prices, your wording, your job types, from the first login. Nobody else’s idea of what an irrigation startup should be worth.
What an irrigation crew gets, on every plan you can grow into
| Capability | Opsler | What it buys you |
|---|---|---|
| Property record with full service history | Yes | Every past visit with its notes, photos and parts used, open before the technician knocks |
| Seasonal and recurring visit series | Yes | Pro. Annual startup, annual winterization or a custom interval — set once, arrives every year |
| Route optimisation for the day | Yes | Pro. The day comes back in the right driving order, so the extra repair fits |
| Per-service checklist that travels onto the job | Yes | The same startup routine in the same order, whichever technician runs it |
| Technician assignment with overlap warnings | Yes | The clash surfaces while you can still fix it, and the dispatcher keeps the final say |
| Before/after photos, notes and a signature on site | Yes | Every visit you invoice has the evidence sitting behind it |
| Estimates for repairs and upgrades, built at the property | Yes | From your own catalog — one price, or Good/Better/Best when there is a bigger job in it |
| One-time-code approval with a signature | Yes | The yes is on the record with a time against it, and converts straight into a scheduled job |
| Parts tracked across warehouse, truck and van | Yes | Deducted on completion, with low-stock alerts before a van runs dry mid-season |
| Invoice built from the completed visit | Yes | Direct-send or office review, set per job — nobody types it up that evening |
| The full visit with no signal | Yes | Job, photos, notes, checklist, signature, completion, invoice and payment. Uploads on reconnect |
Pricing is $25 per seat per month with no seat minimum and no tier above it — an owner and two technicians is $75 a month, published where you can check it. Budding is free forever for 2 seats and 50 jobs a month, and the 14-day Pro trial does not ask for a card. Full pricing.
Irrigation business software questions
It is irrigation business software in the operational sense — customers, scheduling, technicians, field records, estimates, parts and invoicing — used by small trade businesses, irrigation among them. The shape of the year it is built around is yours: a booking season, a repair season, a shutdown season, and a book of properties that has to be worked twice whether or not anyone remembers to call. If your revenue is service and repair on systems that already exist, this is the closer fit than any general landscaping page.
Pro is $25 per seat per month with no seat minimum — an owner and two technicians is three seats, $75 a month, and there is no tier above it to be upsold into. Two people can run the whole business on the free Budding plan instead: 2 seats (one admin, one technician), 50 jobs a month, unlimited customers, free forever with no clock on it. The 14-day Pro trial does not ask for a card.
Set the annual pattern once and the round keeps arriving. A property on a fixed yearly cycle runs as a recurring series on Pro — an annual startup, a separate annual winterization, or a custom interval if the contract runs differently — so next March the work is already on the board, assigned, with the checklist attached. New customers, one-off repairs and upgrade work drop onto the same board alongside it, so the two seasons and the year between them are one schedule, not three.
Yes, on Pro, and a property can carry more than one series at a time — an annual startup and a separate annual winterization sitting on the same record. Each occurrence lands as an ordinary job with the property's full history attached, and moving one visit is one edit that leaves the rest of the series exactly where it was.
Yes. Route optimisation is an Opsler feature on Pro: the day comes back in the right driving order, with less time lost between properties and room for the extra repair that used to wait until next week. On a day with eleven scattered service calls across a county, that is an extra call or two you get paid for.
The whole visit. A technician's device pulls down the day's jobs, the service and parts catalogs, tax settings, the van's stock and recent customer history before they leave. From there, with no bars at all, they open the job, read the property's history, add photos and notes, work the checklist, move the job through its statuses, capture the signature, complete the visit, finish the invoice and record the payment. It all uploads on its own the moment the truck is back in range — which is why a rural property at the end of a gravel road costs you the same as one in town.
Opsler runs the business around the system rather than the system itself. Design canvases, head layouts, hydraulic and precipitation-rate calculations and remote controller programming stay in the specialist tools you already own. What Opsler owns is everything those tools never touch: who is going out, when, what the repair sells for, what came off the truck, and whether the invoice was paid.
Run your next winterization round on it. Budding is free forever for 2 seats and 50 jobs a month; Pro is $25 per seat per month with no minimum.
Start the 14-day trialReady to Run Your Business Without the Chaos?
Scheduling, dispatch, estimates, invoicing, customer portal, and a free branded website — start completely free, upgrade to Pro when you scale.
Free forever on the Budding plan. No credit card required.