Small team. Serious QA.
We're a small team building shippable systems the agentic way — a micro team aimed at macro products. Testaumate is our QA product: a test-management platform that works today, and an agentic layer — authoring, healing, triage — that we are building on top of it.
Why we're building Testaumate
Test creation, and especially test maintenance, is expensive and brittle. Locators break, suites go flaky, and teams stop trusting automation enough to gate CI on it.
The current wave of agentic tools solves web authoring — and stops there. We think that's one level too shallow. So we're building the Author engine that authors intent-rich cases from an API spec, a URL, or a story, and re-authors them when they break — with healing we intend to measure rather than assert. And we're putting it on a clean Test Management foundation, because if the team doesn't trust the surface they meet first, the agents never get used.
- Author once into a case that stores intent, not a throwaway script
- Heal by re-authoring — the same engine, measured rather than asserted
- A TM foundation clean enough to actually live in
Three principles we don't trade away.
Small team, high bar. These are the calls we make again and again while building Testaumate.
Right architecture, not shortcuts
We narrow scope for a pilot, never quality. The platform is built modular from the start — separable control and execution planes, agents as contracts — so it can grow surface by surface instead of being rebuilt later.
Measured, not asserted
Self-healing is only worth trusting if you can see how good it is. We report heal quality — precision, recall, flake rate, false-heal rate — so the team decides whether to rely on it, rather than taking our word for it.
Clean beats cluttered
The incumbents are feature-rich and high-friction. We treat low-friction, self-explanatory UX as a real differentiator — the entry point that earns a team's confidence, not an afterthought bolted onto the moat.
The QA chain — Lead, Manager, Head.
At a small org it can be one person wearing all three hats; at an enterprise, three distinct people. We build the daily experience for the Lead, with the reports and controls the roles above them own.
Lives in the product daily
Structures the repository, owns suites, runs, and coverage, reviews cases — and is the one who judges whether the self-healing is trustworthy enough to rely on. The MVP is optimized for this user.
Runs the team & process
Owns team-level dashboards, work assignment, and operational control — configuring integrations, RBAC, suites, and process. A key influencer and buyer.
Sets the standard
Consumes executive and trend reports, sets org-wide standards and governance, and owns vendor selection and budget. The economic buyer.
We're onboarding early teams now.
If test maintenance is eating your sprints, bring a real suite and let the agents show what they can take off your plate.