Onboarding walks through four things in order, and the order matters — each step needs the one before it.
Connect and analyze
Connect your bank first, then anything else you use. Nothing else in the platform can say anything specific about your business until there is data behind it.
The bank is the single most valuable connection, because it is the only source that records what actually happened rather than what was supposed to. See connecting your bank.
Patterns
With data connected, the recurring shapes in it are identified: what repeats, what your normal looks like, where the money reliably goes.
This step is doing something you cannot do by hand — a year of transactions holds patterns nobody notices while living through them month to month.
Training the assistant
The assistant is told about your business: what you do, how you are structured, what matters to you.
Worth spending real time on rather than clicking through. Everything the assistant says afterwards is shaped by this, and the difference between "we do HVAC" and a proper description of your trade, your customers and your seasonality is the difference between generic answers and useful ones.
Locking a baseline
The last step records where the business stood at the start.
This is the step whose value arrives later. In six months you will want to know whether things improved, and that question needs a starting point that was captured before you began changing anything. It cannot be reconstructed afterwards, because the data will have moved on — see health reports.
Also worth doing early
Two things that are not part of the wizard and pay back immediately: set up invoicing so payment and reminders are handled, and fill in your business identity, particularly the time zone, before reading any report closely.
Then the first week.
Your first health report
At the end of onboarding a health report is produced from what has been connected. It is the baseline everything later is measured against — see health reports and the health score.
If it says it is not ready, it is still being generated. That is expected on a workspace connected moments earlier: the first report waits for the initial history to arrive from each connection, which takes longer than a routine update — see data freshness.
Coming back shortly, or asking for it again, is the whole of the remedy. It is not an error and nothing has been lost.
A thin first report means the connections have not delivered much yet rather than that the business is doing badly. It fills out as history arrives, and the figures that matter become readable within days rather than immediately.