16 years in QA across web, mobile and API. Builds Claude-powered agentic workflows: test generation, self-healing E2E and the commands that tie them together.
Your QA area,
built end to end.
A senior QA duo from Argentina. We set up your QA area from the ground up — manual, automation or both, with AI and Playwright — and hand it over to your team in eight weeks.
- $ /build-and-ship PROJ-142
- ✓ Resolve repoyour-repo/
- ✓ Generate 4-file chain3 reused · 1 new
- ✓ Duplicate coverage check0 overlaps
- ✓ SDET rules review0 critical
- ✗ Test executionTimeoutError
- ↻ Root cause found, fixingattempt 2
- ✓ Test execution3 passed (44.0s)
- ✓ git-flowPR #1789 opened
6d 2h → 1d 19h// current engagement with a global digital platform · client identity confidential
A client that trusted the process
— and renewed the full team.
“You did a fantastic job and I couldn’t be happier with the results you achieved. Based on the team’s performance, the plan is to keep the full team in place.”
“They’ve spearheaded the automation testing process and framework in a few months. We are now at a point where we can exponentially grow our test suite and focus on the ones that are priority.”
- Weekly flaky tests: 12 → 0
- Time wasted by the 20 worst offenders: −66%
- Every failure gets a root cause, never a retry bump
And when it goes red, it’s real: most failures came from feature flags changing existing flows, caught before release.
QA at the endIssues caught at PRShared environmentsIsolated env per branchRisky releasesPassing suite required to mergeUnclear QA ownershipQuality is everyone’s job
// one enterprise client · maturity Jul 2025 – Apr 2026 · KPIs as of Sep 2026 · client identity confidential
Built around what you need.
Yours in eight weeks.
- week 0DiscoveryYour product, team and where quality hurts.
- week 0–1AgreementScope, success criteria and timeline in writing.
- weeks 1–7BuildStrategy, tests and tools, proven on your real flows.
- week 8HandoverWe document and train. Your team runs it.
- afterOptional supportMonthly maintenance and new commands.
Our edge:
AI that does the heavy lifting — under human review.
Commands and agents installed in your repo, governed by your conventions as rules the AI respects on every file it touches.
Watch /build-and-ship run in 60 seconds.
From a Jira ticket to a reviewed pull request. Generates Page Object, Steps, Constants and Spec, checks duplicate coverage, reviews the diff against your conventions and runs the test for real before opening the PR.
Finds the real cause of intermittent failures — races, shared data, bad waits — and ships a fix. Never a retry bump or a longer sleep.
Reads traces from failing tests and repairs broken locators and page objects when the UI changes, without touching the rest of the suite.
Reviews pull requests against your SDET conventions and leaves precise inline comments your team can act on.
Traces what a PR actually touches, runs only the relevant specs and reports the result on the ticket.
A flaky suite is worse than no suite.
Illustration, not live data. We treat flakiness as a bug with a root cause, never a retry bump.
How much time would automation give back?
Two senior SDETs. Nobody junior behind the curtain.
QA lead and senior SDET since 2011. Leads an automation team and designs AI agents that turn requirements and live user flows into running E2E tests.
Questions we usually get.
That’s where we add the most value. We set up the whole area from scratch, or just the piece you’re missing.
A working QA area: strategy, test cases, an automation suite in your CI, AI commands (optional), metrics and a trained team.
Your team owns it. If you want, we stay on with optional monthly support: suite maintenance, new commands and PR reviews.
No. We can migrate you from Cypress, Selenium or WebdriverIO.
Mainly Claude Code and Codex, with custom commands and MCP integrations.
Yes. Your team keeps its own license (Claude Code or Codex), so everything keeps working after we step back.
Everything runs in your environment, under your policies.
We scope to fit, and flag it early if anything changes.
Argentina (GMT-3), overlapping US hours. English and Spanish.
Got a QA challenge?
Let's solve it.
30 minutes, a conversation — not a sales pitch.