AI AUTOMATIONS AND INTEGRATIONS

Your systems already hold the answer.
They just don't talk.

In every business I've looked at, a large share of the manual work is people carrying information between systems that were never designed to meet. I connect them, and put judgement only where judgement actually adds something.

Book a conversation

Free, 30 minutes, no obligation.

steve@steveholloway.co.uk
Fixed priceYou own it outrightThere's always a manual route
Fixed priceYou own it outrightThere's always a manual route
THE RULE

The AI is the easy part.

The expensive part is everything around the model: assembling the data, understanding the process, knowing where each value came from and who checks it.

WHAT THIS LOOKS LIKE IN PRACTICE

The work that happens between your systems.

AN MCP SERVER ON BULLHORN

Recruiters work with Bullhorn, the recruitment CRM, in plain language: searches, updates and notes, instead of clicking through its screens record by record.

BULLHORN TO XERO

Customers are created and updated in Xero automatically, and invoice notifications and finance blocks appear in Bullhorn. Recruiters are told when a finance action is theirs, such as talking to a customer about an invoice. The notifications and emails once sent by hand are gone.

INTIME AND ETZ TO BULLHORN AND MICROSOFT DYNAMICS

New timesheet users are set up in InTime and ETZ, timesheets and their status show in Bullhorn, with a warning when one has not been submitted, and draft invoices are created in Dynamics. Nobody sets up those users, checks timesheets outside Bullhorn or drafts those invoices by hand.

HUBSPOT TO BULLHORN

Inbound call information reaches Bullhorn, so recruiters no longer look in two systems.

A PROOF OF CONCEPT

AI completion of PDF forms, tested across fillable, non-fillable and scanned forms, with accuracy measured field by field for each model and route.

THE QUESTION EVERYONE ASKS

"What happens when the AI gets it wrong?"

A manual route stays open. That is written into our master services agreement and our terms of business. The agreement says:

"Where a capability depends on a model or an external source, a manual route will remain available so that its failure does not stop the Client working, unless the Statement of Work says otherwise."

Beyond the agreement, this is how it usually works:

WHEN A TRANSFER FAILS

It is retried automatically. If it still fails, a named person in your team is alerted, with the record. A reconciliation report shows what did not arrive, and your team re-runs it or finishes it by hand. I fix defects in the integration itself.

WHEN THE OUTPUT IS WRONG

What the AI produces is a draft, and a named person reviews it before it is submitted or sent. A rejected item is marked in its system of record and finished by hand there, so it is neither lost nor redone by the automation.

Start with the design. Stop after it if you want.

Book a conversation

Free, 30 minutes, no obligation.

steve@steveholloway.co.uk