Platform & support
with less translation.
The care after launch: speed, security, accessibility and a team that answers when it matters.
What this division
is accountable for.
- Issues detected before customers report them
- Performance and accessibility that do not decay
- A verified, rehearsed restore path
- A named senior engineer who knows your system
Launch day is the start of the interesting part. Everything that determines whether a digital investment holds its value happens afterwards, in months where nothing dramatic occurs and small amounts of attention compound.
This division exists for that period. Updates applied, performance defended with budgets in CI, accessibility maintained rather than re-audited annually, security hardened before an incident rather than during one.
It also holds our white-label practice, where the client is another agency and the deliverable is quiet, senior capacity under someone else’s brand.
What sits
inside it.
Website & app maintenance
Ongoing updates, monitoring and a senior person to reach when something needs deciding.
Speed & performance optimisation
Core Web Vitals, bundle size and server response times taken seriously enough to move revenue.
Hosting & domain management
Infrastructure, DNS and deploy pipelines managed so uptime stops being your problem.
Accessibility (ADA/WCAG)
Audits and remediation that make the product usable for everyone and defensible on paper.
Security hardening & SSL
Hardening, patching, certificates and headers — the unglamorous work that prevents the bad week.
White-label development
Senior build capacity for agencies, under your brand, to your standard, on your timeline.
Three engagement
shapes.
Most clients start with the first and decide about the others once there is evidence on the table.
Health assessment
A baseline across performance, security, accessibility, dependency risk and access control, with findings ranked by consequence and a costed remediation list.
Remediation programme
The ranked list worked through, with automated gates added in CI so the same problems cannot quietly return two releases later.
Care retainer
Updates, monitoring, verified backups, defined response times, an improvement allowance and a quarterly technical review with a prioritised action list.
Four stages, visible throughout.
Assess
A baseline across performance, security, accessibility and dependency risk, with findings ranked by consequence.
Stabilise
The urgent items closed first: exposed surfaces, failing checks, missing backups, unpatched dependencies.
Automate
Budgets, scans and alerts moved into CI and monitoring, so regressions are caught by machines rather than customers.
Review
A quarterly session on what changed, what is drifting and what deserves next quarter’s attention.
- Nobody has updated the CMS or dependencies in a year
- A client security questionnaire has arrived and you cannot answer it
- Search Console is flagging Core Web Vitals as needing improvement
- Your previous agency has moved on and taken the context with them
- —You want a penetration test certificate without fixing anything underneath
- —You need 24/7 follow-the-sun operations cover
- —The application is beyond economic repair and needs replacing
We would rather point you to a specialist in the first conversation than sell you our second-best skill.
Recent work from this division.
Platform & support, answered.
Typically four business hours for a critical outage, one business day for a functional defect, and a scheduled slot for improvements. The exact commitment goes in the agreement — a vague promise to be responsive is worth nothing at 9am on a Monday.
Yes, after a short onboarding audit so we can run it locally, understand the deployment path and record the risks we find. Occasionally that audit concludes the honest answer is a rebuild, and we say so rather than billing to maintain something unmaintainable.
No. You hold the accounts and pay providers directly at cost while we manage the configuration. Marking up infrastructure creates an incentive we would rather not have, and it makes leaving harder than it should be.
No. Overlays cannot repair heading structure, unlabelled inputs or keyboard traps, they frequently interfere with a user’s own assistive technology, and they have not prevented litigation. We fix the underlying markup at component level.
Bring us a platform & support problem.
Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.