What we build

Connect AI to the systems you already run.

AI that reads from and writes to your accounting, CRM, email, file and bank systems, within limits you set, with a record of every step.

Last updated

An AI integration lets AI read from and write to the systems you already have, within limits you set, instead of people copying between them. It is worth doing when staff spend hours moving or matching the same facts between two systems, and the rule for matching them can be written down.

What is an AI integration?

Most firms already own the systems they need. The trouble is the gap between them: someone reads a figure in one system and types it into another, or compares two lists by eye. An integration closes that gap. The AI reads from one system, checks what it found against a second, and writes the result back.

Each connection starts with what it is allowed to touch. Where the two systems disagree, the software sets the item aside for a person instead of guessing.

Data read from your systemOnly what is allowed
Matched and checkedAgainst a second system
A person reviews the mismatchesExceptions only
Written back, record keptAppend-only

Is an integration the right fit?

It fits when

  • Staff copy the same facts from one system to another every day or every week.
  • Two systems hold the same record and drift apart over time.
  • The rule for matching items can be written down in plain words.
  • The data arrives as files, statements or emails that a person now reads by eye.
  • You want a record of what moved, when and why.

It is the wrong tool when

  • Your two systems already offer a built in connection that does the job.
  • The transfer happens twice a year and a person can do it in an hour.
  • The matching rules change every time and cannot be written down.
  • A system you rely on offers no way to read from or write to it.

What can you connect for a firm like ours?

These are illustrations of connections that can be built. They are examples of the job, not client work. Real work is further down the page.

CPA and accounting firms

Example

Bank feed to general ledger

Today
A bookkeeper compares each bank line with the ledger by eye at month end and hunts for the entries that do not agree.
The build
The build reads the bank feed and the ledger each day and matches the lines it can. It sets aside the ones it cannot, with the reason, in a short exceptions list.
A person still decides
The bookkeeper clears each exception and approves any adjustment.
Example

Practice management to billing

Today
At the end of each period, staff copy hours and engagement terms from the practice system into the billing system and check them against the engagement letter.
The build
The build reads the recorded time and the engagement terms, prepares the draft invoice lines and flags time that falls outside the agreed scope.
A person still decides
The engagement partner approves each invoice before it is sent.

Investment advisers and asset managers

Example

CRM to portfolio system

Today
Client names, addresses and household groupings are kept in two systems, and an associate compares them before each review cycle.
The build
The build reads both systems and lists every client whose record differs. For simple differences it prepares the correction for the system that is out of date.
A person still decides
An associate approves each change before it is written.
Example

Custodian files to the reporting system

Today
Staff download position and transaction files from each custodian and load them into the reporting system, checking totals as they go.
The build
The build collects each file, checks it against the prior day and against the reporting system, and loads what agrees. A file that fails a check waits for review.
A person still decides
The operations lead decides what to do with any file that fails a check.

Law firms

Example

Document management to matter records

Today
Documents are saved in the document system, and a legal assistant updates the matter record by hand to say what has arrived.
The build
The build reads new documents in each matter folder, names them by type and date, and updates the matter record. Anything it cannot place is listed for review.
A person still decides
The responsible attorney decides what belongs in the matter and what does not.
Example

E-signature status to the matter checklist

Today
Staff check each signature request by hand to see who has signed, then tick the item on the closing checklist.
The build
The build reads the status of each signature request and updates the matching checklist item. It lists the signers who are still outstanding and drafts a reminder.
A person still decides
The attorney or paralegal sends the reminder and decides when the matter can close.

Mortgage and lending

Example

Loan origination system to the conditions tracker

Today
When the underwriter issues conditions, a processor retypes them into a tracker, and the two lists differ by the end of the week.
The build
The build reads the conditions in the origination system and keeps the tracker in step with them. It marks a condition as cleared only when a matching document is on file.
A person still decides
The processor and underwriter decide whether a document satisfies a condition.
Example

Credit and income documents to the file checklist

Today
A processor opens each credit report, pay stub and tax form to confirm it is in the file and covers the right period.
The build
The build reads each document, records the borrower, period and type, and ticks the matching line of the file checklist. It lists what is missing or out of date.
A person still decides
The underwriter reviews the file and makes the credit decision.

Operations-heavy businesses

Example

Job system to invoicing

Today
Office staff look through the completed jobs to find those with no invoice, then key each invoice into the accounting system.
The build
The build reads completed jobs, compares them with the invoices already raised and prepares draft invoices for the jobs that have none.
A person still decides
Office staff review each draft and decide what is sent.
Example

Card and ACH settlements to deposits

Today
Someone adds up settlement reports from the card processor and the bank transfers, then tries to match the total to a deposit on the statement.
The build
The build groups the settlements into the deposits they belong to and checks each group against the bank feed. A group that does not match is set aside.
A person still decides
The bookkeeper investigates each group that does not match.

