Research deserves better than a report.
We’re building the research operating system - software where customer understanding flows from question to insight to shipped change, and back again. A repository stores. reOS circulates.
Most research doesn't fail in the field.
It fails afterwards. A team does careful work - recruits thoughtfully, interviews well, analyzes honestly - and the result becomes a deck. The deck gets presented once, nodded at, and filed. Six months later someone asks the same question, and the loop starts over from zero. We watched this happen at every company we’d worked at, and it never stopped feeling like a waste of something precious.
Then AI changed the economics. Plausible findings are now cheap - a model can generate a hundred an hour. What became scarce is trust: claims you can actually check, traced to the second a customer said them. Tools that summarize were suddenly everywhere. Tools that let you verify were nowhere.
reOS is our answer to both problems at once. Every insight is validated against its source. Every finding becomes a tracked initiative. And every shipped change notifies the customers who asked - and seeds the next question. Research stops being a deliverable and starts being how the company learns.
Principles we won’t trade away.
Four convictions that shape every product decision - written down so you can hold us to them.
If a claim can’t be traced to its source, it doesn’t ship. An insight you can’t check is an opinion with good formatting.
Research isn’t done when the deck is presented. It’s done when the change ships and the next question is already asked.
Studies shouldn’t be silos. Your tenth study starts from everything the first nine learned - that’s what an operating system is for.
Powerful doesn’t mean loud. reOS should feel like water finding its level - steady, fluid, and out of your way.
A small team, close to the work.
Researchers, engineers, and designers who've sat through enough readouts to know where they go to die. We talk to customers every week - in reOS, naturally.
If closing the loop sounds like your kind of problem, we’d like to hear from you.