Brief
Ninety-minute call. You get a script with step IDs, expected results and device segmentation before anyone is paid.
Break it here, not in front of your users.
We take builds apart on the hardware, radios and assistive setups your roadmap quietly assumes. Real handsets, throttled networks, screened testers, and a report your engineers can act on inside four days.
01 / Studio
Ten years of unflattering findings
We are a small Colorado studio, not a staff-augmentation shop. Four people run the waves; 1,240 screened testers supply the hardware. Every number below is measured, not promised.
10Years trading
41.6kSessions accepted
96hMedian report
2.1%Defect escape
02 / Rate card
Services & rates
Priced per wave or per accepted session. No retainer required, no minimum term. Net 30 from report delivery.
| Service | Scope | Window | Rate |
|---|---|---|---|
| Release gate reviewRG-01 · scripted | Forty-step script across the eight device classes your analytics actually show | 5 business days | $4,800 / wave |
| Device matrix sweepDM-02 · paid per accepted session | Install, first run, permissions, backgrounding, rotation, uninstall | 72 h | $3.20 / session |
| Network-condition runsNC-03 · radio | 3G latency, 8% loss, mid-transfer drop, airplane-mode recovery, captive portal | 48 h | $2.60 / session |
| Accessibility auditAC-04 · WCAG 2.2 AA | VoiceOver and TalkBack passes, switch access, 200% text, focus order, contrast | 8 business days | $5,600 / audit |
| Telemetry captureTC-05 · payload | Event payload screenshots from real devices, reconciled against your tracking plan | 48 h | $2.10 / session |
| Store submission dry runSS-06 · pre-flight | Metadata, screenshots, privacy manifest, review-risk notes before you submit | 3 business days | $1,450 / run |
Sessions are paid per accepted session — a session is accepted when the brief, screenshots and timings are complete and match the script. Rejected sessions are re-run free once. Nothing is billed until the report is delivered.
03 / Deliverable
What comes back
- 01
Reproduction, not adjectives. Device model, OS build, radio state, exact step index and a timestamped screen capture for every finding.
- 02
Severity that maps to your tracker. Field names match Jira, Linear and GitHub issue templates, so the CSV imports clean.
- 03
Pass evidence too. A gate review that only lists failures is not a gate review — you get the passes with the same fidelity.
- 04
Redacted by default. Account names, tokens and customer data are masked in captures unless you send a test tenant.
DM-02 / session 4471Accepted
14:02:11 device Pixel 7a / Android 15
14:02:19 install ok · cold start 1.9 s
14:02:44 perms: camera ▮▮▮▮▮▮ granted
14:03:02 rotate landscape · layout ok
14:03:37 background 30 s · resume ok
14:04:05 throttle 3G · upload stalls
14:04:40 defect D-1182 retry loop
14:06:12 evidence 4 shots + logcat
14:07:00 submit · reviewed 14:31
04 / Process
Four steps, no theatre
Waves run to a written script so results are comparable week to week, and so a tester cannot quietly freestyle around the bug.
Recruit
Testers are matched on handset, OS build and carrier. Ten to forty per wave, screened on a dry run step first.
Run
Sessions land in a queue you can watch live. Incomplete or off-script sessions are rejected inside the hour.
Report
Findings, passes, captures and a severity summary. Delivered as PDF plus CSV, with a walkthrough call on request.
05 / Context
Sectors we already know
Domain context shortens scoping. If your product touches money, health data or a checkout, we have run it before.
Fintech onboardingInsurance quotingClinical intakeTelehealthLogistics trackingField serviceUtilities billingEdTechMarketplacesLoyalty walletsPublic sector portalsTravel booking
06 / Panel
Own a handset? Get paid for twenty minutes.
We pay independent testers per accepted session — $1 to $5, set by device class and script length. Payouts go out within two business days of an accepted session, as a digital reward card. No invoices, no minimum volume.
- 18+, US or EU, your own device and SIM
- Brief is a flow, a device and a fixed window
- Accepted sessions pay; incomplete ones are re-run once free
07 / FAQ
Questions we get first
How fast can a wave start?
Intake closes Monday for the same week. A standard device sweep runs within 72 hours of a signed script; a release gate needs five business days because the script is written against your analytics.
Who actually runs the sessions?
Independent testers on our panel, each screened on a dry-run step and paid per accepted session. Four of us write scripts, review submissions and assemble reports. No offshore subcontracting.
Do you sign an NDA?
Yes, mutual, before the script is shared. Testers sign a per-wave confidentiality addendum and never see production credentials.
What if a session is incomplete?
It is rejected inside the hour with a reason. The tester re-runs once at no cost to you. If it is our recruiting mistake, we replace the tester and the session does not count against the wave.
Can you cover both iOS and Android?
Yes — 1,240 devices across both, from iPhone SE to current flagships and from budget Android to foldables. Segmentation follows your analytics, not a fixed menu.
Do you work outside the US?
Yes. Roughly a third of waves in the last two years were EU clients, run by EU-panel testers on EU carriers so the radio and store behaviour match the market.
08 / Contact
Send the build. We'll break it on purpose.
Tell us the platform, the release date and the devices that scare you. You get a script outline and a fixed price before anything starts.