The Essentials: Build an Architecture Firm's Production Workflow

Choosing Your Software Stack

Most firms end up needing Revit for construction documents and multi-discipline coordination, even if SketchUp handles early concept massing, the AEC Collection runs roughly $2,545/seat/year, a real fixed cost to budget for before your first invoice clears. AutoCAD-only practices still exist for smaller residential work, but they increasingly struggle to coordinate with structural and MEP consultants who have moved to BIM workflows, which means more manual cross-checking and more risk of clashes that only surface during construction. Decide now rather than mid-project, since switching platforms partway through a job set is far more expensive, in both licensing cost and redrawn hours, than picking correctly at the start.

Locking In Your Subconsultant Network

Small architecture firms don't do structural, MEP, or civil engineering in-house, you need a structural engineer and an MEP engineer you can call before you have a signed contract, not after. A typical residential design-to-permit timeline of 3-9 months doesn't leave room to shop for engineers mid-project when a client is expecting fast turnaround. Negotiate your standard sub-consultant fee splits now (structural typically runs 15-25% of the architectural fee on residential work, MEP often similar on commercial TI) so pricing a new project takes hours, not weeks, and so you can quote a client with confidence on your very first inquiry call.

Production Standards and QC

Build a CAD/BIM standard, sheet numbering, layer or category conventions, title block templates, before your first drawing set, not while redlining your first permit rejection under deadline pressure. Establish a QC checkpoint at each phase transition (schematic design to design development, design development to construction documents) where someone other than the drawing's author reviews it against code and the owner's program. Plan reviewers reject a meaningful share of first submittals for coordination errors between disciplines; a defined QC step, even a self-review checklist for a true solo practice, catches most of these before they cost you weeks in a resubmittal cycle.

Common Mistakes at This Stage

Firms that skip this phase discover their software choice mid-project when a consultant can't open their files, or discover their structural engineer is unavailable for six weeks right when a client needs a fast turnaround. Others skip written CAD standards entirely, so every drawing set looks different across projects and QC becomes guesswork rather than a repeatable process. Building these systems before your first client, even informally on a single page of standards, pays for itself the first time a deadline gets tight and there's no time left to figure things out from scratch.

Setting Up Before You Need It

The temptation is to build workflow systems reactively, project by project, but that guarantees your first client experiences your least mature process. Spend a focused week before your first signed contract setting up your CAD/BIM template, drafting a one-page subconsultant agreement template, and writing down your QC checklist even if it's only five bullet points. This upfront investment is small compared to the cost of redoing a drawing set's numbering scheme mid-project or scrambling for an engineer referral while a client is waiting on a proposal.

Piloting Your Workflow on a Low-Stakes Project

Before committing your new software stack, subconsultant relationships, and QC checklist to a high-value client project, test the full workflow end to end on something lower stakes, a friend's small addition, a pro bono community project, or even a hypothetical project you run through the motions on. This surfaces gaps while the cost of a mistake is low, rather than discovering them on a paying client's timeline, where the cost of redoing work or missing a deadline is measured in real dollars and real reputation.

Documenting Decisions as You Make Them

Keep a running log of the small workflow decisions you make on your first project, which sheet order worked, which consultant communication style caused delays, which QC step actually caught something. This becomes the seed of your firm's real standards document, written from lived experience rather than theory, and it's far easier to build incrementally from project one than to reconstruct from memory after project five.

Take this further

FREQUENTLY ASKED QUESTIONS