Problems › We Cannot Tell If the Strategy Is Working › Energy & Utilities Services
A strategy that cannot be wrong cannot be checked, and most written strategies for utility contractors are written so that they cannot be wrong. What makes this harder for utility contractors is structural: 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. Any credible answer therefore has to hold 18.0 and 71.4 in the same view, which is exactly where most internal analysis stops because the two live in different systems.
A strategy that cannot be wrong cannot be checked, and most written strategies for utility contractors are written so that they cannot be wrong. What makes this harder for utility contractors is structural: 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. Any credible answer therefore has to hold 18.0 and 71.4 in the same view, which is exactly where most internal analysis stops because the two live in different systems.
The usual reason a strategy cannot be evaluated is that it was never stated in a form that could fail. Shifting revenue under master service agreements to automation and controls produces no observation that would contradict it if craft utilisation remains at 71.4 or project write-downs continue, so the approach survives indefinitely regardless of results on regulated utility asset projects.
A checkable strategy names the mechanism — this change in automation work produces this movement in craft utilisation or backlog by this date — and the observation that would say the mechanism is not working, such as utilisation staying below the level needed to offset lost overhead line work inside the outage window.
The other frequent cause is lag. Strategies on master service agreements operate on horizons longer than reporting cycles, so the honest response is to identify leading indicators that move early, such as the 18.0 and 23 metrics on new automation bookings, and to state in advance what they should read.
These three together are the signature. One on its own usually points somewhere else.
✓ Craft utilisation sits at 71.4 with no written threshold that would mark the automation shift as failing inside current outage windows.
✓ Progress appears only as completed activity on master service agreements and backlog additions rather than any change in project write-downs.
✓ Procurement officers and field leads disagree on whether the revenue shift to 248.6 million dollars is working and cannot settle it with the 6.6 metric or any other shared number.
The move that usually makes it worse. Adding more reporting on backlog and outage windows, which increases the volume of numbers without making the strategy falsifiable.
It is for you if you run or finance a utility contractor and the strategy has no failure condition written anywhere. 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 · Customer Value Architecture · 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 Proprietary EFF Methodology, 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.
The mechanism it depends on, not the outcome it promises. Outcomes lag; mechanisms move early and tell you sooner whether the causal claim holds.
Decide before starting, and tie it to the mechanism's natural cycle. Deciding afterwards guarantees the timeline is chosen to fit whatever result arrived.
That is usually a sign the strategy was not specific enough to produce a clean test. Narrow it until one number would settle the argument.
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 · ไทย · हिन्दी · עברית