What You Actually Charge For
An architect sends a fee proposal, and somewhere on it, explicitly or not, is a list of what the client is paying for. Concept drawings. Working drawings. So many site visits. A set of deliverables, priced. This is how the profession quotes, because it is the part that can be quoted, the tangible outputs a client can see and count and hold the architect to. And it feels honest, because these things are real and the client does receive them. But it quietly misdescribes the entire transaction, because the drawings are not what the client is actually buying.
What the client is buying is judgment. The knowing, in a glance at a plan, that a room will feel wrong before anyone has lived in it. The instinct that a detail will leak, that a contractor's proposed shortcut will cost more later, that a layout the client loves will frustrate them in five years. The years of accumulated knowledge of what not to do, which is most of what separates an architect from a draughtsman, and almost all of what protects a client from an expensive mistake. That is the product. The drawings are just the form the judgment happens to take on its way out.
But judgment cannot be line-itemed. There is no row on a proposal that says thirty years of knowing what won't work. So it gets folded, invisibly, into the price of the drawings, and the moment it does, something is lost. The client, looking at the proposal, sees a price attached to a set of documents, and reasonably starts to evaluate it the way you evaluate documents, by comparing what this architect charges for drawings against what another one does. The single most valuable thing the architect offers has been quietly priced at zero and bundled into the one thing that can be comparison-shopped.
Everything that goes wrong in the fee conversation follows from this. Once the price is attached to the drawings, the negotiation is about the drawings. The client asks why this set of documents costs what it costs, and pushes on that number, and the architect defends that number, and the entire exchange happens on the terms of the deliverable. The judgment never enters the room, because it was never named as a thing being sold. Both sides argue about the price of paper while the actual product, the expertise that makes the paper worth anything, sits unmentioned on the table between them. An architect cannot defend the value of their judgment in a conversation that has been framed, from the first line of the proposal, as being about documents.
The clearest way to see the cost of this is to put two architects side by side. A junior architect, three years out, produces a set of working drawings. A principal with thirty years produces a set of working drawings for the same house. On paper, in the proposal, these look like nearly the same thing, a comparable set of documents, and they get priced within some reasonable distance of each other, because that is what the market will bear for a set of drawings. But they are not the same thing at all. The principal's set carries thirty years of caught mistakes, of details that won't fail, of a plan quietly corrected before it ever reached the page. The client pays a small premium for the name and receives an enormous premium in avoided disaster, none of which is visible, none of which is priced, because the one thing that genuinely differed between the two architects was the one thing the proposal had no way to show.
And the invisibility runs in both directions, which is the part that makes it so hard to fix. The client cannot see the judgment, so they cannot value it. But the architect often cannot show it either, because they have no record of it. The mistakes they caught were caught silently and never happened, so they left no trace. The problems they prevented did not occur, so there is nothing to point to. An architect asking to be paid for their judgment is asking to be paid for a long list of things that, thanks to the judgment, never went wrong, which is the hardest possible thing to invoice for, because the proof of the work is the absence of the disaster.
None of this is solved by learning to sell harder, or by adding a line to the proposal that says judgment, which persuades nobody. What can change is narrower. An architect who can actually see what their work has produced across projects, which ones came out well, where a problem was caught before it became expensive, what the practice's judgment has actually been worth to the people who paid for it, is an architect who has begun to build the record that the proposal alone can never carry. This is part of what Projectsmate is for, not to put a price on judgment, which cannot be done, but to make the results of that judgment visible, so that over time the architect is no longer arguing purely about the cost of drawings, but pointing to a body of work whose value was always real and never, until now, something they could show.