Quickstart

This walkthrough takes roughly five minutes. At the end of it you’ll have answered a real question with your own data and kept the answer as a Report that re-runs itself next week.

You don’t need to learn any UI. You don’t need to write SQL. You don’t need to build a dashboard first. Drop in a file, ask a question, keep the answer.

Before you begin

You’ll want three things within reach:

• An email address you can receive a verification code at.
• A spreadsheet — CSV or Excel — with at least a few hundred rows. A week of signups, a month of orders, a product catalog, a table of anything. If you don’t have one handy, you can skip to step 2 and grab our sample CSV.
• Five minutes.

The Free plan is the full agent, not a demo. You’ll have enough tokens to finish one real question with follow-ups — no credit card.

1. Sign up

Head to console.tablize.com. Paste in your email. Tablize sends you a one-time code, you paste it back, and you’re in. No password, no setup wizard, no 12-step onboarding.

First thing you’ll see is an empty workspace. One Chat panel in the middle, a Sidebar on the left that’s mostly empty on purpose — Reports, Apps, and other destinations appear once you actually make something worth keeping.

2. Drop in a spreadsheet

Click anywhere in the Chat area, or drag a CSV straight onto the page. Tablize accepts CSV, Excel (.xlsx), Parquet, SQLite, and JSON. It sniffs the schema on the way in, so you don’t pick column types by hand.

For this walkthrough we’ll use a sample CSV of a small SaaS’s weekly signups. Download signups-sample.csv if you want to follow along exactly, or use your own — the steps are identical.

The file lands as a table. You’ll see a quick confirmation in the Chat; no separate “import wizard” to click through.

3. Ask your first question

Type a question in plain English. Anything you’d ask a junior analyst works here — you don’t have to pre-digest it into SQL or metrics.

For the sample file, try:

What does last week’s signup data tell you?

Tablize writes the query, runs it, and narrates the answer. You’ll see each tool call appear as a grey row — you can click any of them to see the underlying SQL or Python. Trust, but verifiable.

A few things are worth noticing in this screen:

• The tool-call rows (sql.query, python.analyze) are the agent showing its work. Click to see the SQL; you can edit it and re-run if you disagree.
• The chart is live markup, not a bitmap. It stays crisp at any zoom and respects the theme you’re using.
• The Keep bar at the bottom is always there once the answer is worth keeping. Every answer has one.

4. Keep the answer

Hit ＋ Save as Report. No modal, no form, no category picker. The Report slides into the right half of the screen so you can see what you just saved without losing the chat.

The Report you just saved is already scheduled to re-run every Monday at 09:00. Next week it’ll show up in your inbox — or, if you want, on a public shareable link you can drop into your team’s Notion.

You can also pick ＋ Watch weekly instead: that creates a recurring check that stays quiet unless last week looks genuinely off.

5. Come back next week

Close the tab. The workspace is persistent (on the Plus plan and above) — data, Reports, Scripts, and Watches survive. Your next session starts with a Sidebar that now has a Reports entry with a ① badge, and the weekly Report already prepared.

The loop from here:

• Ask a new question about the same data.
• Keep it if it’s worth keeping.
• Watch if you want to be told when something changes.
• Build a Dashboard or a small App when you want to hand the answer to a teammate.

What you just built

In five minutes you went from “here’s a CSV” to “here’s a weekly Report that re-runs itself.” That’s the core Tablize loop, just scaled down. Every other part of the product — connecting databases, live integrations, IoT feeds, app generation, watches on sensors — plugs into the same three beats: Connect, Ask, Keep.

Next steps

• Core concepts — the 5-minute mental model for the whole product.
• The Keep loop — a tour of all five ways an answer can be kept.
• Connect databases — move from a CSV to a live Postgres or Supabase.
• Integrations — the 39 built-in connectors, from Stripe to GA4.