Fit assessment
Check the fit before you invest more time.
Answer five questions about company count, user count, workflow priority, dependencies, and excluded requirements. The result explains a boundary; it is not a score, purchasing recommendation, or promise of availability.
Check your current fit
Catalog basis. This guide uses Core: 5 users / 1 company and Pro: 25 users / 3 companies, not the upcoming package allowances or trial entitlements.
Five questions, answered only in this browser. Nothing is sent or saved. This is a scope guide, not a purchase recommendation.
More than 3 companies, more than 25 users, or any excluded requirement: not a current fit. Within those limits, an unlisted workflow or a specific bank connection, migration, integration or support need must be checked. Otherwise, consider Core for 1 company and up to 5 users, or Pro for up to 3 companies and 25 users. Confirm the workflow and package scope before deciding.
Review upcoming Core and Pro packages — a separate allowance basisWhat the assessment considers
- How many companies need the workflow today?
- How many people need access?
- Which workflow matters most: customer records, invoices and PDFs, pro formas, receivables, or company-scoped accounting?
- Do you need a specific bank connection, QuickBooks Online migration, third-party app or support arrangement before you can proceed?
- Is payroll, tax filing, consolidation, intercompany automation, enterprise ERP scope, or a certified compliance program essential?
Transparent rules, in priority order
Catalog basis. These guide limits are separate from the upcoming package allowances and are not trial entitlements.
A not-current-fit condition takes precedence over a validation condition. A validation condition takes precedence over a candidate result. A smaller footprint does not offset a missing essential capability. Company and user counts must be positive whole numbers.
Scroll horizontally to see all columns on smaller screens. Keyboard: focus the table and use the arrow keys.
| Condition | Result | Why |
|---|---|---|
| An excluded requirement is essential, or the requirement exceeds 3 companies or 25 users. | Not a current fit | The current workflow scope or included package limits do not cover the requirement. |
| Scale is within the limits, but a migration, bank-feed, integration, support, or unlisted-workflow requirement is unresolved. | Validate before moving forward | A missing dependency is not made available by a candidate package result. |
| A supported workflow is the priority, no excluded requirement is essential, and there is no unresolved day-one dependency. | Candidate for further evaluation | Core is a candidate within 1 company and 5 users; Pro is a candidate within 3 companies and 25 users when Core limits are exceeded. |
Use the same guide without JavaScript
Catalog basis. These guide limits are separate from the upcoming package allowances and are not trial entitlements.
These written rules remain usable if the interactive controls are unavailable. There is no hidden weighting, numerical score, or need to submit your answers.
- Write down your company count and user count. If either exceeds the published Pro limit, the current catalog does not fit.
- Check the excluded requirements. If any is essential, stop at not a current fit.
- Check day-one dependencies and any workflow not described in the feature pages. If one remains unresolved, validate before moving forward.
- If none of those conditions applies, use Core’s limits of 1 company and 5 users or Pro’s limits of 3 companies and 25 users as the starting point for further evaluation.
What a result cannot establish
Answers are processed in your browser, are not sent to a server, and are not saved by this assessment. Reset clears the current answers and result.
The assessment does not evaluate value for money, implementation effort, accounting or tax treatment, security compliance, future roadmap delivery, or whether a limited-availability workflow can be enabled for you. Check the particular workflow and any hard support requirement separately.