Price Balansix against the practice workflow it connects, not against one isolated bookkeeping licence.
Balansix is designed to consolidate functions that practices commonly buy, integrate and administer separately. The pricing model follows the active client base so the commercial model grows with the practice rather than charging a separate licence for every module.
per active client, per month
25-client minimum.
For larger practices or firms with more complex implementation, migration, support or commercial requirements.
Compare it with the workflow Balansix is replacing: client administration, engagement, records intake, bookkeeping, year-end schedules, final accounts, client reporting, staff time and the integrations needed to keep those products talking to each other.
Client-led pricing makes the commercial conversation easier to understand: as the practice adds active clients to Balansix, the subscription grows with the work being managed through the platform.
The 25-client minimum gives a defined entry point while allowing smaller practices to adopt the full connected platform.
Add active clients as the firm grows rather than jumping between artificial feature tiers.
The value proposition is the connected platform, not a deliberately incomplete base tier that requires a chain of paid add-ons.
An active client is a client record being managed through the Balansix service during the subscription period. Your commercial proposal should define the treatment of archived or disengaged clients.
The core proposition is a connected platform rather than separate subscriptions for each workflow. Any practice-specific implementation or enterprise services are agreed separately where applicable.
Yes. A phased migration is often the most controlled route. Practices can begin with an agreed cohort, validate the workflow and then move further client groups in stages.
The client-led model is intended to avoid multiplying the commercial model simply because several authorised staff work on the same client. User access still remains individual for security and audit purposes.
Migration scope depends on the systems, data and history you want to bring across. The migration plan distinguishes essential opening data from information that is better retained in its existing archive.
Bring a real client workflow to the demonstration and compare how many handoffs, re-keying points and separate systems Balansix can remove.