Skip to content
SpeedOzAI strategy, implementation and operations
AI implementation services

The AI writes a good reply. It just can’t see the customer. We connect it to your CRM, ERP, website and internal tools.

For businesses of about 50 to 500 people whose work is spread across a CRM, an ERP or accounts system, a shared inbox and a website.

We connect the AI apps your team already uses to the systems your work lives in, test them on real work with your people, and hand over a setup where a named person decides what the AI may change.

See an example integration map
Your CRM, ERP, website and inbox connect to the AI through one governed layer. Reads pass straight through. A change waits there until a named person approves it, and both are recorded.

Most AI stalls between the demo and Monday.

A demo answers from a few documents. Real work needs the customer record, the stock level and last week’s email, and someone who has decided what the AI is allowed to touch.

It can’t see the work

Staff copy a customer’s history out of the CRM, paste it into ChatGPT, then paste the answer back. The time saved goes on the copying.

What we doConnect the AI to the systems where the work sits, through the vendor’s own connector where one exists.

Or it can see everything

One shared admin key reaches every record, so nobody will let it near real data and the pilot stays a pilot.

What we doEach system starts closed. We propose the least each job needs, and a named person on your side approves it.

Nobody owns it after launch

The consultant moves on, a sign-in expires, and the first anyone hears of it is a customer who never got a reply.

What we doHand over who looks after what, in writing, and keep running it with you if you want us to.
What’s included

Four pieces of work, done with your team.

We shape the scope around your goals, the systems you already run and the people who will use it. Timelines and deliverables are confirmed in writing for your project.

System integration

We connect the AI to your CRM, ERP, inbox, website and internal tools through supported connectors and APIs, using the vendor’s own connector where there is one.

Data preparation

We map the information each job needs, where it lives and who may read it. Nothing is copied into a new AI database.

Operational rollout

We test integrations and their exceptions, agree what happens when something fails, then launch through an agreed rollout plan.

Team enablement

Plain guidance for the people using it: what the AI does on its own, what it asks first, and when to step in.

Where implementation sits in our six phases
Discover
Prioritise
Not sure what to connect first? Start with AI strategy consulting.
Connect
Govern
Launch
This service: from a scoped plan to people using it on real work.
Improve
Running it, after go-live.
The integration map

Every system, what it reads and what asks first, on one page.

Before anything connects, you get a written map like this one. A named person on your side signs it off, and nothing is switched on that isn’t on it.

An example, not a client. A 60-person wholesale distributor on HubSpot, Dynamics 365 Business Central, Microsoft 365 and Confluence, with a chat on its website. The actions are the real ones each system offers.

Integration mapSales and service team · example
Signed off by Priya
System Reads on its own Asks first Off
CRMReadyHubSpotEach person signs in
Reads on its own
Find a contact or company
Look up a deal and its stage
Asks first
Create or move a deal
Off
Bulk update records
ERPReadyDynamics 365 Business CentralEach person signs in with Microsoft
Reads on its own
Check item stock
Look up a sales invoice or quote
Asks first
Create a sales quote or invoice
Off
Post an invoice
InboxReadyMicrosoft 365Each person signs in
Reads on its own
Read an email thread
Check calendar availability
Asks first
Send an email
Off
Delete an email or event
Internal toolsReadyConfluenceEach person signs in
Reads on its own
Search pages
Read a page
Asks first
Update a page
Off
Turn on a public link
WebsitePart of setupChat on your websiteVisitors don’t sign in
Reads on its own
The pages and answers you approve
Asks first
Pass an enquiry to HubSpot as a new contact
Off
Quote a price or promise stock
Reads
nothing changes
Ask first
waits for the named person
Off
refused and recorded; only the owner can turn it on
What each system can do

One enquiry through this map

Example
  1. Microsoft 365
    An email asks for 40 cartons by Friday

    Sam asks Claude to quote it from his Outlook.

    Read an email thread
  2. Business Central
    Stock checked

    52 on hand, so Friday is possible.

    Check item stock
  3. HubSpot
    Customer found

    An open deal, and the quote they accepted last month.

    Look up a deal and its stage
  4. Business Central
    Quote created, once approved

    Creating a quote changes data, so it waits for Priya, who approves it on her phone.

    Approved by Priya
  5. Microsoft 365
    Reply drafted in Sam’s Outlook

    Sam reads it and sends it himself. Every step is on the record.

    Draft the reply
