How should an agency price an accessibility monitoring retainer for Shopify clients?

Price the monitoring retainer on store complexity, not client revenue. A retainer that names its tiers, its included work, and its reporting cadence is easy to sell and easy to deliver. A retainer priced by gut feel turns into unpaid scope creep by month three.

Price the vigilance, not the audit

An audit is a project with a beginning and an end. Monitoring is the work that keeps the audit's results true: monthly scans, regression checks after theme and app changes, and a human review of what the scanners cannot see. Clients understand this distinction when you state it plainly. The pitch is simple: the audit fixed the known problems, the retainer makes sure they stay fixed while the store keeps changing.

This framing also sets the right anchor. If the audit cost the client several thousand dollars, a monthly retainer that is a fraction of that feels like insurance, not a second purchase. Agencies that pitch monitoring as a new project get compared to the audit price. Agencies that pitch it as protection for the audit investment get compared to the cost of a demand letter.

Tier by store complexity, not by revenue

Three tiers cover almost every Shopify client. The variables that matter are the number of templates, the number of installed apps, how many languages or markets are live, and how often the store changes. A 12-template store with five apps and one market is a small tier. A 40-template store with 25 apps, three markets, and weekly content changes is a large tier. Revenue is a poor proxy, because a high-revenue store with a clean, stable theme costs less to monitor than a mid-revenue store with an app for everything.

Write the tier boundaries into the proposal. When a client crosses a boundary, for example by adding a second market or installing a review app that injects widgets across every product page, the price moves up at the next renewal. Stated boundaries make the increase a contract term, not a negotiation.

Name exactly what the retainer includes

The most common retainer failure is ambiguity. List the included work: the monthly automated scan with a diff against baseline, the quarterly manual spot check, regression checks within a set number of business days after theme updates or app installs, and the plain-language report the client files. Then list what it does not include: remediation work, emergency fixes after a demand letter, and audits of entirely new builds. Excluded work is quoted separately, which keeps the retainer profitable and the upsell natural.

Also name the response time. Monitoring without a response commitment is just watching. A commitment like "critical regressions flagged within two business days" turns scans into a service and gives the client's legal team something concrete to point at.

Build the price from real hours and real costs

Start with the labor: how many hours does the monthly scan review take for this tier, how many hours does the quarterly manual check take, and how many hours of client communication and reporting. Add the tooling costs, scan licenses and monitoring seats, apportioned per client. Then add margin. This bottom-up number is usually higher than the agency's instinct, which is the point. Retainers priced by instinct quietly lose money because the reporting and communication hours are the easiest to forget and the hardest to cut.

Sanity check the result against the client's risk. If the monthly retainer is a tenth of the audit fee and the client ships changes monthly, the math works for both sides. If the client changes nothing for a year, a lighter tier or a quarterly cadence is more honest. Selling a heavy retainer to a static store is a churn risk waiting to happen.

Put the reporting cadence in the SOW

The report is the product the client actually sees, so the SOW should describe it: a monthly one-page trend summary with scan results, and a quarterly review with manual findings and recommendations, delivered by a fixed date. Clients renew retainers they can read. They cancel retainers that arrive as raw scan exports with no interpretation, because those look like something a free tool could produce.

Archive every report in a shared folder the client controls, named with dates. Over time this becomes a diligence file that demonstrates continuous attention to accessibility, which is exactly what a plaintiff's attorney asks about. The retainer then serves two purposes: it keeps the store clean, and it builds the paper trail.

Raise the price when scope grows, automatically

Stores grow. A theme migration, a redesign, a new market, or a pile of new apps changes the monitoring workload. Write an annual review clause into the retainer: once a year the agency re-tiers the client against the current store, and the price adjusts up or down. This keeps the retainer aligned with reality without a tense renegotiation every time the client installs an app.

Clients rarely object to a clause they signed. What they object to is surprise. The tier boundaries, the included work, the reporting dates, and the annual re-tiering are all stated up front. An agency that prices monitoring this way sells it once and renews it for years, which is the entire point of a retainer.