Ahmed Omar left one of the largest engineering firms in the country two years ago. He had helped grow a regional office from 30 to 100 people. He knew the business. He knew the clients.

He left because the systems were broken, and he was tired of working around them instead of for the people paying the bills.

Today, Slate, his structural engineering firm, is profitable, growing, and almost never the lowest-cost option. They win on speed.

That should tell you something about how to evaluate your project team.

“We’re almost always the fastest”

In construction, schedule is money. Every week of delay on a commercial project is lost rent. On a development, it’s carrying costs, interest expense, and market timing risk that compounds in ways that don’t show up neatly on any one line of a pro forma.

Speed from your engineering team isn’t just a nice-to-have. It’s a financial variable.

Most owners accept slow as a given. It’s just how engineering works. You wait, they deliver, you review, they revise. The cycle takes what it takes.

Slate challenged that assumption. They built their firm around responsiveness as a core deliverable, not a side effect of being good at their jobs. They are almost never the cheapest. Owners keep hiring them anyway.

Because when your schedule slips, the cheapest fee on the engineering contract is irrelevant. The lost revenue from the delay is the real cost.

The new firm model: no timesheets, no phase gates, no pretending

Traditional firms track hours. They bill in six-minute increments. They run reports on utilization rates. They spread hours to projects with open budgets.

None of that serves you. It serves the firm’s accounting system.

Slate doesn’t do timesheets. They’re salaried, milestone-based, and focused on cash flow and client quality, not billable hour optimization. Projects move in phases defined by actual deliverable completion, not arbitrary percentage milestones that exist primarily as billing anchors.

What that means for you as an owner: you’re paying for a delivered outcome, not for time logged. The incentives align. When Slate’s team works smarter and faster, they don’t need to pad hours to hit a target. They deliver and move on.

When you evaluate your next engineering contract, ask how they bill. Ask what “50% complete” actually means and how they arrived at that number. The answers will tell you whether their process is built around your outcome or their revenue model.

AI as an equalizer, not just a buzzword

Small firms have always had a disadvantage against large ones in terms of resources. Can’t afford the specialized staff. Can’t risk new verticals without the bench depth. Can’t compete on every project type.

AI changes that math.

A firm like Slate can use AI for code and standards research that would have taken days of manual lookup. They can validate structural assumptions against references in minutes. AI note-takers capture meeting decisions so the principal doesn’t need to attend every coordination call. New market verticals can be tested without hiring five people first.

This means the firm evaluating your project might be two years old and outperforming a 200-person incumbent. Not because they’re cutting corners, but because they’ve rebuilt the workflow from scratch instead of dragging legacy systems into the present.

The size of a firm no longer reliably predicts delivery quality or speed. What predicts it is whether the team has built their process around your outcomes.

The direct connection most owners are missing

On many projects, you hire an architect, the architect hires a structural engineer, and you never talk to the structural engineer directly. The architect coordinates. Information flows through a filter.

On high-stakes projects (stadiums, complex commercial, anything where structural decisions significantly drive cost) some owners are going direct. Hiring engineers separately. Getting structural input into their pro forma early. Understanding how the engineering decisions affect budget before they’re baked into the design.

This isn’t radical. It’s just owners taking more ownership of their own project. The engineers who work well in direct relationships with owners (who can explain the trade-offs in plain language, who show up accountable to your schedule, not just to the architect’s document set) are the ones worth finding.

The firms built around that direct-service model exist. They’re often smaller. They’re often faster. They’re almost never the ones with the fanciest marketing.

What to ask before you sign the engineering contract

How do you handle schedule compression? If the design is running behind, what’s your process for catching up, and has that process actually worked?

How do you bill and what triggers your invoices? Is it time, or is it specific, definable deliverables?

What does your team look like on this project, and how available is the principal? (The person who sold you the engagement often isn’t the one doing the work.)

What AI tools are you using, and how do they affect your delivery timeline? A firm that can’t answer this question hasn’t thought seriously about efficiency.

Have you worked directly with owners, or do you typically coordinate through the architect? Direct experience with owners means different habits, more plain-language communication, more comfort with business-driven decision-making, more accountability to your schedule instead of a project hierarchy.

Speed is underpriced

You’re probably not paying a premium for fast. You’re probably evaluating engineering contracts primarily on fee. That’s a reasonable starting point, but it misses the most expensive variable in your project: time.

Find the engineers who are genuinely fast, demonstrably accountable, and built their firm to serve you rather than their internal billing system. They exist. They’re worth what they charge.

And they’re winning work from firms twenty times their size. For good reason.