Verity for web development agencies
The build ends and the obligation does not. Verity holds every site you look after — its hosting, its dependencies, its renewals and the requests nobody billed.
Verity runs the agency. Hosting panels and code repositories stay where they are.
Verity / Agency
LiveSites under care
74
Sites without a retainer
29
Small requests this month
138
Dependencies overdue
23 sites
Needs attention
Illustrative figures. Verity shows your own agency in this shape.
How the business runs
A web agency’s risk is not the build. It is the accumulating population of sites it launched and is still expected to look after. Seventy-four sites under care, twenty-nine of them without an active retainer but still sending requests, is a support business the agency did not intend to start.
The second characteristic is that the small requests are the leak. Ninety-two unbilled requests in a month, each individually too small to invoice, is a substantial amount of agency time given away — and it is given away most often to the clients who have no retainer.
The third is technical obligation. Sites need dependency and security updates, and twenty-three sites overdue is exposure that will be attributed to the agency regardless of what the contract says, because the agency is who the client will call.
The fourth is renewals. Domains, certificates and hosting all expire, and an expiry the agency manages but the client owns is a failure that lands entirely on the agency.
The fifth is platform currency. Sites on unsupported versions need upgrades that nobody has quoted, and the conversation gets harder the longer it waits.
Verity holds every site with its hosting, dependencies, renewals, retainer state and request history in one place.
What Verity calls these things
What gets in the way
Web agency difficulties come from obligations that outlive the project that created them.
Small requests are done and never billed
Each one is too small to invoice and together they are substantial.
In Verity Every request is recorded with time and a billing state, so the total is visible.
Sites without retainers still receive support
A client whose contract ended still calls and is still helped.
In Verity Retainer state sits on the site, so support without cover is a visible decision.
Dependency and security updates fall behind
Updates are done when someone remembers, across dozens of sites.
In Verity Update status is held per site with overdue exposure surfaced.
Renewals expire on the agency’s watch
Domains and certificates the client owns and the agency manages lapse.
In Verity Renewals carry ownership, expiry and an owner ahead of the date.
Upgrades are needed and never quoted
A site on an unsupported version needs work nobody has proposed.
In Verity Platform currency is tracked per site with upgrade quotes raised.
Site knowledge lives with one developer
Whoever built it is the only person who can safely change it.
In Verity Sites carry their stack, access, quirks and history independently of who built them.
The complete system
One system across sites, obligations, requests and clients.
Work
Each site carries its stack, hosting, launch date, current platform versions, retainer state and history.
Why it matters here The site, not the project, is the unit the agency remains responsible for.
In practice Seventy-four sites under care across forty-one clients.
Workflows
Every request carries the site, requester, time taken, billing state and outcome.
Why it matters here Unbilled small requests are the agency’s largest quiet cost.
In practice Ninety-two requests done and unbilled this month.
Control
One permission model and one audit trail, with update status, security patches and supported version state held per site.
Why it matters here Exposure attaches to the agency whether or not the contract says so.
In practice Twenty-three sites with overdue dependency updates.
Inventory
Hosting accounts, domains and certificates carry ownership, cost, renewal date and the site they serve.
Why it matters here A renewal the agency manages and the client owns is the agency’s failure if it lapses.
In practice Six renewals within thirty days.
Relationships
Clients carry their sites, retainer scope and state, request volume and commercial position.
Why it matters here Support given without cover is a decision that should be made deliberately.
In practice Twenty-nine sites without a retainer still receiving requests.
People
Staff carry site knowledge, assignments, request handling and availability.
Why it matters here Single-person site knowledge is an operational risk across an estate.
In practice Sites where only one developer has working knowledge.
Orders
Build projects, upgrade quotes, retainers and out-of-scope work carry a billing state.
Why it matters here Upgrades and out-of-scope work only get paid if they are proposed.
In practice Upgrade quotes outstanding for unsupported sites.
Reports and analytics
Site estate health, update currency, request volume and billing, renewal exposure and client profitability come from the records.
Why it matters here The estate is the business, and its health is measurable.
In practice Unbilled hours by client and site.
Verity AI
Verity AI answers from your own site, request, renewal and client records, respects permissions, and can create assigned follow-ups.
Why it matters here The useful questions are about unbilled work and technical exposure.
In practice "Which sites are overdue for updates?" returns twenty-three with their clients.
Communication
Request conversations, renewal notices and upgrade proposals attach to the site and client.
Why it matters here Most agency disputes are about what was agreed and when.
In practice Renewal notice recorded against the domain and client.
Records
Site access requirements, environment documentation and quirks attach to the site.
Why it matters here Site knowledge must survive the developer who built it.
In practice Environment documentation available for any assigned developer.
Schedule
Update work and upgrades are planned against developer availability and client windows.
Why it matters here Maintenance across an estate has to be scheduled, not improvised.
In practice Update work planned across sites by month.
Work in motion
These already happen. Recorded, the estate stops being an unpriced obligation.
Recording the absence of a retainer is as important as recording its presence.
Checking coverage before doing the work is the only moment the conversation is easy.
Prioritising by exposure rather than by client noise is what reduces real risk.
Client-owned assets still need the agency to raise the renewal.
A recorded client decision to defer is what protects the agency later.
Verity AI
Verity AI reads the same site, request, renewal and client records the agency creates as it works. It answers from your own agency, respects permissions, and can turn an answer into a quote or a maintenance plan.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the agency’s own records at the point the condition is met.
When
A request arrives for a site without retainer cover
When
A site falls behind on updates
When
A domain or certificate approaches expiry
When
A site reaches an unsupported platform version
When
Unbilled hours pass a threshold for a client
What you can understand
Estate health, request volume and margin from working records.
Verity records the agency’s operations. Hosting panels and code repositories continue as they are.
One system, different ways of seeing it
Everyone works from the same records.
Founder
What are we giving away?
Unbilled hours by client, sites without cover, profitability, upgrade opportunities.
Technical lead
Where is the exposure?
Update currency, unsupported versions, renewals, single-person site knowledge.
Developer
What am I working on and how does this site work?
Assigned requests, site stack and documentation, access, maintenance windows.
Account manager
What does the client need?
Request volume against retainer, renewals, upgrade proposals, reporting.
Where it is used
Every small request recorded with time and billing state, so the monthly total the agency gives away becomes visible and negotiable.
Each launched site held with its stack, hosting, dependencies and retainer state, because responsibility outlives the project that created it.
Update and security status per site with overdue exposure prioritised, since risk attaches to the agency regardless of contract wording.
Domains, certificates and hosting with ownership, expiry and an assigned owner, including assets the client owns and the agency manages.
Sites on unsupported versions identified with scoped work and a recorded client decision, including a decision to defer.
Stack, access, documentation and quirks held against the site rather than in the head of whoever built it.
Plain-language questions across sites, requests, renewals and clients, with quotes and maintenance plans raised in the same step.
Getting there
Hosting panels and code repositories continue and are mapped during implementation. Sites with stacks and hosting details, clients and retainer scopes, request history, renewal calendars and documentation are brought across.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your own site, request, renewal and client records: which sites are overdue for updates, how much unbilled work was done and for whom, which sites receive support without a retainer, which domains expire next month. Each answer can become a quote or a maintenance plan.
Because the project ends and the responsibility does not. A site launched two years ago still needs updates, still has renewals, and still generates requests, and that population of sites is the agency’s real operational picture.
Every request is recorded against a site with time taken and a billing state, and coverage is checked before the work is done. Individually the requests are too small to invoice; recorded together they become a retainer conversation.
Update and dependency status is held per site with overdue exposure prioritised, so maintenance is scheduled across the estate rather than done when someone remembers or when something breaks.
They are recorded with ownership, expiry and an assigned owner. A lapse on an asset the client owns but the agency manages lands on the agency, so the renewal has to be raised regardless of who pays.
Sites on unsupported versions are identified with the work scoped and a quotation raised, and the client’s decision — including a decision to defer — is recorded, which protects the agency later.
No. Hosting panels and repositories continue as they are. Verity holds the agency around them — sites, obligations, requests, renewals, clients and margin.
About four weeks: discovery and mapping of the site estate, retainer scopes, update practice and renewal responsibilities, configuration, migration of sites and clients, then an ongoing operations partnership.
They cluster on the clients without retainers. Tell us how requests are recorded today.