Skip to main content

We test. You ship.

Your ~10 most important flows, like sign-up and payment, tested before every release, so your customers don't find the bugs first.

We write and maintain the tests. A person checks every failure.

Book a 30-minute pilot call

If the agreed flows aren't running by the end of week 3, the pilot is free.

Right now

Who tests your release today?

In most small software companies, the developer who built the feature tests it, logged in, on their own laptop. The next people to try it are your customers.

Developers test what they changed.

Nobody walks sign-up or payment again after an unrelated change, and that's where things break quietly.

Customers don't file bug reports.

A stranger whose sign-up fails just leaves. You find out weeks later, as a dip in the numbers.

The test suite stopped when its owner left.

Someone set up automated tests once. Today they fail in the pipeline and nobody looks.

24 of 28

SaaS products we signed up for as strangers in our latest research batch had a defect in sign-up. See the study

How it works

Four steps, then it runs with every release

  1. 01

    We agree your flows

    Together we pick the ~10 flows your customers rely on: sign-up, login, payment, your core action. We write them in plain language and you confirm them.

  2. 02

    We write the tests

    An AI testing agent walks your app like a normal user. It reads the screen, not your code, so a renamed button doesn't break the test.

  3. 03

    They run before every release

    From your CI, or with one click by you or us. The agent's run finishes in minutes, with steps and screenshots.

  4. 04

    A person checks every failure

    A red test is a question: is it your app, or our test? We answer it before you see it.

What lands before every release

A green run, or a short list of real defects

Every defect comes with the steps to reproduce it, a screenshot and one line of business impact. Nothing else reaches you.

Release report · Demo app
Release 2.14 · triggered from CI
8 of 10 green2 reviewed defects
  1. 1Sign up as a new userGreen
  2. 2Verify the e-mail addressGreen
  3. 3Wrong password, then the right oneGreen
  4. 4Reset the passwordGreen
  5. 5Pay for a plan (sandbox)Green
  6. 6First action in an empty accountGreen
  7. 7Invite a colleagueReviewed defect
  8. 8Create a project (core action)Green
  9. 9Upgrade, then downgradeReviewed defect
  10. 10Cancel the subscriptionGreen
Defect · Invite a colleague

The invite link opens an “expired link” page

  1. Log in as the account owner.
  2. Open Team and invite a new e-mail address.
  3. Open the invite e-mail in the test inbox and click the link.
  4. Expected: a sign-up form. Actual: “This link has expired.”

Business impact: New teammates can't join, so accounts stay single-user.

Reviewed by a person on our team before it was sent.

Defect · Upgrade, then downgrade

The plan page still shows the higher plan after a downgrade

  1. Upgrade to the higher plan with a sandbox test card.
  2. Downgrade back to the lower plan.
  3. Reload Billing.
  4. Expected: the lower plan. Actual: the higher plan and its price.

Business impact: Customers may think they're still paying the higher price.

Reviewed by a person on our team before it was sent.

A sample built from invented demo data. Your report uses your flows and your release.
The offer

Start with six weeks. Keep going only if it pays off.

One way in, one service after it, and more when you need it. No tiers to compare and no annual contract.

  1. Step 16 weeks

    6-week managed pilot

    In six weeks, your ~10 most important flows are tested before every release, and you decide with evidence whether to keep going.

    Week 1
    We pick your flows together and agree in writing what success looks like. First findings arrive with steps and screenshots.
    Weeks 2 and 3
    The tests run from your CI or with one click. The first rounds include test fixes on our side.
    Weeks 4 and 5
    The flows run before every release. We keep the tests working as your product changes.
    Week 6
    An end-of-pilot report: what we found, what your team fixed, what's still open. We check it against the week 1 criteria, and you decide.

    If the agreed flows aren't running by the end of week 3, the pilot is free.

    From you: a test account and about an hour a week.

  2. Step 2Month to month

    Managed testing

    After the pilot, we keep doing the work.

    • Your flows run before every release, from your CI or with one click.
    • We update the tests when your product changes.
    • A person checks every failure, so you only hear about real problems.
    • A short monthly check-in: what we found, and which flows to add, drop or swap.
    • Plain-language tests and reports anyone on your team can read and download.
    Not included

    Fixing your bugs (that stays with your team), penetration tests or legal audits, unit tests, and native mobile apps.

Step 3When you need it

Grow with us

