Ever finished a fee proposal, looked at the number, and then changed it anyway?
Maybe you bring it down a little because the studio is quiet next quarter. Maybe the client mentioned they're speaking to a couple of other architects, and suddenly your original fee feels a bit ambitious. Or maybe you really like the project and wouldn't mind having it in your portfolio. So you make a small adjustment and tell yourself it makes sense.
And sometimes, it does.
The problem is that once the proposal goes out, that number becomes the fee. It goes into the agreement, gets invoiced over the next several months, and eventually the project is finished. You move on to the next one. But you probably don't record why you quoted that amount in the first place, or whether the adjustment you made actually worked out in your favour.
Now imagine doing that across a dozen projects. Each time, you're making a decision based on what feels right in that particular moment. But when you sit down to price the next project, how much do you actually know about how those previous decisions turned out?
Here's a simple way to find out. Pull up the last five proposals you've sent for broadly similar projects. Nothing wildly different in scale or scope. Work out the fee against the actual time each project took, including all those extra hours spent coordinating, chasing consultants and sorting out things that weren't originally planned. Put the numbers next to each other.
You might find that the projects you thought were priced well weren't necessarily the ones that worked out best. Or that two fairly similar projects ended up earning you very different amounts for your time. Either way, it's worth understanding why.
Because quite often, the difference has less to do with the project itself and more to do with what was happening when you wrote the proposal. How busy the studio was. Whether you had enough work lined up for the next few months. Whether a previous client had made the last project particularly difficult. Or simply how much you wanted to win this particular job.
And honestly, that's understandable. When the pipeline looks quiet, taking on a project at a lower fee can feel better than having an empty schedule. When you're busy, you might feel more comfortable quoting what you think the work is actually worth. Neither decision is automatically wrong. Running a practice means making decisions based on circumstances, and a rigid rate card isn't going to account for every difference between projects.
But here's where it gets tricky. You might be making these adjustments for perfectly reasonable reasons without ever finding out whether they were the right ones.
Say you tend to lower your fee when the studio is quiet. That seems sensible enough. But what if those are also the projects where the scope ends up expanding, the client needs more hand-holding, or the consultants require far more coordination than you expected? You could end up accepting less money for a project that takes more time than the ones you priced higher.
That's worth knowing, isn't it? Because if you spotted that pattern, you could think twice before making the same adjustment next time. You might change how you define the scope, account for additional coordination or approach the fee conversation differently.
The trouble is, most practices don't have an easy way to make that comparison. The proposal is saved in one folder, the project files are somewhere else, and the actual time spent delivering the work may not have been recorded at all. You remember that one project was difficult, or that another went surprisingly smoothly, but remembering the general experience isn't the same as having something you can compare.
So when the next enquiry comes in, you start again. You look at the project, think about the client, consider how busy the studio is and arrive at a number. You've probably made this decision dozens of times before, but you're still relying heavily on instinct because you haven't kept the information that would help you make a more informed decision.
And that's a strange thing about running an architecture practice. You build up years of experience with materials, consultants, contractors, clients and the design process. You learn what works and what doesn't. Yet when it comes to pricing, so much of that experience stays in your head instead of becoming something you can actually use.
You don't need to turn fee setting into a complicated financial exercise to start changing that. Begin with five recent proposals. Compare the fees with the time each project actually took, then think back to what was happening when you quoted each one. Were you trying to fill a quiet period? Did you underestimate the coordination involved? Did you make an adjustment to win the client that you wouldn't make again today?
You might not find a neat answer straight away, but you'll have something concrete to work with the next time you price a similar project.
Projectsmate helps you keep each project's fee alongside the time spent delivering it, so you can look back at what the work actually involved instead of relying entirely on memory. Over time, those records give you a much better starting point for your next proposal.
Because the goal isn't to charge the same fee for every project. It's to understand why you're charging what you are, and whether those decisions are working for your practice.
You've already spent years learning how to price projects. It's probably time to start using what those projects have taught you.