Go-live

Go-live is a checklist, not a date.

We plan the rollout around your operations. Every connection is tested on ordinary work and on the awkward cases, and the fallback for each system is agreed before anyone relies on it.

The people you name go firstIt is released to the people and channels you nominate, and widens only when you agree.
When a system stops answering, a person takes overThe AI stops rather than retrying, and the task names the system and the person it is waiting on. A failed write is never retried, so one quote never becomes two.
Approvers typically practise before day oneEach named approver usually approves and refuses a test request from their phone, so the first real one isn’t the first they have seen.
Go-live checklistSales team, first eight people · example
Ready to launch
  • Integration map signed offPriya, operations manager
  • Each person signed in as themselvesHubSpot, Business Central and Microsoft 365
  • Ask first tested from Priya’s phoneA test quote held, then approved
  • Off tested on Post an invoiceRefused, and the refusal recorded
  • Awkward cases runA duplicate contact, an unreadable PDF, an order at 9pm
  • Fallback agreed for each systemIf Business Central stops answering, the request goes to Sam
  • Guidance sent to the first eight peopleWhat runs, what asks first, when to step in
  • Go or no-go with the team leadGo, from Sam. Live for the first eight on Monday.
An example of the shape, not a real record.
Deliverables

What you get, and what stays yours.

An integration and data-flow planThe map for every system in scope: how each one signs in, what the AI may read, what asks first and what stays off.
Configured connections and workflowsLive and tested, with access set per team and Ask first on anything that changes a record or leaves the business.
Testing and rollout documentationWhat was tested, what failed and what changed, the go-live checklist, and the fallback for each system.
Team handover and operating guidanceShort guidance for the people using it and for your approvers, and who to call when something looks wrong.
What stays yours
Your systems. They stay the source of truth. Nothing is migrated.
Your sign-ins. Each person signs in as themselves. Granting access needs a decision; taking it away needs only you.
The record. Every request, refusals included, on a record nobody can edit, and you can export it any time.
The paperwork. The map, the test notes and the guidance are yours to keep.
Price

Start free. Then a fixed scope, in writing.

Every stage is agreed in writing before it starts. These are starting figures for businesses of about 50 to 500 people.

EvaluationFree

A person reads your request and replies within one business day. Nothing is connected.

Six-week pilotAUD $5,000

One process, one team, on your real systems. Credited in full against setup if you continue.

SetupFrom AUD $5,000

A fixed scope, quoted in writing, typically live in about 4 to 6 weeks.

Running itFrom AUD $900 a month

For the whole organisation, not per seat.

Before we start

What people ask before connecting anything.

Anything else, ask in the evaluation. A person answers within one business day.

Usually, and we check before we promise. We look at the APIs, access controls and connectors your systems offer before the scope is confirmed. On our integrations list, each system is Ready, Connected during setup at no extra cost, or needs a scoping workshop with a fixed price first.

We plan the rollout around your operations, test the key workflows on real work, and agree fallback and escalation before launch. It goes to the people and channels you nominate first, and widens only when you agree.

No. Your CRM, ERP and inbox stay the source of truth. The AI reads what a job needs at the moment it needs it, through the access you approved, and changes a record only through Ask first or an action you have allowed.

Then we start with a scoping workshop, at a fixed price agreed before it starts. You get a written list of what the system allows and a price to connect it, then decide. A connector built for your business alone is priced separately.

Claude, ChatGPT or Copilot, approved per team by a named person. People sign in as themselves, and each app gets what their team is allowed, no more.

You can, with the guidance we hand over. Or we run it for you: connections kept healthy, exceptions watched, and a written read, typically each month, decisions first.

Bring one system and one slow job.

Tell us what you run on and where the work waits. A person reads it and replies within one business day with a practical first step, and whether a pilot fits.