How do I build a rate card that reflects real effort?

Build your rate card from the effort your team actually puts into the work, not from a round number that feels about right in a spreadsheet. Set a rate for each role using the hours that work tends to require, then test the card against a few recently completed jobs. If it still holds up when you rebuild real scopes with actual effort, you can trust it on the next quote, including the one that somehow needs to go out this afternoon.

Why a rate card should start from effort

A rate card earns its keep when it helps you turn a real scope into a quote your team can actually deliver. Pick the rates first and squeeze the work into them later, and you may get a tidy estimate that barely resembles the job waiting on the other side. The spreadsheet will look fine. Your capacity plan may disagree.

Start with the services your shop actually sells. Pull a few recent projects apart by phase, deliverable, role, and hours. Who touched the work, including after it looked almost done? How much effort did each contribution take? Which supporting tasks had to happen before the deliverable was actually ready? Learn the delivery pattern before you assign a rate.

This is where small firms often undercount the work without meaning to. The design or development is visible, so it gets estimated. Strategy, project management, internal review, client communication, testing, and handoff are easier to miss, especially the approval follow-up that happens after everyone thought the work was finished. Leave those out of the card and every quote starts with a hole in it.

Think of the card as an internal estimating tool, not a laminated menu for clients. It helps you build the work from evidence and see whether the team has enough capacity to keep the commitment.

Set role-based rates grounded in real hours

Create separate roles only where the work is meaningfully different. Strategy, design, development, content, quality review, and project management may need their own rates because the experience or responsibility is different. If two roles behave the same way in delivery, do not invent a distinction just to make the card look more sophisticated.

Next, look at the hours each role used on comparable jobs. Do not build the card around your cleanest, fastest project, the rare one where everything simply behaved. Use a small group and look for the normal range. A straightforward homepage concept may need one amount of senior design time. Add several audiences or review groups, and the same deliverable can need much more.

Build the estimate by multiplying each role’s expected hours by its rate. The math depends on those hours being honest. A rate cannot rescue a scope that forgot project management, review, testing, handoff, or another required part of delivery.

Keep the units consistent. If your firm quotes in half days or full days, convert those units to hours internally so you can compare the estimate with capacity and actual effort. That keeps a half day from becoming a surprisingly elastic unit once the work reaches the team. When several people share a role, spell out the experience level the rate assumes.

This is also the logic behind estimating a project by effort. Both approaches start with the work the team has to deliver, not with a number somebody picked before scoping the job.

Pressure-test rates against completed jobs

Choose three to five completed projects and rebuild their original scopes with the proposed card. Use the actual hours, not the old estimates. It is a little project archaeology, but it shows you far more than another round of guessing. Compare the rebuilt result with the original quote and with the effort pattern you want the card to support.

You are looking for the places where the card tells the wrong story. Did project management vanish because nobody tracked it cleanly? Is a blended design role hiding a lot of senior review? Does the card make a routine job look overly complex, or flatten a genuinely complex job into the same shape as everything else?

Every shop has a weird job, but one oddball is not a reason to rewrite the whole card. First, work out whether the gap came from the rate, the effort assumption, scope drift, work that was new to the team, or rework. The card should fit the work your team repeats, not every strange thing that happened once. Put the unusual conditions in the estimate where they belong.

This exercise also tells you whether the role list is usable. If every project needs a custom exception, the card is probably too simple. If it has twelve nearly identical roles that nobody can choose between, it has probably gone too far in the other direction.

Account for complexity and seniority, not just role

A label can hide a big difference in effort. Configuring a familiar integration is not the same job as designing an unfamiliar architecture. Extending an approved design system is not the same job as developing the first concept. The role may be identical on the card, but the delivery is not.

Handle that difference with role levels, complexity ranges, or explicit senior review hours. Keep it readable. If the person building an estimate needs a decoder ring, the card has gone too far. “Design” and “Senior Design” may be all one firm needs. Another might keep a single design rate and size tasks as standard, complex, or exploratory.

Do not let seniority do the job of a clear task definition. A senior person may finish familiar work quickly. A junior person may need more time and review. Estimate the team setup you actually plan to use. If a junior teammate handles production with senior oversight, include both contributions.

Put the complexity in the scope assumptions too. The number of stakeholders, technical dependencies, content readiness, approval rounds, and unfamiliar subject matter can all change the effort even when the role stays the same. An approval chain can grow without changing the role name. It still changes the work.

If the work is too uncertain to size yet, use a range or a discovery phase. Calling the uncertainty a special high rate does not make it less uncertain.

Revisit the card as your effort data grows

Review the card on a regular schedule, and look again when completed jobs keep showing the same mismatch. Do not wait until it becomes the mysterious spreadsheet nobody wants to touch. Twice a year may be plenty for a firm with a stable service mix. If your services or team structure are changing, you may need to review it more often.

During the review, compare estimated and actual hours by role and project type. Suppose content strategy keeps taking more effort than expected. Do not automatically fiddle with the rate. Check the role assumption, task breakdown, client inputs, and review process, then change the part that is actually wrong.

Put a version date on the card. Every estimate should show which version it used, or older work becomes hard to interpret. Tell the people who scope projects what changed and why. A quiet update is how two people at the same shop end up quoting similar work differently, while both insist their version is current.

That same effort history matters for recurring work and retainers too. How do I quote retainers so the scope stays realistic? starts in the same place: how much monthly effort does this work genuinely require?

Treat the card as a working record of what your shop has learned, not something carved in stone and defended forever. Each quote should still trace back to the work you expect the team to perform.

FAQ

How many roles should a rate card have?

Use enough roles to capture real differences in effort and skill, and stop there. Strategy, design, development, and project management may each need a rate. If two roles demand the same effort and skill, combine them. A small shop should be able to use the card without reopening the role debate every time it scopes a job.

Should I show my rate card to clients?

You can, but most firms use the card internally to build an estimate and present one project figure instead of every line-by-line rate. Its main job is to improve your own scoping. It can do that whether or not the client sees the details.

How often should I update my rate card?

Review the card when a group of completed jobs consistently runs over or under the effort you quoted. For a stable firm, a couple of reviews each year may be enough. Revisit it sooner when your delivery history shows that the old assumptions no longer match the work.