The 90-Day AI Pilot — botzen.ai
The 90-Day AI Pilot · for large companies

You already know AI can help. Getting it in is the slow part.

A core system nobody dares touch. Security and compliance teams with every reason to be cautious. The 90-Day AI Pilot is built for exactly that room. One department, one process, a measured result, nothing written to or removed from your existing systems.

Built for larger companies where the problem is getting AI past security, risk and IT.

Enquire about a pilot See how it works

No obligation. Just clarity on where a pilot would land, and where it wouldn't.

1 department1 process90 days0 writes to your systems

The most important thing to understand

A layer on top of what you have. Not a replacement.

Nothing gets ripped out. The AI layer sits over what you already have, reads across it, and does the bridging your people currently do by hand. The finance team keep the system they trust. The underwriters keep the screens they know. IT stays out of a project they never asked for. Same systems. Same people. Running better.

Nothing gets ripped out. Your team keep the systems they know, and the teams that matter stay happy. Same systems. Same people. Running better.

What you have Core systemCRM · ERP · ATS · DMS Email & files Spreadsheets + What we add AI layer reads across, read-only = Running better Core systemCRM · ERP · ATS · DMS Email & files Spreadsheets Untouched Ninety days to prove it Same systems, same people What you have Core systemCRM · ERP · ATS · DMS Email & files Spreadsheets + What we add AI layer reads across, read-only = Running better Core systemCRM · ERP · ATS · DMS Email & files Spreadsheets
Why AI stalls in big companies

The business case was easy. The integration queue is where it gets stuck.

Most large companies have already agreed AI is worth doing. Then it hits the plumbing.

"Don't break it, we need it"The core system is twenty years old. Everyone depends on it, and nobody wants to be the one who touches it.
The security queueAnything new waits a quarter for a review that asks the same questions every time.
The change boardAnything that touches production goes into a cycle measured in months.
Nowhere safe to try itThere's no way to test AI on real work without touching production. So it never gets tested.

The pilot is built so nobody has to be brave. Read-only, on your existing platform, no new system of record. Nothing for IT to worry about, and nothing for the team to fear.

Two routes to the same goal

Most AI projects are integration projects in disguise. This one isn't.

The usual route Business case Tool selection Security review Integration project Change board Pilot, eventually Rollout Measured in quarters The 90-Day AI Pilot Map Build Run weeks 1 to 3 · governance pack for IT and risk included weeks 4 to 8 · read-only, on your platform Ninety days
The usual route Measured in quarters
Business case
Tool selection
Security review
Integration project
Change board
Pilot, eventually
Rollout
The 90-Day AI Pilot Ninety days
Map
Build
Run

The security and governance questions get answered in week three, as a deliverable, instead of sitting in a queue.

Skip the queue. Start with one process.

Enquire about a pilot
Where the pilot lands

Your systems work. The gaps between them are the job.

Big companies don't have an AI problem. They have a seams problem. The hours go on moving information between systems that were never built to talk to each other.

Today

Staff re-key from PDFs into the system, answer one query from three screens, and rebuild the same document from scratch every week.

In the pilot

AI reads across every source, drafts the answer with citations, and a named person approves it. Nothing gets written back to your systems.

Six sectors, one pattern

Where it could start

These are examples, not assumptions. You know your biggest pain point better than we do, and the process is chosen with your team in the first three weeks. These are the kinds of seams we often find.

Engineering

bids and RFIs

Tenders built by hunting through old projects. RFIs drafted from scratch. Specs scattered across SharePoint and email.

Logistics

customer queries

One shipment question answered from three screens. Customs paperwork checked by hand. Carrier data in five formats.

Insurance

submission intake

Broker submissions arriving as PDFs and re-keyed by underwriters. Gaps flagged by hand. Claims files nobody can search.

Real estate

lease abstraction

Leases read line by line to answer one question. Tenant enquiries handled from an inbox. Valuations in a spreadsheet.

Recruitment

CV and spec admin

CVs in every format, job specs rewritten weekly, candidate notes across email and the tracking system. AI formats and drafts. It never screens or ranks people.

Accountancy

client onboarding and files

Engagement letters, onboarding packs and audit files rebuilt for every client. Tax correspondence answered by digging through last year's folder.

How it works

Three stages. Ninety days. Every pilot runs the same way.

A fixed sequence, so your IT, risk and finance teams know exactly what happens when.

MAP BUILD RUN wk 1 wk 3 wk 8 wk 12 Process Maps, Pilot Plan, Governance Pack Workspace, training, one workflow, tested Live, measured, Pilot Report
MAP
BUILD
RUN
wk 1wk 3wk 8wk 12
01

Map

Weeks 1 to 3

  • Pick the process with your team.
  • Map it. Cut the steps that shouldn't exist.
  • Baseline the time, volume and errors.
  • Governance Pack written for your IT and risk people.

You get: your Process Maps, the Pilot Plan and the Governance Pack.

02

Build

Weeks 4 to 8

  • A sanctioned AI workspace on your platform, under your rules.
  • Your team trained to use it properly.
  • One workflow built at the seam. A named person signs off every output.
  • Tested against your own past cases before anyone relies on it.

You get: a working workflow and a trained team.

03

Run

Weeks 9 to 12

  • Live with the team, on real work.
  • Measured every week against the baseline.
  • Tuned as issues show up.
  • Handed over with documentation and a roadmap to scale.

You get: the Pilot Report, with the numbers.

What to expect

What you'll have at the end of ninety days

We don't promise a percentage before we've seen your process. We promise a measured number, a team that knows how to use it, and everything we build handed over to you.

Pilot Report · week 12 · illustrative layout One process, measured twice Baseline (Map) Week 12 (Run) Time per case Turnaround Rework and errors Hours returned to the team Weekly adoption

