A rate card that's hard to update, buried in an old document, scattered across several proposal templates, tends to just stop getting updated, and a quote built off a stale number costs real margin every single time it happens. The problem usually isn't that rates never get reconsidered, it's that updating them is enough friction that it keeps getting deferred.
A rate card that stays current isn't a more complicated one. It's one built so updating it is actually easy enough to happen.
A stale rate card costs real money every time someone quotes off it
Every quote built from an outdated rate is a small, invisible loss that compounds across every project it touches. The cost of a stale rate card isn't obvious in any single instance, which is exactly why it's easy to let it go stale in the first place.
Keep it in one authoritative place, not scattered across old proposals
If the "real" rate card is actually whatever number is in the most recent proposal someone happens to find, there's no single source of truth to update in the first place. Keep one authoritative version and have every quote pull from it directly.
In Stelaah, service rates can live as a single source of truth that estimates and proposals draw from directly, so a rate update propagates without hunting down every old template. See how estimates works.
Separate the underlying rate from how it's presented to a given client
The base rate and how it's framed for a specific proposal, packaged, itemized, bundled, are two different things, and conflating them makes the underlying number harder to keep consistent. Keep the actual rate separate from its presentation so updating one doesn't require touching every past format.
Set a real, recurring cadence for reviewing it, not an occasional afterthought
A rate card reviewed only when someone happens to notice it feels off drifts further out of date the longer that takes. Set an actual recurring cadence, quarterly or twice a year, to review it deliberately rather than waiting for the problem to become obvious.
Make the reason behind a rate change explicit when you update it
A silent rate increase invites the question of why, whenever a client happens to compare notes with an old proposal. Note briefly what changed and why, cost increases, added capability, so a rate update has a clear, defensible rationale behind it.
A simple checklist
If you do nothing else, do these five things:
- Keep one authoritative rate card, not scattered old proposals.
- Separate the underlying rate from how it's presented per client.
- Set a real recurring cadence for reviewing it.
- Note the reason behind a rate change when you make one.
- Make quoting pull from the current rate directly, not a stale copy.
Do that, and a rate card stays a source of truth the team can trust, not a document quietly costing money the longer it goes unchecked.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
