Fixed price, hourly or a dedicated developer: which model suits your agency?

Three ways to buy development from a white-label partner, what each one is good and bad at, and how to choose the right model for each client project.

When an agency starts working with a development partner, the first commercial question is how to pay for the work. There are three common answers: a fixed price per project, an hourly rate, or a dedicated developer on a monthly fee.

None of them is better in general. Each one suits a different kind of work, and most agencies end up using more than one. The mistake is picking one model and forcing every project into it.

Fixed price: you buy an outcome

You agree a scope, a price and a delivery date. The partner carries the risk of the estimate being wrong.

Good for:

  • Websites and builds with approved designs
  • Client portals and MVPs with a clear feature list
  • Work you have already quoted to your client at a fixed price

Watch out for:

  • Vague scope. A fixed price is only as good as the specification behind it. If the brief says “user dashboard”, you and your partner may be imagining very different things.
  • Change requests. Every new idea from the client becomes a separate conversation about cost. That is fair, but it slows things down if the client is still working out what they want.
  • Padding. A partner carrying all the risk will price that risk in. On a well-defined project the padding is small. On a vague one, it is not.

How to make it work: agree the scope in writing, including what is not included. Split larger projects into stages, each with its own price, so neither side is guessing months ahead.

Hourly: you buy time

You pay for the hours worked, usually reported weekly or monthly.

Good for:

  • Bug fixes and small changes on existing sites
  • Work where the scope genuinely cannot be known in advance, such as investigating a performance problem
  • Early discovery work before a fixed-price quote

Watch out for:

  • Open-ended cost. Without a cap, a small job can drift. Ask for an estimate and a “check in with me before going over X hours” rule.
  • Reporting. Hourly billing needs a clear record of what each hour was spent on. If you cannot explain the invoice to your own client, the reporting is not good enough.

How to make it work: agree a monthly cap, a minimum time unit (15 or 30 minutes), and a short note against every block of time.

Dedicated developer: you buy a person’s month

A developer works only on your accounts for a fixed monthly fee. They join your stand-ups, learn your coding standards and get to know your clients’ systems.

Good for:

  • Agencies with a steady flow of development work
  • Long-running products and retainers
  • Teams that want someone who knows the history of every client site

Watch out for:

  • Quiet months. You pay whether or not there is work. Only commit when your pipeline can keep one person busy most of the time.
  • Single point of failure. If one person holds all the knowledge, illness or holidays become a problem. Ask your partner who covers when your developer is away.
  • Lock-in. Check the notice period. A month’s notice is reasonable; longer terms should come with a lower rate.

How to make it work: treat the developer like a member of your team. Give them access to the same tools, a clear backlog and a named person to ask questions.

A simple way to choose

Ask three questions about each piece of work:

  1. Can you write down exactly what “done” looks like? If yes, fixed price is usually the cleanest option.
  2. Is the work a stream of small tasks rather than one project? If yes, hourly with a cap, or a block of monthly hours.
  3. Will you have roughly a full-time person’s worth of work for the next six months? If yes, a dedicated developer is often the best value and the least management effort.

Plenty of agencies combine them: a dedicated developer for their main retainer clients, fixed-price projects for new builds, and a block of hours for care plans.

Comparing quotes fairly

When you compare partners, compare like with like:

  • Fixed price: check what is included. Testing, deployment, documentation and a bug-fix period after launch all cost time. A cheaper quote may simply leave them out.
  • Hourly: compare the rate and the reporting. A lower rate with no visibility is not cheaper if hours drift.
  • Dedicated: ask how many hours a month you actually get, what happens during public holidays, and who covers absences.

Start small, whichever model you pick

Whatever model you settle on, start with a small paid pilot task. One or two weeks of real work tells you more about a partner’s code, communication and reliability than any sales call. Once the pilot goes well, choosing the model for the next project gets much easier, because you know who you are working with.

How we handle it

At The Ahmad Group we offer all three: fixed-price projects, monthly blocks of hours, and dedicated developers with 30 days’ notice. New partners start with a fixed-price pilot task, so you can judge the work before deciding how to continue.

Not sure which model fits your next project?

Send us the brief. We will tell you which model we would suggest, and why, before you commit to anything.

WhatsApp us