How an Architecture Firm Runs on One Work OS

An architecture firm has a demanding operational profile: long, phased projects delivered over months or years, fees agreed early against scopes that inevitably evolve, and a web of consultants who must be coordinated. The design work happens in specialist CAD and modeling tools, and it should. But the business of the practice, winning work, managing phases, tracking fees against effort, and coordinating consultants, is operations, and it decides whether beautiful work is also profitable work.

This guide describes how an architecture firm runs its business development, phased project delivery, contracts, and fee tracking on one work OS, keeping the design tools for design and unifying the coupled operational work.

Business development and the agreement

Architecture pipeline is relationship-driven and often slow, and it needs to connect to delivery because the same principals sell and lead the work. The CRM holds prospects and opportunities with their stage, value, and owning principal, and proposals attach to the record. When a project is won, the owner-architect agreement is executed through e-signature and stored on the record that becomes the project, so the fee structure and scope that were negotiated are on the record the team delivers against.

Because a firm's next commission often comes from a past client, the account carries the full history of prior projects, agreements, and relationships, which makes the next pursuit far stronger.

Phased delivery and the project

An architecture project runs in recognized phases, from concept and schematic design through documentation and construction administration, and each phase has its own deliverables, reviews, and fee portion. Projects and tasks model the phases with owners, milestones, and review gates, so the project architect runs the work from one place and the principal sees phase status without interrupting the studio.

Consultants, structural, mechanical, civil, are coordinated against the project, and their agreements and deliverables live on the record. The firm manages the whole delivery team from one place rather than from a tangle of email threads.

• Model the project in phases with milestones and review gates.
• Coordinate consultants and their deliverables against the project record.
• Give principals phase status without pulling the studio into meetings.

Fees, time, and profitability by phase

The central economic question in architecture is whether the effort spent on a phase matches the fee allocated to it, and answering it requires tracking time against the phase. Time tracking on the project records shows, phase by phase, how the firm is performing against its fee, which is the early warning that a phase is overrunning while there is still time to manage it. Analytics rolls this into project and firm-level profitability, so principals see which project types and clients actually pay.

This is the difference between a firm that discovers a loss at project close and one that manages fee and effort in real time, phase by phase.

The studio and the repeatable structure

An architecture firm is a studio of people with different roles and utilization, and HR holds the team, roles, and availability on the same platform that staffs the projects. Automations carry the firm's repeatable structure: the phased project template when a commission is won, review-gate prompts at each phase transition, and reminders tied to fee milestones.

A firm that runs this way keeps its design tools for design and puts its coupled operations, pipeline, phases, consultants, fees, and people, on one model. The principals get a clear, live view of both the design and the business, and the practice runs as deliberately as it designs.