Find the rust
before your users do.
Independent audits for apps, websites and platforms. We test what your users experience and what your system actually does, on the phones and networks they really use. Every problem comes back with proof, a severity and a specific fix.
- Five lenses in every audit
- Evidence behind every finding
- Checked against WCAG 2.2 AA
- Re-check included
Findings
Sorted by severity, highest first
Evidence
Screen-reader recording: the amount field has no label, so the form can’t be submitted.
Recommended fix
Add a visible label tied to the field, and announce validation errors as they appear.
Built for products people can’t afford to see fail.
Five lenses, one inspection
Most audits stop at what’s on the screen. Ours also tests the rules underneath, the habits of the people using it, and the conditions it has to survive. All five lenses, in every audit.
Can people finish what they came to do?
We walk through your most important journeys the way your customers would, and record every point where they hesitate, guess or give up.
- Key journeys completed without help
- Labels, steps and errors that make sense
- Dead ends and loops found and traced
Does it work for everyone?
We test with keyboards, screen readers and low-vision settings, and check every screen against WCAG 2.2 AA.
- Screen-reader and keyboard walkthroughs
- Contrast, focus and text-size checks
- A conformance summary you can share with partners and regulators
Do the rules behave as the business intends?
We push states, edge cases and integrations until the logic either holds or breaks, then show exactly where it broke.
- States and transitions that contradict each other
- Edge cases and integration failures
- Silent errors users never get told about
Does it fit how people really behave?
We look at the devices, routines and workarounds of your actual users, not the ideal user in the spec.
- Features people never find
- Workarounds staff and customers invent
- Flows built for habits users don’t have
Does it survive real conditions?
We test on slow and dropping networks, shared devices, peak days and staff handovers, and we follow every payment through to the end, because that is where products actually run.
- Slow, dropping and offline connections
- Mobile-money, card and USSD payments followed end to end
- Shared devices, peak days and staff handovers
Inside the
inspection bay
Your product goes up on the lift. Each lens has its own instrument, and every reading feeds the same report.
See the full processProof, not opinions
What makes a Bayrust report something your team acts on the same week, instead of a document that sits in a folder.
Every finding is a tagged part
An ID, a lens, a severity, replayable evidence and a specific fix. Nothing vague, nothing to argue about.
Tested where your users are
Low-cost Android phones, slow and dropping networks, shared devices, mobile money and USSD. The conditions your product actually lives in.
Written for two readers
Engineers get reproduction steps, delivered straight into Jira, GitHub, Trello or a spreadsheet. Leaders get one page on what to fund first.
Independent by design
We don’t build software or sell tools, so there’s no follow-on contract to protect. The report says what’s true, not what’s convenient.
The re-check is included
Once your team ships the fixes, we inspect every one again and confirm the rust is really gone, with fresh evidence.
You don’t need a crisis to need an audit
The teams closest to a product are the last to see its rust. An outside inspection is worth it at four moments.
Before a launch
The cheapest moment to find rust is before your customers do. We can inspect prototypes, staging and beta builds.
Before you accept a vendor’s delivery
An independent check that what you paid for actually works, before the final invoice is signed.
When customers complain and nobody knows why
Support calls are rising, completion is falling, and the team can’t agree on the cause. We find it.
Once a year, as a health check
Products drift as features pile up. A yearly inspection catches the rust before it spreads.
Led by a product designer, not a sales team
Bayrust is led by Aston Guevara Seka, who has spent eight years designing digital products and reviewing what development teams actually ship. Every audit is done by people who have built products themselves, so every fix we recommend is one a real team can ship.
- Senior UX designer at a Nordic EdTech company, working on its design system and reviewing the quality of what teams ship
- Former lead product designer of a vehicle telematics platform
- Product designer since 2018, across food tech, software and education
- BSc (Hons) Entrepreneurial Leadership, First Class, African Leadership University
What teams say after the re-check
[CLIENT NAME]
[ROLE, ORGANISATION]
“[CLIENT QUOTE about what the audit revealed and what changed afterwards.]”
[RESULT]
[WHAT IT MEASURES]
[RESULT]
[WHAT IT MEASURES]
Questions teams ask before an audit
Can’t find yours? Ask us at [YOUR EMAIL].
A report with every finding (its ID, lens, severity, evidence, steps to reproduce and a recommended fix), a one-page summary for leadership, a walkthrough session with your team, and a re-check once you have shipped the fixes.
Most audits take [X–Y] business days from intake to report, depending on how many journeys and platforms are in scope. We confirm the dates before we start, and the re-check is scheduled once your fixes are live.
Access to the product or a test environment, test accounts, one contact person on your team, and an hour to walk us through your users and what matters most to the business.
No honest auditor can promise a number, because results depend on what your team ships. What we do guarantee is that every finding is real, backed by evidence, and comes with a fix your team can act on.
No. We stay independent, so we don’t write your production code or sell you a rebuild. Every finding comes with a specific recommended fix, and we confirm it in the re-check.
Yes. We inspect prototypes, staging environments and beta releases. Before launch is the cheapest time to find rust.
WCAG 2.2 at level AA. Every accessibility finding is mapped to the criterion it fails, and you get a conformance summary you can share with partners, funders or regulators.
We work under a confidentiality agreement, use test accounts wherever possible, and never put your customers’ personal data in our reports.
Each audit has one fixed price, agreed before we start and including the re-check. It depends on the number of journeys, platforms and lenses in scope. [PRICING DETAILS]