Investor Brief · 2026

AI writes the code. Qestro writes the tests.

Developers ship at vibe-coding speed with Cursor, Claude Code, and Windsurf. The tests don't keep up. Qestro is the testing layer for AI-written software — paste a URL, describe what to verify in plain English, and get production-grade test cases across browser, mobile, and API. Self-healing assertions mean tests fix themselves when the UI shifts. Written once, run everywhere.

Category
AI-native QATest automation, post-LLM
Stage
Pre-Seedv0.1 in production
Founded
2025Tel Aviv · remote
Live At
qestro.appapi.qestro.app · qestro.io
01 · Thesis

Every wave of how-we-write-code creates a new layer of how-we-test-code.

Manual → Selenium. Cloud → SauceLabs. Mobile → Appium. CI/CD → Cypress. AI-assisted coding is the next wave — and it is the largest yet. Cursor crossed $2B ARR by February 2026 with 1M+ daily active users and 64% of Fortune 500 building on it. GitHub Copilot crossed 1.8M paid subscribers in late 2025. The tooling category that catches what they ship is open. Qestro builds it.

Bet 1

AI coding goes mainstream

By 2027, >60% of new code in production will pass through an AI pair-programming step. Volume of code grows; volume of human QA does not.

Bet 2

Tests become the bottleneck

Existing tools (Cypress, Playwright) demand a human-written test for every feature. That throughput cap is the chokepoint of vibe-coding. The market needs an AI-native generator + healer.

Bet 3

A unified surface wins

Today browser, mobile, and API testing live in three silos with three vendors. AI agents don't care about silos — they generate across them. The winner ships one platform, one prompt, three runtimes.

02 · Problem

Vibe coding ships fast. Vibe testing doesn't exist yet.

AI coding tools generate features in minutes. Tests still take days. The asymmetry is the bug.

Today · The broken loop

  • Dev uses Cursor / Claude Code to ship a feature in 20 minutes.
  • Writing the Playwright test takes 2 hours: hunt selectors, mock data, plumbing.
  • Selector breaks on the next UI iteration. Test goes red. CI is noisy.
  • Mobile and API tests live in different repos, different vendors, different mental models.
  • QA team becomes a queue. Velocity dies. AI advantage erased.

With Qestro · The closed loop

  • Dev pastes the new URL into Qestro and types one sentence in plain English.
  • Qestro's 6-agent swarm generates Playwright + Maestro + API tests in <30 seconds.
  • When the UI shifts, the self-healing engine detects, suggests, and merges the fix.
  • Browser, mobile, and API tests share one editor, one runtime, one analytics surface.
  • QA becomes a co-pilot, not a queue. Vibe-coding velocity holds end-to-end.
03 · Product

One prompt. Three runtimes. A six-agent AI swarm under the hood.

Qestro is not a wrapper around Playwright with a chat box. It is an end-to-end test orchestration platform built on a sequenced multi-agent pipeline that authors, verifies, heals, and runs tests — across web, mobile, and API — from a single SaaS surface.

Pillar I

AI Test Generation Swarm

Six specialist agents — Intake, Explorer, Planner, Codegen, Verifier, Aggregator — run inside a Cloudflare Durable Object. Acceptance criteria in, runnable Playwright code out, persisted as a versioned test case. Verifier refuses to ship code that fails static or dry-run checks. Auditable per agent, per tool call, per token.

Pillar II

Self-Healing Engine

When a test fails, Claude analyzes the diff between the live DOM snapshot and the expected selector. Selector-drift, timing-flake, and assertion-mismatch are auto-classified. A suggested fix is rendered alongside the run; one click merges. Reduces test-maintenance load — the industry's #1 reason teams give up on E2E automation.

Pillar III

Multi-Runtime Orchestration

A unified ITestRunner interface dispatches the same generated plan to Playwright (Chrome / Firefox / WebKit), Maestro (iOS / Android), or Axios (REST / GraphQL). Mobile and API are first-class, not bolted on. Cross-runtime analytics in one dashboard.

Pillar IV

Live Where Devs Live

