Who Owns the Client, the Fee, and the Technical Calls?

Most architecture firms have a project architect and a project manager on every project. Fewer have a written answer to which one owns the client relationship, which one controls the fee, and which one makes the final call when they disagree.

That gap is a business problem. Not an org-chart problem, not a job-description problem— a business problem. When clients don't know who to call, they call whoever picks up. When fee conversations don't happen, the project margin erodes before anyone notices. When the PA and PM reach different conclusions about a design decision, someone loses— and if the firm hasn't decided in advance who that is, the principal gets the Friday afternoon call.

Three questions cut through this:

• Who owns the client?
• Who owns the fee?
• Who owns the technical calls?

The title tells you the job. The authority map tells you the firm.

Project Architect vs Project Manager: What Each Role Does

The project architect owns the technical quality of what gets built. The project manager owns the business of how and when it gets built. The AIA defines the PM as the firm's "main contact with clients for schedule, budget, and scope management"¹— a definition the PA role does not share.

That distinction matters more than the title. Both roles require deep knowledge of architecture and project delivery. But their domains are different, and when firms treat them as interchangeable, both quality and profitability suffer.

Here's how the two roles divide:

Stone Group Architects puts it plainly: the PA focuses on what the building becomes; the PM focuses on how and when it gets built². Archinect's job title guides describe the PA as "the guardian of the drawings"— the person who decides whether a contractor proposal maintains design intent— and the PM as the firm's primary point of contact for financial and contractual matters³.

This article covers the intra-firm PA/PM relationship in traditional design delivery. Construction managers on the owner's side carry a separate role definition and a separate BLS code— a different conversation entirely.

Who Owns the Client Relationship?

In most firms, the project manager owns the day-to-day client relationship— meeting attendance, deliverable communication, budget conversations. The principal or partner often owns the deeper relationship: the trust, the future work, the referrals. Both can be true at the same time.

The AIA is precise about the PM's client role: "main contact with clients for schedule, budget, and scope management."¹ That's operational contact— not all contact, and not the relationship that produces repeat work. The PA also speaks with clients, but specifically about design-related questions. When a contractor asks about design intent, that call goes to the PA. When a client asks why the project is running over budget, that call goes to the PM⁴.

This becomes a scaling a founder-led professional services firm problem when client ownership goes undefined. Three signs client ownership is unclear:

• Clients get conflicting messages from the PA and PM on scope, schedule, or cost
• The PA starts fielding budget questions they're not positioned to answer
• The PM finds out about design changes that affect fee— after the work is already done

In firms under ten people, one person often holds both the PA and PM roles and both client relationships⁵. That's rational at that size. But above roughly ten staff, the layered model (PM as operational client owner, principal as relationship owner) typically produces cleaner projects and cleaner client conversations.

Who Owns the Fee— and the Cost of Getting It Wrong

The project manager owns the fee. That means writing the initial estimate, tracking hours against budget, and, critically, identifying and recovering scope creep before it erodes the project margin.

The AIA is explicit: the PM "prepares fee estimates and contract proposals."^{1 6} But Aldrich Advisors, an AEC financial advisory firm, puts a number on what happens when that defense breaks down: architecture firms lose 8–14% of total project hours to uncompensated work annually⁷. For a $3M revenue firm, that's $240,000–$420,000 in services that never get billed.

"Architecture fees have almost no room to absorb a drip." — Aldrich Advisors⁷

Scope creep rarely arrives as an obvious change you'd naturally invoice. It arrives as a slow drip of accommodated requests— an extra site visit, a revised finish schedule, one more design option for the owner. What scope creep looks like in practice:

• A client requests design changes after design development is closed— and the PA accommodates them without looping in the PM
• The PM approves a "minor" schedule extension without documenting the fee adjustment
• Contractor RFIs that require significant design work get answered without a change order conversation

The PA's risk here is real. Design changes extend scope. When the PA makes technical decisions without PM awareness, the fee can erode silently. The principle is simple: the PA owns the technical call; the PM owns whether that call has fee implications. These two must communicate actively or the margin bleeds.

Who Owns the Technical Calls— and What the Stamp Means

The project architect owns technical design decisions— materials, details, code compliance, consultant coordination, and what gets built. When a licensed architect stamps drawings, they are legally certifying that the work was done under their responsible control and that they accept responsibility for its accuracy and compliance⁸.

The PA's decision domains:

• Design intent— maintaining the design across all phases and responding to design questions from contractors and consultants
• Code compliance— ensuring the building meets local codes, zoning requirements, and accessibility standards
• Consultant coordination— directing structural, mechanical, electrical, and plumbing engineers to integrate their work with the design
• Drawing QA/QC— reviewing construction documents for accuracy and completeness before issue

The stamp is not a formality. An architect's signature and stamp mean the drawings "were created by the architect or under their responsible control"⁸— a legal act that carries direct liability. In many firms, it's the principal, not the PA, who stamps; PAs develop the documents, principals seal them. But whoever holds the stamp owns the legal responsibility.

