One Subscription, Every Capability

A guesthouse owner signs up for a booking tool. It is good. Three months later she hires someone to handle weekend inquiries, and the tool asks for another monthly fee before that person can log in.

So she does what every small business does. She writes the password on a sticky note and hands it over.

Nothing about that is unusual, and nothing about it is her fault. The pricing told her that adding a colleague was a cost, and she believed it. What it did not tell her is what she gave up: there is now no record of who answered which customer, no way to remove access when the weekend help moves on, and as far as the software knows, she still works alone. The software has become slightly worse at exactly the moment it should have become more useful.

We built Backoffice for businesses like hers, and the first decision we made about pricing was that it would not do this.

Per Seat Pricing Charges For The Thing You Wanted

Per seat pricing sounds fair. More people, more value, more money. For a large company with a procurement department it more or less is.

A small business is not a smaller version of that. It is an owner and one or two other people, and the whole point of the tool is that all of them can see the same inquiry, the same booking, the same customer. The second seat is not extra value. It is the reason the product is worth having at all. Charge for it and the owner has to weigh whether her part-time help is worth a monthly fee for the privilege of not sharing a login.

Most decide the answer is no, and the sticky note wins. The vendor's dashboard records one happy user. The business has two people using an account built for one.

Per Module Pricing Puts Help Behind The Next Tier

The other common model sells by capability. Customer management in the base plan, bookings in the next one up, the assistant that answers your website visitors in the one above that.

It looks reasonable on a comparison table, and it feels very different from inside the product. A business on the base plan spends its day looking at things it has not bought. Every screen has a locked section. Every problem the tool could solve is one upgrade away. What the customer sees is not a product but a catalogue of what they have declined, and the capability that would have helped most is, reliably, the one behind the next tier. That is not a coincidence. It is how the tiers get designed.

There is a subtler cost. When a capability is a paid add-on, the vendor has to build it as one. The booking feature cannot lean on the customer records, because a customer might have one without the other. The assistant cannot draft a reply to an inquiry, because that would be one add-on doing the work of another. The product becomes a set of boxes that happen to share a login, and the seams show.

What We Do Instead

A business on Backoffice pays once, and that subscription unlocks everything. Customer records, inquiries, bookings, calendars, the website assistant, all of it. There is no charge for adding a manager and no tier where a capability lives.

That leaves an obvious question, which is how anyone stays in business when one feature costs nothing to serve and another draws on paid AI every time it runs. Answering an inquiry costs us nothing. Training an assistant on a website does. Charging the same flat price for both means either overcharging the business that never touches AI or losing money on the one that leans on it.

So the plans differ in one thing only: how much AI work they include. It is an allowance inside a capability every plan already has, not a paywall in front of it. Every business can switch the assistant on. What the plan decides is how much of the month's answering it covers.

Paid For Is Not The Same As Switched On

Charging once forced a distinction we now think every product should make, whether or not it prices this way.

A plan decides what a business has paid for. The owner decides what is switched on. Those are two separate settings, and neither one reads the other.

That sounds like bookkeeping, and it changes what the product means. A restaurant that does not want a chatbot on its website turns it off, and that is a decision about the restaurant, not a statement about its bill. Nothing downgrades. Nothing gets locked. The owner can turn it back on in a month when the season picks up, and it is exactly where she left it. Switching a capability off is the customer's choice about how to run their business, and the software has no business turning it into a sales conversation.

In an add-on model those two settings collapse into one. Off means unpaid, and unpaid means locked, and the product has to keep asking whether you have bought the thing before it does anything. Every new feature inherits that question.

It Changes What Gets Built, Too

This is the part we did not fully expect. Pricing everything together changed the shape of the product on the inside.

When a new capability arrives, it arrives as a section of the same product, available to everyone, rather than as another subscription with its own gate. Nobody has to decide which tier it belongs in, so nobody is tempted to hold back the useful part for the expensive one. And because every capability is present in every account, capabilities can lean on each other freely. The assistant that answers website visitors also drafts replies to inquiries in the inbox, because it can assume both are there. A booking attaches to the same customer the inquiry came from. The product is built as one thing because it is sold as one thing.

There is a discipline in it as well. A capability that costs nothing to include has to earn its place by being used, not by being bought. If nobody switches it on, that is the feedback, and it is far more honest feedback than a conversion rate on an upgrade button.

What To Ask Before You Buy

Three questions tell you quickly whether a tool's pricing is on your side.

• What does it cost to add one more person? If every login has a price, your team will end up sharing one account, and you lose the record of who did what along with the ability to remove someone's access when they leave.
• Which of the features on the pricing page are included in my plan? The ones that are not will still be on your screen every day, locked. Make sure the plan you are buying covers what you actually need, not what you might upgrade to.
• If I switch a feature on, does my bill change? Turning something on should be a decision about how you run your business, not a new line on the invoice. If every capability you enable adds a charge, you will end up using the few you have paid for and working around the rest.

Pricing is the first thing a product tells you about who it was designed for. One that charges you for hiring, and charges you again for the feature you needed, was designed for somebody else.

If you run a small business and want to see what one subscription covers, the Backoffice pricing page has the numbers, and the portfolio entry has the product. If you are building software of your own and weighing how to price it, talk to us. We have been on both sides of the decision.