I've spent decades on both sides of the consulting table. The worst engagements have one thing in common: the customer can't see what the work actually cost, hour by hour. The best ones have the opposite - a shared, boring, accurate record of time.
Why 'value-based pricing' hides problems
Projects that bill by 'value' or by phase are un-auditable. When a milestone slips, you can't tell whether the work was genuinely harder, whether the estimate was fantasy, or whether the team was somewhere else. You argue about vibes.
Per-hour with an open log isn't about being cheap - it's about being checkable. Every engineering manager's job gets easier the moment they can see what their hours bought this week.
What a useful hours log looks like
- One entry per task, tied to the code or PR it produced
- Logged continuously, not reconstructed at month-end
- Visible to the customer in real time, not in a surprise report
- Reviewed together in a weekly demo - 'here's what we did, here's what's next'
What goes in the demo
A transparent log is only half of it. The weekly demo answers: What changed? What was measured? What's next? If a consultant can't show you merged PRs, dashboards and runbooks every week, the log alone won't save you.
We show the hours because the work stands up to inspection. If a vendor balks at showing theirs, ask why.
Next time you hire an engineering vendor, don't ask for a discount - ask for the log. The right partner is happy to show it.