Multi-tenant PageSpeed monitoring under $100: what agencies actually buy

#webperf #corewebvitals #agency #monitoring

An agency can open ChatGPT, paste a PageSpeed Insights URL, and get a plausible fix list before lunch. That loop feels like monitoring until the account manager asks for last month’s LCP trend across twenty WordPress clients and nobody has a shared schedule, a named alert owner, or a history that survives holiday leave. Multi-tenant PageSpeed monitoring under $100 is not a cheaper way to run one more free check; it is the purchase of portfolio coverage that still fits a three-digit ops line.

What agencies actually buy in that band is flatter than the vendor shortlist suggests. They buy pooled site and test caps under one organisation subscription, workspaces that keep client brands separate, and reporting an account team can open without pinging the engineer who wrote the cron. The pricing tables and tier caps live on our blog in Affordable Multi-Tenant Performance Monitoring Under $100/Month. The day-to-day shape of one dashboard across many client sites is in Multiple Client Sites, One Dashboard. What follows here is the buying story: what lands on the purchase order when the brief says “keep Core Web Vitals coverage under a hundred dollars.”

What agencies mean by multi-tenant PageSpeed monitoring under $100

In agency language, multi-tenant means one customer account that holds many client organisations, sites, and schedules without minting a new invoice line per domain. Under $100 means the list price for that organisation-shaped monitor fits a three-digit monthly ceiling before you add flagship real-user monitoring (RUM) seats. The job is scheduled lab coverage on money URLs, CrUX context where PageSpeed Insights publishes it, budgets and alerts with named responders, and history long enough for a quarterly business review.

That purchase is easy to confuse with adjacent tools. A free PageSpeed Insights run is a diagnostic, an AI chat that proposes CSS changes is a fix assistant, and an uptime product with a small page-speed monitor allowance is infrastructure health with speed as a sidecar. Agencies that say they want multi-tenant PageSpeed monitoring under $100 usually want the portfolio job, not another one-off score.

If the roster is still under roughly ten priority URLs and one engineer already owns automation, DIY can still hold for a while. Once account managers need shared history and the URL list grows every campaign week, the under-$100 question becomes whether the maths is flat at the organisation or multiplies per monitored slot. That is the fork most agencies hit before they ever open a pricing page.

AI fix loops are not the same purchase as a portfolio schedule

The confusion shows up often on social threads: someone ships an agent that reads Lighthouse findings and opens a pull request, then treats that as “we have monitoring.” Fix loops are useful on sites you can change, yet they are not a substitute for knowing which client homepage went amber on mobile three Tuesdays ago while the developer who owns the agent was offline. The first job remediates; the second proves the roster stayed inside budget when nobody was watching the chat.

A scheduled portfolio monitor answers a different question. It keeps URL inventories current, runs PageSpeed Insights (or equivalent) on a cadence the retainer can defend, stores history the account team can export, and routes budget breaches to someone other than the person who wrote the workflow. The AI loop still belongs in the stack as a remediation layer on sites you deploy, yet it does not replace the system of record for twenty client origins. Buying under-$100 multi-tenant coverage while also keeping an AI fix assistant is a sensible layering story, but buying only the assistant and calling the retainer “monitored” is how QBR slides become screenshots again. The SOW reads cleaner when both jobs are named, so the account team knows which tool answers which question.

What actually lands on the purchase order

When the buy is honest, the purchase order or statement of work names jobs, not logos. Logos without owners still leave the retainer on hero labour. In our experience the under-$100 multi-tenant buy usually includes:

a flat organisation subscription with published site and monthly test caps,
enough workspaces to separate client brands without a second vendor,
scheduled lab runs on agreed money URLs (not “every URL we ever shipped”),
shared history and exports the account team can open,
budgets and alerts with named owners,
a clear non-goal: this is not deep RUM on every brochure domain.

What usually does not land on that same line item: unlimited regions and devices per URL, enterprise RUM seats, or a promise to monitor forty properties when the published site cap is twenty-five. Those gaps belong in a later tier or a thinner URL list, not in silent overages. Saying the non-goals out loud is cheaper than explaining a surprise invoice mid-engagement.

Procurement still needs plain wording for the row. That is a different essay from the purchase shape itself; for translating milliseconds into finance language, see our Hashnode notes on procurement budgets and selling Core Web Vitals monitoring without calling the line item “latency.” Here the decision is simpler: either you are buying organisation-scoped scheduled coverage under a three-digit ceiling, or you are still assembling DIY layers and should say so in the SOW. Ambiguous wording is how “monitoring” gets approved as a free checker and then fails the first multi-client review.