The PM can influence technical decisions for cost and schedule reasons. What the PM cannot do is override the PA on code compliance or safety matters. That's where license authority is non-negotiable, and where the firm's E&O (errors and omissions, or professional liability) coverage draws a clear line¹.

The Friction Point— When PA and PM Disagree

The most common PA/PM conflict: the project manager approves a material substitution to save schedule, and the project architect rejects it on design quality grounds. Who wins depends on what your firm's authority structure says in advance— and most firms haven't written it down⁹.

In practice, the authority framework looks like this:

"Design intent" in this context means the overall visual and performance character the design is committed to achieving— the standard the PA applies when evaluating whether a material substitution or contractor proposal maintains what the building is supposed to become.

IllustrArch, which covers architecture career structures, recommends "clarifying decision authority in contracts upfront"⁹ specifically to prevent this scenario from landing on the principal's desk at 5pm on a Friday. The practical version of that is a one-page authority matrix: agreed in onboarding, referenced when it matters.

Most AEC firms write vague job descriptions and call it role clarity. The actual work is deciding in advance who makes which call when the two leads disagree. Producing a written authority matrix— even a simple one that specifies three or four classes of decisions and who owns each— prevents the principal from being the tiebreaker on every project.

What belongs in an authority matrix:

• Decision class (design quality vs. code compliance vs. cost/schedule)
• Who makes the call (PA / PM / both required / principal required)
• Escalation path when they disagree
• Who is authorized to have fee-adjustment conversations with the client

Hierarchy varies across firms. In some, the PM supervises the PA. In others, the PA is senior. In many, they operate in parallel with the principal as the final escalation¹⁰. None of these is wrong— but whichever structure your firm uses, it should be explicit.

Firm Size Changes Everything— When to Split vs. Combine Roles

In firms under ten people, one person typically carries both the PA and PM role on every project— and that's the right call. The overhead of coordinating between two specialists isn't worth it at that scale. Above roughly ten staff, separation usually improves both design quality and project profitability.

Wikipedia's entry on the project architect role confirms this practical threshold: in smaller companies with fewer than ten employees, "one person may have responsibilities of both a project architect and a project manager."⁵ Stone Group Architects takes the other approach and assigns both a dedicated PA and PM to every project to "ensure both design integrity and delivery precision."²

Both structures work. Three hierarchy patterns that exist in practice:

• PM supervises PA— common in delivery-focused firms where budget and schedule are the primary accountability
• PA senior to PM— common in design-focused firms where the design lead holds primary authority
• Parallel with principal as tiebreaker— a common structure in mid-size firms; avoids the hierarchy argument while keeping escalation clear¹⁰

As firms grow past the ten-staff mark, the most common structural pitfall is continuing to run both roles informally out of one person— often a senior PA who has absorbed PM responsibilities without the title or the fee authority that lets them actually do the job. Naming the structure explicitly is what prevents the ambiguity from compounding.

Salary, Career Path, and Which Track to Choose

At the median, the pay is comparable. The BLS reports architects at $96,690 and construction managers at $106,980 (May 2024)¹¹¹², but the more useful figure is Monograph's 2025 benchmark: architectural project managers average $94,690–$102,000 nationally, with steepest salary growth between years five and ten¹³.

A few important caveats on the BLS numbers: "architects" covers all architects, not specifically project architects; "construction managers" covers owner's-side construction management, not architecture firm PMs. Use these as general benchmarks, not precise comparisons. Coastal firms pay more— roughly 20–30% over national averages¹³.

The career tracks diverge at the senior level:

• PA track: Deep design expertise, QA/QC leadership, eventually Principal of Design or technical director
• PM track: Client management, business development, eventually firm principal, COO, or practice leader

Some firms maintain dual-track advancement where PA and PM sit at the same level. Others default to PA → PM as the progression path. As Archinect's PM guide notes: "the variations that firms employ are wide and nuanced."⁴ The practical implication for firm leaders: if your advancement structure defaults to PA → PM, you may be losing strong technical leads who didn't sign up to become client managers— and gaining PMs who weren't particularly drawn to the role.

AI Tools Are Shifting the Monitoring Layer— Not the Authority

Project management software like Monograph, Deltek, and BQE is getting smarter— and what firms are discovering is that the tools surface a question most haven't formally answered yet. These platforms now surface real-time scope creep warnings and fee-burn dashboards— work that used to live entirely in the PM's head. What they cannot do is make the authority call: when the system flags a problem, who decides what to do?

Three things AI-augmented PM tools now do:

• Flag utilization rates when a project is burning hours faster than the fee schedule allows
• Surface scope variance when actual work deviates from contracted deliverables
• Generate budget and timeline alerts before month-end review catches a problem

The data surfaces faster. Conflicts that used to emerge at month-end review now emerge in real time. But the data doesn't decide anything. The authority question— PA or PM, or escalate to principal— still falls to people¹³.

For firm leaders: AI monitoring tools amplify whatever decision-making process already exists. If the authority structure is clear, the alerts land with an owner. If it's unclear, the alerts just create more Friday afternoon calls.