Bars are illustrative. The numbers come from your process, measured in Map and again in Run.

What the Pilot Report measures

  • Time per case. Minutes to prepare one bid, one submission, one query, one lease question. Before and after.
  • Turnaround. How long the customer, broker or candidate waits.
  • Rework and errors. How often it comes back wrong.
  • Hours returned. What the team gets back each week, and what they spend it on.
  • Adoption. How many of the team actually use it, week by week.
  • Accuracy on the test set. The score against your own past cases, before go-live.

What changes for your team

TodayIn the pilot
Rebuilding the same document from scratchA first draft assembled from what you already have, with sources
Re-keying information from one system into anotherExtracted, summarized, gaps flagged, checked by a person
Answering one question from three screensOne answer, cited, ready to send
Reading a long file to find one detailThe detail, the page it's on, the answer
Hunting for what was done last timeFound, summarized and reused

What you walk away with

  • Your Process Maps and the baseline numbers.
  • The Governance Pack, approved by your IT and risk people.
  • A sanctioned AI workspace, configured to your rules.
  • A trained team who use it without help.
  • One working workflow with a named approver.
  • The test set and its accuracy score.
  • The Pilot Report and a roadmap for the next process.

All of it yours to keep. No lock-in.

Want to know what your number could be? Tell us about the process.

Enquire about a pilot
The questions your risk committee will ask

Built to get past IT, legal and risk. Not around them.

Security

  • Your data is never used to train a model. It's in the contract.
  • Data stays in your own cloud tenancy and region.
  • The AI sees only what the logged-in person could already open.
  • Read-only during the pilot. Nothing written to or removed from your existing systems.
  • Every prompt and output logged for audit.

Confidence in outputs

  • Every answer cites the document and page it came from.
  • AI drafts, extracts and summarizes. Your people decide.
  • Tested against fifty to a hundred of your real past cases before go-live.
  • Low-confidence cases are flagged and routed to a person.
  • Nothing changes silently. Model and prompt versions are pinned.

Regulation

  • Risk classification and data protection impact assessment done in Map.
  • No automated decisions about people. In recruitment, AI never screens or ranks candidates.
  • Copyright on outputs is indemnified by the platform.
  • An audit trail built for your regulator, not bolted on later.

Your people

  • Time back, not headcount out. Said early, in writing.
  • The team pick the process, so nobody has change done to them.
  • The people who've kept the old system alive for years are the experts here, not the obstacle.
  • Nobody is asked to trust a black box. Every output has a name on it.
  • Training is part of the pilot, not an extra. Works councils or unions briefed early if you have them.
Is this for you?

Who the pilot is built for

A good fit

  • A large company in engineering, logistics, insurance, real estate, recruitment or accountancy.
  • You already believe AI can help. Integration is what's been slow.
  • A department head with a budget and one process that hurts.
  • A named owner who can give the pilot two to four hours a week.

Not a fit

  • Still deciding whether AI is relevant to the business at all.
  • Looking for a chatbot on the website.
  • Wanting AI to make customer-facing or hiring decisions on day one.
  • A smaller business. For that, the AI Operating System is the better starting point.

Sounds like you? Let's find the process.

Enquire about a pilot
Adrian Hegarty, founder of botzen.ai
Who leads it

Adrian Hegarty, founder of botzen.ai, leads every pilot. Ten years a digital entrepreneur. BSc Technology with Design at Ulster University, turned AI engineer. Ran an e-commerce retention marketing company building email and SMS systems for online brands, and now points the same skillset at AI.

Adrian sets the approach, the governance and the sign-off gates, and stays accountable for the result. A delivery team builds to that standard, wherever you are.

Ethan Pollak

"I can testify that Adrian is an AI expert!"

Ethan Pollak
Co-Founder & CEO, Pulse Devices

Questions

The things people ask on the call

Our IT backlog is a year long. How does this get in?

Because it doesn't join the backlog. The pilot runs inside an enterprise AI platform your IT team can approve in one review, reads your documents read-only, and creates no new system of record. There is no integration project to schedule.

What does "pilot" mean here?

A small, time-boxed trial before any bigger commitment. One department, one process, ninety days, measured against a baseline. If it works, you scale it. If it doesn't, you've lost very little and learned a lot.

Do we have to change our systems?

No. The AI sits on top of what you already run and reads across it. Your core system stays exactly where it is, whether that's an ERP, a policy system, a warehouse system, practice software or a property platform.

We already have an AI platform. Why would we need this?

Good. We build on it. The pilot isn't a platform. It's the process, the training and one working workflow with a measured result, delivered on whatever platform your IT team has already approved.

Our core system can't be touched. Does that kill it?

No. The first process is usually built on documents, emails and exports, not live system integration. That's where the hours go, and it's where the AI layer can read without anyone touching the core system.

Our team is nervous about AI. Will this land?

That's normal, and it's why they pick the process rather than have one picked for them. Nothing is automated behind their backs, every output has a person's name on it, and the first thing they see is the tedious part of their week getting shorter. Nervous teams tend to become the strongest advocates once they've watched it work on their own files.

What does it cost?

The pilot is a fixed fee, not a day rate, and it's discussed on the call once we know the process and the department. Any platform seats or usage are contracted by you directly and never marked up.

What happens after ninety days?

You keep everything that was built. It's yours. If the numbers earn it, we move to the next process and the next team, month by month, with notice to cancel.

Start with a conversation

Find the one process worth piloting.

One conversation. We'll look at where your people are bridging systems by hand, decide whether a pilot makes sense, and if it does, agree what to measure.

Enquire about a pilot

No obligation. If a pilot isn't the right move, you'll leave with clarity anyway.