Architecture firms usually arrive at this evaluation from one of two directions: a firm that has outgrown Deltek or a QuickBooks-plus-spreadsheets setup, or a firm merging with an engineering partner already on Acumatica and asking whether they should move over too. Same answer both times — architecture, like civil and structural engineering, is a Projects-module fit. The phase-based, deliverable-driven nature of architectural work maps closely onto Acumatica's task and billing structure; it does not need Construction Edition's field-construction tooling.
AIA-style phases map directly onto project tasks
Most architecture firms bill against the standard AIA phase breakdown — schematic design, design development, construction documents, bidding/negotiation, construction administration — and each phase typically has its own fee percentage of the total project fee. That maps cleanly onto Acumatica project tasks, each with its own billing rule, so a firm can bill SD and DD as fixed-fee milestones as they complete, then switch to T&M for construction administration where scope is inherently unpredictable.
Project: 25-201 Lakeview Office Building
Task 100 Schematic Design 15% of fee, Milestone billing
Task 200 Design Development 20% of fee, Milestone billing
Task 300 Construction Documents 40% of fee, Milestone billing
Task 400 Bidding/Negotiation 5% of fee, Milestone billing
Task 500 Construction Admin 20% of fee, T&M against a not-to-exceed capDrawing sets and deliverables are the integration gap
Acumatica is not a document/drawing management system, and I do not pretend otherwise to clients — firms keep their CAD or BIM files and drawing sets in whatever PLM/DMS they already use (BIM 360, Newforma, or plain structured file storage), and the practical integration work is attaching the milestone deliverable record or a reference link to the Acumatica project task when a phase completes, so accounting can trigger the milestone invoice off an actual delivered-and-accepted event rather than a verbal "yeah it's done." That is usually a light integration — a webhook or scheduled sync writing a note/attachment onto the task — not a rebuild of the firm's document workflow inside the ERP.
Architecture projects carry structural, MEP, and civil sub-consultants as reimbursable pass-through costs, often marked up. Set these up as their own cost codes/categories distinct from the firm's own labor from the start — mixing consultant pass-throughs into the same cost code as internal labor makes the utilization and profitability reports (the ones principals actually read) misleading, because pass-through revenue with near-zero margin gets blended with billable staff time that should carry real margin.
Wrapping up
Treat an architecture firm implementation as AIA-phase-based project accounting on standard Projects, with light integration to whatever drawing/deliverable system the firm already trusts. The fit is genuinely good here — it just is not the same product conversation as a general contractor's Construction Edition build, and conflating the two leads to either over-buying modules or under-scoping the actual integration work.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.