Tithi Mondal

Article5 min readUpdated

Fixed Price vs Hourly Design Project: Which Suits You

Fixed price vs hourly design project: how each pricing model works, when each suits you, and how milestones and retainers control scope creep.

By Tithi Mondal, UI/UX Designer

Two ways designers charge

When you ask how designers charge, you usually hear two answers: a fixed price for the project, or an hourly rate. A third group of options, milestone payments and retainers, mixes the two.

None of these is automatically fair or unfair. Each moves risk to a different side. With a fixed price, the designer carries the risk of the work taking longer. With hourly billing, the client carries it. Understanding this helps you pick the model that matches your project.

For a general view of design budgets, see the UI/UX design cost guide.

How a fixed price project works

In a fixed price project, you and the designer agree on a defined scope and one total price. Scope means: what is being made, how many screens or concepts, how many revisions and when it is delivered.

Where it works well

  • A logo, with a set number of concepts and revision rounds.
  • A social media post pack or an icon set.
  • A presentation with a known number of slides.
  • A first app or website design where the screens and user roles are listed.

For these, you know the cost before you start. That helps with budgeting, especially for small businesses and startups where every rupee is planned.

Where it struggles

  • The scope is unclear or still changing.
  • You want to explore many directions without limits.
  • Research findings may change the plan midway.

A fixed price is only as good as the scope behind it. If the scope is vague, disagreements start later.

How hourly billing works

With hourly billing, you pay for the time the designer spends, usually tracked and reported. The total depends on how long the work takes.

Where it works well

  • Early exploration when you are not sure what you need.
  • Small, unpredictable tasks, such as fixing screens or reviewing a developer's build.
  • Work that depends on a lot of back and forth with your team.

Where it struggles

  • The client cannot predict the final bill.
  • Slow feedback from the client can raise the cost.
  • Some clients feel nervous watching the hours add up.

Hourly billing needs trust and clear reports. Ask for a time estimate, a cap or a regular update, so you stay in control.

Milestone payments: a middle path

Milestone payments split a fixed price into stages tied to progress. For example:

  1. A portion to begin.
  2. A portion after wireframes are approved.
  3. A portion on delivery of final design and files.

For small projects, the simplest version is half to begin and half on completion. That is how I work: 50% to start and 50% when the work is finished, by UPI, bank transfer or PayPal for international clients.

Milestones protect both sides. The designer gets commitment before starting. You pay in proportion to what you have seen. For larger app projects with several stages, tying payments to stages makes the process visible. The mobile app design process shows what those stages usually are.

Design retainers: for ongoing work

A retainer is a regular monthly arrangement where you reserve a set amount of a designer's time or a set list of deliverables.

It suits you if:

  • You publish social media posts every week.
  • Your product keeps releasing new features.
  • You want a designer who already knows your brand and reacts quickly.

Agree what the retainer covers: how many hours or tasks, how requests are made, how quickly they are answered, and what happens to unused time. Also agree how either side can end it, with a reasonable notice period.

Scope creep: the real issue

Whatever model you choose, scope creep is the main source of friction. Scope creep means the project grows beyond what was agreed, through small additions that each seem harmless: "Can we add one more screen?" "Can we also do a Hindi version?"

Here is how to manage it:

  • Write the scope. List screens, deliverables and revision rounds in the quote.
  • Define a revision. A revision is a change to what was agreed. A new feature is not a revision.
  • Keep a change list. When a new request arises, note it and price it separately or schedule it for the next phase.
  • Decide who approves. If three people give feedback, conflicting changes multiply. Name one decision maker.
  • Share a brief early. A strong design brief prevents many surprises.

This is not about being strict. It is about being clear, so the project stays friendly.

A small example. Say you hire a designer for a ten screen fixed price app design, and halfway you ask for a referral screen, a Hindi version and a dark mode. Each request is reasonable, and each adds screens and checks. If the quote says clearly what is included, the designer can tell you the cost of each addition on the same day, and you can decide whether it belongs in version one or version two. Without that clarity, the same conversation turns into an argument about what was promised.

The same applies to hourly work. Without a cap or regular updates, small requests quietly add hours. A short weekly message with hours used and work done keeps both sides honest.

Which model should you choose

Your situationBest fitWhy
Logo, posts, icons, presentationFixed priceSmall, clear deliverables
First version of an app or website with listed screensFixed price with milestonesKnown scope, staged payments
Unsure of requirements, early explorationHourly with a capFlexibility to learn
Weekly content or continuous product updatesRetainerSteady work and quick response
Fixing or reviewing after developmentHourlySmall, varied tasks

A simple rule: if you can list what you want, use a fixed price. If you cannot yet, use hourly for a short discovery stage, then convert to a fixed price for the real build.

What I do

For logos, posts, icons, illustrations and presentations, I give set prices. For apps and websites, I give a custom quote based on screens and user roles, with 50% to begin and 50% on completion and two to three revision rounds included. Typical app or website design takes two to four weeks.

If you are not sure which model fits, tell me what you are building and I will suggest one. You can start with the cost calculator or get in touch.

Frequently asked questions

What is a revision round?

It is one set of changes you ask for after seeing the work, within the agreed scope. A new feature or a new direction is normally treated as additional work.

Can a fixed price project still change?

Yes, but changes beyond the written scope are usually quoted separately. Agree on this before the project starts.

Is a retainer cheaper than paying per project?

Not always. It gives you steady access and faster response, which is valuable for ongoing work, but it only makes sense if you have enough regular tasks.

Should I pay the full amount upfront?

A split payment is safer and common practice, such as half to begin and half on completion. It protects both you and the designer.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.