Blog · · 4 min read
Fixed-price vs hourly: the visibility each one needs
Hourly makes you watch progress; fixed-price makes you watch scope and milestones. What to monitor under each — and the rhythm that fits both.
Fixed-price and hourly contracts don't just allocate risk differently — they change what you need to see. Hourly puts delivery risk on you, so you need progress-per-time visibility. Fixed-price puts it on the contractor, so you need scope, quality, and milestone visibility instead. Most visibility failures with contractors come from watching the wrong thing for the contract you signed.
TL;DR
Hourly: you carry the risk of slow progress — watch outcomes against invoiced time, weekly, grounded in real activity (never surveillance). Fixed-price: the contractor carries delivery risk, so they'll protect margin under pressure — watch scope drift, quality shortcuts, and milestone trajectory. Both models need the same backbone: a weekly outcomes update agreed at kickoff, landing somewhere you'll actually see it.
What are you actually buying under each model?
Under hourly, you're buying time and absorbing the uncertainty about how much of it the work needs. If the task takes three weeks instead of one, that's your budget. Rational hourly visibility therefore asks: is time converting into progress at a sane rate?
Under fixed-price, you're buying an outcome at a known cost, and the contractor absorbs the overrun. Which sounds safer — until you notice how a rational contractor protects a squeezed margin: trimming the invisible work (tests, edge cases, cleanup), reinterpreting ambiguous scope downward, or going quiet while trying to fix a bad estimate privately. Rational fixed-price visibility asks: is the outcome still the one I specified, arriving when promised, built to last past the invoice?
Same contractor, same project — two different dashboards.
What should you watch on hourly work?
Outcomes against time, at a weekly grain. Concretely: a weekly update of what's done (grounded in actual activity — commits, completed tasks, shipped items), read next to the hours on the invoice. You're pattern-matching across weeks, not auditing days: fifteen hours that produced "investigated several approaches" is fine once and a conversation the third time.
What this deliberately isn't: screenshot software, keystroke counters, or activity scores. Surveillance tools measure presence, not progress — a contractor can look busy all week and ship nothing, or disappear for two days and return with the hard problem solved. Worse, monitoring poisons the relationship with your best people, who have options and use them. Outcome visibility gives you better information at zero trust cost.
The red flag worth acting on: hours flat or climbing while visible outcomes shrink, for two-plus consecutive weeks. Not proof of a problem — proof of a conversation.
What should you watch on fixed-price work?
Three things surveillance could never catch:
- Scope drift. Ambiguity always resolves toward the cheaper interpretation when margin is squeezed. Weekly outcome updates surface the interpretation gap while it's still a conversation — "wait, does 'search' include filters?" — instead of at delivery.
- The quiet middle. Fixed-price engagements fail in a characteristic shape: enthusiastic start, long silence, then a flurry of bad news near the deadline. The silence is the signal — it's usually where a wrong estimate is being privately wrestled. A standing weekly rhythm makes the quiet impossible to miss in week two instead of week seven.
- Milestone trajectory. Break anything over two weeks into visible milestones and watch the trajectory, not the promises. "Milestone 2 slipped three days" in week three is planning; discovered in week eight it's a crisis.
What works for both models?
The backbone is identical, which is convenient if you run a mixed bench: a weekly, outcomes-first update, agreed at kickoff, landing in one place you actually look. Set it up before work starts — the contractor kickoff checklist makes it one line in the working agreement — and it reads as professionalism rather than distrust under either contract.
This gets more valuable the more contractors you run, because the formats line up and patterns pop — the whole argument of managing multiple freelancers without becoming a PM. It's also exactly what WorkedOn's business side automates: each contractor's real activity becomes a weekly update in a consistent shape, hourly and fixed-price people side by side, with blockers visible the day they appear. You watch outcomes; nobody gets surveilled; the contract model becomes a pricing detail instead of a visibility problem.
And if you're weighing whether the next hire should be a contractor at all, the contractor-vs-employee cost model covers the coordination overhead that rarely makes it into the rate comparison.
FAQ
Do fixed-price contracts mean I don't need progress updates?
No — they change what updates are for. You're not verifying hours; you're catching scope drift and quality shortcuts early, and confirming the milestone trajectory before the deadline reveals it.
How do I verify hourly work without surveillance software?
Watch outcomes against time, not activity: a weekly update grounded in real work (commits, completed tasks, shipped items) next to the invoiced hours. Patterns over weeks tell you far more than screenshots ever could.
Which contract type is safer for a first engagement?
Fixed-price for well-specified, bounded work; hourly for exploratory or evolving work. The bigger safety lever is the same for both: a weekly visibility rhythm agreed at kickoff.
What's the visibility red flag under each model?
Hourly: hours climbing while visible outcomes stay flat across multiple weeks. Fixed-price: a long quiet middle — silence until near the deadline usually means a discovery you'll hear about too late.