Custom Software for Architecture and Engineering Firms: Phases, Fees, and Utilization

The overrun you find out about in the invoice run

A design development phase was budgeted at four hundred hours. Somewhere in week six, a structural revision came back and two sheets had to be reworked. Nobody flagged it, because nobody had a reason to — the work was legitimate, the team did it, and the hours went onto timesheets under the right project number.

The principal finds out at the end of the month, when the invoice gets assembled and the phase has burned five hundred and forty hours against a fee that assumed four hundred. The phase is over. The money is spent. The only decisions left are whether to eat it or start an uncomfortable conversation with a client about work that was completed weeks ago.

This is the defining operational problem in a small or mid-size design firm, and it is not a discipline problem. Architects and engineers track their time carefully. The issue is that the time data and the fee data live in a system designed to produce invoices and financial statements — both of which are backward-looking by nature. A firm can have immaculate records and still be flying blind on the only question that matters while the work is happening: are we ahead or behind, right now, on this phase?

Why design firms are a hard fit for generic software

Professional services software generally assumes a project is a bucket of hours with a budget. Design work does not behave that way, and the mismatches compound:

• Fee is allocated by phase, not by project. Being under budget in schematic design does not make you healthy if design development is already forty percent over — but a project-level number averages the two together and shows you nothing.
• A large share of the fee flows out to consultants. Structural, MEP, civil, and landscape sit on your contract, on your schedule, and against your fee, and most systems treat them as a payables line rather than as scope with a status.
• Scope creep arrives as a favor, not a request. The client asks for one more option on a facade study. It takes eleven hours. It was never an additional service, because nobody wrote it down at the moment it was agreed to.
• The deliverable is a set of documents with a review process. Percent complete is genuinely knowable — but only if someone is tracking sheets and reviews, which no accounting system does.
• Utilization matters as much as project margin. A profitable project staffed by people who were sixty percent billable is not the win it looks like on the project report.

Firms respond to all of this the same way. Someone builds a spreadsheet. It works, because a spreadsheet is infinitely flexible, and then it stops working, because it depends entirely on one person updating it and on everyone else remembering it exists. Eventually the firm is running its most important operational number in a file that nobody trusts and everyone quotes.

Start with phase-level earned value

If a design firm builds only one thing, it should be this: a live view, per project and per phase, of fee allocated, hours spent, percent complete, and what that implies about where the phase will land.

The mechanics are not complicated. You already have the fee breakdown from the contract. You already have hours from timesheets. The missing piece is percent complete, and the mistake most firms make is asking a project architect to supply it as a judgment call. That number is unreliable in a predictable direction — people report progress optimistically, right up until the week the deadline makes it impossible.

Derive it instead. Define the deliverable set for each phase once, in the way your firm actually works, and let progress fall out of it:

• The sheet list for the phase, with a status on each sheet: not started, in progress, internal review, issued.
• Consultant inputs required for the phase, and whether each has been received — because a phase is not ninety percent done while it is waiting on MEP.
• Internal QA milestones, so a set that has not been through a check is not counted as finished work.
• Client review cycles, with the date sent and the date comments came back, which is where schedules quietly lose two and three weeks at a time.

Once progress is computed rather than estimated, the useful alert becomes possible: this phase is sixty percent through its fee and forty percent through its deliverables. That message, in week six instead of week twelve, is the entire value of the system. It converts a write-off into a decision — reduce scope, restaff, or go to the client while the work is still ahead of you.

Additional services: the fee you never asked for

Nearly every design firm under-bills additional services, and nearly every principal knows it. The reason is almost never the contract, which usually defines additional services perfectly well. The reason is that the extra work gets agreed to in a phone call or a site visit, by someone who is thinking about the design problem rather than the fee, and it is never captured at the moment it happens.

The fix is the same one that works for change orders in construction: make capturing it take less than a minute, and put the capture point where the conversation happens rather than back at a desk. A short entry — project, what was requested, who asked, rough hours — creates a record. A weekly review of those records turns them into either a billed additional service or a deliberate decision to absorb it as a relationship investment.

Both outcomes are fine. What is not fine is a firm that absorbs several hundred hours a year without ever deciding to, and without knowing which clients it happens with most.

Consultant coordination as tracked scope

On a typical building project, a meaningful share of the contract value passes through the prime firm to consultants. That money is treated as an accounting transaction and almost never as a managed piece of scope, which is why consultant coordination is the most common source of schedule slip on small firm projects.

The version worth building is unglamorous and effective: every consultant on every project, with their contracted scope, their fee, what they owe you for the current phase, when it was due, and what has actually arrived. One screen that answers the question a principal asks every week — what are we waiting on, and who has it been sitting with?

The same structure handles the paperwork that surrounds it. RFIs and submittals during construction administration are a well-defined workflow with a clock on them, and firms routinely track them in email folders. A response deadline that nobody is watching is a liability, not an inconvenience.

Utilization that reflects how the firm is actually staffed

Utilization reports out of standard accounting software tend to be a single ratio per person per month, which is enough to tell a principal that something is wrong and not nearly enough to tell them what.

What a firm running a dozen concurrent projects needs is forward-looking: who is committed to what over the next eight weeks, where the gaps are, and which upcoming phase is going to need a person who is currently booked solid. That is a staffing plan, and it is the difference between winning a project you can actually deliver and winning one that will consume the team.

The data to build it is already in the office. Fee remaining per phase, plus the schedule for each project, produces a defensible estimate of demand by role. Compare that against real capacity and the hiring conversation stops being a matter of instinct.

What to build first

The firms that get value out of this do not attempt a comprehensive practice management system. They pick the one thing that is costing the most and build that, then extend once it is in daily use. A reasonable order for most design firms:

• Phase-level fee and hours tracking with derived percent complete, plus an alert when burn outruns progress. This is where the recovered money usually is.
• A one-minute additional services capture, reviewed weekly, so extra scope becomes a decision instead of a leak.
• Consultant status by project and phase, so coordination gaps surface before they become schedule slip.
• An eight-week staffing view built from remaining fee and project schedules.
• A client-facing project status page, which cuts down status calls and quietly makes your firm easier to work with than the competition.

Most of this reads from systems you already run. If your time and billing lives in a practice management platform or in QuickBooks, the build should pull from it rather than ask anyone to enter hours twice. The fastest way to kill a system like this is to make the team maintain it in parallel with the tools they already use.

Built around how your practice runs

Brad Walker has spent more than twenty years building operational software, and works with professional services firms and construction businesses from Wake Forest, NC — an area with no shortage of architecture and engineering practices serving the Triangle. Work with a design firm always starts the same way: what does your phase structure actually look like, where does a project stop moving, and what number do you wish you had on a Tuesday that you only get at month end?

Engagements are fixed price, with the scope agreed before development starts. You know what you are getting, what it costs, and when your team will have it.

Frequently asked questions

If your firm is finding out about phase overruns after the phase is finished, that is a fixable reporting problem rather than a management failure. Start the conversation. The first step is a discovery call to map how projects move through your practice today and where the fee is going.