How I Price Brand Identity Projects

Pricing Is a Design Problem

How you price design work communicates something about how you value it. Hourly billing signals that you're selling time. Project-based pricing signals that you're selling outcomes. Value-based pricing signals that you understand the business impact of what you're delivering.

I've used all three models at different points in my career. Here's what I've learned.

Why I Moved Away From Hourly Billing

Hourly billing creates the wrong incentives for both sides of the relationship. For me, it rewards slow work and punishes efficiency. A designer who's faster because they're more experienced earns less per project than a slower, less experienced designer at the same rate. That's backwards.

For the client, hourly billing creates anxiety. Every email, every revision, every phone call runs the meter. The relationship becomes adversarial — the client wants to minimize time spent, the designer wants to produce quality work that takes the time it takes.

Project-based pricing solves both problems. I price based on what I know the project requires, the client knows what they're committing to, and neither of us is watching the clock.

How I Build a Project Estimate

For a brand identity project, I start with the scope: what deliverables are included, how many concepts will be presented, how many revision rounds are included, what file formats and documentation are delivered.

Then I estimate the time honestly. How many hours of research? How many of concept development? How many of presentation preparation, refinement, file production, and documentation? I multiply those hours by a rate that reflects my expertise, overhead, and the business value being created.

I don't share the underlying hourly calculation with clients. I present the project investment as a single number representing the deliverable, not a time calculation.

The Value Conversation

For significant brand identity projects — an identity for a funded startup, a rebrand for an established business, a visual system for a regional institution — I have a value conversation before scoping the work.

What is this identity worth to the business? What are the costs of the current identity problem? What would it mean for customer acquisition, employee pride, or investor confidence if the brand looked and communicated exactly right?

These conversations sometimes reveal that my initial scope estimate was too conservative. A brand identity for a company doing $20M in revenue is worth more than the same work for a startup with ten customers. The deliverables might be identical. The value created is not.

What Goes Into a Proposal

My proposals include a clear scope description, the investment, a payment schedule, what's included (revision rounds, file formats, applications), what's excluded, the project timeline, and terms.

The scope description is detailed enough to protect both parties. Vague scope creates scope creep disputes. Detailed scope creates a shared understanding of what's being built.

The Rate Conversation

I don't negotiate on quality, but I do negotiate on scope. If a client needs a lower investment, we reduce the scope — fewer concept directions, fewer revision rounds, fewer deliverables. We don't reduce the quality of what's delivered.

This framing keeps the conversation productive. It's not about whether my work is worth what I charge — it's about what the client needs and can invest in. Sometimes the answer is a smaller, more focused project that delivers excellent work within a tighter scope.

The Long Game

Clients who are treated fairly and get excellent work become long-term relationships. A brand identity client from five years ago has referred six other clients to me. The financial value of that relationship far exceeds the margin I might have gained by underpricing the original project.

Price your work honestly, deliver excellent work, and treat clients like partners. The economics work out.