We’re a small, bootstrapped team that’s been deep in QA consulting for a while. Across projects, we’ve seen the same issues repeat: • Test generation is slow and manual • Maintenance is painful (especially flaky selectors) • Reporting sometime sucks • Flaky tests kill confidence in automation

So we started building something that: • Observes browser interactions and generates Node.js test code • Uses AI (including vision models) for self-healing + stable selectors • Is now adding LLM + natural language support on top

We’ve spoken with several CTOs who manage teams of manual QA engineers. A recurring theme is that they want to empower those teams to move into automation, but are overwhelmed by the crowded landscape of tools claiming to do that.

Our challenge is that while we think we can genuinely help with our tool, the space is incredibly crowded: 1) No-code/low-code tools: Tricentis Tosca, Leapwork, Reflect, ACCELQ, Katalon, so many others 2) AI-native startups (many YC-backed): Browser Use, Momentic, Meticulous, Fix AI, Spur, Browser Base, Intryc, Skyvern, BugBug, and ton of them. 3) RPA: UIPath, Automation Anywhere, Blueprism 4) Plus tons of QA consulting companies offering bundled services and their products

Even with all these tools, we’ve found that complex, product-specific test cases still fall through the cracks. That’s why many teams still rely on Selenium, Cypress, or Playwright to build custom frameworks — especially when they need deeper logic, API integration, CI/CD workflows, or custom deployment handling.

⸻

Where we’re stuck: 1) We generate actual code, so our ideal user is SDETs, QA automation engineers, or developers 2) But we don’t want to leave behind manual testers who want to do automation 3) Should we build a no-code UI layer on top now — or focus on technical users first?

Also, from a go-to-market perspective: 4) Should we open source the base tool and build developer trust? 5) Should we go closed-source SaaS from the beginning? 6) Or productize as a QA service powered by our internal tool, like QA Wolf, Muuktest or Rainforest QA?

Right now, we’re actively interviewing CTOs, VPs of Engineering, and senior engineers to understand where we can deliver the most value — and whether this is something they’d actually buy.

If you’ve built a devtool, QA platform, or anything in a competitive B2B space: • How would you approach this today? • Would you prioritize devs or manual testers? • Would you start with open-source, SaaS, or productise service?

Thanks for reading!