How it works

How an audit
works, step by step.

Five stages, from a free scoping call to the re-check that confirms the rust is gone. At every stage you know exactly what we need from you and what you’ll get next.

[X–Y] business days, typicallyFixed price, agreed upfrontRe-check included
  1. 1

    Intake

    Days 1–3

    We meet your team, learn who your users are and what the business needs, and agree the journeys, platforms and lenses in scope.

    What we need from you

    An hour of your team’s time, product access and test accounts.

    What you get

    A signed scope with a fixed price and dates.

  2. 2

    Inspection

    [X–Y] business days

    We inspect every journey in scope through all five lenses, on real devices and real network conditions, and talk to users or staff where habits matter.

    What we need from you

    A contact who can answer quick questions.

    What you get

    Progress updates, and an early warning for anything critical.

  3. 3

    Report and walkthrough

    End of inspection

    We deliver the full report and walk your team through it, so engineers know what to fix and leaders know what to fund first.

    What we need from you

    The people who will prioritise and fix the work.

    What you get

    The report, a one-page leadership summary, a [90-minute] walkthrough, and findings delivered into Jira, GitHub, Trello or a spreadsheet.

  4. 4

    Your team fixes

    Your schedule

    Your engineers ship the fixes. We stay available for questions about any finding while you work.

    What we need from you

    Time to implement the recommended fixes.

    What you get

    Up to [N] follow-up calls about any finding while you work.

  5. 5

    Re-check

    When you’re ready

    We inspect every fixed finding again and confirm whether the rust is gone, with fresh evidence.

    What we need from you

    Notice that the fixes are live.

    What you get

    An updated report showing what’s resolved.

AUD-014 · System logicMajor

Payment marked successful before the mobile-money callback returns

Evidence

Recording on a throttled connection: success screen shown, callback fails, customer charged with no order.

Steps to reproduce

Android 10, 3G profile with 2 s latency. Pay any bill, then lose the network for 5 seconds.

Recommended fix

Show a pending state with a reference number until the callback confirms.

Re-check: open
Anatomy of a finding

Every finding has the same six parts

ID and lens

A unique reference and the lens it was found through, so every finding can be tracked to its fix.

Severity

How much harm it causes and how many people it affects. It sets the order of work.

Evidence

A screen recording, screenshot or log that anyone can replay. No finding without proof.

Steps to reproduce

The exact device, network and actions that trigger it, so your engineers see it first time.

Recommended fix

A specific change your team can implement, written for your stack.

Re-check status

Open, fixed or confirmed. Updated after the re-check with fresh evidence.

Severity

A severity that sets the order of work

Critical

Blocks a core task or causes harm: lost money, exposed data, people locked out. Fix before anything else.

Major

Causes real failure or confusion for many users, with a painful workaround at best.

Minor

Friction or inconsistency that slows people down but doesn’t stop them.

Passed

Inspected and working as intended. Recorded so you know what we checked.

The report

What’s in your report

Written for two readers: the team that fixes the problems, and the leaders who decide what to fund first.

Open the sample report

Executive summary

One page for leaders: what we found, what it costs you, and what to fund first.

Findings register

Every finding with its ID, lens, severity, evidence and fix.

Lens scorecards

How the product performs through each of the five lenses.

Evidence library

Recordings and screenshots behind every finding.

Fix plan

Findings grouped into a practical order of work for your team.

Accessibility conformance summary

WCAG 2.2 AA results you can share with partners, funders and regulators.

One fixed price, agreed before we start

No hourly billing and no surprises. The price depends on the size of the inspection, and it includes the re-check. [PRICING DETAILS]

What we don’t promise: a specific conversion number. Results depend on what your team ships. What we do promise: every finding is real, evidenced and fixable.

What shapes the scope

  • How many journeys are in scope
  • Which platforms: web, Android, iOS, USSD
  • Which of the five lenses you need
  • Whether we interview users or staff

Where’s the rust in your product?

Book a free scoping call. We’ll learn what you’ve built and who uses it, then send a fixed-price proposal within [RESPONSE TIME].

Founding clients: we’re taking on [N] organisations this year at a reduced rate, in exchange for permission to publish a case study.