Customer Says "Just Make It Work" Translation to Scope Decision Tree

Why this matters

"Just make it work" sounds like permission and is often a trap. The customer is expressing urgency and a desire to skip the diagnosis they do not want to hear, but the phrase says nothing about budget, scope, or what "work" means to them. A tech who takes it literally can spend hours and a large bill on a repair the customer never authorized in their head, then face a dispute at sign-off. A tech who hears it as a blank check can over-scope a job the customer wanted patched cheaply. The translation job is to convert an emotional, open-ended phrase into a defined scope with a defined outcome and a defined limit, before any wrench turns. This article structures that across any trade.

Symptom presentation

The customer, faced with a problem, waves off the technical explanation and says some version of "I don't care how, just fix it" or "just make it work." The tone is usually frustration or time pressure. The phrase is the customer trying to delegate the whole decision, which feels like trust but creates ambiguity about what was actually agreed to.

The hidden variables are scope (full repair, temporary fix, or replacement), budget (which the customer has in mind but did not state), and definition of done (restore to like-new, or just stop the immediate problem). All three must be pinned before work, because "just make it work" will not survive a surprise at the invoice.

Quick checks at intake

Translate "work" into a concrete outcome. "When you say make it work, do you want it running today, or fully repaired so it doesn't come back?" The gap between those two is enormous in time and cost.

Surface the budget without making it the whole conversation. "There are a couple of ways to handle this at different price points; let me lay them out." This converts a blank check into a chosen option and prevents sign-off shock.

Set a checkpoint. Agree that you will diagnose, then return with options before committing to a major repair. "Just make it work" is permission to investigate, not pre-authorization for an open-ended bill.

Isolation tree

Branch A: simple, low-cost fault with one obvious fix. "Just make it work" is genuine permission; proceed and inform. When the repair is small and clearly within any reasonable expectation, the phrase is a real go-ahead. Do the work, then explain what you did.

Branch B: the fix is moderate and the customer's budget is unknown. Stop and present options before committing. Convert the open phrase into a chosen scope: repair option, temporary option, or defer. The customer who said "just make it work" still needs to pick which "work" they are buying.

Branch C: the real fix is major (replacement, large repair) but a temporary patch exists. Lay out both explicitly. "I can get it running today, but it will fail again; the lasting fix is larger. Which do you want?" The customer's "just make it work" usually means the cheap path, but you must let them choose knowingly.

Branch D: "make it work" is impossible without addressing an underlying condition. A repair that will not hold unless something upstream is fixed (a part that fails again without correcting the cause, a fix blocked by a code or safety issue). Explain that "work" requires the root cause addressed, and scope accordingly. Do not patch a symptom you know will recur and bill it as a fix.

Branch E: the request implies bypassing a safety device or code requirement to "make it work." Decline that path explicitly. "Make it work" does not authorize defeating a safety, and you will not do it. Offer the compliant fix instead.

Branch F: the customer is emotionally escalated and wants reassurance more than a decision. Slow down, restate the situation calmly, and give them a clear recommended option. Many "just make it work" outbursts resolve once the customer feels heard and handed a clear path rather than a menu of fear.

Branch G: the scope is genuinely unclear even after questioning. Diagnose first, document findings, and present a written scope with options before any committing work. When in doubt, the checkpoint protects both sides.

Confirming scope

Confirm by getting an explicit yes to a specific scope and a specific outcome, not to the phrase. "I'll do X, it will cost about Y, and it will be working in the sense of Z" with the customer agreeing is the real authorization. Capture it on the work order or estimate.

Avoid acting on the bare phrase for anything beyond a trivial fix. The translation is not optional; "just make it work" is the start of the scoping conversation, not the end of it. A documented scope is what protects you at sign-off when the customer's memory of "just make it work" turns into "I didn't agree to that."

Restate the agreed outcome before leaving and confirm it matches their definition of done. The mismatch between your "fixed" and their "working" is the most common source of post-job disputes.

Next steps

Once scope is confirmed, proceed and document what was authorized. If the job grows during the work, stop and reconfirm; the original "just make it work" does not extend to a larger scope discovered mid-repair.

If the customer refuses to define scope or budget and demands you proceed open-ended, set a clear cap and a checkpoint in writing, or decline the open-ended commitment. Protecting the customer from an unexpected bill is part of the job, even when they wave off the conversation.

References

• NARI (National Association of the Remodeling Industry) standards of practice; scope definition and change documentation.
• PHCC (Plumbing-Heating-Cooling Contractors Association) business and ethics guidance.
• ACCA service operations best practices (estimate and authorization discipline).
• OSHA 29 CFR 1910 (safety devices may not be defeated to satisfy a customer request).