We design and build custom AI for your finance, operations, sales and service teams, inside the ERP, CRM and banks you already run. It takes on the work that grows with your business. Your people approve what matters, and you own everything we build.
Your growth shouldn't wait on manual work. More customers, more volume and new markets add work between your systems. Since 2021, we have built production AI that takes it on.
- Medical manufacturing
- 60%
- less manual entry across 4 markets
- Beverage manufacturing
- 15 min
- per invoice run, down from 3 days
- Payments
- 99.25%
- of 4.6M transactions a period matched automatically
- Private equity
- 3 weeks
- earlier warning of cash-flow risks across 20+ companies
Built into the systems you already run
SAP
Microsoft Dynamics 365
Salesforce
Oracle NetSuite
HubSpot
Zendesk
Sage
Xero
DATEV
SharePoint
Snowflake
Databricks
Azure
AWS
OpenAI
How It Works
A payments operator reconciles every card settlement against its ledger. A workflow in code runs the steps. Two agents with narrow, read-only jobs do the reading and the investigating, rules keep what must be exact, and one person approves the real exception.
Every rule is written down, traced to its source and kept in the system, not in someone's head.
- 01
Work arrives
A provider's settlement file lands: 18,402 card payments in that provider's own format. Daily, from every provider and entity.
- 02
A reading agent reads it
It turns each provider's format into ledger lines, with a confidence for every field. It can read the file and nothing else.
- 03
Rules check it
Rules in code own what must be exact: counts, amounts, duplicates and the agreed fee schedule. No model decides a number.
- 04
An investigating agent prepares the exception
One payout is €38.20 short. A second agent, with read-only access to the ledger, the bank and the fee schedule, gathers the evidence and drafts the reason. Finance approves.
- 05
Posted once, and logged
After approval the workflow posts once through the ledger API. Every agent step, rule and decision stays in the case record.
Provider settlement files
Settlement file BP-0914settlements@brisholtpay.com
Daily settlement, 14 September.
18,402 card transactions settled for €2,316,480.55 gross.
Fees deducted at source: €11,582.40. Net payout on 15 September.
References use the new format BP-yyyymmdd-n from this file.
Reconciliation runWaiting for approval
- Merchant and provider IDLedger
- Transaction countLedger
- Duplicate referencesLedger
- Payout dateBank
- Net payout amountBank
Payout €38.20 below the expected net amount (fee not in the agreed schedule)
Sent to Anna de Vries, FinanceApproveApproved by Anna de Vries, 09:43
Posted to the ledger through its API. Every step logged.
- Behind the screen
- WorkflowRuns the steps, keeps the case recordCodeRunning
- Reading agentSettlement file to ledger linesReads the file onlyDone
- RulesCounts, amounts, duplicates, feesCodeDone
- Investigating agentEvidence and reason for the exceptionReads ledger, bank, feesRunning
- Anna de VriesApproves the exceptionFinanceRunning
- PostingPosts once, after approvalWrites to the ledger APIWaiting
Modelled on the reconciliation system we built for a payments operator, matching 4.6 million transactions a period at 99.25%. Client names and figures are changed to protect confidentiality.
Workflows We Run in Production
Each one runs inside a client's own systems today, with a measured result.
Operations · Medical manufacturing
Multi-market commercial operations
Bredent Medical
- Goal
- Run four European markets as one business.
- What stood in the way
- Each market ran its own Dynamics 365 or legacy system, so orders and stock were retyped between them.
60%
less manual entry, and one real-time view of all four markets
IT · Public sector
IT ticket triage
National digitalisation agency
- Goal
- Route a national service desk's tickets to the right team, faster.
- What stood in the way
- No data could leave the agency's own servers, so cloud AI was ruled out.
Finance · Payments and gaming
Payment reconciliation
Payments operator
- Goal
- Keep reconciliation on time as transaction volume grows.
- What stood in the way
- Millions of transactions a period were matched largely by hand.
Finance · Beverage manufacturing
Invoice to payment
Beverage manufacturer
- Goal
- Pay suppliers on time as order volume grows.
- What stood in the way
- Invoices, orders and goods receipts were matched by hand across the ERP and inboxes.
15 min
per invoice run, down from 3 days, with 94% matched automatically
Reporting · Private equity
Portfolio reporting
Private equity group
- Goal
- See every portfolio company clearly as the group adds more.
- What stood in the way
- Twenty-plus companies on different ERPs reported in spreadsheets.
3 weeks
earlier warning of cash-flow risks, 20+ companies in one layer
Validated with clients as proofs of concept
Industries we build for
- Manufacturing
- Logistics
- Retail
- Healthcare
- Financial services
- Insurance
- Private equity
- Payments
- Media
- Telecom
- Energy
- Professional services
- Public sector
Connected. Controlled. Owned.
Connected
It runs inside the ERP, CRM and banks you already have. No migration, and no new platform for your teams to learn.
Controlled
Rules own what must be exact, your people approve what matters, and every decision is logged for the auditor.
Owned
You keep the code, the rules, the tests and the operating manual. Your team runs the system after we leave.
Trusted by teams at
We ran four markets on systems that did not talk to each other. SIEL connected them without replacing anything, and for the first time we see all four in one view. The retyping went with it.
Partners we deliver with
Three Ways to Work With Us
Start with one workflow and extend only when the results justify it.
- 01
Workflow Assessment
Two weeks with your process owners and system records. A measured baseline and a clear build decision, including when not to build.
Two weeks. Read-only access under NDA. Fixed fee.
- 02
First System Delivery
We build in your environment on your existing systems and validate against real cases before the system carries live work.
Scope and fixed fee agreed after the assessment.
- 03
Embedded Engineering
Our engineers stay alongside your team to extend the system or build the next one, each with its own handover.
Time-boxed per workflow. Fixed fee per workflow.
Questions Before the First Call
What leadership teams ask us before the first call.
How do we choose the first workflow?
It begins with a two-week Workflow Assessment. Our senior engineers map how the work moves through your systems, measure the current baseline and identify the workflow, internal or customer-facing, where AI will add the most capacity under rules that can be verified. The assessment states what should not be built as clearly as what should. It carries a fixed fee, agreed in writing before work begins.
How do we prove a system works before it goes live?
We validate each system against real cases agreed with your team and measure it against the baseline from the assessment. Approval steps and exception paths are tested with the people who will use them. The system goes live only when the results meet the thresholds you have signed off.
How does the AI stay under your control?
The AI reads and proposes; it does not act alone. Business rules agreed with you determine what is permitted, and any item below your confidence threshold, or rejected by a rule, is routed to a named approver with the evidence. Nothing is written to your systems until it passes these checks. Data stays in the environment you specify, and every step is recorded for audit.
What do we leave behind at handover?
A production system running in your environment, owned entirely by your organisation: source code, business rules, test cases and documentation, with no licence to renew. Your team receives an operating runbook and training. Where continued support is preferred, our engineers remain embedded for a defined term.
Discuss Your Operation With Our Engineers.
Describe one workflow and the systems it relies on. A senior engineer responds within two business days with an initial assessment: what we would build, what we would not, and why.