A model becomes yoursthe moment it reachesyour company's data.
Everyone can license the same models. What no one else has is your email, your shared drives, your CRM, your APIs — the record of how your business actually works. We connect the model to those systems, read the scans and photographs that never arrive as clean data, and write results back through your platform's own API.
What we installat this layer.
Your systems, connected
Email, shared drives, CRM, ticketing, the systems of record you already run. Read through their own APIs, under the permissions you already grant people.
Documents as they arrive
Scans, photographs, and forwarded attachments read as images, the way a person reads them. Every field carries a confidence score, and a blank is flagged for review, never invented.
Harmonization
One picture across sources that were never meant to join, built on a patent in data ingestion and harmonization.
Write-back through your API
Results commit through your platform's own API, into the system your team already works in, with retries designed around its nightly downtime.
“Some of it is a photograph of a form someone took on their phone, and it still has to come out right.”
Every message gets read, scored, and routed.
A renewal pack, a purchase order confirmation, a referral letter — none of it arrives in the same shape twice. Each one gets read, checked against a confidence floor, and routed: run automatically, held for a person to review, or recognized as a duplicate and dropped. Nothing above the floor waits on a person; nothing below it runs without one.
Already part of the workflow.
Higher up this page, “your CRM” usually means one of the names below: the systems a business like yours already runs on. We reach them as part of building the workflow, not as a separate integration product billed on its own contract and renewed every year whether anyone touches it. What a dedicated integration platform would charge for on top is already inside the price of the workflow itself.
| System | What it is for | How we reach it | Workflows mapped |
|---|---|---|---|
Proclaim Case management that predates the API era | System of record for matter and claim files, and the system every other process eventually has to agree with. | Read through its own interfaces and scheduled exports; writes commit through the platform's API, with retries designed around its nightly downtime. | 3 |
Acturis The policy platform most UK brokers already run their book on | System of record for policy administration: quotes, renewals, endorsements and the trail a regulator expects behind each one. | Reached through its own web services API, down to policy, endorsement and mid-term adjustment level, under the same user permissions a broker already holds. | 3 |
Salesforce The CRM most sales and account teams already run pipeline through | System of record for accounts, opportunities and the contact history a renewal, a quote or a new instruction gets checked against. | Reached through its REST and Bulk APIs, scoped to the same objects and fields a logged-in user would see. | Not yet mapped |
Zoho CRM A CRM smaller distribution and industrial teams already run on | Holds the customer and deal record for teams too small to justify a heavier CRM, and the first place a sales question gets answered. | Reached through its REST API and webhooks, with module-level permissions matching what a user already has. | Not yet mapped |
Microsoft Dynamics 365 The CRM and ERP suite bundled with an existing Microsoft estate | Holds customer records and, in the same tenant, order and inventory data, for organizations that standardized on Microsoft rather than adding a separate CRM. | Reached through its Web API and Dataverse connectors, inheriting the Entra ID permissions already assigned to a user. | Not yet mapped |
Microsoft 365 and Outlook Where most instructions and requests actually arrive | The inbox and calendar every other system's inputs first pass through, and the record of who asked for what and when. | Reached through the Microsoft Graph API, mailbox by mailbox, under delegated permissions rather than a standing account with full access. | 16 |
SharePoint The document library most Microsoft-tenant firms already store files in | Holds the working file for a matter, a claim or a job: correspondence, drafts and the versions that came before the final one. | Reached through the Microsoft Graph API, site by site and library by library, matching the folder permissions already in place. | 13 |
Shared drives and file stores The network share or cloud drive that predates any document system | Where documents land before, or instead of, a proper document management system: scans, exports and the folder everyone already knows to check. | Reached through a scoped service account or the drive provider's own API, read-only unless a write path is agreed folder by folder. | 3 |
SAP The ERP behind purchasing, inventory and finance at larger sites | System of record for purchase orders, stock levels and cost data, and the system a supply exception or a delivery mismatch has to reconcile against. | Reached through its OData and RFC interfaces where they are exposed, or through scheduled batch exports where they are not. | 4 |
NetSuite A cloud ERP common at mid-sized distribution and retail operations | System of record for orders, inventory and the general ledger, in a single tenant that finance and operations both work from. | Reached through its SuiteTalk REST and SOAP web services, under a role scoped to the records a job actually needs. | 1 |
Warehouse management The system that tracks stock from the dock door to the pick face | System of record for stock location, pick and pack status, and the source of truth a delivery query has to check first. | Reached through the platform's own API where one exists, or through scheduled file drops from the scanner and terminal estate where it does not. | 2 |
Shopify and marketplace channels Storefront and order data across a store and its marketplace listings | System of record for orders, returns and stock levels as customers see them, across a store and however many channels it sells through. | Reached through the Admin API for the storefront itself, and through each marketplace's own seller API for listings placed there. | 2 |
Practice management The system a healthcare or legal practice already books, bills and files against | System of record for appointments, matters or episodes of care, and the billing narrative that has to match what actually happened. | Reached through the platform's own API where one is offered, or through scheduled exports and a review-only portal login where it is not. | 4 |
Finance and ledger systems The general ledger every number eventually has to tie back to | System of record for the transactions everything else generates, and the place a leakage or reconciliation question always ends up. | Reached through the ledger platform's own API where it has one, or through a scheduled export in the format its accountants already use. | 3 |
Why it holds
~60 cases a day, 15 minutes down to 2.
A regional insurer's claims intake runs on this layer in production: scanned instructions to structured case files, measured on their own samples.
Book a call.We'll come back with specifics.
Start with your people or with the work. One job at a time, on probation, measured in hours and money. Everything we build stays yours.