How to price freelance design work and charge for scope changes

I price freelance design work by calculating a sustainable cost floor, defining the outcome and scope, then choosing a fee that reflects the responsibility and uncertainty involved. I put revision limits, client dependencies and payment milestones in writing, and require an approved change order before starting additional work.

How to calculate your minimum freelance design rate

I start with the business maths, not a competitor’s rate card. My annual revenue requirement needs to cover personal pay before tax, business costs and a reserve for gaps between projects. I divide that requirement by realistic billable days, not every weekday in the calendar. Sales calls, bookkeeping, proposals and holidays all consume capacity. Treating them as free time produces a rate that only works when nothing goes wrong.

For a worked example, assume £40,000 for personal pay, £10,000 in operating costs and £10,000 for reserves. At 120 billable days, the minimum is £500 a day. Those are illustrative inputs, not market benchmarks. If only 100 days are billable, the same business needs £600 a day. I would adjust the inputs for my circumstances and get local advice on tax treatment.

That rate is a floor for estimating, not necessarily the number on the proposal. Eight days of work at £500 gives me a £4,000 internal baseline. It does not automatically justify a £4,000 fixed fee. I still need to account for estimation risk, review effort and the commercial responsibility I’m accepting.

How to frame design value without promising revenue

Before I quote, I ask what decision or operational result the work needs to support. A redesigned onboarding flow might aim to reduce avoidable support requests, improve completion or make a new product easier to evaluate. “Make it more modern” gives me almost nothing to price against. I want a baseline, an owner for the measure and a reason the work matters now.

Suppose a client handles 200 onboarding support requests a month, each taking 15 minutes. That is 50 hours of support effort. I can use that calculation to discuss the size of the problem, but I cannot claim my design will recover all 50 hours. Product defects, acquisition quality and implementation decisions may matter more than the interface. I separate the intended benefit from the deliverables I can actually control.

Value helps me choose the appropriate depth of work and explain the fee. It is not permission to invent a return figure. I might offer a focused diagnostic or a larger design engagement, each with a different decision it enables. I skip decorative package tiers where the only meaningful difference is how many screens I promise.

When to use a fixed fee, day rate or paid discovery

I use a fixed fee when I can describe the output, dependencies and acceptance process with reasonable confidence. I use a day rate when the client needs capacity and will actively manage priorities. When the problem itself is unclear, I prefer a paid discovery phase with its own deliverables. That might produce a workflow map, a prioritised problem list and a grounded estimate for the next phase.

Returning to the eight-day example, I might allow two additional days for review and known uncertainty, producing a £5,000 fixed fee. That is an estimating decision, not a universal contingency percentage. I would not use those two days to absorb an undefined research programme or a second product. If the uncertainty could double the effort, I would narrow the engagement before fixing the price.

I also make the trade-off visible. A fixed fee buys an agreed result within stated boundaries. A day rate buys time, not an unlimited output commitment. I avoid a fixed price attached to a backlog the client can expand indefinitely. That arrangement transfers the uncertainty to me while leaving the client in control of its size.

What to include in a design project scope

I use the Aiga standard agreement as a structural reference: the project proposal and the contractual terms do different jobs. My proposal explains the actual engagement. The terms address matters such as payment, rights and termination. I treat the Freelancers Union contract tool as another starting point for making obligations explicit, not as a substitute for legal advice in the jurisdiction governing the work.

For an illustrative onboarding project, I would specify one existing customer type, one platform and the states included in the flow. I would name the deliverables, such as a flow diagram, annotated designs and a handover session. I would also state exclusions: production code, recruitment, copywriting, additional languages and unrelated account settings. A screen count alone is a weak boundary because one screen can contain several difficult behaviours.

I define a revision round as one consolidated response from the named approver, submitted against the agreed brief. Two rounds means two rounds, not two rounds per stakeholder. I set client deadlines for access, content and feedback, and explain how delays affect scheduling. Acceptance should refer to the agreed deliverables and requirements. I won’t make payment depend on an undefined promise that everyone will be happy.

How to write and price a design change order

I distinguish a correction from a change. Missing a state explicitly included in the brief is my problem to fix. Adding a second customer type, reversing an approved direction or requesting another research round changes the agreement. Feedback is not automatically additional scope. I compare the request with the written boundary before discussing money, otherwise every review risks becoming a negotiation.

My change order records the requested addition, affected deliverables, extra fee, revised dates and any new dependencies. For example: “Add administrator onboarding, including three additional states and one consolidated review round. Additional fee: £1,250. Delivery moves from 14 October to 17 October, provided approval arrives by 8 October.” The numbers are illustrative. I estimate the extra work, including rework and coordination, rather than charging only for drawing time.

I require written approval from the authorised client contact before starting the addition. If the budget cannot move, I offer a scope swap and document what comes out. If the deadline cannot move, I explain what can realistically fit. I don’t quietly do the work and argue over the invoice later. A change log makes those decisions easier to track.

How to set payment terms and check project profitability

I connect invoices to observable milestones. For a £5,000 engagement, an illustrative schedule is £2,000 before booking, £2,000 on delivery of the agreed design direction and £1,000 at handover. I state payment due dates, applicable taxes, expenses and what happens if payment is late. Any provision about rights transferring after payment needs to match the contract and local law, not an assumption tucked into an invoice.

During delivery, I track time even when I’m not billing by the hour. I separate planned production, reviews, client delays and approved additions. At completion, I compare the fee with actual effort and direct project costs. A £5,000 fee over ten days is £500 a day before those costs; over fourteen days it falls to about £357. That difference tells me whether my estimate or boundaries failed.

I also record why the estimate moved. If stakeholder coordination consumed three unexpected days, the next proposal needs a clearer approval process or a coordination allowance. If my own execution was slow, that is not automatically billable to the client. I change the relevant assumption rather than adding a vague surcharge to every future quote.

Questions people ask

How much should I charge for freelance design work?

I calculate a minimum rate from annual revenue needs and realistic billable capacity, then estimate the engagement. I adjust the quote for scope, uncertainty and responsibility rather than treating an online average as my price.

Is it better to charge hourly or per project for design?

I charge per project when the deliverables and approval process are clear. I use time-based pricing for changing priorities, with a spending limit and regular reviews so the client can control the budget.

How many design revisions should I include?

I include the number the decision process actually needs, often two consolidated rounds for a tightly scoped engagement. I define a round and distinguish revisions within the brief from requests that change it.

How do I charge a client for extra design work?

I explain which agreed boundary the request changes, then send a written change order with the fee and schedule impact. I wait for approval before starting, or agree an explicit scope swap if the budget is fixed.

Where I checked my thinking

• Aiga standard form of agreement for design services
• Freelancers Union contract tool