Skip to content
ARB Codes

Hosting and support

Testing before launch

The journeys that matter are tested on real browsers and devices, and the checks every release needs are set to run automatically.

The issue

What leads teams to ask us

  • Customers find the bugs

  • A release breaks what worked before

  • Older phones are never tested

What is covered

Inside the work

We set the scope around your goal each time. Most projects contain the parts listed here.

  • Test plansDrawn from your real user journeys.
  • Automated testsEach release checked from end to end.
  • Device testingOld and new phones, tablets and browsers.
  • Performance testingHow it copes under load.
  • Accessibility checksContrast, screen readers and keyboard.

The steps

How we deliver

  1. 01DiscoverWe study how your business runs, settle the goals, then send a written scope with a fixed quote.
  2. 02DesignBefore any code is written, you sign off a clickable prototype, one screen at a time.
  3. 03BuildSprints of two weeks. Each one ends with you trying the real product.
  4. 04LaunchGo-live happens at a quiet hour. We train your team and pass over every account.
  5. 05CareA monthly plan keeps it safe, quick and getting better as you grow.

One-off project

An agreed scope at a fixed quote, paid by milestone. Once it's paid, the code and accounts are yours.

Monthly care plan

A subscription paid monthly so your software stays secure, monitored and improving, with written response times.

Common questions

Answers up front

Can you test an app made by another team?

Yes. We can serve as your independent QA team.

How do you price this?

It is a one-off project. We agree a fixed quote after a short call and you pay it in milestones. A monthly care plan covering hosting, updates and support can be added after launch.

Tell us what you'd like built.

Describe the problem in a few lines. One call later, a written scope and a fixed quote reach you within 48 hours.