Native Atlassian Forge app inside Jira issues — generate, link, and run tests without leaving the ticket. MCP server published for Claude Desktop, Cursor, and Windsurf. CLI for terminal-first teams. CI/CD plugins for GitHub Actions and GitLab. Qestro meets developers where they already are.

6agents
In the test-gen swarm
3runtimes
Web · mobile · API · one platform
<30sp95
From prompt to runnable Playwright
95%readiness
v1.0 GA shipping Q3 2026
04 · Why now

Three forces converging in a twelve-month window.

Force 1

AI coding crossed the chasm

Cursor: $2B ARR · 1M+ DAU · 64% of Fortune 500. Copilot: 1.8M paid subscribers. Claude Code hits 93% on coding benchmarks. 100M+ lines of AI-assisted code shipped per day. Test debt scales with code volume, not with headcount.

Force 2

Gartner names the category

October 2025: Gartner published its first Magic Quadrant for AI-Augmented Software Testing Tools — formal market recognition. Forecast: 80% of enterprises will integrate AI-augmented testing by 2027, up from just 15% in early 2023. Category creation phase is over; consolidation phase is starting.

Force 3

Capital flows confirm the thesis

2025 saw unprecedented VC inflows into AI testing. Momentic raised $15M Series A (Standard Capital, Dropbox Ventures, YC). QA Wolf raised $36M for mobile expansion. Mabl pivoted to "Agentic Tester". Testim was absorbed by Tricentis. The market votes the thesis is real.

05 · Market

A $24B market growing to $84B by 2034 — and the AI-native slot is open.

The category is large, growing, and structurally unconsolidated. Incumbents (mabl, Tricentis-owned Testim, SmartBear) predate the LLM era and are retrofitting agentic features under pressure. Open-source frameworks (Cypress, Playwright, Maestro) require a human author per test. The AI-native, vibe-coding-first slot is open.

$24.25B2026 TAM
Global test automation software market (GMI / Fortune Business Insights, 2026).
16.8%CAGR · '26–'34
Compounding driver: AI-assisted code volume growth outpaces human QA throughput.
$84.2B2034 projected
Total addressable category trajectory (long-horizon investor frame).
$8.81BAI-native · 2025
AI test automation specific segment, separated by MarketsAndMarkets.
$35.96BAI-native · 2032
22.3% CAGR — the fastest-growing slice of the parent market.
80%by 2027
Enterprise adoption forecast for AI-augmented testing (Gartner, 2024). Up from 15% in 2023.
SAM · Serviceable

$4.2B · AI-adjacent QA

Engineering orgs using at least one AI coding tool in production. With Cursor at 50K+ enterprise customers alone, the AI-coding-adopting universe is now in the hundreds of thousands of teams. ACVs range $3K–$80K depending on tier.

SOM · Reachable Year 1

$120M · Vibe-coding-first teams

Cursor/Claude Code-native shops, primarily 10–200 engineer Series A–C companies. Qestro's wedge: the teams that have already replaced StackOverflow with their IDE's chat panel and now hit a QA wall.

06 · Moat

Five layers of defensibility, each compounding.

Layer 1 · Data

Failure-pattern flywheel

Every test run feeds the self-healing engine. Selector-drift patterns, flakiness signatures, retry profiles — proprietary corpus that competitors can't synthesize. Compounds with every customer.

Layer 2 · Distribution

Native AI-IDE integration

Published as an MCP server in Claude Desktop, Cursor, and Windsurf. Qestro is one of the first three QA tools discoverable inside the AI tooling registry — first-mover advantage in agentic workflows.

Layer 3 · Workflow

Jira-native generation

Atlassian Forge app inside every issue. Acceptance criteria → tests, in one click. Forge marketplace listings compound exposure without paid CAC. 250K+ Atlassian Cloud sites are addressable distribution.

Layer 4 · Architecture

Edge-native cost structure

Workers + D1 + Durable Objects = sub-$0.01 marginal cost per test run. Competitors built on AWS pay 40–100× more for the same workload. Pricing power flows from this gap.

Layer 5 · Surface

Three runtimes, one platform

No competitor ships web + mobile + API + visual regression + load testing on a single platform with shared analytics. Bundle pricing dominates point-solution stacks over a 36-month horizon.

