Should I Take This Low-Margin Job? A Decision Tree
Why this matters
Not every job worth doing is worth doing at full margin, and not every thin-margin job is a mistake. The trap is deciding by gut. A job that looks lean can still be the right call, and a job that looks fine can quietly lose you money once you count the true costs. This is a diagnosis path: start with the simplest question (does it even cover its direct costs?) and work up to the strategic ones. Run any soft job through this before you say yes.
Start here: does it clear its own direct costs?
Direct costs are the costs that exist only because you took this job: materials, the labor hours on it, permits, subcontractor fees, the fuel and vehicle wear to get there.
- If the price does not cover direct costs: stop. This is not a low-margin job, it is a losing job. You pay to do it. The only times this is ever defensible are a deliberate, one-time loss leader you can afford, or honoring a warranty or relationship obligation. Otherwise, decline or re-price.
- If the price clears direct costs with something left over: good. That leftover is contribution margin, the money the job throws off to help cover your overhead and profit. Continue down the tree.
Next: how thin is the contribution, and against what?
Compare the leftover (price minus direct costs) as a percentage of the price against your normal job.
- If the contribution margin is only modestly below your usual: this is a routine pricing decision, not a red flag. Weigh it on convenience and fit.
- If the contribution margin is far below your usual: the job is real but lean. It only makes sense if something else justifies it. Keep going.
The capacity question: are you busy or slow?
This is the question that flips the answer more than any other.
- If your crew is fully booked: a thin-margin job has a real cost beyond its own numbers, the opportunity cost. Every hour on a lean job is an hour you cannot sell at full margin to someone else. When you are busy, a low-margin job displaces a better one. Decline unless there is a strong strategic reason.
- If you have idle capacity (a tech with empty days, a slow season): the math changes. Your fixed costs (payroll, rent, vehicles) are being paid whether the tech works or not. A job that clears its direct costs and contributes anything toward that overhead is better than an idle day earning nothing. When you are slow, lean work that contributes is often worth taking.
This is the single biggest reason "should I take it" has no fixed answer. The same job is a yes in February and a no in July.
The strategic check: is there value the price does not show?
Some jobs are worth more than their margin because of what they lead to.
- If the customer is a likely repeat or a maintenance-agreement candidate: a thin first job that opens a long relationship can pay back many times over. Weigh the lifetime value, not the one ticket.
- If the job is a foot in the door with a property manager, builder, or referral source: the real return is the next ten jobs, not this one.
- If it fills a dead slot that builds a tech's hours or skills: there is value in keeping good people busy and sharp.
- If it is a pure favor with no follow-on and no idle capacity: there is no hidden value. Judge it on the margin alone.
Be honest here. "It might lead to more work" is the most over-used excuse for underpricing. Demand a concrete reason, not a hope.
The hidden-cost check: what are you not counting?
Before you commit, gut-check the costs that do not show up on a quick estimate.
- Travel and setup time for a distant or fiddly job can quietly halve the margin.
- Risk and rework. A job with an unclear scope, a difficult customer, or a tricky access point can run long and turn a thin margin negative.
- Payment risk. A customer who haggles hard up front often pays slowly. A lean margin plus slow payment plus collection effort is a bad trade.
- Warranty and callback exposure. Cheap work you have to revisit costs you twice.
If two or more of these apply to a job that is already lean, the realistic margin is thinner than the estimate says. Re-price or pass.
The decision, in one line
Take the lean job when it clears its direct costs, you have idle capacity to fill or a concrete strategic payoff, and the hidden costs are low. Decline it when it fails to cover direct costs, when you are busy and it displaces better work, or when "it might lead to something" is the only argument for it.
References
- SBA guidance on pricing and break-even analysis
- Standard managerial-accounting practice on contribution margin and opportunity cost
- See related: Job Profitability by Service Type
- See related: Financial Warning Signs on the Monthly Statements