Fit assessment
Check the fit before you invest more time.
Compare your requirements with the upcoming package structure. This scope guide does not confirm current trial availability, purchase eligibility or a delivery date.
Explore this page ↘Check your fit with the upcoming packages
Five questions, answered only in this browser. Nothing is sent or saved. This is a scope guide, not a purchase recommendation.
An excluded requirement means not a current fit. More than one company, more than ten users, an unlisted workflow or an essential bank-feed, migration, integration or support dependency needs validation. Otherwise, evaluate upcoming Core for one company and up to 3 users, or Pro for one company and up to 10 users or pro-forma work. New package allowances are not confirmation of current availability.
Review Core and ProWhat 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?
- Is a live bank feed, QuickBooks Online migration, named third-party integration, or defined support arrangement essential 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
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.
| Condition | Result | Why |
|---|---|---|
| An excluded capability is essential. | Not a current fit | A planned package does not establish payroll, filing, consolidation or other excluded capabilities. |
| More than one company, more than ten users, or an unresolved migration, bank-feed, integration, support or unlisted-workflow dependency. | Validate before moving forward | Additional-company pricing is planned, but user allocation and specific availability require confirmation. |
| One company, up to ten users, a described workflow and no unresolved day-one dependency. | Candidate for an upcoming package | Core is a starting point for up to 3 users; Pro for up to 10 users or a pro-forma requirement. Confirm availability before committing. |
Use the same guide without JavaScript
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 company and user counts. More than one company or more than ten users requires validation, not an assumed shared seat pool.
- If an excluded requirement is essential, stop at not a current fit.
- If a day-one dependency or unlisted workflow is unresolved, validate before moving forward.
- Otherwise, evaluate upcoming Core for one company and up to 3 users, or Pro for one company and up to 10 users or pro-forma work. This is not confirmation of current availability.
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.