Running a practice: many companies, one Tiybe account

Software written for a business and software written for a practice are solving different problems. A business has one set of books and wants them to be excellent. A practice has thirty, and wants them to be consistent, current and — above all — impossible to lose track of.

Tiybe is built to be used both ways. This is the second way.

Companies live on one subscription

A "company" in Tiybe is one complete set of books: its own chart of accounts, its own ledgers, its own returns. A practice adds each client as a company on the same subscription, rather than maintaining a separate login, a separate bill and a separate mental model per client.

Each plan includes a number of companies, and that number is one of the main things separating the plans. It is also, for most practices, the axis they actually upgrade along — a firm crosses a company count long before it runs out of features. The pricing page carries the current inclusions per plan.

Because billing is per company, growth is proportionate: taking on a client adds one company's cost, not a step change.

People, and what they can reach

Users are included per company rather than charged per seat, so putting the right colleague on a file is not a purchasing decision.

What matters more at practice scale is the second half of that: granular role permissions control what each person can do, not merely which companies they can open. That is the difference between a junior who can enter transactions and a partner who can approve and file, expressed once as a role rather than re-decided per client.

The audit trail

Every practice eventually has to answer a question of the form "who changed this, and when". The audit trail and activity log exists for that, and it is worth thinking of as a practice feature rather than a security feature.

The value is not primarily catching wrongdoing. It is being able to reconstruct what happened on a file six months later, when the person who did the work is on another engagement and the client is asking why a figure moved.

Consistency across files

The advantage a practice has over its individual clients is that it can standardise. Tiybe leans on that in a few places worth knowing about:

1. A pre-configured chart of accounts, so a new client starts from a known structure instead of whatever they had before.
2. A custom chart of accounts where a client genuinely does not fit the standard one, so the exception is deliberate rather than accidental.
3. A compliance calendar per company, so the question "what is outstanding" has an answer that does not depend on anyone's memory.
4. Customer and vendor ledgers in the same structure everywhere, so a partner reviewing an unfamiliar file already knows where to look.

Consistency is what makes a practice's work reviewable. A file that is laid out like the other twenty-nine can be checked in minutes.

Questions worth asking before you choose a plan

If you are evaluating Tiybe for a practice rather than a business, these are the questions that usually determine the answer.

• How many companies do you carry today, and how many will you carry in a year? This sets the plan more often than any feature does.
• How many people need to be inside a given client's books at once?
• Do you need role permissions that differ by seniority, or is everyone in your team trusted with everything?
• Which clients need the annual compliance set, and which only the monthly returns?
• Does any client need something outside the core plans — multi-currency, inventory, payroll — and is that add-on available today or still coming?

The pricing page answers the inclusion questions with live figures. The rest are worth a conversation: tell us how your practice is shaped and we will tell you honestly which plan fits, including when the answer is the cheaper one.