Statwing
Summer 2012AcquiredDead simple statistical analysis software. Like R or SPSS but easy to…
Pressure-test this opportunity
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
Dead simple statistical analysis software. Like R or SPSS but easy to…
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
Statwing had a genuinely sharp insight: the barrier to statistical analysis was never the math, it was the expertise — knowing which test to run and how to read the result. Founded in 2012 by John Le Plat and Greg Laughlin, the San Francisco company built web-based software that let business users, analysts, and market researchers analyze data without an R or SPSS background, automatically choosing the right statistical test and explaining the answer in plain English.[4]
It was a small, capital-efficient company — famously a three-person team — backed by notable angels including Cloudera's Jeff Hammerbacher.[5] In May 2016, Qualtrics acquired Statwing in its first-ever acquisition, relocating the tiny team to Seattle and folding the technology into its platform as consumable statistics.[2] The lesson is clean: "make an expert skill easy" is a powerful product idea but a structural feature, most valuable embedded where the data already lives — which is exactly where Statwing ended up, at a fair outcome for a lean team.
John Le Plat and Greg Laughlin founded Statwing in 2012 and took it through Y Combinator's Summer 2012 batch.[4] Their insight came from watching how non-statisticians actually failed at data analysis: the tools (R, SPSS, SAS) assumed you already knew statistics — which test fits which data, how to check assumptions, how to interpret a p-value. The computation was never the hard part; the expertise gate was. Statwing's idea was to remove that gate.
The product reflected the insight precisely. A user uploaded data, picked the variables they cared about, and Statwing automatically selected the appropriate statistical test, ran it, and returned results in plain English a non-expert could act on.[3] The company stayed deliberately small and capital-efficient, attracting respected angels — Jeff Hammerbacher of Cloudera, Jason Seats of Slicehost and TechStars, Diego Basch of IndexTank — who recognized both the UX insight and the quality of the execution.[5] It was a focused team solving a real, specific problem well.
Statwing was a web app that made statistical analysis accessible to people without statistics training. Instead of writing code or navigating SPSS's dense menus, a user loaded a dataset, selected the relationship they wanted to explore, and Statwing figured out the rest: it chose the correct test for the data types involved, checked relevant conditions, computed the result, and presented it in clear language — often with a sentence like "these groups are significantly different" rather than a raw statistical table.[3]
The genius was in the defaults and the translation layer. Choosing the right test and interpreting output correctly are exactly where non-experts go wrong, and Statwing encoded that judgment so users didn't have to.[7] This was a real product innovation, but it was also inherently a capability that gained the most value when attached to data people already had. Statwing required users to bring data to it; embedded in a platform that already held the data — like a survey tool — the same capability would be far more powerful, because it would remove a step and meet users where they worked.
Statwing served non-statistician knowledge workers — market researchers, analysts, product and marketing teams — who needed answers from data but lacked formal statistical training.
The demand for accessible data analysis is huge, but the market for a standalone "easy stats" destination tool is narrower than the market for that capability embedded in tools people already use.
Statwing competed against incumbent statistical software (SPSS, SAS, R) on the axis of ease, and against the do-nothing option of guessing or asking a data-savvy colleague.[6] Its differentiation — genuine accessibility — was real, but it faced a structural ceiling: a standalone analysis tool must convince users to export their data into yet another product, adding friction. The capability was most defensible not as a destination but as a feature inside a platform that owned the data and workflow, which is precisely why a data platform, not a competitor, became the acquirer.
Statwing sold subscriptions to its web-based analysis tool, staying lean enough that a small user base could sustain a small team.[5] The capital efficiency was the point: with a three-person team and modest angel funding, Statwing didn't need a huge outcome to be a success for its founders and backers. The economics of a standalone easy-stats tool were probably always modest — the capability's full value required embedding — but by staying small, Statwing kept its options open, and Qualtrics's acquisition delivered a clean result without the company ever needing to prove a large standalone business.[1]
The central mechanism is that Statwing's insight — remove the expertise gate on statistics — creates enormous value, but that value is realized most fully when embedded where the data already is.[3] A standalone tool makes users import data and switch contexts; a platform that owns the data can offer the same easy analysis in place, with less friction and more reach. So the natural endgame for an "easy X for non-experts" capability is to become a feature of the platform that owns the workflow. Qualtrics, which holds vast survey and experience data, bought Statwing precisely to make analyzing that data consumable — turning the capability into a feature at the point of maximum value.[1]
Statwing's capital discipline — a three-person team on modest funding — meant it didn't need a large acquisition to be a win.[2] This is the recurring lesson of the capital-efficient companies in this collection: by not raising or spending at a scale that demands a huge outcome, a lean team turns a modest, undisclosed acquisition into a genuinely good result. Statwing never had to answer whether "easy stats" could be a large standalone business, because it stayed small enough that it didn't need to be.
The acquisition placed Statwing's people and technology exactly where the capability belonged — inside a data platform, applied to data users already had. The team joined Qualtrics's Seattle office and the technology became part of the product's consumable-statistics offering.[8] The capability lived on and reached more users than a standalone tool likely would have, which is the ideal outcome for a feature-shaped innovation: it gets absorbed where it can do the most good.