Most business software has a hidden primary user, and it isn't the person running the business. It's the admin — the IT person, the consultant, the operations specialist whose job is to configure the tool. Enterprise software is designed to be configured, because in a large company someone is paid to configure it. We made a different choice, and it shapes everything: we build for the owner, the person who has to actually run a business with the thing, and who does not have an admin.
Why the difference matters so much.
Software built for the admin optimizes for configurability — endless settings, custom fields, permission matrices, workflow builders. That's the right call when a specialist will spend weeks tailoring it before anyone else touches it. But for a 12-person business with no specialist, every configuration option is a question the owner has to answer, a decision they're not equipped to make, a reason the tool sits half-set-up forever. Flexibility designed for an admin becomes a burden for an owner.
A setting is a gift to someone whose job is configuration and a tax on someone whose job is running the business.
The owner's actual constraints.
The owner of a small business has no time, no specialist, and no patience for a setup project — and they're right not to, because their job is the business, not the software. They need the tool to be useful with its defaults, to make good decisions on their behalf, and to never require a consultant. Every time software demands configuration it doesn't strictly need, it's quietly assuming an admin who isn't there.
What building for the owner means.
It means sensible defaults that work out of the box, so the tool is useful before any setup. It means hiding complexity until it's needed, rather than presenting all of it up front as proof of power. It means every feature has to justify its existence to a busy non-specialist, not to a checklist. And it means saying no to the kind of infinite configurability that impresses in a sales demo and paralyzes in real life. The owner doesn't want a platform to build on. They want a business to run.
We design for the person in charge, not the person they'd have to hire to set up someone else's software. It's a less flattering design target — owners don't care about your configuration depth — but it's the honest one for teams of 5 to 50. Build for the owner, and the admin turns out to be a role nobody needs.