WordPress Development
Dedicated Developer vs Hourly vs Per-Project: Which Model Fits Your Agency?
Hourly, per-project or a monthly plan? A comparison of the three white label billing models on cost predictability, margin risk and admin load, with five questions to pick the right one.
You have decided to outsource development. Now a provider asks whether you want hourly, per-project or a dedicated WordPress developer monthly, and the honest answer is that you do not know yet. Choosing wrong is expensive in a way that is invisible for about two months and then obvious all at once.
This post compares the three billing models on cost predictability, margin risk, admin load and the type of work each suits, then gives you a way to pick based on your own pipeline data.
The three models at a glance
| Hourly | Per-project | Dedicated monthly | |
|---|---|---|---|
| Typical published pricing | $50–$99/hr | Quoted per build | From about $2,900/mo for a junior; hour blocks about $749–$3,999/mo |
| Cost known upfront | No | Yes, until scope changes | Yes |
| Who carries estimate risk | You | The provider | Shared |
| Admin overhead | High — approvals per task | Medium — one negotiation per build | Low — one invoice, one backlog |
| Flexibility mid-project | High | Low | High |
| Waste risk | Scope creep | Padded quotes | Unused hours |
| Best for | Sporadic small fixes | One-off builds with locked scope | Continuous, varied workload |
Those pricing figures are published rates at the time of writing across the white label market, useful as a sanity check rather than a quote.
Hourly: flexible, and quietly the most expensive
Hourly billing is the easiest to start and the hardest to run a business on. It suits genuinely sporadic work — a plugin conflict here, a template tweak there — where committing to a monthly fee would waste money.
The problems appear once volume grows. There is no cost ceiling, so every client quote you write is an act of faith. Each task requires an estimate, an approval and an invoice line, which is administrative work nobody is paying you for. And the incentives are mildly wrong: a provider billing by the hour has no financial reason to finish quickly, even if most are professional enough not to act on that.
Use hourly below roughly 10 hours a month. Above that, the effective rate inside a monthly plan is usually far lower — mid-$30s per hour rather than $50–$99 — and the admin disappears.
Per-project: clean on paper, brittle in practice
Fixed-price project work moves estimate risk onto the provider, which sounds like the best deal available. It is, for a genuinely locked scope: a marketing site rebuild from a signed-off Figma file, a defined migration, a specific plugin build.
Two things break it. First, WordPress projects rarely stay locked. The client sees the staging site and wants a filter on the archive. That is a change request, which means a renegotiation, which means delay and friction at exactly the point you want momentum. Second, the provider prices in a risk buffer, so you pay for uncertainty whether or not it materialises.
Per-project works well as a first engagement with a new partner, because it caps your downside while you evaluate them. It works badly as a permanent operating model for an agency with continuous delivery. Scoping discipline is what keeps it viable — our post on WooCommerce build scoping shows how much detail a fixed price really needs.
Dedicated WordPress developer monthly: predictable capacity
A monthly arrangement buys a band of capacity rather than a list of tasks. You pay a fixed fee, assign whatever mix of work you have, and get a known cost you can quote against for the whole quarter.
There are two shapes of this in the market. A true dedicated developer retainer assigns one named person to you full-time, with published pricing commonly starting around $2,900 a month for a junior. A monthly hour block gives you a band of hours delivered by a team, typically from about $749–$799 for 15–20 hours up to about $3,999 for 100–120 hours.
The hour block usually wins for agencies, for one reason: skill coverage. A single dedicated junior cannot build a custom block theme, debug a WooCommerce subscription flow and clean a malware infection equally well. A banded team plan can route each of those to someone appropriate. mb3techs plans run $699 for 15–20 hours, $1,199 for 30–35, $1,899 for 50–60 with full builds and two stacks, and $3,599 for 100–120 with a dedicated lead developer and proposal support — the details are on the dedicated monthly plans page.
The genuine downside is unused hours in a quiet month. Size to your median, not your peak, and the exposure stays small.
Choosing: five questions about your own pipeline
- What is your median monthly development requirement? Under 10 hours, stay hourly. Between 15 and 120, a monthly band fits. Consistently above that, consider a dedicated arrangement or a hire.
- How much does it vary? A narrow range suits per-project or a dedicated developer. A wide range strongly favours a monthly band you can flex work into.
- How many stacks and disciplines does your work touch? More than two, and a single dedicated developer will be a bottleneck.
- How locked is your typical scope? If clients routinely change their minds mid-build, fixed-price work will cost you margin in renegotiation and goodwill.
- How much admin can you absorb? Hourly generates approvals, per-project generates negotiations, monthly generates one invoice and a backlog. Value your own time honestly.
Most agencies with steady client work land on a monthly band, keep a per-project option for large one-off builds outside the plan, and stop using hourly entirely. The full model landscape is covered in the white label WordPress development guide for agencies.
A quick margin illustration
Say you deliver 45 hours of development in a month. At $70 an hour billed hourly, that is $3,150 of input cost. On a 50–60 hour band at $1,899 the same work costs you $1,899, with no per-task approvals and a fee you knew in advance. On $9,000 of client revenue that is the difference between roughly 65% and 79% gross margin — before counting the hours you did not spend chasing estimates.
The caveat is symmetrical. Deliver only 12 hours that month and the hourly route costs $840 against the same $1,899. The model only pays when the volume is really there, which is why the median matters more than the peak.
Switching models without disruption
If you are moving from hourly to monthly, do not migrate everything at once. Run one month in parallel: put the predictable maintenance and small-feature work into the plan, keep active fixed-price builds where they are, and track hours consumed against the band. You will know within a month whether you sized correctly.
Two structural details make switching low-risk. Month-to-month terms with 30 days notice mean a wrong band costs one month, not a year. And billing frequency is a lever once you are settled — quarterly prepayment commonly saves 10% and annual 15%, which on a mid-tier plan is meaningful money for a decision you have already tested.
If the underlying question is whether to outsource at all rather than which model to use, white label vs in-house WordPress developer runs the comparison against hiring, and the 2026 cost breakdown has the full pricing tables. What is covered under each engagement type is listed on the white label WordPress development service page.
Frequently asked questions
Can I combine models?
Yes, and most established agencies do. A monthly band covers continuous work while occasional large builds are quoted separately as projects. Agree upfront how work is allocated between the two so a big build does not quietly consume your retainer hours.
What if I outgrow my plan mid-month?
Ask how overage is handled before you sign — some providers bill extra hours at an hourly rate, others ask you to upgrade the band. Either is workable; discovering the policy during a launch week is not.
Is a dedicated developer better than a team plan?
Only when your work is high-volume and narrow. One person gives you deep familiarity with your codebase but a single skill profile and no holiday cover. A banded team plan trades some continuity for breadth, which suits most agency portfolios better.
How do I quote clients against a monthly plan?
Price on client value, not on your cost per hour. Internally, track hours consumed per client so you can see which accounts are eroding margin. Agencies commonly target 50–70% gross margin on outsourced development after briefing and review time.
Does a monthly plan lock me in?
It depends on the provider. mb3techs plans are month-to-month with no lock-in and 30 days notice to cancel, with prepayment discounts optional rather than required. Treat any mandatory annual commitment before a trial as a pricing risk you are taking blind.
If you want to work out which band matches your median workload, the hour tiers and what each includes are published on the dedicated plans page.
// related