Spur logo

Spur

Spur is your AI QA Engineer. Test your websites with natural language.

Summer 2024active2024Website
Artificial IntelligenceDeveloper ToolsB2B
Sponsored
Documenso logo

Documenso

Open source e-signing

The open source DocuSign alternative. Beautiful, modern, and built for developers.

Learn more →
?

Your Company Here

Sponsor slot available

Want to be listed as a sponsor? Reach thousands of founders and developers.

Report from about 2 months ago

What do they actually do

Spur provides an AI-powered quality assurance tool that lets teams describe website tests in plain English and have the system run them end‑to‑end in a real browser. It focuses on validating critical user flows like checkout, payments, and localization without requiring code or brittle selectors. Tests can be set up quickly, run on demand or on a schedule, and produce evidence and alerts when something breaks (homepage, docs quick start).

Under the hood, Spur uses a vision‑first approach: the AI interacts with the site based on what it “sees,” similar to how a human tester operates the UI, which can reduce flakiness from minor DOM or UI changes (docs: vision‑first approach). The company works with teams that need broad, repeatable coverage across regions, languages, and partner pages, and it publishes customer case studies (e.g., Norse Atlantic Airways) to show how issues were caught before impacting revenue (Norse Atlantic case study).

Who are their target customer(s)

  • E‑commerce product/engineering teams running checkout and catalogs: They need to ensure new releases don’t break revenue flows across locales, payment methods, and partner pages, but manual pre‑launch sweeps are slow and incomplete; missed bugs have caused revenue loss (homepage, Norse case).
  • Small engineering teams/startups without dedicated QA: They ship frequently but rely on manual checks or fragile automation, burning engineering time and still missing broad coverage (YC profile, pilot process).
  • Product/experiment owners (pricing, localization, feature flags): Experiments can fail silently due to pricing, regional availability, or third‑party breakages and need reliable pre‑launch validation to avoid hidden revenue impact (homepage use cases, Norse case).
  • QA managers/test‑automation engineers: They fight flaky UI scripts and high maintenance; tests break on UI changes and slow releases, creating a maintenance tax they want to lower (docs: vision‑first, YC profile problem).
  • Ops/engineering teams for multi‑region or multi‑language products (travel, marketplaces, global retail): They must cover many variants and languages reliably and can’t feasibly validate all edge cases by hand on each deploy (homepage use cases, customer examples).

How would they acquire their first 10, 50, and 100 customers

  • First 10: Founder‑led, high‑touch 7‑day pilots for YC startups and known e‑commerce/travel brands using a scripted onboarding (kickoff, hands‑on setup, daily check‑ins) to prove value quickly; close with live demo evidence and the Norse Atlantic case study (pilot process, Norse case).
  • First 50: Turn the 1‑week pilot into a repeatable playbook: targeted outbound by an SDR/BDR, founder‑led demos, dedicated Slack onboarding, and content (3–4 case studies/blogs) to build trust; use documentation and quick start guides to shrink time‑to‑value (docs quick start, blog/case studies).
  • First 100: Add a small sales team for account‑based outreach in key verticals; formalize partner channels (e.g., agencies/Shopify partners, QA consultancies) with webinars and co‑marketing; convert via on‑demand demos, case studies with concrete savings, and a lighter self‑serve path using no‑code quick start (Norse ROI, docs: start in minutes).

What is the rough total addressable market

Top-down context:

Estimates for the global automation testing market in 2024 range widely but point to a large, fast‑growing category: sources place it roughly between ~$18B and ~$36B in 2024, with mid‑ to high‑teens CAGR through the next decade (Fortune Business Insights, Precedence Research). Broader software testing (services + tools) is also sizable and growing (TBRC software testing).

Bottom-up calculation:

Focus on Spur’s near‑term serviceable market in web commerce and travel: ~65k Shopify Plus merchants as a proxy for mid‑market/enterprise ecommerce plus ~1.1k airlines, along with comparable enterprise ecommerce on other platforms. At a $30k average ACV and ~7% adoption across these segments, the serviceable market is roughly $180M–$250M; at ~15% adoption, ~$400M+ (StoreLeads Shopify Plus count, ATAG airlines count).

Assumptions:

  • Shopify Plus (~65k live stores) is a reasonable proxy for mid‑market/enterprise ecommerce needing robust checkout QA; similar complexity exists on other platforms (StoreLeads).
  • There are ~1,100 airlines globally that operate complex, high‑stakes booking/ancillary flows relevant to Spur’s value proposition (ATAG).
  • Average ACV for managed AI QA across these segments is ~$30k, with adoption scenarios of ~7% (early) to ~15% (maturing).

Who are some of their notable competitors

  • mabl: Cloud SaaS end‑to‑end test platform with AI‑assisted authoring, “self‑healing,” and web/mobile/API coverage; overlaps with Spur on low‑/no‑code creation and maintenance reduction (mabl AI).
  • Testim (Tricentis Testim): Low‑code UI test automation with AI‑driven locators and fast authoring; positions around stability and speed of creation, now part of Tricentis’ suite (Testim product).
  • testRigor: Codeless, plain‑English test platform targeting non‑technical teams; emphasizes writing tests in everyday language with low maintenance for regression suites (testRigor).
  • Applitools: Leader in visual AI testing and cross‑browser/device visual regression; often complements functional suites but overlaps on catching UI/localization regressions (Applitools).
  • Cypress: Open‑source, developer‑first E2E framework with a commercial cloud and emerging AI/NL features; preferred by teams wanting code‑centric control vs. fully managed codeless QA (Cypress).