Services
For startups, agencies and software teams that ship a native app and do not have an internal QA function. You get evidence about an agreed build, a prioritised defect list, and a recommendation. You keep the release decision.
Who it's for
Small mobile agencies at client handover. Native startups approaching a first launch or a substantial update. Product owners whose developers test their own changes. Founders whose AI-assisted app works in the demo and has not had an independent pass.
Native iOS and Android only. Flutter and React Native are outside this offer. Regulated, safety-critical and broad multi-platform work sits outside the standard packages.
Flagship
One platform, one candidate build. Target delivery is five business days after the build, access and scope are confirmed, subject to booking availability.
If the agreed work cannot fit the allowance, we narrow the scope or revise the quote before booking. Coverage is not silently cut when the clock runs out.
Inside the allowance
Relevant items are selected to fit the package. A full submission review, a pentest, and a load test are separate work.
Also available
Same rule on every package: platform, build, cases, devices, environment, time and retest limits are written down before the start date.
One store, one app version, using the listing and access you supply. Screenshots, metadata, reviewer credentials, purchase flows and privacy questions. We flag gaps. We do not invent declarations about your data collection.
from £395 Target 3 business days · up to 4 hours · one document recheck
Book a submission reviewA reserved amount of regression, not an unlimited promise. Onboarding needs a paid baseline or a prior audit with coverage we can reuse. Unused time expires at the end of the month.
from £499 per month · see Starter, Growth and Agency
See the monthly limitsCross-device QA from £595, and a regression baseline setup from £495, when the audit shows those are the actual next step. Both are scoped on the pricing page.
See the full price listQuestions
No. We lead the agreed testing process. You provide a build, access, the intended behaviour, and someone who can answer questions and resolve issues.
The standard service supplies an actionable report and the scoped retest. Development work is quoted separately, when it is available. Native app build is a separate offer.
No. The report records the tested scope, the findings and the remaining risks. Your team makes the final release decision. Store review can still reject a build we recommended.
Yes, on supported native platforms and within the agreed scope. We assess observable behaviour. An app that itself contains AI features — output quality, unsafe responses, cost — is a different scope.
We agree the device and OS matrix before booking, and the report separates physical devices from simulators. Only combinations we can actually run are offered.
Yes. That is the normal arrangement. We work inside your existing release process and do not list the company, the product, or our involvement on this site, in a pitch, or in a public write-up unless you agree in writing. An NDA is signed before a build, source code, credentials, or the detail of an internal workflow is shared.
No. We test an installed build — TestFlight, Play internal testing, or another distribution link. Share crash symbols if you want readable traces. Credentials are agreed on a separate channel, not in the enquiry form.
Other services
These stay available. They are not steps you have to buy before testing.