Compound effect

The moat is the loop

More tests → richer failure corpus → better healing → less maintenance → more adoption → more tests. The loop only closes for a player who owns generation, execution, and audit — Qestro's full-stack scope is the moat.

07 · Competitive landscape

The category is crowded. The AI-native slot is empty.

Platform Funding (latest) AI Generation Self-Healing Mobile API Jira-Native MCP / Agent-Ready
Qestro Pre-Seed (raising) ✓ Multi-agent ✓ Claude-powered ✓ Maestro ✓ Forge app ✓ MCP server
mabl $77M total ~ Agentic Tester (2025) ~ Heuristic ~ Web only ~
Testim (Tricentis) Acquired ~ Record/replay ~ Smart Locators
Momentic $15M Series A '25 ✓ LLM-driven ~ ~
QA Wolf $36M (managed) ✗ Humans ✗ Humans ~ New
Meticulous Series A ~ Session-replay
Cypress / Playwright Open source ✗ Framework only ~ DIY

Two structural gaps in the competitive set: (1) no incumbent ships a real multi-agent pipeline — mabl's "Agentic Tester" is a 2025 marketing pivot on top of legacy ML, and Momentic is single-agent LLM. (2) No competitor is MCP-discoverable inside Claude Desktop, Cursor, or Windsurf. The AI-agent registry is the new App Store distribution layer — incumbents haven't shown up.

08 · Business model

Land via free tier, expand via usage and surface.

Bottom-up SaaS with a frictionless free tier feeding pure-product virality from AI-IDE integrations, expanding through usage-based runs and enterprise compliance modules.

Free

$0

5 projects · 100 runs/month · solo developers. Acquisition tier; converts via run-cap nudges.

Starter

$99/mo

50 projects · 5K runs · Playwright + API · seed-stage teams.

Pro · Sweet spot

$499/mo

500 projects · 50K runs · mobile · CI/CD · visual regression · 10–50 engineer teams.

Enterprise

Custom

Unlimited · SSO/SAML · SOC 2 · on-prem option · 200+ engineers · regulated industries.

Target unit economics at scale (modeled, not yet realized): Gross margin 82% · CAC payback <8 months on Pro tier · Net revenue retention >130% driven by run-volume expansion.

08b · Go-to-market

Hybrid PLG + sales, matched to the dev-tools playbook that's actually winning in 2026.

Dev-tools categories with ACVs between $5K and $50K are dominated by hybrid motion — bottom-up product adoption feeding top-down sales conversations. Pure PLG is too slow for enterprise; pure sales-led can't reach individual developers. Qestro's pricing tiers ($99–$499 self-serve, custom enterprise) map exactly to this band.

Channel 1 · Inside the IDE

MCP-native distribution

Qestro is published as an MCP server in Claude Desktop, Cursor, and Windsurf. A developer asks Cursor to "write tests for this PR" and Cursor calls Qestro. Distribution happens at the surface where AI-coding teams already live — zero paid CAC, friction near zero.

Channel 2 · Inside Jira

Forge marketplace listing

Atlassian Cloud is the standard work tracker for the SAM. Qestro's Forge app converts acceptance criteria → tests inside the issue itself. 250K+ Atlassian Cloud sites are addressable, with marketplace search as a free acquisition channel.

Channel 3 · Where devs talk

Developer-led content

Twitter / r/programming / dev.to / YouTube. Founder posts shipped product + AI-agent learnings daily. Content fuels organic top-of-funnel; product self-serve converts. DevRel hire (round 1) scales this from one voice to a team.

Motion · Land

PLG-first acquisition

Free tier (5 projects, 100 runs/mo) is the front door. Time-to-value < 5 minutes: paste URL, describe in English, get a runnable test. Self-serve upgrade triggers on run-volume + project-count walls. Slack/Discord community for friction support.

Motion · Expand

Sales-assisted on team signals

When a Pro team adds 10+ seats or hits 50% of run budget, sales is paged. SDR reaches out with an audit + Enterprise SSO/SAML conversation. Pattern proven by Notion, Linear, Vercel, Sentry — and now LLM-augmented by AI marketing agents in the workflow.

