It’s About Business: Your Company Is Not Eleven Subscriptions
Posted: 2026 | Category: Business Platform
The Tuesday Where Nobody Knows Where the Customer Lives
A client calls. They want to know where their order is.
You open the CRM to find them. Their address is there, but slightly wrong, because the correct one is in the invoicing tool. The quote is a PDF on a shared drive, exported from a tool you stopped paying for. The order status is a column in a spreadsheet that one person maintains. The support thread about the delay sits in a helpdesk product that has no idea any of the other things exist.
Four tabs and six minutes later you say “let me check and call you back.”
Nobody chose this. It happened one subscription at a time. Each tool was reasonable alone. Together they are a company that cannot answer a question about itself.
Every tool was a reasonable decision on its own. Nobody ever decided on the whole.
What the Big Systems Get Right
There is a category of software that solves exactly this, and it is worth being honest about why it wins.
One coherent system. Customers, quotes, orders, invoices, tickets and projects sit in the same place, and they know about each other. No sync jobs. No “which one is right.”
One way of modelling things. Every business object is described the same way: it has fields, it has views, it has permissions, it has an audit trail. Learn it once and every screen in the company works the same.
New modules without a new codebase. When the business needs something it did not need last year, that thing appears inside the system you already run. It does not become a twelfth subscription with its own login.
Customisable per company without forking. Your business is not the reference implementation. You add a field, change a workflow, rename a status, and upgrades still arrive.
It stays yours. The data model is visible, the data is exportable, and the thing runs where you put it.
Those five properties are the actual product. Everything else is decoration.
It’s About Business has all five. And then it does the hard part differently.
The Difference: the Model Is Data, Not Code
In most systems of this kind, an entity is code. There is a customer table, a customer class, a customer form, a customer controller. Adding a new business object means a developer, a branch, a migration and a release. Configuration gets you a field. Anything structural gets you a project.
In It’s About Business there is no order table and no customer table. There is a small generic core that stores entity definitions, field definitions, view definitions, and records as JSONB. One generic API serves every entity. One generic renderer draws every screen. A list, a kanban board, a calendar and a detail form are all just view definitions read at runtime.
The consequence is the whole point: a new entity is configuration, not a development project.
You want to track machine maintenance, or subcontractor certificates, or sample requests, or whatever your business does that no vendor has heard of. That is a definition. It gets a list, a kanban, a detail form, validation, relations, an audit trail and an API the moment it exists. Nobody writes a page for it.
How It Works
Packs. A pack is plain data describing entities, fields, views, seed records, automations and menu items. The built-in ones cover CRM, support, quoting and an issue tracker. Installing one upserts the definitions and gets out of the way.
Packs compound. A base pack provides a capability, say a customer. Other packs require it and graft their own fields and views onto that same shared customer rather than inventing a second one. Every contribution is tagged with the pack it came from, so re-syncing one pack never wipes another’s work. Fields you added by hand are marked as yours and survive upgrades.
Field types that do real work. Text, number, date, enum, relation, sequence, plus computed fields with formulas and rollups that aggregate over child records. Order lines are inline detail-children on the order form. Relation integrity governs deletes, so nothing quietly orphans itself.
Views you actually use. Server-side lists with pagination, JSONB search, sorting and facets. Kanban boards you drag cards across. Calendars. Detail forms built from the entity’s own sections.
Automations and documents. Domain events trigger rules that fire actions, plus manual buttons for the things a human should decide. HTML templates render to PDF, so quotes and orders leave the building looking like your company rather than like a database.
AI where it earns its place. AI intake turns a natural-language description into records. PackStudio drafts an entire pack from a prompt, which you review and install. Schema is authored through packs and drafts, never by clicking around in a live definition editor, because that is how live systems get broken.
Multi-tenant throughout. Every query is workspace-filtered. User-facing records are archived and restored, never hard-deleted from the UI. Everything is logged.
The Inbox
There is a pack for the thing you do fifty times a day and never follow up on: capture.
A link, a screenshot, a half-formed thought. It lands in the inbox, and the server fetches the page, grabs a preview image, shows it to a vision model, and writes back a title, a summary, a suggested action and a classification onto a self-growing topic taxonomy. Then you decide what it becomes: an issue on any board, a reference, a read-later, or nothing. It is the fix for treating a messaging app’s saved messages as a scratchpad that nothing ever comes out of.
Most businesses have one process no vendor has ever heard of. That is the one worth modelling.
Who This Unsticks
Companies on eleven subscriptions. You are paying for eleven logins, eleven exports and zero coherent answers. One system, one model, one place the truth lives.
Businesses whose work does not fit a template. If your core process is unusual enough that every vendor demo ends in “we could build that for you,” you are the case this was designed for. Unusual is configuration here.
Teams who outgrew a spreadsheet. You want the flexibility of a sheet with relations, permissions, validation, an audit trail and an API.
Two Native Companions
A business platform that only exists in a browser tab is half a platform.
IAB Inbox is an iPhone app with a share extension. Two taps from the share sheet and a link, a note or a screenshot is on a board, enriched and classified, instead of lost in saved messages.
Get Started
Still opening four tabs to answer one question about a customer?
Visit iab.glue.blue and model the thing your business actually does.
It’s About Business is built by glue.blue - we stick solutions to problems. Permanently.
Ready to stop running your company across eleven tools? → Get Started → Contact Us
Posted in: Business Platform, ERP, CRM, Automation