For teams and programmes
I step in where the stakes are high: a QA practice that needs building or resetting, a migration or launch that can't afford surprises, or an AI idea that has to survive contact with real data. I lead the work, make the calls, and leave behind something your team can run.
Ways to work together
3 to 12 months, part- or full-time
Lead your QA function or a critical programme while you hire, with a handover plan agreed from day one. I've built a QA function across 11 product teams from nothing.
Scoped to the programme
Rules for who moves when, data checks before anyone looks at screens, and written go/no-go decisions. The approach behind moving 2 million customers to a new app.
Build, platform and handover
Agents with masking, audit trails, cost controls and tests, wired into Slack, Jira, Asana and your data, then handed to your team to run.
Two weeks, fixed scope
An independent look at your QA practice or your AI plans, ending in a written report and a prioritised plan you can act on with or without me.
Automation and AI
Reporting generated from live sources, instead of chased by hand.
Not demos: masked, cost-controlled, tested and observable from day one.
Turning one successful agent into a way of building agents.
In numbers
The record
Problems reported in chat were getting lost, and sorting each one meant reading 50-message threads. I built an agent that turns every report into a tracked ticket, routes it to the right owner and keeps the person who raised it updated. The team runs it without me.
Two high-risk programmes run as one: moving customers group by group while switching off the old app. I set the rules for who moved when, and ran two testing approaches side by side to bring the timeline forward by weeks.
I led delivery of a multi-agent system that researches markets, customers and compliance in parallel, then merges the three verdicts into a sourced, one-page recommendation. Every claim is cited, disagreement stays visible, and a mid-build rescue cut each run from $26 to $0.87.
Career paths, hiring, standards and a leadership layer underneath me, so the function grew without depending on one person. QA went from being seen as a blocker to being trusted in the room where decisions get made.
Under pressure to ship new login security before the busiest period of the year, I ran an evidence-based readiness check. It found real regressions that could have locked customers out, and the release was paused with interim protections in place.
I brought in a new monitoring tool, used it to find exactly where logins were failing, then led the fix across design, engineering and QA. The improvement showed up in the numbers straight after release.
Contact
A few lines is enough. Every enquiry comes straight to me, and you’ll get a considered reply: a straight answer, a question or two, or an honest “I’m not the right fit”.
Prefer email? hello@firstniyyah.com