Services

Support with a response time in writing.

Fixes, updates and security patching against a written response time.

Website & App Maintenance with a Written SLA

This is what decides whether a system still works in three years. Bug fixes, feature updates and security patching run on a tiered SLA, so the answer to "how quickly will someone look at this" is a number in a contract.

Security patches go out monthly, feature requests go through a visible pipeline, and every quarter you get a written health report on the system.

What you get

Tiered SLA response times
Monthly security patching
Feature request pipeline
Dedicated support channel
Quarterly system health report

Tiered SLA
Response time in writing: Quarterly
System health report

Work, writing and lessons on this.

Concept studies are self-initiated and labelled as such. The writing and lessons are free to read.

Process

How an engagement runs.

The same six phases every time, so you always know what is happening now and what you get at the end of it.

Engagement

W1 W4 W8 W12 ▸ Go live Ongoing

Week 1–2

Discover

Interview the people who will use it daily. Audit what runs today. Find the real constraint first.

Stakeholder interviews
Current-system audit
Scope document

Each phase ends with something usable and a real option to stop. You keep what is built.

Questions

Maintenance & after-sales support: questions we get asked.

If yours is not here, ask us directly.

Ask us directly

Launch is step four of six. From go-live the system moves onto a maintenance subscription with a tiered SLA: monthly security patching, bug fixes, a named support channel and a quarterly health report. It is a paid arrangement rather than a goodwill promise, and that is exactly why a response time can be held against it.

Not contractually. The maintenance subscription is cancellable, and the code, the data and the infrastructure are yours. In practice any team taking over a system needs a handover period, so we write architecture notes and runbooks as we go rather than assembling them in the month somebody leaves. We would rather you renew because it is the obvious choice than because leaving is painful.

You do. Full IP transfer on final payment, including source files, code and the design system. No licensing, no retainer lock-in on your own assets.

Keep going

Other services.

Next step

Have an idea? We will turn it into a system.

Thirty minutes, no slides. You leave knowing what we would build first and what it costs to run.

Get a quote See how it works

Or email us directly at hello@uxatom.com