Add more when your business does. We quote it first and start only after you say yes.

  • On request
    More flows

    Add flows as your product grows. Extra flows change the price from the next month.

  • Included
    Release gate in your CI

    A red run can block the release right away, on the agent's result. A person then checks whether it was your app or our test.

  • On request
    Daily checks on your live site

    Your key flows run every day on production, with sandbox payments only and nothing sent to real customers.

  • On request
    Mobile web and API checks

    Your flows in a phone-size browser, and checks on the API behind them.

  • On request
    Visual, accessibility and speed checks

    Catch layout changes and basic accessibility or speed problems. Not a legal or compliance audit.

  • Included
    Handover when you hire QA

    Your new QA person starts with running tests and evidence. Move to a license and keep the tests.

  • On request

    For bigger teams, we work inside your release process with your people.

  • On request
    Workshops for your team

    A hands-on session for developers or product people on testing with AI agents.

After week 6, you choose

  • ContinueWe keep running and maintaining your flows before every release.
  • Switch to a licenseYour team runs the tests itself, and keeps the tests we wrote.
  • StopYou keep the end-of-pilot report and the tests you downloaded.

Flexible terms

  • Pilot first. No annual contract.
  • Month to month after the pilot. Cancel any time, effective next month.
  • Swap flows for free at the monthly check-in. Extra flows change the price.
  • Fewer than 10 flows is fine. Start with your most important ones.
  • You keep the downloaded tests and reports, even if you stop.
  • Anything beyond your flows is quoted first.
Book a 30-minute pilot call

If the agreed flows aren't running by the end of week 3, the pilot is free.

6-week pilot with success criteria agreed in writing in week 1. Then month to month, no annual contract.

Why you can trust what we send

A person behind every result

Marcel Veselka, founder of Wopee.io

I've spent more than 20 years in software testing, and I run a small SaaS company too. For weeks our own sign-up chart showed zero while people were signing up. The sign-up worked; the tracking behind it didn't, and nobody owned it. That's the gap we fill: someone owns your critical flows, every release. You talk to me on the first call.

Marcel Veselka, founder of Wopee.io
  • 28SaaS products we signed up for as strangers
  • 24 of 28had a defect in sign-up
  • 363 of 381findings held up when a person re-checked them
  • 15 of 381were our own mistake, and we published that

From our latest public research batch. Read how we tested 28 SaaS products

How we decide a failure is real

The agent's run finishes in minutes. Then a person on our team looks at every red test against the trace and the video, which can take longer. If our test was wrong, we fix it. Only defects in your app reach you, each with steps, a screenshot and one line of business impact.

Red test
A person checks the trace and video
App defect: sent to you, with evidence
Our test: we fix it, it never reaches your report
How pricing works

Priced by your flows. No seats, no per-run fees.

We don't publish a price for managed testing, because it depends on your product. Here is what sets it, and what you get for it.

  • What sets the priceHow many flows we cover and how often you release. Nothing else.
  • What's includedWriting, running and maintaining the tests, a person checking every failure, and the monthly check-in.
  • Never billedRuns, seats, reports, or fixing a test that was our mistake.
  • Compared with one QA hireA hire means recruiting, onboarding and months before the first useful test, and testing pauses when they're on holiday or leave. With us, first findings arrive in week 1 and the tests stay when people change.

After the 30-minute call, you get a written quote within one business day.

Compared with the alternatives

What changes when we do the testing

Six things owners and CTOs weigh when nobody owns testing yet. More dots means better for you: 1 is least favourable, 5 most.

Swipe to compare all four.

  • Managed testing
    We do the testing
    Time to first results
    Week 1
    Effort for your team
    About an hour a week
    Release confidence
    Your ~10 key flows, every release
    Trust in results
    A person checks every failure
    Risk
    Keeps running. Cancel monthly
    Cost
    A fixed monthly fee
  • Hire a QA engineer
    One person in-house
    Time to first results
    Months: hiring, then onboarding
    Effort for your team
    Hiring and managing a person
    Release confidence
    Good, while they have time
    Trust in results
    Your hire checks them
    Risk
    Pauses when they're away or leave
    Cost
    A salary, plus recruiting
  • Your developers test
    Your existing engineers
    Time to first results
    Now, when someone has time
    Effort for your team
    Developer hours every release
    Release confidence
    Mostly what they changed
    Trust in results
    Checked when someone has time
    Risk
    Stops when deadlines hit
    Cost
    Looks free, costs developer time
  • A Wopee.io license
    Your team runs our agents
    Time to first results
    After your team builds tests
    Effort for your team
    Your team writes and runs tests
    Release confidence
    Good, if your team keeps it up
    Trust in results
    Your team checks them
    Risk
    Depends on your team
    Cost
    License fee plus your team's time

