We built Vindex because requirements quality keeps deciding what ships — and what breaks.
Matthias and the Auxiliary Digital team kept seeing the same pattern: teams did not have a code problem first. They had requirements that looked ready, then turned into rework and production defects once engineering started.
Used in our work
Auxiliary Digital uses Vindex every day.
The tool came from our own delivery process. We use it to review story health before planning, so the same problems do not keep turning into sprint rework.
Built inside Auxiliary Digital
Used by the team every day
Every day
Used in Auxiliary Digital delivery work
Before planning
Where story health gets checked
- Stories looked ready in planning, then turned into rework by Wednesday.
- Teams were arguing over estimates when the real problem was unclear scope.
- Acceptance criteria were missing, vague, or impossible to test.
Why we built it
Vindex started as a way to stop our own bad requirements before we built them.
At Auxiliary Digital, we help teams ship software. The hardest delivery problems rarely start as code problems. They start as vague scope, missing acceptance criteria, hidden dependencies, and outcomes no one can test.
We use Vindex every day because it gives our team a clear quality gate before work reaches planning. That daily use is why we want to bring it to your organization too.
Built from real delivery work
Auxiliary Digital uses Vindex every day on the work we plan, review, and deliver. The product exists because the problem kept showing up in real projects.
Focused on story health
Vindex gives product and engineering a shared read on whether a story is actually ready, before planning turns ambiguity into delivery risk.
Designed for serious teams
Requirements often carry product, customer, and operational context. Vindex is built with security and data boundaries in mind from the start.
Meet the team
The people behind Vindex.
A small team that watched the same sprint failure repeat across real delivery work — and built the tool they wished their teams had.
Matthias Pupillo
Managing Partner, Auxiliary Digital
Leads Auxiliary Digital and started Vindex after watching the same requirements failures resurface across delivery projects.
Connect with Matthias on LinkedIn
Kevin Kozlowski
Client Partner
Works with client teams every day — the refinement problems they run into are what keep Vindex's findings honest.
Connect with Kevin on LinkedIn
Noelle McIntyre
Account Manager, Vindex
Helps teams get from their first score to a working quality gate, and makes sure what they learn reaches the product.
Connect with Noelle on LinkedIn
Want to talk to one of us directly? Get in touch.