Once, there was a question
Picture someone who runs a sales team. It is Monday morning, the numbers from last month are in, and one of them looks wrong. Renewals have dipped. Nobody mentioned it on Friday.
They have a question, and it is a good one: why? They know the customers, the deals and the people. They know this business better than any analyst could. The one thing they cannot do is ask the data.
Every day, the question waited
So the question goes where questions go. Someone has to find where the data lives, work out how it fits together, write a query, pick a chart, put it on a dashboard and publish it. That is six steps and at least two tools, and it usually happens in somebody else's queue.
The answer comes back on Thursday. By then the meeting it was for has happened, and the answer has raised a second question, which joins the back of the same queue.
A dashboard was meant to end this. Do the six steps once and let everyone look. It works for the numbers a team checks every week. For everything else, a dashboard is a set of answers to the questions someone thought of on the day it was built. The moment a number on it looks odd, it has nothing more to say.
So most questions were never asked at all. It was not worth the wait. People went with what they already believed.
Until one day, the question could simply be asked
Then large language models became good at turning a plain-English question into an analysis. Upload a spreadsheet to a chat assistant, type the question the way you would ask a colleague, and an answer appears in seconds.
For the first time, the person with the question and the person who could answer it were the same person. The queue was gone. It looked like the end of the story.
Because of that, we saw what was still missing
It was not the end. The answer arrived quickly, and then three things went wrong with it.
It scrolled away. The chart from an hour ago was somewhere up the thread, and by next week it was gone.
It could not be checked. A confident paragraph and a tidy chart say nothing about which rows were counted or how a figure was worked out. Our sales lead is about to walk into a room and say a number out loud. They need to know it is right.
It could not be handed over. A colleague who was not in the conversation got a screenshot, and you cannot ask a screenshot a question.
Speed was never the whole problem. An answer you cannot keep, check or share is only a little better than no answer.
Because of that, we set out to build the rest
Those three gaps became the brief. Each one turned into a decision that still shapes the product.
Answers should last, so every answer lands on a canvas as a chart, a figure, a table or a written insight, and stays there. The next chapter explains why we chose a canvas over a chat window.
Numbers should be checkable, so charts are built on Apache Superset, an open-source analytics project that many data teams already use, and every chart can show how it was calculated in plain words. How it works walks through it.
Work should be easy to hand over, so a canvas can be shared with your team, and whoever opens it sees the whole investigation, not a screenshot of where it ended.
Two more decisions came from the same place. People should be able to trust where their data goes, so managed AI is included on every plan, and you can bring your own provider key instead. And some teams cannot send data to someone else's cloud at all, so there is an on-premise edition that runs on your own servers, with a local model if you need one.
Until finally, the question got its answer on Monday
Go back to that Monday morning. The number looks wrong. This time the sales lead uploads last month's export and asks why renewals dipped.
A chart lands on the canvas. They select it and ask for the same thing by region, and the second chart sits beside the first. They open How it's calculated on the one that matters and read the steps. Then they share the canvas with the person who owns that region, who can see every step that led there.
Nobody waited until Thursday. And the second question, the one the first answer always raises, was asked the moment it came to mind.
And ever since
That is why we built DashboardGPT: for teams with questions and no time to build dashboards, and for analysts who want to explore something quickly and then show their working to people who were not in the room.
This is the first chapter of a longer account. We will write down the decisions we made, the reasoning behind them and the things we got wrong. Product pages tell you what a tool does. We think you should also be able to read why.
If you would rather see it than read about it, the playground runs the product on sample data with no account, and you can try it on a file of your own.