The onboarding funnel is a super-admin screen. Of the workspaces created in a window you choose, it shows how many reached each of the four milestones that define onboarded - opening balances reconciled, a first invoice, a first bank reconciliation, and past data imported if there was any - and how many are onboarded overall. The same table is drawn for everyone, then split by vertical, then split by where the workspace came from.
It changes nothing. To see which individual workspaces are behind a number, open the onboarding tracker.
How a percentage is worked out
Conversion is the workspaces that reached a step divided by those that reached it plus those that have not. The line under each percentage gives the counts, so a 100% that is one workspace out of one reads as exactly that.
- It is counted from what the books show today, not from past events. A customer who reversed a reconciliation stops counting as converted for that step, which is what an operator wants to know.
- A workspace with nothing to import is left out of the past-data step rather than counted as failing it, and the cell says how many were left out.
- A step nobody could read is shown as could not be read in its own line. It is never counted as a failure to convert and never as a success.
- A cell with no one to measure says so and shows no percentage. A blank percentage and 0% are different statements, and only the second means nobody converted.
The window and its limit
The funnel covers the newest workspaces created in the window, up to a fixed number. When a window holds more than that, the screen says it is showing the newest and that older ones are not counted, rather than presenting a partial cohort as the whole.
Vertical and source
The vertical comes from the owner's stated industry. Workspaces with none, or with one that does not match a vertical, are their own group called trade not stated, not folded into another.
The source is thinner than it looks. Most self-serve signups read app, because campaign and referrer detail is captured before anyone signs in and is not yet joined to the workspace. Workspaces credited to a partner read partner. A workspace whose source was recorded as nothing is source not recorded, and one whose source could not be read is source could not be read - two different groups on purpose.
When something could not be read
If the list of workspaces itself cannot be read, the screen says so and shows no numbers. If a table behind the vertical or the source split cannot be read, that split is marked as unreliable instead of quietly drawing a table of unknowns.
The imports inbox has shipped but its database change has not been applied yet. While that is true the screen says the imports table is not in this database, so you do not assume import jobs are included in these numbers. The past-data step reads earlier migration runs instead.