the operator

A bird that eats bugs. Literally.

I’m Matt. I build the QA function for AI-native startups: the evals, the framework, the release judgment. That’s what lets you ship fast without shipping broken.

the name

My last venture was called Eterkoppe, archaic Swedish for spider, because spiders eat bugs. Vireo keeps the theme, tighter: a small songbird that lives on insects, and Latin for “I am green.” Same idea, fewer legs.

career arc

Over a decade catching bugs for a living.

  1. localization QA

    I started where most people don’t notice quality at all, localization QA, then owned 800+ test cases on a multi-platform HR product. It taught me that quality is a system, not a phase.

  2. regulated gaming · 5 yrs

    Five years as Senior/Lead QA on a multi-jurisdictional gaming platform serving 300+ casino locations across 7+ jurisdictions. Zero tolerance for defects, 100% compliance record. I co-built a Playwright/pytest framework that cut manual cycles 40% and reached 75% automated coverage, 700+ scripts across financial transactions and regulatory validation. Real money, real consequences, no “move fast and break things.”

  3. AI-native SaaS · now

    Today I’m the sole QA architect on an AI-native, multi-tenant SaaS platform: TypeScript + Playwright across three Next.js apps, a tRPC API, and a full CI matrix on GitHub Actions, plus the AI-specific layer: prompt regression, output validation, injection safety, and API cost monitoring. That’s the moat I bring to your team.

working principles

Four rules I don’t break.

This is the manifesto. If we work together, these are the defaults.

  1. 01

    QA accelerates, never blocks.

    A good quality function lets you ship faster, not slower. If testing is a bottleneck, it’s built wrong.

  2. 02

    Build in, don’t bolt on.

    Quality designed into the pipeline beats quality inspected at the end, every time.

  3. 03

    Automate the repeatable.

    Human attention is expensive. Spend it on judgment, not on re-running the same check by hand.

  4. 04

    Catch it where it’s cheap.

    A bug caught in CI costs minutes. The same bug in production costs a weekend, or a customer.

Want the bug-eater on your team?

Book a 20-minute call, or start with the free readiness grader. Either way you’ll get a straight, senior read on where your quality actually stands.