Getting started with Supper

Your first real answer, in under a day.

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.

Day 1
Live
First real answers, on your live data, the day you connect a source.
Your effort
<1 hr
Usual investment from a team over the first month of a Supper integration.
Week 4
Self-serve
Whole team self-serving, recurring reports automated in the background.
The sequence

Six steps from a cold start to a self-serve team.

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.

01
You Day 1 · ~5 min / source

Connect your sources.

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.

Snowflake BigQuery Redshift Databricks Salesforce HubSpot Stripe Postgres dbt + many more
02
Supper AI Overnight · 0 effort from you

Supper builds your semantic model.

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.

03
Your FDA DAYS 2–4 · ASYNC REVIEW

Your FDA refines the model with your team.

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.

  • Metric definitions encoded to spec — ARR, churn, pipeline
  • Conflicting definitions resolved across sources
  • Cross-source relationships validated end to end
  • Permissions and field-level access applied
Supper Data Model — the left rail shows Business Logic (terms, metrics, constraints, quirks) and Skills, with a skill detail open showing description, status, trigger, and scope.

The Data Model Your business logic and reusable skills, encoded once and editable in place — the layer every answer is built on.

04
Supper AI Days 3–4 · no setup required

A starter content library is generated for you.

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 conversations — the questions most teams ask first
  • Auto-built dashboards — live views of your core metrics
  • Data summaries — plain-language overviews per source
  • Suggested questions — prompts tailored to your data
Supper chart builder — a conversational panel suggesting ways to visualize the data, next to a finished stacked bar chart of monthly revenue by customer segment with its data source noted.

Starter content Supper proposes visualizations and renders charts from live sources — ready to pin to a dashboard or drop into a recurring report.

05
Your FDA Day 5 · first users live

Your team asks its first real questions.

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.

  • Plain language — no SQL, no filters, no dashboards to rebuild
  • Live data — answered at ask time, not a stale export
  • Shows its work — the logic behind every answer, on tap
  • Conversational — follow up without re-explaining context
Supper agent chat — a plain-language question, a verified answer with reasoning, and a Context panel listing the business logic terms the answer applied, each marked active and editable.

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.

06
Your FDA Weeks 2–4 · ongoing

Your team grows into the platform.

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.

  • Recurring reports automated on a schedule
  • Live dashboards for your most-requested analyses
  • Broader rollout — FDA trains your power users
  • Usage report — questions answered, time saved, next steps
Who does what

Integrate in days, not weeks. Supper builds, you consume.

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.

Workstream
Week 1
Days 1–7
Week 2
Days 8–14
Week 3
Days 15–21
Week 4
Days 22–30
Supper & your FDA 8 workstreams · 0 effort from you
Connect & validate sources
AI builds semantic model
Encode your business logic
Generate starter content
Onboard & train your team
Build workflows & dashboards
Tune the model on real usage
Usage report & roadmap
Your team 3 quick steps · ~3 hrs total
Authorize source connections
Review & approve the model
Nominate your first users

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.

Before we start

What we need from you to kick off.

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.

01
Technical & business stakeholder

A point of contact on each side — someone who knows the data, and someone who owns the outcomes we're driving toward.

02
Existing reports or dashboards

The reports your team relies on today, so we can recreate them and automate the ones you rebuild by hand.

03
Data sources

The warehouses, databases, and SaaS tools you want connected — and who can authorize access to each.

04
Use cases & departments

Which teams will use Supper first, and the questions they most need answered. This shapes your starter content.

05
Business logic documentation — if you have it

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.

Start today. Ask your first question tomorrow.

Connect one source and your FDA is in touch within one business day. The order of operations does the rest.