Prefer to run it yourself? License prices are public, per user per month, on the pricing page.

Two people decide this

Answers for the CEO, and for the CTO

Money, risk and time on one side. Access, CI, noise and ownership on the other. Send each half to the person who asks.

CEOQuestions we hear from the CEO

What will it cost?
It's priced by your flows and how often you release. We look at your product, talk for 30 minutes, and send a written quote within one business day.
What if it doesn't work for us?
We agree the success criteria in writing in week 1 and check them in week 6. If it isn't worth it, you stop and keep the report.
How much of my team's time does it take?
About an hour a week, plus a test account.
Are we locked in?
No. Month to month after the pilot, cancel any time, effective next month. You keep the tests and reports you downloaded.
Will it help when a customer or investor asks how we test?
Every release gets a report of which flows ran and what failed. It's a record of your test process, not a certification.

CTOQuestions we hear from the CTO

How does it plug into our release?
Trigger a run from your CI or with one click. If you switch the gate on, a red run blocks the release right away, on the agent's result. A person then reviews each failure, which can take longer than the run, and tells you whether it was your app or our test.
What access do you need?
A test account, on staging or production as you prefer, plus a bot-protection exception or a sandbox where needed. Nothing is sent to your real customers, payments run only in a sandbox with test cards, we never train models on your code or test data, and EU data residency with a DPA is standard.
What about flaky tests?
A person checks every failure first. When our test was wrong, we fix it and it never reaches your report. The agent can be wrong, so we promise evidence and review, not zero false alarms.
Who owns the tests?
They're written in plain language and you can download them. Prefer to run them yourselves later? Switch to a license and keep them.
What can't it do?
CAPTCHAs, bot walls and 2FA need a bypass or a test account. It doesn't replace unit tests, and it isn't a penetration test or a legal audit. Native mobile apps are out of scope today.
Why not let our coding agent write the tests?
A coding agent tests the code it just wrote. We test your app from the outside, like a stranger, and a person owns every failure.
Not ready for a call?

Send your URL, get 3 findings free

Send us your product's URL. An agent signs up as a stranger and walks your first steps, and you get 3 findings with steps and screenshots within 2 business days. If we find fewer, you hear that too. Nothing from the check is ever posted.

  1. 1Your URL
  2. 2We sign up as a stranger
  3. 33 findings in your inbox

Step 1 of 2

We use your e-mail only to send the findings and one follow-up.

or bring it to a pilot call

FAQ

Other questions

What if the pilot doesn't work out?

If the agreed flows aren't running by the end of week 3, the pilot is free. We agree the flows in writing in week 1, so there is nothing to argue about at the end of week 3.

How fast do we see results?

In the first week. The agent signs up as a stranger and walks your flows, and the first findings arrive with steps and screenshots. From week 2 the tests run from your CI or with one click.

What happens when our UI changes?

Maintenance is part of the service. The agent reads the screen, not your code, so many changes don't break the tests at all. When one does, we update the test, and you only hear about it if the app is at fault.

Can we change flows later?

Yes. Swap flows for free at the monthly check-in. Extra flows change the price from the next month.

Can you test our mobile app?

Mobile web, in a phone-size browser, on request. Native mobile apps are out of scope today.

Do you fix the bugs you find?

No, fixing stays with your team. You get each defect with steps, screenshots and one line of business impact, so it's quick to act on.

What happens to our tests if we stop?

You keep the reports and the tests you downloaded. You can also switch to a license and keep running them yourselves.

How is this different from a license?

With a license your team drives the agents, and prices are public per user on the pricing page. With managed testing we do the work.

How is this different from the enterprise pilot?

The enterprise pilot is built for QA teams: 8 weeks, your people build about 20 tests with our coaching, and it asks 3 to 5 person-days per sprint. The 6-week managed pilot is for teams without QA: we do the work, and you give about an hour a week.

Book a 30-minute pilot call

Pick a time. We look at your product first.

If the agreed flows aren't running by the end of week 3, the pilot is free.

6-week pilot with success criteria agreed in writing in week 1. Then month to month, no annual contract.

  1. 1Before the callA founder looks at your product.
  2. 2On the callWhich flows we'd start with, and how the pilot would run.
  3. 3Within one business dayA written quote.

After week 6: continue, switch to a license and keep the tests, or stop and keep the report.

No deck. No sales sequence afterwards.

Prefer to run the tests yourself? See license pricing