For firms investing in AI governance strategy for professional services firms: clarify the authority structure before the tools arrive. An unclear authority structure doesn't get clearer when the monitoring is automated— it just produces flags that nobody owns. A system that surfaces problems nobody is accountable for is worse than no system at all. Getting human accountability clear before tools make the ambiguity visible— that's what a fractional AI officer actually does in a firm at this stage.

And it's worth noting: the hidden costs of AI projects often trace back here— to unclear ownership structures that the tools expose but don't create.

The Business Case for Role Clarity

Every architecture firm eventually answers these questions— either in advance in writing, or in the middle of a client crisis. Firms that answer them early keep more of their fee, run cleaner projects, and give their PAs and PMs a structure that lets both roles do their best work.

The three answers, stated plainly:

1. PM owns the client (day-to-day) and the fee— writing estimates, tracking hours, defending against scope creep
2. PA owns technical design decisions and the stamp— drawing quality, code compliance, design intent through construction
3. Authority conflicts (design quality, substitution approvals, finish standards) need a written escalation path— the middle ground where vague job descriptions stop working

The business math is straightforward. At $3M revenue, losing 8–14% of project hours to uncompensated scope creep costs $240,000–$420,000 per year⁷. A one-page authority matrix costs nothing. The title tells you the job. The authority map tells you the firm.

If you're bringing AI implementation in professional services into your project delivery workflow, the authority structure should come first. Dan Cumberland Labs works with professional services firms on exactly this kind of implementation— clarifying what humans own before the systems arrive. Start there before the tools do.

FAQ

What is the difference between a project architect and a project manager?

A project architect is a licensed professional responsible for the technical quality of building design— drawings, code compliance, and consultant coordination. A project manager in an architecture firm manages the business of project delivery: client communication, fee budget, schedule, and scope. The PA owns what gets built; the PM owns how and when it gets built.

Does a project manager in an architecture firm need to be a licensed architect?

No— licensure is preferred but not required¹³. Some firms specifically use the PM title to allow non-licensed senior staff to hold the role legally, since the title does not contain the word "architect," which insurance carriers may restrict to licensed professionals.

Who makes design decisions— the project architect or project manager?

The project architect owns design decisions: material selections, design intent, code compliance, and construction document quality³. The project manager may influence decisions that affect cost or schedule but cannot override the PA on code compliance or safety matters, where the licensed architect's judgment— and legal liability— applies⁹.

When should a firm separate the project architect and project manager roles?

Generally above approximately ten staff, separation improves both design quality and project profitability⁵. Below that threshold, one person handling both roles is rational— the coordination overhead between two specialists isn't worth it at smaller scale.

What is the salary difference between a project architect and a project manager?

At the median, compensation is comparable. The BLS reports architects at $96,690 and construction managers at $106,980 (May 2024)¹¹¹². Monograph's 2025 benchmark for architectural project managers is $94,690–$102,000 nationally, with steepest growth between years five and ten of experience¹³.

References

1. American Institute of Architects, "Definition of Architectural Positions" (2025)— https://www.aia.org/resource-center/definition-of-architectural-positions
2. Stone Group Architects, "Understanding the Role of a Project Architect vs. Project Manager" (2024)— https://stonegrouparchitects.com/understanding-the-role-of-a-project-architects-vs-project-manager/
3. Archinect, "Archinect's Guide to Job Titles: Project Architect" (2024)— https://archinect.com/features/article/150189473/archinect-s-guide-to-job-titles-project-architect
4. Archinect, "Archinect's Guide to Job Titles: Project Manager" (2024)— https://archinect.com/features/article/150200691/archinect-s-guide-to-job-titles-project-manager
5. Wikipedia, "Project Architect" (2024)— https://en.wikipedia.org/wiki/Project_architect
6. American Institute of Architects, "2025 AIA Compensation & Benefits Report— Position Descriptions" (2025)— https://www.aia.org/sites/default/files/2025-09/2025%20AIA%20Compensation%20%26%20Benefits%20Report-position%20descriptions.pdf
7. Aldrich Advisors, "How to Handle Scope Creep in Your Architecture or Engineering Firm" (2024)— https://aldrichadvisors.com/insights/architects-engineers/ae-scope-creep/
8. Archinect Forum / State Licensing Boards, "Stamping drawings as PA not partner" (2024)— https://archinect.com/forum/thread/150279436/stamping-drawings-as-pa-not-partner
9. IllustrArch, "Project Architect vs Project Manager: Key Roles" (2024)— https://illustrarch.com/career/107590-architect-vs-project-manager.html
10. Archinect, "Not worth it to become a PM?" (2024)— https://archinect.com/forum/thread/150165262/not-worth-it-to-become-a-pm
11. U.S. Bureau of Labor Statistics, "Occupational Employment and Wage Statistics— Architects, Except Landscape and Naval (17-1011)" (May 2024)— https://www.bls.gov/oes/current/oes171011.htm
12. U.S. Bureau of Labor Statistics, "Occupational Employment and Wage Statistics— Construction Managers (11-9021)" (May 2024)— https://www.bls.gov/oes/current/oes119021.htm
13. Monograph, "Architectural Project Manager Salary Guide 2025" (2025)— https://monograph.com/blog/architectural-project-manager-salary-guide-2025