Your question gets read before anything gets built.
You write a question in your own words. Before anything runs, we read what kind of question it is, what field it comes from and what shape of data it needs. That reading decides how deep the answer goes and which method answers it. Here are three real readings:
How an answer is put together: behind the answer →
The question decides the rung, not the budget.
Every question about your data is answered on one of three rungs. It starts like a chatbot and does not stop there.
A total, an average, a count, the highest or lowest group, the value in a given month. It comes back in seconds, read from all of your data, with how it was worked out, and saved so you can find it again instead of asking twice.
What is driving this? Is the difference real? Where is this heading? We run a tested statistical method from our library on your data and interpret it: charts, tables, and a written report that says what the numbers mean and which method produced them. Run it again on next month’s file.
Your own definition of an active customer, your own funnel, the comparison your board asks for every quarter. When no method in the library fits, we build a full analysis for your data, based on proven statistical models. It becomes your own tool, ready the next time the question comes round.
You do not have to choose. Ask the question and we answer at the rung it needs, and we tell you which one that is before any larger piece of work starts. As a guide: a fact from your data is an Answer; why, whether or what next is Analytics; a question specific to how your business works, that you will keep asking, is Custom Analytics. An Answer that turns up something worth pursuing is a good reason to run the Analytics on the same data, and nothing you learned is wasted.
Change one word, get a different expert.
Your question carries several signals and each is read on its own. One of them is the field you work in, and you never pick it from a menu, because your own words already say it. Here is the same question three times, changing only the middle:
The statistics underneath don’t change. The expertise in front of them does, and all you did was describe your own business. If the question isn’t phrased for any one field, that’s a real answer too: you get the generalist, not a guess. The whole story →
The method is named and the working is shown.
Whichever rung your question lands on, the same four things are true of what comes back.
You ask in plain words and we pick the method.
The same data gives the same numbers, and you can run it again on new data.
The method is named and the working is shown, so when someone asks how you know, you can show them.
Everything is saved to your account, and you can ask across all of it later.
It's a link. And it's yours.
Calculated, not hallucinated: the numbers were computed before a word was written.
- ✓Interactive report: explore the charts and diagnostics, not screenshots.
- ✓The method, stated: what was tested, why that test, whether it held.
- ✓PDF & one-click citation: APA, MLA, Chicago, BibTeX.
- ✓The R source: reproducible by anyone, including you.
Every answer puts another landmark on the map.
An analysis doesn’t just answer your question. It finds ideas in your data: that tenure predicts churn, that margin breaks past a discount band, that one cohort behaves unlike the rest. Each becomes a point on a map of your business. The more you ask, the more of the landscape is charted, and the bigger the questions you can ask next.
This is why the questions get better over time. A brand-new tool can only answer from the data in front of it. A charted business can be asked things that cross several analyses at once, and every answer comes back citing the piece of work that proves it.
And your agents can read the same map. Point whichever AI you use at your library and it navigates by these landmarks, answering from your own saved analyses instead of guessing about your industry. The knowledge layer →
Read the code that talks to your data.
The MCP server, the tool contracts and the transport options are public under an MIT licence, so you can see exactly what connects to your assistant before you connect it, and run it yourself if you’d rather.
The statistical analyst in your AI chat: bring data and a question, own a citable, re-runnable analysis. Works in Claude, Cursor, and any MCP client.
Where to start
One email with your data and your question. We take it from there.
Cymple
Data Scientist
Send me your data and question, I’ll send you the analytics.
Try it on your own data
14 days free.
Answers, analytics and custom analytics. No card, no call, nothing to install.
14 days free. →