The Promise a Shop Cannot Make About Someone Else's Money
Why this matters
Every incentive dollar in this business belongs to someone who is not you and is released by a decision you do not make. That sounds obvious until you look at how shops actually write quotes, because the most common way a shop takes on a third party's risk is not by saying something reckless out loud. It is by netting an unapproved incentive off a price on a piece of paper, which converts a utility's discretionary decision into your accounts receivable without anyone noticing. This card is organized around what comes off your promise list and why, because the list of things you can safely promise is short, and the useful work is understanding which safe-sounding items do not belong on it.
The one test everything else hangs on
Before any sentence leaves your mouth or your quote template, ask: does the outcome I am describing rest on a decision my shop makes? If yes, you can promise it. If it rests on a decision made by a utility reviewer, a manufacturer's processing house, a state energy office, or the tax code as applied to a stranger's return, you can describe it, source it, and help the customer pursue it, but you cannot promise it.
That test is the whole card. Everything below is the test applied to the specific claims that keep showing up in real quotes.
The short list you can actually promise
- That you will file. You control whether the package leaves your office and when.
- What you will file. You control the document set, and you can hand the customer a copy of every page.
- When you will file it. Commit to a number: the complete package submitted within 5 business days of commissioning, tuned to whichever program you use most.
- That the equipment installed matches the equipment on the application. You control that, and it is the single most common reason a defective claim is your fault rather than the customer's.
- That you will correct a defect that is yours, at no charge to the customer. You control your own errors. This is the strongest promise on the list and almost nobody makes it.
Notice what all five share: none of them names an amount, an approval, or a date the money arrives.
What comes off the list, and why each one looks safe
"You qualify." It sounds like a factual statement about equipment specifications, which is why techs say it comfortably. It is not. Qualification is a determination made by a reviewer against criteria that commonly include the property type, occupancy, whether the customer is the account holder of record, prior participation within a lookback window, and whether the removed equipment met a condition the program cares about. You can say the equipment meets the efficiency criterion the program's page states today. That is a specification comparison and it is genuinely yours to make. "You qualify" is a verdict.
"It will be about a fifth of the ticket." A remembered payout from a past job is the least reliable number in the building. Programs reset budgets, retier their categories, and change the basis of calculation between seasons. Quote the administrator's posted terms with the date you read them, or quote nothing.
"You should have it by the fall." Processing timelines are queue-dependent and move with volume, and volume in these programs is seasonal in exactly the way your install schedule is. A date you invent becomes the date you are measured against.
"We will handle everything." This one is dangerous precisely because it reads as service rather than as a guarantee. Customers hear it as an assumption of the outcome, not the paperwork. Replace it with the scope: "we prepare and submit the application and send you a copy, and the program decides."
"If it is denied, we will cover it." This converts an administrator's discretionary decision into a fixed liability on your books, priced at zero. Shops offer it in the last five minutes of a sale to break a stall. If you ever choose to do it deliberately, that is a separate decision with its own analysis (see the article on fronting a rebate), made before the appointment, at a number you set, and never invented at a kitchen table.
"The program will still be running when we install." Many programs are funded to a budget for a period and close when the budget is committed, sometimes with little notice. A signed contract with a lead time on equipment is exposed to that in a way a same-day service call is not.
Two words that do most of the damage
"Guaranteed." It has a specific meaning to a customer and no defensible meaning when applied to someone else's approval decision. Strike it from every template, every ad, and every tech's vocabulary. If an incentive amount appears in an advertisement or a written quote as a representation of what the customer will receive, that representation has to be substantiated under the FTC Act's prohibition on deceptive acts and practices (15 U.S.C. 45), and the administrator's dated posted terms is substantiation while your memory of last season is not.
"We." "We are getting you a rebate" merges your shop and the program into one entity in the customer's mind, and once merged they never separate. Name the administrator every single time, by name, including in casual conversation. The customer should be able to repeat who is paying and who is deciding without your help.
Where the promise gets made without anyone speaking
The quote template. A line reading "less incentive" sitting inside the price arithmetic is a promise, and it is a stronger one than anything a tech says, because it is arithmetic on a document the customer keeps. Once an unapproved incentive has been subtracted from the total, the customer's understanding of what they owe is the reduced figure, and if the claim fails you are asking them for money they believe they already settled.
Keep the incentive out of the price block entirely. Put it in a separate, adjacent block that names the administrator, states the terms as posted with the date, and shows an "estimated net if approved" figure with "if approved" on the same line as the figure, never in a footnote. The customer still sees the favorable math. What they do not see is the incentive presented as a discount you are granting.
Worked example: two proposal formats, one season
A shop ran 60 jobs in one season carrying a utility incentive that averaged about a fifth of the ticket. Its own claim log showed roughly 1 in 12 of those claims permanently denied on eligibility, which is 5 of the 60.
Format A, incentive netted into the price. For those 5 denied jobs, the shop has to go back and collect the difference. Each collection is a dispute, because the customer's copy of the quote shows the reduced total as what they owed. At about a fifth of a ticket each, 5 jobs is one full ticket's worth of revenue at risk across the season, chased across 5 separate uncomfortable conversations. Call it 3 hours of office time per dispute and that is 15 hours spent recovering money the shop had already earned, with a real chance of writing some of it off and a certainty of damaging 5 relationships that were fine until the letter arrived.
Format B, incentive in a separate administrator block. The same 5 denials happen, because the format changes nothing about the program's decision. But the customer paid the contract price on the shop's terms months earlier. The denial is a disappointment about money that was never in their hands, delivered by a shop that told them from the start whose decision it was. Zero collection hours, zero disputes, and the shop's job on those 5 files is a support job: read the denial, correct it if it is fixable, resubmit if the window allows.
The exposure difference is not a rounding error and it is not caused by a difference in denial rate. It is caused entirely by which document the customer holds.
What would change this
Two conditions genuinely change the answer, and only two. The first is a program that pays the contractor directly as an instant discount at point of sale, where the administrator has pre-approved the measure and the shop is the party of record. There, netting it is correct, because the shop actually is the one granting the reduction. Read the participation agreement closely enough to know which model you are in, because a program can run both models for different measures.
The second is a program that requires pre-approval before work begins. A pre-approval in hand is a written determination, not a prediction, and it moves "you qualify" from the banned list to the safe list for that specific job, within whatever expiry the approval carries.
The promise worth making that almost nobody makes
Tell the customer that if the claim is denied for a defect in the paperwork your shop prepared, you will fix it and resubmit at no charge, and if the window has closed because you missed a deadline that was yours, you will say so plainly. It costs you nothing on the jobs you handle correctly, it is entirely within your control, and it is the only rebate-related promise in this whole card that a competitor is unlikely to be making. It also puts real pressure on your own document discipline, which is the point.
References
- Federal Trade Commission, prohibition on deceptive acts and practices, 15 U.S.C. 45, and FTC guidance on substantiation of advertising claims
- Program administrator participation agreements, which define whether a shop is a filing party, a party of record, or an instant-discount channel
- ENERGY STAR (U.S. EPA) rebate finder, for identifying the administrator of record before naming one to a customer
- See related: Explaining Rebates and Incentives Without Overpromising; How to Decide Whether to Front a Rebate for a Customer