Enterprise AI built on proprietary technology that is already running
No project starts from zero, and no platform is handed over for the client's team to assemble. The patterns already exist: they are deployed and integrated on top of the systems the organization already has, without replacing the core, the ERP or the system of record.
Proprietary technology that grows with every deployment
Every component that is deployed becomes part of the proprietary technology. The next project does not build it again: it configures it. That is why the predictive maintenance pattern moved from vehicle fleets to industrial equipment without being rewritten, and why the scoring engine runs today over six domains that bear no resemblance to one another — what changes per client is the table of weights, not the engine.
That is what separates this from custom development and from a software license: there is no project that starts on a blank page, and there is no product the client's team has to integrate on its own. The integration is ours.
Auditable by construction, not bolted on afterwards
The team was formed in banking and in regulated sectors. That is not a credential on a slide: it is what decides how things get built. In a bank, a figure that cannot be explained is of no use, however correct it may be.
The model translates; the engine decides.
A deterministic inference engine resolves over explicit, versioned rules. The model contributes language, not content: it does not originate figures.
Behind every assertion there is a derivation trace.
What data went in, what rule was applied, who approved it and since when it has been in force.
The logic does not live in a prompt.
It lives in dated rules and in procedures in the database itself, where it can be read, versioned and argued over years later.
Regulated data does not have to leave the network.
Inference runs on servers the client designates when their data policy requires it.
What the architecture guarantees
Seven decisions taken before the first line was written. They are not limitations still pending removal: they are the stance the work is built with, and they are not negotiated case by case.
They do not replace the core or the systems of record.
They integrate by reading or by interface. None of these components is the source of a piece of data: the source remains the system that already administers it.
The model does not originate figures.
Every amount, balance, date and status comes from the system of record. The component carries them and explains them; it does not calculate or reformulate them. Where a model proposes an adjustment to a figure, the adjustment is recorded as such, separate from the base figure, with its origin and with a confidence penalty, and it does not take effect without a person accepting it.
No automatic execution gate is delivered open.
That capability is enabled by class of operation and by threshold, with written authorization, and only after a period in recommendation mode. The sequence is not negotiable: first it is measured against human judgment, then it is automated.
They do not make a decision with regulatory consequence without a trace.
If it cannot be shown what data went in, what rule was applied and who reviewed it, the decision is not issued. The component asks again, escalates to a human, or admits that it does not know.
No biometrics.
Video analytics is anonymous and aggregated: no facial recognition, no identification of people and no emotion analysis. It is a design stance, not a technical limitation to be lifted on request.
They do not force regulated data to be sent to an external API.
Where the client's policy requires it, inference runs on servers they designate, with open-weight models. What does set a condition is the available compute capacity, which is sized beforehand.
They do not stand in for the person responsible.
The signature, the approval and the final decision stay where they are today. These components prepare, order and explain; judgment and responsibility are not transferred.
Five layers on top of the systems already running
Each layer consumes what the previous one produces. None touches the source system beyond reading it.
Client systems and channels — none of them replaced
ERP · core · CRM · document repository · video surveillance · portal · WhatsApp
Connectors: API · scheduled exports (SFTP / email) · RPA · MCP
Understanding
Document ingestion and classification · Cited retrieval · Multi-signal deduplication · Computer vision
Analysis
Financial consolidation · Treasury · Forecasting · Anomalies · Inventory planning · Predictive maintenance
Decision
Deterministic inference engine · Versioned rules · Derivation trace · Scoring engine · Agent orchestration · Evaluation and audit
Delivery
Conversational channels · Field app · Dispatch · Notifications · Self-service portal · Real-time dashboards
Infrastructure
Sensitivity-based inference routing · Multi-tenant isolation · Concurrent work queue · Observability and proactive alerts
Twenty-seven components in six families
The order is not one of importance but of dependency: the first families produce the data the later ones consume.
Documents and knowledge
The pieces that turn paper, files and email into something you can query. It is where a first project usually starts, because the volume is high and the error is cheap to detect.
Data, finance and integration
The least showy part, and the one that most conditions the rest. The bottleneck in these projects is almost never the model: it is getting the data out of the source system with enough permission, quality and frequency.
Models on the client's data
The five components that learn from the history or from the client's own signal. The pattern is the same in every case; what changes is the calibration against the organization's data, which is done before putting them into operation.
Decision and orchestration
What separates a demonstration from a system that passes an audit. These five components do not produce content: they fix who decides, by what rule, and how it is proven afterwards that the decision was the right one.
Operations, channels and infrastructure
Where the answer comes out, who receives it and where the compute runs. These are the decisions a client tends to leave for last and which in practice determine which use cases are even possible.
Infrastructure
Three cross-cutting pieces that do not show in a demonstration and without which none of the above passes a security review.
The full menu, component by component
The reference sheet details the twenty-seven components with what each one solves, and the platforms of our own that back the inventory. Write to us and we will send it to you.
See the full menuReady to talk?
If you're evaluating an AI solution for your company or want to explore a partnership, a managing partner will respond within 24 hours.