Indexwriting
Writing indexNote / Jul 14, 2025

Field note / graphic design / pricing / freelance

Graphic Design Pricing: What I Charge and Why

A transparent look at how I think about pricing graphic design work — the frameworks, the variables, and the honest conversations.

Published
Jul 14, 2025
Length
2 min read / 467 words
Topics
graphic design, pricing, freelance

Price Communicates Value

Before I get into numbers: pricing is itself a form of brand communication. Designers who underprice signal to clients that the work isn't valuable. Designers who price confidently at market or above market signal that they know their work is worth it.

I've found that raising prices typically improves the quality of client relationships, not just the income. Clients who pay more tend to take the work more seriously, respect the process, and engage more thoughtfully with the output.

Project vs. Day Rate

For new clients and defined-scope projects, I quote project rates. For long-term clients and ongoing retainer work, I work on a day rate. The distinction matters because the risk profile is different.

A project rate puts the scope risk on me — if the project takes longer than I estimated, that's my problem. A day rate puts the scope risk on the client — they pay for what the work actually requires. Both models are fair; they just allocate risk differently, and the pricing structure needs to reflect which party is taking the risk.

What Drives Project Pricing

The variables that drive project cost:

Scope: number of deliverables, number of concepts, revision rounds.

Complexity: a single-color icon is not priced the same as a full brand system with custom type and guidelines.

Timeline: rush timelines cost more. This isn't arbitrary — rush work requires rescheduling other clients' work, working unusual hours, and compressing a process that benefits from time.

Client size and commercial application: large commercial clients with wide distribution pay more for the same work than small nonprofits. The value the work delivers is different.

Rights and exclusivity: work licensed for a single use is priced differently from work transferred with full IP ownership.

The Estimate as Scope Document

I never send a number without a scope description. The estimate specifies what's included: how many concepts, how many revision rounds, what formats are delivered, what's not included.

This protects both of us. When a client asks for something outside the scope, I reference the estimate and quote the addition. The number is not surprising because the scope was agreed.

Having the Pricing Conversation Directly

I've learned to have pricing conversations directly and early. Getting to the presentation stage with a client whose budget is fundamentally incompatible with the work they need wastes time for both parties.

I ask about budget in the first meeting. I tell clients my typical range for the type of work they're describing. If we're not compatible, we find out before either of us has invested significant time. This directness makes the work that proceeds much easier.