← All articles
Nov 16, 20266 min readLer em português

Two Projects of the Same Value Don't Carry the Same Weight

Revenue tells you what a construction company sells, not what it carries. Two projects of the same value can weigh very differently, and complexity is what breaks the structure.

An old balance scale on a job site at dusk: a rough concrete block wrapped in rebar outweighs a smooth block of the same size, with a tower crane behind.

Two $40 million projects land in the backlog the same month.

The first is a logistics warehouse on a flat site, for an owner who has already built three others with the company. Design complete, permits moving, maybe one decision a week.

The second is a high-end residential building in an established neighborhood: watchful neighbors, a basement excavation that needs shoring, architectural drawings still changing, an active buyers' committee, and a city building department that takes months to answer any inquiry.

In revenue, they're worth the same. On the backlog spreadsheet, each takes one line. Inside the company, they have nothing in common.

Revenue Measures What You Sell, Not What You Carry

Most construction companies size themselves by contract value. How much they signed, how much is in backlog, how much they'll bill this year. That's natural. It's the number the bank asks for, the number partners ask about, the number on the financial statements.

The problem is that this number says very little about the effort the company will have to put in.

Effort comes from complexity. And complexity doesn't grow in proportion to contract value. Sometimes a smaller project consumes more executive hours, more meetings, more rework, and more wear on the team than a project worth twice as much.

Anyone who has run both knows this from experience. But almost no company puts a number on it before signing.

Where a Project's Weight Comes From

In thirty years on job sites in Brazil, Angola, and the United States, I've seen a project's weight come almost always from the same sources. None of them show up in the contract value.

  • Technical complexity. Shoring, foundations in difficult soil, specialty systems, interfaces between many trades. Every interface is a place where something may not fit.
  • Number of stakeholders. A single experienced owner is one thing. A group of buyers, an investment fund, an owner's rep hired by the client, the board of the building next door, and a neighborhood association is something else. Each party brings its own expectations, deadlines, and complaint channels.
  • Regulatory environment. Building permits, environmental approvals, the fire marshal, utilities, historic review, traffic authorities. When the approval path is uncertain, the project starts to depend on decisions no one inside the company controls.
  • Design maturity. Drawings that change during construction turn the job site into a coordination office. Every revision creates a decision, and every decision goes up to someone.
  • Available team. The same project weighs one way with a project manager who has done five like it, and another way with one doing it for the first time.

None of these factors is rare. What's rare is someone adding them up before saying yes.

The Weight That Lands on Leadership

There's one effect of complexity that almost always goes unnoticed: it doesn't stay on the job site. It moves up.

A simple project creates problems the project manager can solve. A complex project creates problems that require someone with authority to negotiate with the owner, renegotiate the schedule with the city, approve a change order, replace a subcontractor midstream.

In most founder-led construction companies, that someone is the founder. Or one or two executives.

That's why a single complex project can disrupt the entire company. It doesn't consume only its own resources. It consumes the attention of the people who make decisions for every other project. The simple jobs keep moving, but with no one watching. And that's where, months later, the surprise shows up.

Decision load on leadership is one of the clearest signs that a company is carrying more than it can handle. When the founder spends the whole day fighting fires on a single project, the question isn't whether they're working too little. It's whether the company depends too much on them.

Capacity Against Load

At Elevare™, we call the margin between what an organization can absorb and the weight it carries the Buffer™: Buffer™ = CC™ − CLI™. CC™ represents capacity. CLI™, the complexity load.

The idea is simple, which is exactly why it tends to be ignored. A company doesn't fail because it has too many projects. It fails because the combined complexity of its projects has exceeded its capacity to handle that complexity.

Two construction companies with the same revenue can be in opposite positions. One with room to grow. The other at its limit, even though they look the same from the outside.

And most important: the same company can change positions without any change in revenue. All it takes is three simple projects finishing and three complex ones starting. The backlog number stays the same. The weight doesn't.

That's why taking on a project is a capacity decision, not just a pricing decision.

How to Read Your Backlog by Weight, Not Just Value

You don't need a sophisticated system to start. You need to change the question.

Instead of "What is this project worth?", the backlog meeting also asks "How much will this project weigh?" A few practical ways:

  • Classify each project into a few complexity levels. Low, medium, high. With criteria agreed in advance, not based on the opinion of whoever wants the job.
  • Map who decides what. For each complex project, list what kinds of decisions will need to go up, and to whom. If the answer is always the same person, the bottleneck is already defined.
  • Look at the total, not the single project. One more complex project may be perfectly manageable. The third complex project at the same time, with the same leadership team, almost never is.
  • Match complexity to the team. Before signing, know which project manager will run the job and whether they've done something similar. If the answer is "we'll see," the real complexity is higher than it looks.
  • Measure what isn't in the contract. Executive hours per project, number of owner meetings, number of design revisions. These are indicators that show weight, not revenue.

Five Questions for Your Next Backlog Meeting

  • 1. If you ranked your projects by value and then by complexity, would the order be the same? If not, which list drives your calendar?
  • 2. How many projects in your current backlog depend on decisions by agencies or parties you don't control?
  • 3. Which project consumed the most of your time in the last thirty days? Is it the largest one in the backlog?
  • 4. How many complex projects can your leadership team follow at the same time without the others being left without an owner?
  • 5. Does the next project you're about to sign increase revenue, weight, or both? Do you know how much of each?

Size Is Deceiving

No construction company grows in revenue without growing in complexity. But complexity can grow much faster than revenue, and quietly.

Anyone looking only at project values is looking at the part of the company that shows up on the financial statements. The part that breaks is somewhere else.

Projects are measured in dollars. Companies are measured by the weight they can carry.

Explore the Elevare™ Preliminary Assessment.

Renato Lerner, article author and founder of Elevare™

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.

Elevare™

Want to know your company's organizational balance?

Schedule a conversation →