Quickstart

Wavetable is designed so that one founder, with zero training, gets real value in the first ten minutes. This page walks that exact path.

1. Create a workspace

Sign up with an email and password, then name your workspace. Each workspace is a fully isolated tenant: its own database, its own event log, its own semantic index. Nothing is shared with any other customer.

2. Connect your first sources

Open Settings and connect:

Gmail. Email is the richest record of your business relationships. Wavetable ingests messages as events and proposes claims about the people and companies behind them.
Stripe. Revenue truth. Customers, invoices, and subscriptions arrive with deterministic identity keys, so payment history lines up with the right people.
The site script. A small first-party JavaScript snippet (about 2KB). Paste it into your site and pageviews, form submits, and campaign parameters land in the same graph as your email and revenue.

You can also import a CSV to bring data over from an existing tool.

3. Watch the graph assemble

As events arrive, Wavetable proposes claims (facts with provenance), adjudicates them, and builds projections: people, companies, revenue, pageviews, deduplicated and cross-linked. Open any record and you will see a written narrative in which every sentence carries a citation back to the claims and events that support it.

4. Ask a question

Press the command bar and ask in plain language:

Which pages did my best customers visit before they first paid?

The answer renders as a view with a receipt: the exact read-only query that produced it, the row count, and the plan hash. If the answer is useful, click Promote to pinned and it becomes a shared, versioned view on your Canvas.

5. Approve your first automation

Describe recurring work the same way:

Every trial that goes quiet for 5 days, send a personal check-in unless they have an open ticket.

The Compiler turns this into a workflow artifact and runs it against your own history in shadow mode first. You see a replay report before anything goes live: how many times it would have fired last quarter, with the actual drafts it would have sent. Approve it from the Inbox and it runs deterministically from then on. Sends stay gated until you say otherwise.

6. Point an agent at your business

Every workspace exposes a policy-scoped MCP endpoint. Add it to Claude or any MCP-capable agent and ask questions about your business from wherever you work. Every call is logged and scoped by policies you approved.

That is the whole loop: connect, watch it assemble, ask, approve, delegate. The concepts page explains what is happening underneath.