Taking On a Project Is a Capacity Decision, Not a Pricing Decision

Every contractor has a ritual for deciding whether to take a job. Estimate, margin, schedule, bonding, payment terms. A well-built spreadsheet, a meeting, a signature.

That ritual answers one question very well: does the job pencil out?

It almost never answers the question that decides the company's future: can the company carry it?

Two jobs with the same margin are not the same job

Picture two bids on the table, same contract value, same estimated margin, same schedule.

The first is a warehouse for a client you've worked with three times. Complete construction documents. One point of contact who makes decisions. Subcontractors your team knows by heart.

The second is a mid-rise for a new client. Drawings still being coordinated. An investor committee, an owner's rep hired by the client, a building department known for slow approvals, and a neighboring condo association that has already said it will be watching closely.

On the spreadsheet, they're identical. In real life, the second will consume far more decisions, more meetings, more coordination and more leadership attention — exactly the resource the company has least of.

Margin tells you what the job pays. It doesn't tell you what it costs the organization.

Price measures the job. Capacity measures the company.

An estimate is an exercise about the project: quantities, materials, labor, overhead and profit. It's what contractors do best, and most do it well.

What an estimate doesn't capture is what the job demands from everything outside it:

• Decisions. How many meaningful decisions will this job generate each week — and how many will climb to the principal?
• Interfaces. How many parties does it force the company to deal with: owner, owner's rep, designers, agencies, neighbors, lender?
• People. Who will run this job — and where is that person coming from?
• Attention. What stops being watched on the other jobs during this one's first weeks, which are always the heaviest?

None of this has a line item. All of it has a cost. And that cost doesn't show up on the new job — it shows up on the others, months later, as margin that slipped without a clear explanation.

The bill arrives through the wrong job

This is the mechanism that makes the problem so hard to see.

When a complex job comes in, it rarely loses money on its own. The company puts its best superintendent on it, the principal starts visiting the site twice a week, accounting prioritizes its pay apps. The new job goes well.

The ones that pay are the jobs that lost the best superintendent, the principal's visits and accounting's priority. They don't fail — they lose a little control, a little schedule, a little margin. When the close-out numbers show the effect, nobody connects it to the contract signed months earlier.

The company concludes it has a project management problem. What it actually had was a business development decision problem.

Questions that belong in the go/no-go meeting

You don't need to turn down complex work. Complex work is often what pays best and what takes the company to the next level. You need to accept it knowing what it will ask of you.

Before the next signature, put these on the agenda:

• 1. Who decides on the client's side? One empowered contact is one kind of job. A committee, an owner's rep and an investor are another, even with the same scope.
• 2. Are the drawings done, or will they be finished during construction? Incomplete design isn't just change-order risk. It's a queue of decisions that will land on your team week after week.
• 3. How many outside parties will interfere? Approvals, permits, neighbors, lender, inspectors. Each one is a calendar the company doesn't control.
• 4. Who will run it — and who backfills them? If the answer means pulling someone off a job in progress, the cost of the new job includes what will happen on the other one.
• 5. How many jobs are already mobilizing? The first weeks concentrate coordination effort. Two simultaneous mobilizations weigh far more than two jobs at cruising speed.

If most answers point to more load, the job may still be worth it. But price, schedule or staffing need to reflect that — before signing, not after.

Written no-go triggers

Most contractors turn work down on instinct. The principal looks at it, feels “not this one,” and the bid dies. Sometimes the instinct is right. The problem is that instinct doesn't scale and can't be handed over — and as the company grows, bid decisions end up being made by people who don't have that instinct.

Companies that grow safely tend to have something simple: a short, written list of conditions that force a pause and a second look. Not rules for automatic rejection — triggers for a second conversation. For example:

• a client with no track record and more than one layer of approval;
• construction documents below a minimum level of completion;
• a schedule that requires mobilizing alongside another large job;
• dependence on a public approval whose timing the company can't control;
• key staff who only exist if pulled off a job in progress.

A tripped trigger doesn't kill the job. It changes the conversation: from “what does it pay” to “what will it cost us.”

Growing well means choosing well

In thirty years on job sites in Brazil, Angola and the United States, I've seen few companies fail for lack of work. I've seen many worn down by the job they shouldn't have taken at that moment — not because it was a bad job, but because it arrived when the company had no room for it.

Backlog shows what the company sold. It doesn't show whether the company fits inside what it sold.

Next time a bid reaches your desk with a handsome margin, ask the question the spreadsheet doesn't: what will this job ask of us that isn't in the estimate?

If nobody in the room can answer, the job isn't ready to be approved.

To assess whether your company has the capacity for the next job before signing the contract, explore the Elevare™ Organizational Capability Assessment.

Renato Lerner

Founder, Elevare™

Renato Lerner has 30 years of experience in construction in Brazil, Angola, and the United States. He is the founder of Elevare™ and creator of the Organizational Capability Diagnostic.