Every founder I know who's worked with a developer on hourly rate eventually has the same complaint: the meter never stops. Every question costs money. Every scope clarification costs money. The thing they bought was supposed to be a product; what they got was a relationship where the cheapest move is silence.
I quote fixed-scope, milestone-based. Not out of principle, out of math. Here's the case, and the exception.
The hidden cost of hourly
Hourly feels safe in the moment. You pay only for time worked, you can stop anytime, no commitment. The problem is what it does to the incentives inside the project.
Under hourly:
- Every question is billable. So the founder stops asking. The developer ships what they think was asked, not what was needed.
- Clarifying scope takes time. Time is billable. So scope stays vague. Vague scope balloons.
- The developer has no reason to ship faster. More hours is more revenue. The honest ones don't pad. The rest don't have to pad — they just work at a leisurely pace and call it senior judgment.
- There's no Friday. No point in the week where the work is done and you can look at something. The project is a subscription, not a project.
At the end you have a mountain of Toggl entries you can't audit, a product that almost does the thing, and a conversation about "how much longer" that never ends.
Why fixed-scope flips the incentives
Fixed-scope, done honestly, inverts every one of those problems:
- Questions are free. I'd rather clarify the spec for an hour and save a week of rebuilding than bill you for the confusion.
- Scope is written down and signed. Changes are possible — they just need a written change request with a new price and timeline. No silent drift.
- I want to ship faster. If I'm efficient I earn more per hour of actual work. If I underestimate, I eat it. My incentives match yours.
- There's a Friday. Every milestone ends in a demo you can open in a browser. Continue or walk away — your call.
I earn more on good projects, less on the ones I misjudged. Averaged out, it works. More importantly, nobody's watching the clock.
What "fixed" actually means (and doesn't)
"Fixed price" is a phrase agencies abuse. Three things have to be true for it to be honest:
-
The scope is written down before the quote is given. Specific flows, specific features, specific integrations. Not "build me an MVP." If a developer quotes off a vague description, they're either padding for uncertainty or they'll come back later with "that wasn't included."
-
Scope changes go through a written change request. Same format as the original quote, just smaller. Price and timeline adjustment in writing, signed, before work on the change starts. No surprise invoices, no "oh that's extra" at delivery.
-
The quote is broken into milestones with shippable deliverables. "Fixed €30K paid at the end" isn't a fixed-price project, that's a trust fall. "Fixed €30K split into six €5K milestones, each ending in something demoable" is a real commitment, on both sides.
Any of the three missing, and the quote is a story, not a price.
When hourly genuinely wins
Four cases where hourly is the right structure and I'll tell you so:
- You have senior developers and just need extra hands. Team augmentation, contractor joining sprints, unblocking hard features. Scope is too dynamic to predict, the team's conventions are the boss. I quote weekly retainers (€4.5K/wk in my case) instead of per-project.
- The work is genuinely exploratory research. "We want to see if X is possible." You're buying the exploration, not a product. Fixed-scope would just be pretending to know the answer already.
- You're making very small incremental changes to a product you already own. 2-hour fixes, post-launch tweaks. Writing a scope doc for a €300 fix is absurd.
- You're in an ongoing, trust-built relationship. Year three with the same developer, quarterly budget, known velocity. Hourly and retainer converge; either works.
Everything else — new builds, rebuilds, feature launches, MVPs — is a fixed-scope problem. Treating it as hourly is giving up before you start.
How to press for a fixed quote
Sometimes a developer says "I only do hourly." That's a data point, not a wall. Try this:
Write a one-page spec yourself first. The three user flows you need, the single success metric, the integrations, the deadline. (I wrote more about this in what a custom SaaS MVP actually costs.) Now you have something to quote against.
Ask for a time estimate in hours. If they say "maybe 80 hours," you can say: "OK, at your rate that's €X. Would you be willing to commit to that number fixed, for this exact spec, with change requests for anything new?" Most developers who "only do hourly" will say yes when the scope is crisp. The ones who won't — walk away. You've learned something.
If fixed-scope isn't available, demand milestones. Even under hourly, you can structure the engagement as: "€5K cap per 2-week sprint, each sprint ends in something shippable, we renew or stop at the end." That's not true fixed-scope, but it gives you the escape hatch. It's what hourly engagements look like when both sides are acting in good faith.
The psychological benefit nobody talks about
Fixed-scope has a weird second-order effect: you relax. You stop thinking about the meter. You stop timing meetings. You ask the questions you actually need answers to. You start treating the developer as someone you're building with, not something you're renting by the hour.
I noticed this with my own clients. The first-time fixed-scope client is always nervous in week one. By week three, they're emailing me half-formed ideas at 11 pm because they know there's no invoice attached. The work gets better. The relationship gets better. The founder stops resenting the project.
You're not paying for that peace, it comes with fixed-scope for free. But it's the part that, a year in, you'll notice most.
If you want a fixed quote against your idea, send me a rough brief and I'll come back with milestones and a number. No pressure; if the fit's wrong I'll say so. Book a 20-min call.