How do I price a backlog audit?
7 min read · Updated
Price a backlog audit as a fixed-fee product tiered by backlog size, not as billed hours. The audit has a defined input (an export), a defined output (a report), and an automatable middle; that shape productizes, and productized work earns margin that hourly work structurally can’t.
The numbers below are illustrative math to structure your own pricing, not market rates. What matters is the model: size-banded tiers, value anchoring, and a delivery cost you actually know.
Why fixed-fee and not hourly?
Because hourly pricing makes your efficiency the client’s discount. If scoring the backlog takes you a day instead of three weeks, hourly billing hands the entire gain to the buyer and invites time-metering (“why did the audit take 30 hours?”). Fixed-fee pricing lets the conversation be about the deliverable and its value, keeps the quote to one number, and rewards you for every improvement you make to your own process. The prerequisite for fixed-fee confidence is a predictable delivery cost, which is what automated scoring gives you.
How do I tier by backlog size?
Size bands make scoping a single question (“roughly how many stories?”) instead of a discovery call. A workable three-band structure:
- Up to 500 stories: a team-level backlog; one report, one readout.
- Up to 2,500 stories: a product or program backlog; adds quality-by-epic hotspots to the readout.
- Beyond 2,500: portfolio scale; price the band custom, because the readout audience (multiple teams, a PMO) changes more than the scoring cost does.
Note what the bands price: the analysis and readout surface, not the scoring effort. Automated scoring makes a 20,000-story backlog barely more expensive to score than a 2,000-story one; what grows is the curation and the audience.
What belongs in each tier?
- Baseline: full-coverage scoring, the white-labeled written report, and the complete per-story dataset as a spreadsheet.
- Standard: adds a live readout with the sponsor, plus hand-written rewrites of the 10 worst stories (the artifact teams circulate afterward).
- Premium: adds a second scoring round after the client’s team revises, with the round-over-round improvement section in the final report. This is the tier that sells the follow-on engagement by itself, because it ends with measured progress instead of a snapshot.
What do I anchor the price against?
Against what the audit prevents and precedes, never against your hours. Two anchors work in the room. First, the delivery spend the backlog is about to drive: a six-person team building for six months from a weak backlog is a large number, and an audit priced at a fraction of one sprint reads as cheap insurance. Second, the cost of the failure mode: every story the audit flags as untestable or oversized is a candidate clarification thread, rework loop, or escaped defect. You don’t need invented statistics for this anchor; walk the client through three of their own worst stories and let them price the damage themselves.
What does delivering the audit cost me?
Two inputs: scoring and judgment. With Vindex for Agencies, scoring is priced in prepaid credits at 1 credit per unique story per project, with every re-scoring round of that story included free; the exact cost is shown before each run, and credits never expire. Your judgment (curation, notes, the readout) is the fixed block of senior time per tier. Both inputs are known before you quote, which is what makes the fixed fee safe. Pricing for the credits themselves is on the pricing page.
Should the audit ever be free?
Discounted as a wedge, yes; free, rarely. A paid audit, even modestly priced, gets a readout meeting with a sponsor who takes the findings seriously; a free audit gets forwarded. The exception is a live pursuit where the audit replaces a capabilities deck: a scored slice of the prospect’s own backlog is a more persuasive pitch than anything about you. Cap the free version at a slice, keep the branded report for paying clients, and let the premium tier’s re-score round convert the audit into the ongoing engagement.
Related guides
Scope creep on fixed-bid work starts in the requirements, not the change requests. How agencies and consultancies catch vague, oversized stories before signing, and put evidence behind every scope conversation.
Split an inherited backlog three ways before you price it: what you can size, what needs one question answered, and what cannot be sized as written. How to quote each bucket and present the split as rigour rather than hedging.
