Problems › We Keep Discounting to Win Deals › Energy & Utilities Services
Routine discounting is usually a proof problem and an incentive problem around craft utilisation in outage windows, and almost never a price problem. The version of this question that applies to utility contractors is not the generic one. Margin improvement requires shifting revenue to automation and controls but that reduces overhead line work and operating profit unless utilization exceeds 79 percent which outage scheduling prevents — so an answer that ignores 18.0 will be confidently wrong. The analysis has to start from 71.4 and 23 rather than from revenue.
Routine discounting is usually a proof problem and an incentive problem around craft utilisation in outage windows, and almost never a price problem. The version of this question that applies to utility contractors is not the generic one. Margin improvement requires shifting revenue to automation and controls but that reduces overhead line work and operating profit unless utilization exceeds 79 percent which outage scheduling prevents — so an answer that ignores 18.0 will be confidently wrong. The analysis has to start from 71.4 and 23 rather than from revenue.
When discounting becomes normal on master service agreements, the effective rate has been reset and the original terms are decoration. That has a cost beyond the margin: it tells the utility procurement officer what you actually charge on regulated utility asset projects, and it is very hard to reverse without losing backlog.
The causes are consistent. The value of shifting revenue to automation and controls is not proven against overhead line work, so price becomes the only variable left to discuss. Or the sales incentive rewards closing master service agreements over margin, in which case discounting is exactly the rational behaviour even when craft utilisation sits at 71.4. Or discretion is unlimited, and unlimited discretion is always used.
The diagnostic is the distribution. If discounts cluster at the end of a quarter or at particular individuals, the cause is incentive and authority, not price, and project write-downs follow when outage scheduling keeps utilisation from supporting the shift.
These three together are the signature. One on its own usually points somewhere else.
✓ Craft utilisation readings fall below 71.4 in the final weeks before outage windows close
✓ Discount levels differ sharply between crews on comparable master service agreements
✓ Sales requests price authority instead of proof material for automation and controls work
The move that usually makes it worse. Lowering list price to reflect reality, which resets the anchor and produces the same discount off the new number within two quarters.
It is for you if you run or finance a utility contractor and discounts spike at period end. It is the situation where the numbers are available but nobody has put them in an order that produces a decision.
It is not for you if Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Below is an excerpt from a real run of this analysis on a utility contractor. It is a sample profile rather than a customer, and it is unedited engine output — this is the format you get, on your own numbers.
The subject is Verrick Energy Services, a sample company profile used for testing rather than a customer — 248.6 million dollars revenue from regulated utility asset projects.
Excerpt from a real Percision run · Quick Market Scan · sample company profile
The move. Monetise 9.2-day energised outage reliability inside existing MSAs to expand share-of-wallet and lift blended margin 135 bps.
| Investment required | $0.6–0.9 M (retention bonuses for 150 senior linemen and minor estimating-process tweaks) |
| Expected return | Base case: 4.8× return on $0.75 M investment via $3.6 M incremental gross profit in Year 2; conservative range 3.2–6.1× based on 200–300 bps premium capture. |
| Revenue, year 1 | $255–260 M (+3–5 % vs FY2025) |
| Revenue, year 2 | $265–275 M (+7–11 % vs FY2025) |
| Revenue, year 3 | $280–295 M (+13–19 % vs FY2025) |
| Exit criteria | Strategy should be reversed if, within 18 months, (a) craft utilisation has not reached 75 % OR (b) at least 2 of 3 targeted MSA renewals have not been signed with explicit energised-window guarantees, OR (c) substation-segment gross margin remains below 19.5 % after premium pricing implementation. |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Pricing & Revenue Optimization, one of 29 engagements the platform runs. For utility contractors it works through 18.0, 71.4, 23 and 6.6, then produces the sequence rather than a list of options — which move first, what it funds, and the observation that would say the sequence is wrong.
You watch the analysis get built before paying anything. Read a complete report here if you would rather see the depth first.
Cap the discretion and pay on margin rather than on revenue. Discounting is a rational response to a quota measured in revenue with unlimited price authority attached.
No — as a deliberate, structured exchange for something you want, such as term, volume or a reference. As a reflex at the close of a negotiation, it is margin given away for nothing.
Move them at renewal with notice and a reason, and accept that some will leave. The alternative is a permanent two-tier price the rest of the market eventually discovers.
Materially, yes. Margin improvement requires shifting revenue to automation and controls but that reduces overhead line work and operating profit unless utilization exceeds 79 percent which outage scheduling prevents — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are 18.0, 71.4, 23, and an answer built on industry-general benchmarks will usually point at the wrong one first.
Less than most people expect. Your last twelve months of revenue and cost split the way you already split it, plus whatever you hold on 18.0 and 71.4. The analysis is explicit about what it is assuming where your data stops, which is more useful than waiting for numbers you may never have.
Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.
Describe my situation →Prefer to skip ahead? Go straight to the free diagnostic.
English · Español · Deutsch · Português · Français · Italiano · Nederlands · 日本語 · 한국어 · 中文 · Polski · Svenska · Türkçe · العربية · Tiếng Việt · ไทย · हिन्दी · עברית