A former customer found me at a trade show booth in April and I didn't place him right away. He'd moved companies since we worked together, and the face arrived before the context did.

He remembered me, though — and not for a tool or a feature. He wanted to pick up a conversation about a data problem we'd been chasing at his old company, like we'd left off mid-sentence.

Construction is relationship-heavy, so people remembering each other isn't remarkable. What struck me is that the thinking survived at all — and that it survived because it happened to be in his head, and he happened to walk past my booth. A company changes, a job ends, the people in the room move on, and the judgment they built together walks out with them.

In preconstruction, that's normal. It shouldn't be.

Where preconstruction expertise breaks down

Part of the answer is simple: it's a natural function of how many people we work with, and how many conversations happen in a single career. Multiply that by how fast this industry has grown, and you get an ocean of hard-won judgment that never gets written down anywhere.

If you happened to sit near the right estimator, or came up under the right mentor, you got it. If you didn't, you're rebuilding something new. Over and over and over again.

I’ve heard this sentiment in many conversations I’ve had with Brian Labossier, who leads commercial precon at Wright-Ryan Construction. 

Brian's been through this more than once — Sage, then Destini, now building out a team at WR — and every time, the hardest part is the knowledge transfer; getting his people systems that preserve their work and their expertise.

It's also an expensive problem, simply.

If a junior estimator leaves a scope item out because nobody told them to look for it, the firm is the one holding the bag — not the estimator, and not the mentor who might have caught it. 

The relationship between mentor and mentee catches a lot of that risk today. But not everyone gets that relationship. And even the best one only protects what it's actually there to see.

What "scaling expertise" actually means

Judgment has to have somewhere to go; a place where everyone, at any level of the organization, can reach it.

We have technology to thank for this today. Any tool that’s worth its salt, shares the estimator's expertise through a few key avenues. 

  • Cloud-based systems are the precondition. Once the work lives in a central place, rather than one guy’s desktop, knowledge access stops depending on tenure, geography, or who's still on the payroll.
  • Centralized data is what makes judgment provable instead of anecdotal. I’m talking about a well-built cost database here — one that’s created to store historical costs and assumptions from previous projects. With filters and formulas and all the other bells-and-whistles, you can check it against the record that actually produced it.
  • Systems are where it becomes concrete. A system lets a senior estimator take all the logic in their head (the kind of thing they'd normally have to explain to one junior at a time) and build it into one component, once. You don't have to teach the logic behind it; it’s just usable. As an example, learn how Systems work in Ediphi.

That's the theory. What actually changes when a firm builds this in, not just talks about it?

What this looks like built into the work

When expertise is scaled by technology, a few things shift at once.

First, turnover, retirement, and job changes stop feeling so existential. That great estimator who leaves helped build your processes — more importantly, they helped build your reputation. You get to keep that investment.

Suddenly, new offices and new hires inherit guardrails. It’s no longer the familiar battle of learning over several years and a few expensive mistakes.

Then, the senior estimator's role changes shape. They spend less time catching errors and more time on the judgment calls that can’t be reduced to a rule.

Unscaleable expertise is money left on the table; a real cost that nobody puts a number on. 

I’m reminded of this every time I’m in the field or out on the floor. A conversation years later, on a different job, with someone who remembers not what you built, but how you thought — that's proof the judgment was worth more than the moment it was needed in.

Technology's job is to make sure it doesn't take a chance encounter to find the next person who needs it.