Better Pay Starts Here: The Firm Owner's Guide to Fixing the Delivery Model

Fix the delivery model before you fix the tools

Once you can see where time is going, the instinct is often to reach for technology. If we had a better plugin, a smarter CDE, a proper automation — then we'd fix this.

Sometimes that's true. But more often, the inefficiency is structural, not technical. The tools are fine. The problem is in how the work flows: unclear handoffs, ambiguous responsibilities, information that should be standardised but isn't, decisions that get made too late and force rework downstream.

Fixing that requires documenting how work is supposed to flow, then comparing it honestly to how it actually flows. The gap between those two things is usually where the margin is disappearing.

This means:

Standardising the things that don't need to be bespoke. Not every project requires a from-scratch approach to templates, naming conventions, sheet setups, or coordination procedures. Firms that treat every project as a blank canvas are spending time they're not being paid for. Most of what happens on a typical project has happened before. Building standards that capture that knowledge means your team starts further forward every time.

Making responsibilities explicit. One of the most consistent causes of rework is ambiguity about who owns what at the boundaries between people or disciplines. When it's not clear who is responsible for a decision, decisions get deferred — and deferred decisions become expensive late-stage problems. Clear responsibility doesn't require micromanagement; it just requires clarity.

Resolving scope early, in writing. The fee negotiation problem described in Part 1 — where directors absorb scope changes without going back to the client — is partly cultural, but it's also partly structural. Practices that have clear scope definition processes and are disciplined about recording agreed changes have fewer of these conversations, because both sides have a reference point. The ambiguity that enables scope creep to go unchallenged is usually a process failure, not just a client management failure.

Then automate — but only the right things

Once you have clear processes, automation becomes genuinely powerful. Before that, it just speeds up the chaos.

The highest-return automation targets in a typical architecture practice are almost always the same: rule-based, time-consuming, and recurring tasks. Dimensioning. Sheet population. Tag placement. Drawing checking. Compliance verification. Coordination reporting. These are tasks that require judgment to set up correctly — and then require almost no judgment to execute repeatedly. They are also tasks that, when done manually, create fatigue and introduce errors.

A well-implemented automation in one of these areas doesn't just save time. It removes a category of human error and frees up mental bandwidth for the work that actually requires it.

The framing that tends to resonate with practices is this: automation isn't about replacing people. It's about getting the most from the people you have. In a market where hiring is hard, and margins are thin, the ability to deliver more with the same team is a significant competitive advantage — and it's one that's available now, not in some hypothetical AI-enabled future.

The accreditation angle — and why it matters more than you think

The first blog in this series touched on something worth expanding here: the role of systems and accreditations in unlocking work that smaller practices have historically been locked out of.

ISO 9001 (quality management) and ISO 14001 (environmental management) have typically been associated with large firms. The process of achieving them is seen as expensive, bureaucratic, and worthwhile only if you're pursuing major public-sector contracts, and worse... a tick-box exercise!

That perception is changing, though and for good reason.

First, the practical reality: the process of achieving ISO 9001, done properly, forces a practice to document its processes, establish quality controls, and demonstrate that decisions are being made consistently rather than on the fly. That work has value entirely independent of the certificate. Practices that go through it properly almost always emerge with a tighter, more efficient delivery model — not just a piece of paper.

Second, the commercial reality: having the accreditation opens doors. Public sector work, framework contracts, and larger developer relationships increasingly require it. It also signals to private-sector clients that this practice has thought seriously about how it operates. That's differentiation in a market where most firms look similar from the outside.

Third — and this is the part that doesn't get talked about enough — a small practice with proper systems and accreditations can compete credibly against firms five or ten times its size. The large-firm advantage has traditionally been infrastructure: quality management, compliance frameworks, and the systems that give clients confidence. When a smaller firm builds those systems properly, it keeps all of its natural advantages — speed, direct communication, agility, lower overhead — while eliminating the one structural disadvantage that was holding it back.

What this looks like in practice

We mentioned the 20-person firm we worked with in Part 1, and it is a useful illustration.

When a structured review of delivery identified that roughly a quarter of project time was being lost to inefficiency, the temptation was to see that as a staffing problem. The team must need more people, better people, or more experienced people.

It wasn't. The team was capable. The problem was the system they were working in — unclear handoffs, inconsistent standards, and rework due to unresolved upstream issues.

Addressing those things recovered significant time without adding headcount, reduced the chronic pressure that had been normalised, and improved margin on existing work without requiring the practice to win a single new project.

That's the point. Better delivery doesn't just protect margin on future projects. It recovers margin on the ones you're already delivering.

Where to start

Practices like yours that make the most progress on this tend to approach it in the same sequence:

Measure first. Get clear on where time is actually going before deciding what to fix.

Fix the structural issues. Standardise what doesn't need to be bespoke. Clarify responsibilities. Tighten scope management.

Then automate. Identify the highest-frequency, rule-based tasks and systematically remove them from your team's manual workload.

Build credentials deliberately. If ISO accreditation or BIM certification is relevant to the work you want to win, treat it as an investment with a return — not an administrative burden. Also, make sure you have someone who is responsible for keeping this top of people's minds. Done well, it will be part of the day-to-day processes, not an add-on to people's workload.

Measure again. The practices that sustain improvement are those that maintain visibility into delivery performance rather than treating it as a one-off exercise.

None of this is quick. But the compounding effect is significant. A practice that improves its delivery efficiency by 20% doesn't just see a 20% improvement in margin. It sees improved retention, reduced burnout, better-quality work, stronger client relationships — and eventually, the headroom to pay people properly.

That's the connection that gets missed when the conversation stays at the level of fees and market conditions. Better pay isn't primarily a revenue problem. It's a delivery problem. And delivery problems are solvable.

Here at adeptus towers, we are big fans of the 1% mindset. And we think it is a very good way to think about transforming how your business operates daily.

Most firm owners who fix their margins don't do it with a single transformative decision. They do it by improving how the work flows — consistently, incrementally, and without waiting for the perfect moment to start.

That's the principle behind what we'd call the 1% approach to operational performance: not a wholesale reinvention of your practice, but a commitment to making your delivery model measurably better over time. Getting 1% more efficient each week — tightening a standard, removing a manual step, resolving an ambiguity that's been causing rework — compounds into something significant faster than most people expect.

This matters because the alternative is waiting. Waiting for fees to improve. Waiting for the right hire. Waiting for a quieter period that never quite arrives. Most practices that plateau do so not because they lack ambition but because they never quite find the moment to act on it.

The firms that improve do the opposite. They start with what they can see and fix what's in front of them. They treat every project as data — where did we lose time, what would we do differently, what would a standard look like that prevents this happening again? They build ownership of delivery performance into the culture, not just the director's workload. And they stay curious about what better looks like, even when things are going reasonably well.

The measurement step described earlier in this post is where that mindset becomes practical. You don't need a perfect system to start. You need enough visibility to identify one thing to improve — and the discipline to actually improve it, rather than log it and move on.

Small practices have a genuine advantage here. The gap between identifying a problem and fixing it is much shorter when you're not navigating seventeen layers of approval. That agility is an asset — but only if you use it deliberately.

What next?

If you're a firm owner who recognises any of this and wants to understand where the margin is actually going in your practice — and what it would take to recover it — let's talk. We do this work every day. We'll tell you quickly whether we think we can help.

This is Part 2 of a series on operational performance in architecture practices.  Read Part 1 here.