EKK-01 · MMXXVI · QA SERVICE
We build your test safety net.
You keep shipping.
An automated test safety net on your critical flows, wired into your CI. Your first flows run green within two weeks, then we build out the suite. After that we keep the net green as your fractional QA. Scope and price are fixed after the intake, no full-time QA needed.
Free 30-minute QA scan. No strings attached.
You ship often, but there is no safety net.
Every release is a guess
Does the rest still work after this deploy? You only find out when something breaks.
You hear about bugs from a customer
Production is the first place it shows. That is exactly one step too late.
Full-time QA is too expensive
Contracting a test automation engineer costs €13,000 to €15,000 a month (indicative). Hiring one on payroll costs €5,000 to €7,000. Both for something you do not need full-time. But doing nothing costs more.
First an intake, then we build, then we keep it green.
Intake call
Together we set the scope of your test suite: which flows really matter, which applications and environments you work with, and which stack fits your team best. Then you get a quote built around your situation.
Build phase, fixed price
We start with your most important flows: those run green within two weeks. After that we build out the suite and wire it into your CI, with a readable report and a clean handover. How long the full suite takes follows from the scope: the number of critical flows, the number of environments, and how your app is put together. Based on previous engagements, expect four to sixteen weeks. Fixed price, known up front, not hourly.
Fractional QA, monthly
After that we keep the safety net green as your fractional QA: maintaining the suite, covering new releases, adding coverage for new features, and flagging regressions before your customers do.
A safety net you can read, not just run.
- A working Playwright suite on your critical flows, in TypeScript, with stable selectors.
- Integration into your CI/CD, with failure screenshots on every run.
- A business-readable report (Excel) that shows what was tested and what the outcome means.
- Handover and a short knowledge session so your team can carry it forward.
The outcome is verified. Not hundreds of meaningless tests, but a reliable safety net on what matters.
See a sample reportThe same monitoring we sell runs on our own platform.
No borrowed customer logos — just how it works here. Ekkora QA is monitored by its own Guard, day in, day out.
- Over 2,800 automated tests run against every change to our own platform before anything goes live.
- Every test run is judged by Guard — the same product our customers subscribe to. A skipped test does not count as green there; neither does an empty result.
- Every week, the same report a Guard customer gets rolls out here: what ran, what broke, and how much confidence the data deserves.
- Backups run daily and the restore has been rehearsed, not assumed. The difference between those two is exactly the difference we guard for customers.
Why this matters: a QA vendor that doesn't treat its own releases the way it would treat yours is telling you something. We eat what we serve.
See what that report looks likeA senior QA person, for part of the week.
After the build phase we keep your safety net green as your fractional QA. That is an experienced QA person who is yours for a set part of the time, on a monthly basis, instead of a full-time hire.
- No full-time cost. Contracting a test automation engineer easily costs €13,000 to €15,000 a month (indicative). Hiring one on payroll costs €5,000 to €7,000, plus recruitment, onboarding, holidays and sick leave. And most teams do not need forty hours of QA a week.
- Senior judgment anyway. You get someone who knows which flows matter, writes stable selectors and prevents flaky tests. Not a junior counting tests.
- Continuity. The same people know your app and keep the suite green as your product grows. Knowledge does not walk out the door.
- Flexible. Scale up around a big release, scale down when it is quiet. Cancellable monthly, no hiring risk.
- Faster than hiring. Recruiting a QA engineer costs you months before a single test runs: the vacancy, the interviews, the notice period. With us your first flows run within two weeks, and we know your suite because we built it.
What is included? Maintaining the suite, covering new releases, adding coverage for new features, and flagging regressions before your customers call.
Book an intakeExtra work such as visual regression between two environments, performance testing (k6) or CI-gating is discussed and folded into the monthly fee. At the start, or later in the engagement. All amounts follow from the intake, excl. VAT.
Deliver QA under your own name.
Ekkora builds and maintains the test safety net white-label. You add your margin, your clients see no bugs, and you stay the trusted partner. Same product, your brand.
Sharp, honest, fast.
Sharp
We test what matters: your critical flows. No noise, no test theater, no coverage for coverage's sake.
Honest
You see exactly what was tested and what the outcome means, in plain language. No jargon, no black box.
Fast
A working safety net in weeks, not months. What is green today, we keep green.
Questions, answered briefly.
What does it cost?
That depends on the scope, and we set that together in the intake call. After that you get a quote: a fixed price for the build phase, and a monthly fee for the Fractional QA. Not hourly, and no standard package that happens to fit you.
What is a fractional QA?
An experienced QA person who is yours for part of the week, on a monthly basis, instead of a full-time hire. You get senior judgment and someone who owns the quality of your releases, but you only pay for the part you need. No recruitment, no permanent contract, cancellable monthly.
How long does the build phase take?
Your first critical flows run green within two weeks, so you are covered while we keep building. How long the full suite takes follows from the scope: the number of critical flows, the number of environments, and how your app is put together. Based on previous engagements, expect four to sixteen weeks. In the intake we make it concrete, and then it goes into the quote.
What happens in the intake call?
We set the scope of your test suite: which flows really matter, which applications and environments you work with, and which stack fits your team best. That produces a clearly scoped build phase with a fixed price.
Which stack do you use?
Usually Playwright with TypeScript, wired into your existing CI/CD. In the intake we look at which stack fits your team and your application best.
Can I add extra work later?
Yes. Visual regression between two environments, performance testing (k6) or CI-gating is discussed and folded into the monthly fee. That can be at the start, or at a later stage of the engagement.
What if there is little to find?
Then you have a safety net that proves it on every release. We measure on reliability and judgment about what matters, not on the number of tests.