MysteryD Open a case file
CASE LOAD: OPEN NIGHT DESK ON DUTY
MysteryD

Quality assurance & adversarial testing · Los Angeles · est. 2011

We find what's wrong before your users do.

Full-cycle QA and adversarial testing, run like a case file. Plain-English findings, numbered steps to reproduce, nothing fabricated.

Every case is read by a person. The night desk replies within 24 hours.

The night desk

  1. 1
    Intake read. A person reads the form within 24 hours.
  2. 2
    Scope agreed. What gets examined, and what does not, in writing.
  3. 3
    Case file delivered. Findings, reproductions and evidence, or a clean result.
FORM 01

A human replies within 24 hours. Nothing is fabricated.

Services index

02

Ten capabilities in the index. Every engagement is quoted from a written brief; nothing here is a fixed-price package.

  1. 01

    Accessibility scan

    A thorough WCAG 2.1 and 2.2 audit with selectable granularity: pick conformance level A, AA, or AAA, and how deep each check goes. Every barrier ships with the affected criterion and a fix.

  2. 02

    Adversarial UX

    We use the product the way a hostile or careless person would, and record what breaks.

  3. 03

    Agent readiness scan

    We check whether an automated agent can use your product safely, and where it would get stuck or do harm.

  4. 04

    Conversion rate optimization

    B2B or B2C: give us your funnel and we will suggest where it leaks and how to raise your conversion rate.

  5. 05

    E-commerce troubleshooting

    Tell us what is breaking your store: checkout, payments, catalogs, or the thousand small things between. We will help you squash it.

  6. 06

    Full-cycle QA

    We test the whole product the way your users actually move through it, not just the happy path.

  7. 07

    Penetration testing

    Authorized penetration tests against your product, run under agreed scope and rules of engagement. Findings, reproduction steps and results arrive as a case file.

  8. 08

    Privacy scan

    What does your product collect, where does it go, and what does it promise? We audit the gaps and hand you remediation recommendations you can act on.

  9. 09

    Regression and retest

    After your team fixes a defect, we run the same steps again to confirm it is gone and nothing new broke.

  10. 10

    SEO/AIO/GEO scan

    How visible is your product to search engines, and to AI chats and agents? We report where you surface, where you don't, and what to fix.

How a case runs

03

Ten moves, start to finish. The nine steps in the middle run in order on every case. Even when the answer looks obvious, we run the step that would confirm it.

  1. 0

    Open a case file

    Start with the intake form. A person reads it and replies within 24 hours.

  2. 1

    Discover

    We learn what the product is meant to do and where it tends to fail.

  3. 2

    Scope

    We agree on exactly what will be examined and what will not.

  4. 3

    Plan

    We write the test plan before touching the product.

  5. 4

    Prepare

    We set up accounts, data and environments so the tests are repeatable.

  6. 5

    Execute

    We run the plan and try to break each flow on purpose.

  7. 6

    Report

    We write up every finding in plain English with steps to reproduce.

  8. 7

    Retest

    We check each fix against the original reproduction.

  9. 8

    Regression

    We sweep the surrounding flows to confirm the fix broke nothing else.

  10. 9

    Close

    We close the case only when every finding is resolved or accepted by you.

  11. 10

    Reports and evidence

    Every finding ships with numbered steps to reproduce, expected versus observed, and the evidence attached: a case file your team can act on.

FAQ

04
How fast can you start?

Intake is read within 24 hours. A scoped engagement usually starts within a week; release-verification passes can be slotted faster when the date is fixed.

Do you do one-off scans or only full engagements?

Both. Every scan in the services index stands alone: one accessibility scan, one privacy scan, one penetration test. Full-cycle QA is the umbrella when you want the whole product covered.

Can we start with just one flow or one screen?

Yes. Cases are scoped to what you need examined: one checkout flow, one settings screen, one release. Small scope, same case file.

What does an engagement cost?

It depends on scope: how much surface area, how deep the checks go, and how many passes. We quote from your written brief before work starts, so the number is fixed and agreed, never a surprise.

How is pricing set?

Fixed scope, fixed price, agreed before work starts. The budget field on the form helps us scope honestly; if the ask does not fit the budget we say so at intake.

Who actually does the work?

Experienced investigators. We review every result ourselves, confirm each finding against the product, and stand behind everything in the case file. Nothing ships unexamined.

Do you fix the bugs you find, or just report them?

We report. Every finding ships with reproduction steps and evidence your team can act on, and we retest after your fixes. We may suggest how to fix something, but the repair belongs to your team.

What happens to our data and credentials after the case closes?

We retain case materials for 12 months after the case closes, then delete them. Credentials are revoked or returned at close, and access ends with the engagement.

Do you test mobile apps, or only web?

Web is our focus today. We are experienced in mobile and connected TV testing and welcome cases for both; tell us what you need examined.

Can you work inside our CI / on every release?

Yes. Open a case and tell us about your pipeline and release cadence; we will scope a release-verification arrangement that fits.

Do you work under NDA?

Yes. We sign your NDA or provide ours before any build or credential changes hands. Confidentiality is the default, not an add-on.

Do you sign our MSA/DPA, or only yours?

Let's talk about it. It is a tricky area and depends on your organization's focus on compliance versus operationalization. Open a case and we will work through the paperwork together.

What do you need from us?

A build or staging URL, test accounts, and a paragraph on what the product is supposed to do. The intake form is the whole starting requirement.

What if you find nothing?

You get a case file saying exactly what was examined and what passed, with the coverage map. A clean result is a result; we never invent findings to justify the invoice.

The desk

Contact
Every case starts at the intake form: one channel, so nothing is lost and everything stays confidential.
Location
Los Angeles, California
Hours
24/7 · a person replies within 24 hours