Flat organisation caps versus per-site maths

The under-$100 question collapses to how capacity is counted, and the short table below is the decision frame agencies actually use when three vendor demos arrive in the same week.

Pricing shape	How capacity is counted	Fits under $100 when…	Breaks when…
Per monitored URL / slot	Each URL × device × region consumes a slot	One client, deep lab work	Twenty clients each need homepage + checkout
Per-site SaaS seat	Billing scales with domains	Portfolio stays tiny	Retainer count grows faster than tool budget
Flat organisation cap	Sites, tests, workspaces pool under one subscription	Roster grows inside published limits	You exceed site or test caps and need the next tier
DIY scripts + API	Cash cost is low; labour is not	One engineer owns the pipeline	Quota, reporting, and on-call become unpaid platform work

Agencies that stay under $100 with multi-tenant coverage almost always pick the flat organisation row and accept published caps. Per-slot tools can still win for a single high-traffic property; they are a poor match for “monitor the whole WordPress roster for under a hundred.” DIY wins on cash until the labour row on the same budget is honest. If you cannot name that labour owner, you are not really choosing DIY; you are deferring the purchase. Apogee Watcher’s Professional tier is built as that flat-cap shape under the $100 line at list pricing, with Agency as the published step when site or workspace caps bite. Current numbers live on the pricing page, and the buyer story does not change when a list price moves by a few dollars: you are still choosing organisation caps versus per-site multiplication.

When DIY still wins the budget

DIY PageSpeed Insights API scripts, Lighthouse CI, sheets, and a workflow tool still win the purchase when three conditions hold together: the portfolio is small enough that one person can keep URL lists accurate, nobody expects branded client PDFs from the monitoring layer itself, and the team already treats automation ownership as billable engineering time rather than free evenings.

DIY stops winning the under-$100 comparison when any of these repeat: campaign URLs ship and never join the sheet; the digest dies on leave; account managers rebuild slides from CSV; “nightly for everyone” became “nightly for whoever we remembered” under API quota. At that point a flat-cap portfolio monitor is usually cheaper than the labour you were pretending was free, even when the SaaS line sits at $79 rather than $0. The cash line looks worse; the retainer maths usually looks better. DIY still fits as a layer after the portfolio monitor is in place (Lighthouse CI on templates you ship, manual PageSpeed Insights in teaching conversations), because the purchase under $100 is for the jobs DIY stopped covering reliably, not a mandate to delete every script.

FAQ

Can an agency monitor forty client sites under $100/month?

Often not on a single flat-cap Professional-shaped plan if the published site limit is twenty-five. Realistic under-$100 strategies put priority origins on the paid monitor and leave long-tail pages on free diagnostics, or move to the next published tier when the roster honestly exceeds the cap. Pretending forty equals twenty-five is how retainers over-promise.

Is an AI agent that fixes Lighthouse issues the same as multi-tenant monitoring?

No: an agent remediates findings on sites you can change, while multi-tenant monitoring schedules checks, stores history, and alerts across many client organisations whether or not you control the repository. Most agencies need both jobs named separately rather than collapsing them into one “AI monitoring” line.

What should we put on the purchase order so finance understands the buy?

Organisation-scoped scheduled PageSpeed / Core Web Vitals coverage, included site and test caps, retention, seats, and reporting are the rows that usually clear finance. A three-digit portfolio monitor is a different purchase from a four-hundred-dollar RUM seat on one flagship property. The SOW reads better when it states what is out of scope as well as what is included.

Does multi-tenant PageSpeed monitoring replace uptime tools?

No: uptime and SSL watches answer “is the site reachable,” while portfolio PageSpeed monitoring answers “are LCP, INP, and CLS drifting on money URLs.” Many agencies keep both, because green uptime does not mean green Core Web Vitals, and a green Lighthouse score does not mean the origin stayed up overnight.

Buy the portfolio job, then layer the rest

What agencies actually buy under $100 for multi-tenant PageSpeed monitoring is organisation-shaped coverage: flat caps, shared schedules, and history the account team can defend in a review. AI fix loops, free checkers, CI gates, and selective RUM stay in the stack as layers, yet they are not the same line item. The pricing maths and tier caps sit in Affordable Multi-Tenant Performance Monitoring Under $100/Month. For the product shape of many clients in one view, Multiple Client Sites, One Dashboard is the shorter walkthrough, and you can run a check on a client URL before schedules move into a trial.