QA for your critical flows
We find the bugs before your customers do.
Real people try your product the way your customers will, then send your team clear, step-by-step reports of what is broken and what to fix first.
- Ready: User can sign up
- Ready: User can log in
- Ready: User can reset their password
- Blocked: User can share a reportThe Share button does nothing on phones
- Ready: User can upgrade their plan
Result
Not ready to go
4 of 5 checked OK · 1 problem found
Open-source contributors toMDN Web DocsGoogle ChromeCypress
From first audit to protected releases
A simple path that starts free and only continues if it is working for you.
Free mini-audit
A free 45-minute call, then a written report with up to 10 real findings, each with clear steps to reproduce, plus the critical flows we would protect first.
Verify every release
Before each release, we test your critical flows by hand and explore the edge cases around them. You get a clear go / no-go and a written report, and bugs land in your own tracker.
Grow coverage with your product
What we find becomes a living checklist of your critical flows, re-verified every release and extended as your product changes.
Sample report
Bug reports your developers can act on
Every finding follows the same clear format, so nothing needs a follow-up question.
- A clear title that says what is wrong
- Numbered steps to reproduce
- Expected vs actual behaviour
- Severity, environment and evidence
Checkout
Coupon can be applied twice
- Steps to reproduce
- Add any item to the cart and open checkout
- Apply coupon SAVE10, press Back, then apply it again
- Pay with a test card and open the order summary
- Expected
- The coupon is used once per order.
- Actual
- Discount applied twice: total shows €32.40 instead of €36.00.
- Environment
- Staging · Chrome · Desktop
- Evidence
- Screenshot and short screen recording attached
A trained eye for the details that slip through
Real people do not follow the happy path. We test the way they actually use your product, and report what we find so your team can fix it fast.
Critical-flow verification
Sign-up, login, checkout, billing, onboarding: the journeys your revenue depends on, checked against a written checklist before every release.
Exploratory testing
A trained eye looking for what nobody planned for: odd states, confusing UX and the edge cases that only show up when a real person uses the product.
Clear, reproducible bug reports
Every issue comes with steps to reproduce, expected vs actual behaviour, severity and evidence, written so a developer can act on it straight away, in your Jira, Linear or GitHub Issues.
Release sign-off
A clear go / no-go signal with the evidence behind it, so releases stop being a gamble.
The details a script won't notice
A careful human eye checks what real people do, not just the happy path. This is part of what we look at on every release.
Empty, loading and error states
What shows with no data, or when something fails?
Double clicks and fast taps
Pressing Pay twice, or Back mid-flow.
Odd input
Emoji, very long names, apostrophes, pasted spaces.
Slow or lost connection
A request that hangs, then retries.
Dates, time zones and currency
Midnight, daylight saving, 1.000,50 vs 1,000.50.
Roles and permissions
What can a viewer or a removed user still reach?
Devices and browsers
Small screens, Safari, zoomed text.
Keyboard and accessibility basics
Tab order, focus, labels, contrast.
Wording and copy
Typos, unclear errors, mixed languages.
Refresh, back and extra tabs
Reloading mid-checkout, two tabs open.
Emails and notifications
Right content, right link, right time.
Interrupted flows
Leaving halfway and coming back later.
Start here
Get a free mini-audit
See where your product is most exposed before you spend anything.
Book a free mini-audit- A free 45-minute call to understand your product and its critical flows
- Up to 10 real findings, each with steps to reproduce, expected vs actual, severity and evidence
- The critical flows we would protect first, ranked by business risk
- A recommended plan, with no obligation to continue
Free 45-minute call
Pick a time that suits you
Choose a slot for your free mini-audit call. We will take it from there.
Online booking is opening soon
Email us and we will find a time for your free 45-minute mini-audit call.
Email hello@violetflows.comFixed prices for a defined scope
Pay per release, or keep a steady QA partner on a monthly plan.
Release Check
from €450 / release
A one-off check before a release, with no commitment.
- Up to 5 critical flows verified
- Edge-case pass around what changed
- Go / no-go recommendation
- Clear, reproducible bug reports
- Delivered within 48 hours
Most popular
Monthly QA
from €1,500 / month
A steady QA partner for teams that release regularly.
- Up to 4 release checks per month
- Exploratory sessions on new features
- Bug triage and retesting of fixes
- Monthly report with trends and risks
- Priority response within 24 hours
Team
Custom
For larger products or several releases a week.
- Multiple products or environments
- Testers on your release cadence
- Weekly exploratory sessions
- Full regression checklist per release
- Monthly review call
Prices are starting points for a defined scope, so there are no surprise hours. Every engagement begins with the free mini-audit, so you know exactly what you are buying. Larger products or extra environments are quoted individually.
Results
What clients say
Sample testimonial, to be replaced with real client feedback
“Violet Flows found issues our own team had missed, and every report was clear enough for our developers to fix straight away.”
Anna Muster
Engineering Lead, XCompany, Switzerland
Blog
Recently published
Practical notes on bug reporting, edge cases and release checks.
How to write a bug report developers can act on
The simple structure we use for every issue we report, so developers can act on it straight away.
4 min read
Seven edge cases that quietly break checkout
Checkout works on the happy path. These seven situations are where real customers run into trouble.
5 min read
A ten-minute checklist before every release
You do not need a long test plan to catch the worst surprises. Start with these ten checks.
3 min read
Specialist QA, without the agency overhead
Violet Flows is a small, focused QA team. You work directly with the people doing the testing, not an account manager, so feedback is fast and nothing gets lost in translation.
The focus is deliberately narrow: protect the handful of flows your business cannot afford to break, and do it well. Honest scope, clear reporting, and everything handed over to you in your own tools.
Our work goes beyond client projects: we contribute to open-source projects including MDN Web Docs, Google Chrome and Cypress.
Frequently asked questions
What exactly is in the free mini-audit?
We start with a free 45-minute call to understand your product and its most important flows. Afterwards we send you a written report with up to 10 real findings, each written as a clear, reproducible report with steps, expected vs actual behaviour, severity and evidence. You also get the critical flows we would protect first. It is real work, not a sales call, and there is no obligation afterwards. If your product is very clean we may find fewer than 10, and we will tell you honestly.
Is it safe to test our product?
Yes. We test like a normal user, on a staging or test environment or on your public product with your permission. We do not do security penetration testing or load testing, and we never touch real customer data.
How does your bug reporting work?
Every issue includes a clear title, steps to reproduce, expected vs actual behaviour, severity, environment details and evidence such as screenshots or a short recording. We write them in your own tracker (Jira, Linear, GitHub Issues and similar), so your developers can act on them immediately.
Do you offer test automation?
Not at the moment. We focus on experienced human testing, because a trained eye catches edge cases, confusing UX and odd states that scripts miss. If automation would genuinely help your product, we will say so honestly.
Who owns the checklists and reports?
You do. Checklists, test cases and reports are handed over to you, so you are never locked in.
Will you replace our QA or engineering team?
No. We work alongside your team. For companies with no dedicated QA, we act as that function; for teams with QA, we add focused capacity and an independent pair of eyes.
What do you need from us to start?
Access to a staging or test environment (or permission to test your public product), a few test accounts, and a short walkthrough of the product and its most important user journeys.
How quickly can we start?
After the mini-audit and a short kickoff, the first release check can usually happen on your next release.
Ship with confidence
Tell us about your product and we will show you where it is most at risk, for free.
Book a free mini-audit