Why this works for Qestro specifically: the product is a testing tool — developers can prove value alone, but adoption naturally pulls in a team (CI/CD shared) and then a buyer (compliance, audit, enterprise SSO). The expansion path is the product's own logic, not an artifact of pricing.

09 · Roadmap

Eighteen months, one straight line.

Q1 2026 · Shipped
Core platform live
Playwright runner, API runner, self-healing engine, CI/CD integrations, analytics, Jira Forge app, MCP server. v0.1 at 95% production readiness.
Q2 2026 · Just shipped
AI test-generation swarm
Six-agent pipeline orchestrated by Cloudflare Durable Objects. Intake → Explorer → Planner → Codegen → Verifier → Aggregator. Acceptance criteria in, persisted Playwright test out.
Q3 2026 · Now
v1.0 GA · pilot program
50 design-partner companies. Visual regression GA. Load testing GA. SSO/SAML enterprise track. Apple HIG-grade polish on every surface.
Q4 2026
Public launch · self-serve enterprise
SOC 2 Type II. Mobile visual regression. Allure / JUnit integrations. Public marketplace for community test packs.
Q1 2027
Series A · platform expansion
Desktop agent (Electron). Plugin marketplace. On-prem enterprise. International multi-region edge POPs.
Q3 2027
Category-defining scale
Default test layer for every AI-coding shop. Embedded in Cursor / Claude Code / Windsurf onboarding flows. ARR target trajectory toward Series B.
10 · Team

Founder-led, shipping daily.

Qestro is one of seven products in the LunaOS portfolio — an integrated AI-first engineering studio. The technical scope is real: production Cloudflare Workers + D1 + Durable Objects, native macOS app (Vibe Vault), AI-agent orchestration (LunaOS itself). Cross-product learnings compound.

Founder

Shahar Solomon

Founder & CEO. Builder of the LunaOS portfolio (Qestro, AMLIQ, Vibe Vault, FinsavvyAI, OpenSyber, ClawPipe, PushCI). Architect of the multi-agent swarm pattern. Ships product daily; the platform you are reading was deployed via Cloudflare Pages by the same person, an hour ago.

Hiring · Use of funds

Founding team forming

With this round: 1× Founding Engineer (mobile / Maestro depth), 1× Designer (Apple HIG fluency for the QA workflow surface), 1× DevRel (community + MCP / Cursor ecosystem). Lean by design; capital-efficient by architecture.

11 · Ask

Raising $2.5M Pre-Seed to ship v1.0 GA and reach 100 paying teams.

18-month runway. Lean burn structure. Capital-efficient architecture means a check that would fund 9 months at a YC-stage US startup funds 18 months here.

$2.5M
Pre-Seed · SAFE or priced · 18-month runway

Lead investor sought. Open to angels with operator backgrounds in dev tools, DevOps, or AI infra. Strategic checks (Atlassian, Cloudflare ecosystem funds) welcomed.

Use of funds

Founding engineering hires 45%
Design + DevRel 20%
SOC 2 + enterprise readiness 12%
Inference + infra (Anthropic, Cloudflare) 14%
Growth experiments (Cursor / Forge marketplace) 9%
12 · Why this team, why this moment

A first check, at the right edge.

Investors who backed Cypress at Series A, Postman at Seed, or Snyk at Pre-Seed asked the same three questions. Qestro answers them:

Why this team?

Velocity proof, in public

A live platform at 95% readiness, an AI swarm shipped today, a portfolio of seven products in production. Pace is the strongest pre-revenue signal — Qestro's commit graph is the evidence.

Why this moment?

The capital is moving now

2025 saw unprecedented VC inflows into AI testing (QA Financial). Momentic, QA Wolf, Mabl all closed material rounds in '25. Tricentis absorbed Testim. Gartner published the first AI-testing Magic Quadrant. The window where Pre-Seed at $2.5M can still win Series A in 12 months is 2026, not 2028.

Why this thesis?

The verification layer is open

Codegen is solved by foundation labs. Distribution into IDEs is solved by Cursor / Anthropic. The layer that says "this code does what it claims" has no incumbent. Qestro builds it.