Why BWI

The tax nobody puts on the budget

Every services business pays a coordination tax. It does not appear as a line item, which is part of what makes it expensive.

It is the half-hour the new hire spends learning that the CRM calls a contract a “deal,” the document studio calls it a “matter,” and the billing exporter calls it a “project.” It is the senior person who keeps a private spreadsheet because none of the systems can answer the question they actually need. It is the proposal that stalled because the sales tool emailed a PDF to the e-sign tool that emailed a PDF back to the CRM, and somewhere in that chain a number changed and nobody can tell you where. It is the compliance finding that came back because three systems carried three versions of one policy.

Put numbers on it. For a typical mid-market services business running on nine SaaS tools: about three calendar weeks per quarter of senior time spent reconciling, roughly one full-time equivalent on integration plumbing, a procurement review every renewal cycle that runs six weeks because no two vendors agree on what their audit log captures, and a recurring executive conversation about a custom build everyone knows will never actually happen. None of it shows up in the budget under “coordination.” All of it is coordination.

The compliance lead pays a different version of the same tax. Intelligence tools get adopted across departments, on software the security team never approved, against models nobody can name on demand. Output ships with no provenance. When a regulator asks how a recommendation was reached, the answer involves screenshots and a sentence that starts with “we believe.” That is not a defensible posture. It is the absence of one.

Why the usual answers keep the tax in place

There are three standard answers to all of this. Each one leaves the tax exactly where it is.

Stitch the tools together. Buy ten best-of-breed products and an eleventh to connect them: a general-purpose iPaaS, a niche workflow tool, or an in-house service one engineer wrote and the rest of the team is now afraid to touch. It holds for a while. Then the integration layer becomes its own product to maintain. Webhooks fail quietly, field mappings drift, and the connector grows its own audit log, which is one more log to reconcile. The people who keep it running become a small department.

Build it custom. Expensive, slow, and ageing the day it ships. The development partner moves on, the internal team rotates, and two years later the build is a dependency nobody wants to open.

Bolt on a chat panel. The newest answer, sold as if it dissolved the problem. A box that drafts text and answers questions on demand. It is good for interactive exploration and short, throwaway tasks, and it is the wrong shape for operational work, which has state, stages, structured output, and a downstream audit a transcript was never built to hold. The Field Note “The Chatbot Is the Wrong Answer” makes that case in full.

All three share one wrong assumption: that the tools are right in principle and the only problem is connecting them. They are not. Audit trails, brand kits, relationship graphs, and the intelligence layer are not features of any single tool. They are platform concerns.

[VISUAL: Callout. Centered, large weight, dark teal #00405F on white.]

**The system thinks. Humans decide.**

What we built

BWI® starts from a different premise: output should be designed, not improvised. Every operation runs through a structured multi-pass pipeline, each pass with an input schema, an output schema, a writeable intermediate state, and its own row in the audit log. Some passes generate, some verify, some score. Each has its own tunable prompt and its own assigned provider, chosen for the task. The verification passes are the platform refusing to ship a claim it cannot defend.

The platform is provider-agnostic. It routes the right capability to the right model for the work, and rotates when a provider degrades or a better one ships, with no customer involvement and no code release. The capability is the contract; the brand behind it is replaceable.

Intelligence, not AI. The full account of how the pipeline works lives on /platform.

The platform that shows its work

Most SaaS makes three quiet bets that turn out to be costly: that governance can be bolted on later, that customers will accept multi-tenancy as the default, and that data is something the platform owns and the customer rents. BWI was built the other way on all three.

Built to the standard. Architected to ISO 42001 from day one. Full prompt control, full audit, encryption at rest. Formal SOC 2 Type 2 and ISO 42001 certification are targeted ahead of general availability.

[VISUAL: Callout. Centered, large weight, dark teal #00405F on white.]

**Security is not a retrofit. It is woven into the fabric.**

Dedicated by design. Every customer instance is its own deployment, its own database, its own encryption keys. Per-customer or per-entity isolation is enforced in the shared kernel. A business can run twenty of its own entities in one BWI instance and the data physically cannot leak between them. Isolation is the floor, not the upgrade.

Owned by you. Your data is yours. Exportable any time, in usable formats, with nothing to negotiate. If you ever leave, we hand back what is yours. A commitment, not a feature.

[VISUAL: Brand promise callout. Centered, large weight, orange #E26A0E on white. Period included.]

**Making Business Better.**

Who we are

BWI® is an extension of INT, which has been building intelligence layers for new technologies since the 1990s. We have been around long enough to have watched what happens when tools ship without governance. The coordination tax is not a thesis we read about. We paid it ourselves, then built the answer we wanted to be using.

[Request Early Access]

BWI is in limited release. We are onboarding a small cohort of operators ahead of general availability.

[See how the pipeline works → /platform]