# Should an agency bill accessibility remediation per fix or flat fee? | A11yShieldHQ

Source: https://a11yshieldhq.com/blog/2026-10-09-agency-accessibility-remediation-billing-per-fix-or-flat-fee.html

[Home](../index.md) / Client acquisition


Published October 9, 2026

Bill per fix when the scope is small, known, and measurable; bill flat when the site is large, the issues are systemic, or the client needs budget certainty. The billing model that fails is the one chosen before the audit, so price the remediation only after you have seen the findings.

## Why per-fix billing breaks at scale

Per-fix billing starts as the fairest deal in the room: the client pays for exactly what gets fixed, nothing more. It works when the audit finds forty issues, all documented, each with a clear owner. It falls apart when the audit finds four hundred issues, because the counting itself becomes the work. Every finding needs a definition of done, every edge case becomes a negotiation, and the client starts auditing your invoice instead of your work. The relationship turns adversarial at exactly the moment it needs to be collaborative.

The deeper problem is that per-fix billing rewards the wrong behavior on both sides. The agency is paid for volume, so there is a quiet incentive to split findings rather than solve them. The client is paying per unit, so there is a quiet incentive to dispute severity rather than fund fixes. Neither side says this out loud, which makes it worse. The invoice meeting becomes a courtroom, and accessibility work that should take six weeks takes six months of change orders.

There is one more trap: per-fix pricing punishes efficiency. The agency that builds a reusable fix for a repeated pattern, say a keyboard trap in the theme's modal component, has just reduced its own invoice. The agency that hand-fixes every instance earns more. A pricing model that taxes your best work is a model that teaches your team to stop doing their best work. If you bill per fix, bill the pattern once and the instances at a token rate, or you will train your people to be slow.

## What flat fees hide

Flat fees solve the counting problem and create a scope problem. The client loves the number on the proposal. Then the audit reveals that the "simple product page fixes" include a third-party reviews widget with its own shadow DOM, a checkout extension nobody owns, and a mobile nav built in 2019 that needs a rebuild, not a patch. The agency eats the difference, the team quietly rushes, and the quality of the last twenty fixes is visibly worse than the first twenty. Flat fees do not remove risk; they concentrate it on the agency.

The way out is to price the flat fee from a real audit, never from a sales call. The engagement should be two phases: a paid assessment that produces a findings inventory, then a flat remediation quote built on that inventory, with explicit carve-outs for third-party code and platform limitations. Clients accept this structure because they have seen the list. They know what the fee covers. The argument happens once, up front, instead of on every invoice.

Build the escape hatches into the contract anyway. A flat fee should name what happens when a finding requires work outside the agency's control: the app vendor that needs six weeks to ship an accessible update, the checkout flow Shopify will not let you touch, the theme update that reintroduces fixed issues. These are not edge cases; on Shopify stores they are the job. Name them, price them separately, and nobody is surprised.

## The hybrid most agencies land on

The agencies that do this well end up with a hybrid: a flat base fee for the known findings from the audit, a per-pattern rate for repeat issues discovered during remediation, and a capped change budget for surprises. The base fee gives the client budget certainty on the bulk of the work. The per-pattern rate keeps efficiency rewarded: fix the modal component once, apply everywhere, get paid for the pattern and a reduced rate per instance. The change budget, usually ten to fifteen percent of the base, absorbs the unknowns without a new contract.

One discipline matters more than the model: never let remediation start before the audit is signed off. The client must see the findings inventory, agree on severity, and agree on the billing treatment of each bucket before anyone opens a code editor. That meeting is the real deliverable of the assessment phase. Agencies that skip it spend the engagement re-litigating what was agreed; agencies that run it well spend the engagement fixing things.

The billing question is really a trust question. Per-fix says we do not trust each other enough for a single number. Flat says we have done the homework that makes a single number honest. Do the homework first, and either model can work. Skip it, and neither will.

## Frequently asked questions

### Is per fix or flat fee billing better for accessibility remediation?

Each suits a different situation. Per fix billing is clear for a small, well defined list from one audit. Flat fee suits an ongoing remediation program where findings arrive over time. The deciding factor is predictability for the client and a scope both sides can point to when new findings appear.

### What should a remediation quote always include?

The findings covered, the standard they will be fixed to, how fixes will be verified, and what happens when testing reveals deeper template problems. A quote without a verification step is a promise nobody checks.

### How do agencies avoid scope fights over remediation billing?

By logging every fix against the original finding it closes and pricing new categories of work separately, in writing, as they appear. Most disputes come from silent scope growth, not from the billing model itself.