How to write a rate card clients can understand
A good rate card fits on one page and answers one question: what will this cost me. See a sample five-line card, how to word each line, and what to leave off.

A rate card that a client cannot read is a rate card that gets negotiated line by line. The goal is a single page that lets a buyer see what you charge and roughly what a job will cost. This post shows a sample five-line card, how to write each line, and what to keep off it.
What a rate card is for
A rate card does three jobs. It saves you from re-explaining your prices to every enquiry. It lets clients self-qualify before a call. And it gives your team one reference so two people do not quote different rates for the same work.
It is not a full proposal, and it does not need to show every service you offer. Five lines are enough for a small team. If you need more than a page, your offer is probably too complicated for a first conversation.
A sample five-line rate card
Here is a sample for a small agency. All numbers are examples.
- Strategy and planning: $150 per hour
- Design: $110 per hour
- Development: $120 per hour
- Project management: $90 per hour
- Development day rate (8 hours): $900 per day
Under the five lines, add three short notes: what the rates include, how you bill (monthly in arrears, or half upfront), and how long the rates are valid.
Check the day rate. At the hourly rate for development, $120, 8 hours is 8 x $120 = $960. A day rate of $900 is $60 below that, which is $60 / $960 = 6.25% less. That is the saving you are offering for a committed full day, and it makes the day rate easy for you to justify.
How to word each line
Each line should answer "what do I get" in a few words, in the client's language.
- Name the role by the outcome. "Design" is fine. "Creative ideation services" is not.
- Give one unit per line. Hourly or daily, not both on the same line.
- Add a short parenthetical only if it removes a question. For example, "Development (includes testing)".
- Round to numbers that are easy to add. $110 is easier than $107.50.
The numbers should not be picked by feel. Build each from a cost-based formula so the rate covers your costs and a margin. The hourly rate formula takes you through it step by step.
Show clients how to use it
A card with no example leaves the client to do the math, and they may guess low. Add one worked example under the card.
Say a client needs a small campaign page. You expect 20 hours of design and 10 hours of development:
- Design: 20 x $110 = $2,200
- Development: 10 x $120 = $1,200
- Total: $2,200 + $1,200 = $3,400
Label it clearly as an example: "A typical small campaign page: about $3,400." If your real jobs are fixed-fee, say so: "Projects are quoted as a fixed fee; this card shows the rates behind them." Whether to quote fixed or hourly is its own decision, covered in how to choose a pricing model.
Add the three notes under the card
The five lines are only half the page. The notes underneath prevent most of the follow-up questions.
- What the rates include. For example: "Rates include project communication and two rounds of revisions per deliverable."
- How you bill. For example: "Invoiced monthly for hours worked, or half upfront for fixed-fee projects."
- Validity. For example: "Rates valid until 31 March; new rates apply to quotes issued after that date."
Keep each note to one sentence. If a note needs a paragraph, it belongs in your terms and not on the card.
What to leave off the rate card
A rate card is a client document. Several things belong in your own files instead.
- Your costs and your margin. Showing cost per hour invites the question "why not just pay that". Keep it internal. Gross margin is worth tracking, and how to calculate gross margin for agencies shows how, but clients do not need to see it.
- A long list of every small task. Twenty lines of "logo tweak $40" turns the page into a menu to haggle over.
- Discount tiers you have not decided to honor. Anything printed will be quoted back to you.
- Internal job titles. "Senior associate" means nothing outside your office. Use the work: design, development.
- Estimates of how long things take. Hours belong in a quote for a specific job, not on a general rate card.
- Vague "from" prices with no scope. "Websites from $2,000" attracts enquiries you cannot serve at that price.
Test the card before you publish it
Hand the draft to someone outside the business, such as a friend who runs a different company, and give them a made-up job: "You need a two-page leaflet design and a short project check-in each week for a month." Ask them to work out the cost using only the card. If they get stuck, or their answer is far from yours, the card needs a clearer unit or an example.
Do the same inside your team. Give two colleagues the same job and compare totals. If they differ, the card leaves room for two interpretations, and a client will find the cheaper one.
Keep it current
Date the card and review it twice a year, or whenever your costs change. When you raise rates, send existing clients the new card with notice, and apply the new rates to new work first. A card without a date has a way of staying in circulation for years after the numbers stopped being true.
Next step
Draft your own five lines using the layout above, then price one typical job from your last quarter with it. If the total is far from what you actually charged, find out whether the card is wrong or whether you have been undercharging.
Keep reading
- Day rate vs hourly rate: when to quote by the dayLearn when a day rate fits better than an hourly rate, how to price one from your own numbers, and see in a worked example how prep and travel change the price of a two-day workshop.
- Deposits and upfront payments: how much to ask and whenCompare three payment schedules on one $12,000 example project and see which leaves you least exposed, how big a deposit should be, and when to ask for it.
- How to structure a monthly retainer: hours, deliverables or availabilityThree retainer models, each with worked numbers: a block of hours, a fixed list of deliverables, or reserved availability. See when each fits, where each breaks, and how to guard against it.
Ready to run it all in one place?
Projects, clients, time tracking and invoicing in one platform.