Mission control for software quality. Because defects are too expensive.

Before you ship

Most issues feel obvious after users find them.
This checklist helps catch them before release.

You shipped Friday. By Monday a paying customer emailed about a bug that had been live all weekend. You would test it yourself. But you do not have the time.

Pick the QA support your product needs before users see it.

One clear audit, ongoing QA for fast-moving teams, or smoke tests for the flows that cannot break.

QA Audit

€199 one-time

Whether you are launching a new product, releasing a major feature, or handing a build off to a client, get a focused QA pass before it reaches users.

  • 48-hour turnaround
  • Manual QA pass supported by AI-assisted test planning
  • Prioritized bug report, from release-blockers to nice-to-fix issues
  • Reusable test plan your team can run before future releases
  • Proper invoice included
  • Covers up to 3 critical flows

A flow means one complete user path, for example signup, checkout, booking, onboarding, or account upgrade.

Book audit →

Smoke Test Setup

€499 setup
+ €149 / month
  • Automated smoke tests for your top 5 flows
  • Runs on your deployment pipeline
  • Catches broken signups, checkouts, and key actions
  • Monthly maintenance included
  • Clear failure reports when something breaks
  • Proper invoice included
Set up smoke tests →

Who books QA Dispatch

Different teams use the same QA pass for different shipping moments.

Founders close to launch

Running out of time, unable to test everything yourself, and needing an objective set of eyes before going live.

Freelancers and agencies shipping client work

A professional QA pass before handoff, plus a clear report that helps you look thorough and reduces back-and-forth after delivery.

SaaS teams shipping a major release

Extra coverage before a checkout redesign, pricing change, migration, or v2 release reaches real users.

Teams without dedicated QA

Ongoing checks of critical flows so issues do not pile up between sprints.

The second pair of eyes you wish you had before launch.

QA Dispatch operator reviewing a product testing workflow

I'm Ivan. I've spent seven years inside product teams, testing software before it shipped and watching what happened when it didn't get tested enough. QA Dispatch came from a pattern I kept seeing: small teams ship preventable bugs because nobody had time to test properly. I do that part for you.

I move through your product like a real user. Test the critical flows. Push edge cases. Document every issue with reproduction steps your developer can act on immediately, not vague feedback they have to interpret. When the product calls for it, I add Playwright automation, cross-browser testing, and checks across real mobile devices and operating systems.

QA Dispatch operates as an EU VAT-registered company. Every engagement includes a proper invoice, an optional NDA, and a clear scope before work starts.

1

Audit booked

Choose a package, send your product link and login details, and list your top 3 critical flows.

2

Key flows tested

Used like real users would, focused on blockers, broken flows, UX issues, and edge cases.

3

Report delivered

Every issue includes reproduction steps, evidence where useful, severity, and suggested priority.

4

Walkthrough delivered

A short Loom walkthrough helps your team understand what to fix first.

5

Follow-up support included

Questions answered while your developer fixes the findings, on selected packages.

See the kind of evidence you get back.

The report is built for shipping pressure: what broke, how to reproduce it, where it happened, and whether it needs fixing before you ship.

0+

Years inside product teams

0+

Products & platforms tested

0+

Industries and product domains

0+

Issues documented before release

Questions founders usually have.

What if you find nothing?

That is good news. You still get a release-readiness summary, notes on UX friction, and a confidence assessment.

Can you test password-protected products?

Yes. Send staging access, test credentials, or an invite to the tool.

Do you sign NDAs?

Yes. Mutual NDAs are standard. An NDA can be provided or signed before work starts.

What tools do you use?

Manual testing, browser and device checks, screen recordings, screenshots, and AI-assisted test planning.

Can you file bugs in Jira, Linear, or Trello?

Yes, depending on the package. For audits, the report is usually the fastest path. Retainers can include filing bugs directly in your tracker.

How fast can you start?

Audits begin within 48 hours of payment. Retainers begin within 5 business days of signing.

Do you test native mobile apps?

Yes. QA Dispatch also tests native mobile apps on real iOS and Android devices, including onboarding flows, edge cases, and launch-critical user journeys.

Do you test payments with real cards?

Test mode or provided test cards are used. Live payments only if agreed in advance.

Do you test e-commerce and checkout flows?

Yes. QA Dispatch can test checkout-heavy products, including payment gateway states, coupon and discount logic, inventory edge cases, refund flows, account creation during checkout, and mobile purchase friction.

Can the retainer be cancelled?

Anytime, no notice required. The last invoice covers the month you cancelled.

How does VAT work?

Prices are VAT-exclusive. EU business customers with a valid VAT number pay no VAT under reverse charge. Croatian customers pay 25% VAT. Customers outside the EU pay no VAT.

Can I book a single audit for a client project handoff?

Yes. The QA Audit is per project. Many freelancers and agencies use it as a final QA pass before delivering work to their client. The report is yours to share, and can be included with handoff documentation.

Do you work with already-launched products?

Yes. QA Audits work for major feature releases, redesigns, migrations, and fixes, not just first launches. The Retainer and Smoke Test Setup are built for ongoing product work.

We have an internal team but no dedicated QA. Does that fit?

Yes. The Retainer is built for exactly this. It covers regular checks on your most critical flows, with bugs filed directly in your tracker when included in scope.

What is not included?

Do you fix the bugs directly?

No. Issues are documented clearly with reproduction steps so your developer can fix them faster.

Is this a replacement for a full QA department?

No. This is practical shipping QA for founders, agencies, and small teams that need an experienced external review before release.

Do you perform penetration testing or compliance audits?

No. Security penetration testing, formal compliance audits, and legal certification services are not included.

Can you guarantee a bug-free product?

No QA process can guarantee a completely bug-free product. The goal is to reduce risk, catch critical issues early, and improve launch confidence.

Reach out

Choose a time that works for you, or send a message for anything else.

Book a QA call

Get in touch

Share the context you find important about your product and the testing it needs.