// Irrigation supply distributors · Water agency rebate files
Water agency rebate files for commercial irrigation, assembled for a person to review before your customer submits them.
A commercial customer buys controllers, nozzles or flow sensors from you, then asks what the water agency needs: which model number, which dates, which photos. In a free AI proof of concept, AI assembles that file from copies of 20 to 30 past invoices, product lists and program rules, and lists what's missing. Your reviewer, the person at your branch who handles these requests and knows them best, checks each one. Your customer still submits every rebate.
- Rebate files
- 20 to 30
- Eligibility decided
- None
- Rebates submitted
- None
// The one job
From an invoice and a program page to one rebate file
A water agency rebate has its own form, dates and evidence, and it changes with the agency. Your invoice is usually the document everything else leans on, so the request lands on your branch even though the customer is the one applying. Someone reads the program page, pulls the sale and works out what the file still needs.
For the test, AI reads copies of your invoice, the product list and the program's rules and assembles the file: eligible product fields for each line, pre-approval and install dates, site and meter fields, the photos and screenshots the program requires, and a list of what's missing. It decides nothing about eligibility and submits nothing. Your reviewer compares each file with what the customer actually sent in and what came back.
one file
// The hard parts
What an agency's rebate file turns on
The approval date comes first, and each agency runs its own clock. The Metropolitan Water District's commercial rebates in Southern California want a confirmed reservation before the purchase, and a reservation expires 60 days after its effective date. East Bay Municipal Utility District, EBMUD, says commercial customers must apply before purchase or installation, then gives nine months to buy and install. Alameda County Water District and Chandler, Arizona each allow 90 days after written approval or a Notice to Proceed, and San Antonio Water System's rebate offer, once approved, is good for 12 months. The file lines up approval, purchase, install and expiry, and flags an invoice dated ahead of the approval, so a person can see the order of events before anyone sends anything.
Product fields change by line. Metropolitan's rebates need the receipt to show the model number, purchase date and proof of full payment, and they set device minimums of 30 rotating nozzles, 8 sets of large rotary nozzles or 25 in-stem flow regulators. EBMUD pays only for nozzles replacing an entire zone from its qualifying list, and a pressure regulator has to be brass or bronze, one per property. Alameda wants a WaterSense certified controller with a rain sensor unless the model carries its own on-site weather component, and EPA notes labeled controllers can be stand-alone, add-on or plug-in devices. Lines the programs leave out matter too: EBMUD excludes tax, labor and fees, and Alameda excludes installation, site upgrades and subscription fees and subtracts any manufacturer rebate. The file shows each line against the program's list as the customer's copy of the rules states it. Rebate amounts and caps stay as field names, and the file never calculates one.
Site and meter fields have to agree with the water bill, not your ship-to. Metropolitan says the address on the application must match the water bill exactly, wants a separate application for each street address, and issues checks only to the customer listed on that bill, under a W-9 whose name matches. Alameda pays the water account holder. Chandler wants the owner or the party legally responsible for the bill, and EBMUD lists irrigation-only meter properties among its commercial applicants. San Antonio asks for costs itemized by meter. Station counts come from the site as well: Metropolitan and Alameda count only stations physically connected to an in-use system, and Alameda counts the existing controllers. The file flags where your invoice's ship-to, usually a contractor, differs from the bill, for a person to reconcile.
Photos and screenshots have assigned subjects. EBMUD wants the old controller, the new one installed, connected valve wiring, and screenshots of at least two active zones, active schedules with weather features on and a live connection to a weather network or station. Alameda wants the installed controller with its WaterSense label in the picture. Chandler wants two photos, an itemized receipt, proof of payment, a project cost estimate or bid and a signed W-9, without which it won't process the application. San Antonio asks for backflow assembly test records and an Annual Irrigation Checkup report. Metropolitan's inspection vendor makes three attempts to reach the applicant, and the applicant or a designee has to stay for the whole visit. The file lists each item the program names and whether it's in hand.
Some terms outlast the sale. Alameda wants the controller running for at least five years, subscription fees included. San Antonio wants internet connectivity and a contracted licensed irrigator for at least three years. Southern Nevada's program conditions run ten calendar years or until title transfers, and equipment replaced through the program can't be reinstalled in its service area. The file notes these for your customer to read, because they're your customer's to accept. Your reviewer checks every date, field and photo line against the customer's actual submission. Rules and funding change, and Alameda warns its money can run out without notice, so this is a reading of published program pages, not legal advice or a promise of payment.
// What you send
Rebate files your customers already sent in
20 to 30 past rebate files
Commercial requests your branch helped with, approved or denied, with what the customer submitted and what the agency said back. Include any that came back asking for more.
The invoices behind them
Your invoices and product lists for those sales, with amounts blacked out if you'd rather. The test checks that a required field exists, not what the sale was worth.
The rules in force then
The agency's forms, terms and qualifying product lists from the period, the way you had them. A rule that has changed since is marked as of that date.
Customer details held back
Water account numbers, W-9s and site contacts can be masked before anything moves. The file only checks whether each is present. Copies move after the NDA, and a file that can't leave the building gets a look-alike built with your reviewer.
// Before it starts
Agreed before a file changes hands
The owner writes each of these down first.
- Your reviewer
- Named by the owner, usually whoever handles rebate requests at the branch
- Success criteria
- In writing: which fields count, how a missed gap is scored
- Files
- Your reviewer's pick, across the agencies your customers use
- Who decides
- The agency decides eligibility; your customer submits; a person at your branch reviews
- Price
- The live month's range, stated up front, before any file moves
- NDA
- Signed before the first file
// How the test is judged
The file your customer sent in, beside the draft
| Across the same 20 to 30 files | What your customer submitted | Draft rebate file |
|---|---|---|
| Approval, purchase, install and expiry dates, in order | Filled in on your files | Filled in on your files |
| Eligible product fields, line by line | Filled in on your files | Filled in on your files |
| Service address, account and meter fields | Filled in on your files | Filled in on your files |
| Station counts and zone conversions | Filled in on your files | Filled in on your files |
| Photos and screenshots the program names | Filled in on your files | Filled in on your files |
| Lines the program leaves out, such as tax and labor | Filled in on your files | Filled in on your files |
| Items still missing, listed for the customer | Filled in on your files | Filled in on your files |
// After a yes
A month of live rebate requests
Once your reviewer approves, new rebate requests get the same file for about 30 days.
A person at your branch reviews every file before it goes to your customer, and your customer submits it, the same way it works today.
Live files keep being compared with what the agency asks for. Any further job is your decision, priced on its own.
// Possible next jobs
After rebate files, if you want more
- 01Next
Irrigation plan takeoff quotes
A plan, legend and specification read into a draft quote list for your counter.
- 02Then
Program rule change notes
A short note when a program your customers use changes a form, list or deadline your team should know about.
- 03After that
Submittal packets for commercial jobs
Product data matched to each line of a won quote for your salesperson to check.
// One hard limit
The AI never decides eligibility or submits a rebate.
The file records what the program's rules ask for and what your documents show. It never decides whether a product or site is eligible and never submits a rebate. It never touches your ERP, an agency portal or a customer's account, and works only on copies. A person reviews every file, and your customer submits every rebate.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
Rob sets the range on the call from two counts: how many rebate requests you handle in a year and how many agencies they come from.
// Questions
Rebate file questions
Can it tell our customer they qualify?
Do you log in to the agency's portal or the customer's water account?
Which water agencies does it cover?
Does it replace our person who helps customers with rebates?
What about turf replacement and larger conversion projects?

Rob Eason, founder
// Book a proof of concept call
Bring the last rebate file that came back.
A half-hour call with Rob about your branches, your role, the agencies your customers deal with and roughly how many rebate requests you handle in a year. Invoices and customer files stay with you until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
