Graphic Design Billing: How I Price Projects

Pricing is the business conversation that most designers are worst at. Design education doesn't cover it. Most designers learn by making expensive mistakes — undercharging chronically, burning out on hourly billing, or losing projects to competitors because their pricing structure was confusing.

I've rethought my pricing approach several times over my career. Here's where I've landed.

Value-Based vs. Hourly Billing

Hourly billing feels safe because it's legible. You track time, you multiply by rate, the invoice makes obvious sense. But it creates a perverse incentive structure: you're rewarded for taking longer, not for being better. And it caps your income at the number of hours you can work.

More importantly, hourly billing disconnects price from value. A brand identity that takes me forty hours might generate significantly more value for the client than forty hours of work at whatever my hourly rate is. Billing forty hours charges for my time, not for the result.

I moved to project-based pricing years ago and haven't looked back. I quote a fixed price for a defined deliverable set, based on the value the work creates and the market rate for that type of work, not on my estimated hours.

How I Estimate Projects

I start with three questions: What is this work worth to the client? What does comparable work in this market cost? What are the actual deliverables and how complex are they?

What the work is worth to the client is a strategic question about their business — a brand identity for a company raising a series A has a different value ceiling than one for a small retail shop. I price within the range the client's context supports.

Market rate is researched — I talk to other designers, follow industry salary surveys, and pay attention to what projects I hear about in professional networks.

Deliverable complexity is the practical constraint. How many logo directions? How many revision rounds? How many brand system components? These define the scope and the floor.

The Scope Document Is Everything

A fixed-price project without a detailed scope document is an invitation to scope creep. I deliver a written scope statement with every proposal: specifically what is included, what is not included, how many revision rounds are included, and what happens if revisions exceed the included rounds.

This document protects both parties. Clients know what they're buying. I know what I've agreed to deliver.

Scope creep almost always starts with ambiguity. Close the ambiguity with specificity.

Revision Rounds and Their Economics

I include two revision rounds in most identity projects. This is enough for most clients to arrive at an approved direction without being excessive. Revisions beyond the included rounds are billed at a separate rate I specify in the proposal.

This structure gives clients security (they know revision is included) without giving them unlimited revisions (which is how projects become economically unviable).

When to Require a Deposit

Always. I require 50% upfront before starting work on any project. The remaining 50% is due before final files are delivered.

This isn't about mistrust — it's about aligning incentives and ensuring I'm not carrying the financial risk of a project alone. Clients who hesitate to pay a deposit are telling you something important about whether you should take the project.

Raising Your Rates

The right time to raise rates is when you're turning down more work than you want to, when clients accept your quotes without hesitation, or when you feel underpaid relative to the value you're delivering.

The test: quote your new rate on the next project. If the client accepts, your rate is still below market. Keep raising until you start losing projects you wanted to win. That's your market rate.