One platform. Every back office.

Why we're doing this

Every growing business runs on a stack of SaaS that mostly doesn't talk to each other: a CRM, a helpdesk, a project tool, a forms tool, a low-code "automation" thing tied to all of them with brittle Zaps. Each one is fine on its own. Together, they're a tax — on ops time, on the budget, on data quality.

BackOffice is an answer: model the entities your business actually has — Customers, Deals, Tickets, Projects, SKUs, whatever — once, in one workspace, on one data model. Everything else (forms, automations, dashboards, exports) operates on those records. Your team stops translating between tools and starts working on the actual problem.

What we believe

• You own your data. Self-host or ours, your records are yours. No vendor lock-in via "exclusive workflows".
• The model is the product. Every business has a unique shape. Software that forces you into someone else's shape costs you your competitive edge.
• Built for builders. Ops people building the tools their teams use are the centre of gravity, not engineers.
• Plain text + JSON. Templates export as files. The schema is inspectable. AI can reason about it because there's nothing magic underneath.

Where we are

Small team. Bootstrapped. Shipping weekly. Real customers running real operations on BackOffice today — sales pipelines, support queues, project trackers, inventory ledgers. See the changelog for what landed this week and the customers page for who's using it.

Get in touch

Questions, partnership ideas, "you should hire me" emails — all welcome. Hit us up at our contact page.