Services
Three kinds of work, and what each one replaces
We build AI systems and custom software for operations and finance. Not a platform: one system, shaped around one process, built by the people who scoped it.
Where the deadline is
Finance operations
The work that runs to a deadline, breaks when one person is away, and is expensive to get wrong — so the system has to know when to stop and hand the item to someone.
- 01
Three-way match for accounts payable
Invoices read on arrival and matched to the PO and goods receipt in your ERP, within your tolerances. Clean ones post; the rest queue with the reason they stopped.
Instead ofKeying invoices in by hand and finding the mismatches at month-end.
- 02
Bank reconciliation every morning
Bank feeds and the ledger matched daily on amount, reference and a date window you set. Unmatched items queue with the closest candidates already ranked.
Instead ofA monthly reconciliation in a spreadsheet only one person can run.
- 03
A month-end close board
Every close task with an owner, a dependency and a due time. Status is read from the systems where the work happens, not asked for in a meeting.
Instead ofThe close held in one person’s head and chased over email.
- Xero
- QuickBooks
- NetSuite
- Sage
- Dynamics 365
- SAP
- Open Banking
- Plaid
- Stripe
- Excel
Where the paper is
Back-office automation
Documents turned into structured data and routed by policy instead of by memory — the part most vendors demo on clean files and deliver badly on your Tuesday.
- 01
Contract intake and a live register
Signed agreements pulled into a register: parties, term, renewal, payment terms, notice period. Off-template clauses flagged; renewals raised ninety days out.
Instead ofA shared drive of PDFs and a renewal nobody saw coming.
- 02
Supplier and customer onboarding
Forms and documents checked for completeness and cross-checked — company number, bank details, sanctions — then routed by policy. People see only what failed a check.
Instead ofA shared inbox as a queue and rules that live in one person’s judgement.
- 03
Remittance and statement processing
Remittances in any format read and allocated against open invoices. Partial and short payments queue with a proposed allocation to confirm or correct.
Instead ofCopying figures from a PDF into the ledger.
- Gmail
- Microsoft 365
- SharePoint
- Google Drive
- Dropbox
- DocuSign
- Adobe Sign
- Salesforce
- HubSpot
Where no vendor sells
Custom internal tools
The software your team needs and nobody sells, because it is shaped like your process and nothing off the shelf is.
- 01
An exceptions workbench
One screen for every item an automated process refused to decide: why it stopped, the candidates ranked, one action to resolve. Decisions write back to the source.
Instead ofThree tools and a manual step between each.
- 02
Reporting that reads the source
Daily numbers pulled from the systems of record, with the definition of each figure beside it. When two people disagree, the definition settles it.
Instead ofA dashboard fed by a spreadsheet someone updates by hand.
- 03
A controlled replacement for the spreadsheet
The workbook’s logic with what it never had: permissions, validation on entry, an audit log, and a history of every change.
Instead ofA sixteen-tab spreadsheet and a macro nobody will touch.
- Postgres
- SQL Server
- REST APIs
- S3
- CSV
- AWS
- Azure
- GCP
Questions
What people ask before they enquire
With scoping, twice. The first round is us listening; the second restates what we heard, in writing, for you to correct. Nothing is designed until that document is right, because a plan built on a misunderstanding is more expensive than a slow start.
A first pilot on a single process is usually weeks rather than months, because it runs beside what you already do rather than replacing it. The real variable is what your systems can hand us, which is why we check that before quoting rather than after.
Yes — the build is designed to be run by them. The people who will own it are in the room from the pilot onward rather than introduced at the end, and the handover includes the runbook and the documented failure modes, not a login.
Enterprise and SMB both. The work is the same shape either way: a process with volume, a deadline and a person doing it by hand. Marketing and sales operations are within scope but are not where we are strongest — operations and finance are.
Next step
Start with one process
Tell us how one process runs today — whichever one costs the most hours. You get back the shape of the build, a cost range and what moves it, and the cases a system should refuse to decide on its own.