Built and running

Real connections, in use now.

Built and running

A dumpster rental company: deposits that match the bank feed

Before
Done by hand.
What it does
Groups card and ACH payments into deposits that match the bank feed. It runs as a Claude skill in the company's own Claude workspace, with no new software to host.
A person still decides
Office administration works through the exceptions.
Read the story
Built and running

A dumpster rental company: truck activity matched to jobs

Before
Done by hand.
What it does
A daily review of truck activity matched to jobs: time on site, idling and gaps. It was in daily use from the first day.
A person still decides
Office administration works through the exceptions.
Read the story
Built and running

A dumpster rental company: franchise fee filings from job data

Before
Done by hand.
What it does
County franchise fee filings are prepared from job data, inside the company's own Claude workspace.
A person still decides
Office administration works through the exceptions.
Read the story
Built and running

A financial services firm

Before
Daily operations ran on manual work and desktop tools that only a few people could maintain, with no single technology lead.
What it does
The firm's Azure cloud environment and office network were deployed, and the operations tools run in that environment. Senior technology advice continues as an ongoing engagement.
Read the story

Anonymized at client request. Reference calls available under NDA.

Do your people copy between two systems every day?

How does a build work?

Step 1ScopeOne working session. A plan and a fixed price.
Step 2BuildWorking software early and often, on your own documents and systems.
Step 3LaunchYour people trained on their real work.
Step 4RunHosted, watched, improved.

The plan sets the timeline. A two week scoping sprint can first show one connection working on your own files, with a plan and a fixed price for the full build.

  • Map the systems

    List the systems involved and what each holds.

  • Set what it may touch

    Agree what the AI may read and what it may write, in writing.

  • Write the matching rules

    Agree how items are matched and what counts as a mismatch.

  • Test on your own data

    Run the connection on your real files, in read only mode first.

  • Review the exceptions together

    Look at what it set aside and adjust the rules.

  • Train and switch on

    Train the people, then turn on writing with the record running.

What do you get at handover?

  • Working connections

    Running in your environment, between the systems you named.

  • The record of actions

    An append-only record of what was read and written.

  • Written rules

    What each connection may touch and what it may do.

  • Training

    For the people who review the exceptions.

  • A named security review

    Completed before the connection is switched on.

  • Someone to call

    DoubleChecked hosts, watches and improves it after launch.

How is our data handled?

The AI runs in private, client-controlled environments, and client data does not go to public AI services. DoubleChecked contracts directly with Anthropic under commercial terms and a data processing agreement. Deployments include single sign-on, role design, retention settings, audit logging, spend limits and network allowlisting. Zero data retention is available through the API, not the chat interface. See how security works.

Who can get inSingle sign-on and roles
Where it runsA private environment you control
What it may touchLimits set for each connection
Who signs offA person at your company
What it didAn append-only record

What does it connect to?

  • Accounting and general ledger

    Read entries and post approved ones.

  • Document management

    Read and file client and matter documents.

  • Email and calendar

    Read messages and draft replies.

  • CRM

    Keep client records consistent.

  • Bank and card feeds

    Match payments to deposits and invoices.

  • Line of business systems

    Loan, practice, custodian and job systems.

  • Spreadsheets

    Read and update the sheets people rely on.

  • File shares

    Collect statements and reports left in shared folders.

Questions buyers ask

How long does an integration take?

The plan sets the timeline, and you see it before the build starts. A two week scoping sprint can show one connection working on your own files first, so you can judge it with something real.

What will it cost?

Every project gets a fixed price after one working session, and you know the number before the build starts. A working session is 45 minutes on one idea from your company.

Where does our data go?

AI runs in private, client-controlled environments, and client data does not go to public AI services. DoubleChecked contracts directly with Anthropic under commercial terms and a data processing agreement, with no reseller in between.

Who checks the output?

The software checks before it confirms an action, and a person at your company reviews and signs off on outputs that matter. Each build keeps an append-only record of what the software did.

What happens when it is wrong?

Items the software cannot match are set aside for a person instead of guessed. The record shows what was read and written, so the cause can be found and the rule corrected.

What do you need from us?

One person who knows the job, access to the systems involved and a set of real files to test on. Your people are trained on their real work before the connection is switched on.

Can it write to our systems, or only read?

Both are possible, and each connection starts with what it is allowed to touch. Many begin read only, then writing is switched on once you have reviewed the results together.

Tell us what you want connected.

A working session is 45 minutes on one idea from your company: what to build, what it needs, and what it would cost.

  • A fixed price before we build
  • Your data stays in your environment
  • A record of every action
  • Reference calls under NDA
  • NDA before the first session
  • Since 2019
Start a project