EverESSt saves the equivalent of two FTEs – and turns documentation into an asset

How EverESSt used SQAI Suite to accelerate test design, keep documentation current, and put QA insight in the hands of the whole product team.

“SQAI Suite redefined QA by turning documentation into a strategic asset for faster, higher-quality testing.” — Kristof Creemers, EverESSt

The challenge: knowledge everywhere, time nowhere

Like many software teams, EverESSt had no shortage of documentation — it just lived everywhere. Requirements, specs, and context were spread across Confluence and Jira, and a test analyst preparing to write test cases first had to hunt through all of it. That searching was slow, hard to do exhaustively, and expensive: covering it properly meant putting more test resources on the problem.

There was a second, quieter problem. A lot of that documentation was out of date. When a tester worked from a stale page, the resulting test cases were wrong — and fixing them meant first fixing the documentation, by hand.

EverESSt wanted a way to move faster without cutting corners on quality.

The approach: a QA companion plugged into the tools they already use

EverESSt connected SQAI Suite directly to Jira and Confluence, so the platform reads from the same sources the team already maintains — no migration, no copy-paste. Validated test cases flow out to TestRail, keeping the team’s existing test-management workflow intact.

In practice, a test analyst points SQAI at a feature and asks it to pull together every relevant piece of documentation — purpose, status, dependencies, known issues — and return a summary, with the consulted sources shown alongside. The tester stays firmly in control: they verify the summary, spot documentation that’s outdated or contradictory, and correct it before a single test case is written.

That human-in-the-loop step turned out to be one of the most valuable parts. Because SQAI surfaces exactly where each piece of information came from, EverESSt can see at a glance which pages are stale and fix them — turning routine test prep into an ongoing cleanup of their knowledge base.

Beyond QA: the whole product team gets involved

The biggest shift at EverESSt wasn’t only speed — it was who gets to use it. Product owners and business analysts now query SQAI themselves to pull feature information out of Confluence, then correct documentation where needed, without pulling a tester into a meeting to do it. The tester picks up from a cleaner, verified starting point and moves straight to test-case design.

The result is a shared source of understanding: everyone can see the same information, see where it comes from, and help keep it current. Over time, that’s raising the overall quality of EverESSt’s documentation — and teaching the team how to structure Confluence and Jira so the most critical information is easy to find.

What’s next: automation

EverESSt is now building out its test-automation framework with SQAI in mind — designing test scenarios in business-readable formats such as BDD and Gauge, so less-technical team members can contribute, and using SQAI as a coding companion to help generate the framework functions themselves. The goal: keep descriptive test design fast and accessible, and let the platform accelerate the technical work behind it.

The results

• The equivalent of ~2 FTEs saved. According to Filip Michiels (CEO) of EverESSt, SQAI Suite frees up the equivalent of two full-time test team members (in a team of 3).
• Faster test analysis and design — documentation research that used to take significant manual effort is now handled in a fraction of the time.
• Documentation as a living asset, continuously verified and improved as a by-product of everyday QA work.
• A cross-functional QA workflow spanning testers, product owners, and business analysts — all working from the same verified information.