Getting started with Supper
Connect your data, ask a question, get a verified answer. No engineering sprint, no SQL, no data team required — let Supper analyze, normalize, and map your data sources.
Onboarding runs in a fixed order. Each step has an owner — and on all but a few, the owner is us. Here is exactly what happens, in sequence, and what we'll need from you at each one.
Every source connects through a guided self-serve flow — no engineering, no pipeline configuration, no data to move. OAuth, an API token, or credentials, depending on the source. Most connections complete in under five minutes, and every connector is built and maintained by Supper's own team.
The moment a source is connected, Supper's AI scans your entire schema, maps every table and field, infers join paths across sources, translates internal field names into plain language, and generates a first-pass semantic model — automatically. By the time you check in the next morning, the foundation is already built.
This is the difference from tools that need weeks of modeling before your first question. The AI does the heavy lifting upfront, so you can start immediately.
Your Forward Deployed Analyst — a full-time Supper employee with a senior data background — reviews the generated model with your team, encoding your specific business logic and resolving anything that doesn't match how your company actually works. Your team reviews and approves in short async sessions.
The Data Model Your business logic and reusable skills, encoded once and editable in place — the layer every answer is built on.
While the model is being refined, Supper proactively generates starter content from your connected data — so your team are consumers from day one, not builders. No blank canvas, no "where do I start?"
Starter content Supper proposes visualizations and renders charts from live sources — ready to pin to a dashboard or drop into a recurring report.
Your FDA runs a short onboarding with your first group of users. Most get a useful answer within their first ten minutes — in plain language, from live data, with every answer showing the logic it used. Follow-ups work naturally; the agent holds conversation context.
The agent A question, a verified answer, and the Context panel showing exactly which logic and skills produced it — the audit trail built into every response.
Your FDA monitors usage, tunes the model against real question patterns, and automates the recurring work — the Monday report that took three hours becomes something that just shows up in Slack. More users come onboard, gaps get shipped same-day, and you end the month with a usage report and a clear picture of what to build next.
Supper and your FDA carry eight workstreams end to end. Your team has three short tasks — and they're done by the middle of week one.
Across the entire first month, your team spends roughly three hours — authorising connections, approving the model, and naming first users. Supper and your FDA do everything else.
You're not staffing an implementation project. You're pointing us at your data and getting out of the way.
A short list gets your implementation moving. Most teams pull these together in a single kickoff call — and you don't need all of them on day one.
A point of contact on each side — someone who knows the data, and someone who owns the outcomes we're driving toward.
The reports your team relies on today, so we can recreate them and automate the ones you rebuild by hand.
The warehouses, databases, and SaaS tools you want connected — and who can authorize access to each.
Which teams will use Supper first, and the questions they most need answered. This shapes your starter content.
Any existing metric definitions, data dictionaries, or dbt models. Optional — if you don't have them, your FDA writes them with you.
Don't have all of these yet? That's fine. Bring what you have to the kickoff call and your FDA will help you assemble the rest — gathering this is part of what we do, not a prerequisite you have to finish first.
Connect one source and your FDA is in touch within one business day. The order of operations does the rest.