Skip to content
SpeedOzAI strategy, implementation and operations
Go to app
Contact us
Running it

Launch is the start. Not the finish.

An agent that answers your phone needs somebody watching it in month seven, not just in week one. This is what we do after it is live: what we handle without asking, what we bring back to you, and what typically arrives in writing each month, whether or not anything happened.

Request an evaluation
See a monthly read

One letter a month, and the decisions lead it.

Not a dashboard you have to remember to open. A written read of the month, in the order that respects your time: what needs you first, then where things stand, then the numbers. This is what one looks like.

Monthly read · September Acme Pty Ltd · from your SpeedOz team · 1 October 2 decisions waiting

Needs you

Let the after-hours agent create jobs in ServiceM8 Isla Doyle

Callers confirmed 41 bookings by hand this month. Waiting since 12 September.

Reconnect Xero before 3 October Finance

The connection expires and needs a person on your side to sign in again.

Where things stand

Phase 5 of 6. The after-hours voice agent has been live since 2 September. Document summaries are in testing with two people, and nothing has happened out of order.

The month in four numbers

1,284ran 41held for a person 9refused AUD $412cost, within your rate

We recommend

Take away read access to the whole file store. It was used four times, and the job board answered the same question each time.

It arrives whether or not anything happened. A quiet month gets a letter that says so. The value of a monthly read is that it is unconditional: the month you stop hearing from us is the month you would need it.
  1. Apr    2 decisions
  2. May    Quiet month
  3. Jun    1 decision
  4. Jul    Quiet month
  5. Aug    3 decisions
  6. Sep    2 decisions
Your monthly read, every month

Three things go wrong. Two of them are ours.

Credentials expire, connections fail, policies fall due. None of them is a surprise, and the platform has a stated path for each rather than an alert with nothing behind it.

Connections and policiesExample business · this weekChecked 2 minutes ago
  • Microsoft 365 sign-inShared for the business Renewed, same authority
  • ServiceM8 job boardRead the job board Not answering, sent to Isla
  • After-hours agent policyApproved 3 July With Isla, usage attached
Each change lands on the record: what happened, what we did, and who it is waiting on.
A credential comes up for renewal Ours, within the agreed scope

We renew it before it lapses where the provider allows, and tell you when it needs a person on your side. Reissuing a credential never widens reviewed authority.

A connection stops answering Ours, and you are told which system

The agent stops rather than retrying, the work goes to a person, and the task names the system and the person it is waiting on. A failed write is never retried: that is how one job ends up with two invoices.

A policy falls due for review Yours to decide, ours to bring

A review after ninety days, with the usage evidence beside it. Nothing is extended or widened automatically.

Most months we recommend taking access away.

A month of evidence usually argues for less, not more. It is the recommendation nobody selling software makes, so it is worth saying plainly: our improvements are mostly subtractions.

Read every file in the storeAfter-hours agent · granted 2 September
Used 4 times in September. The job board answered the same question each time.
Removed by Isla Doyle · 3 October
An authority nobody used

Read four times in a month where another tool answers the same question, we recommend removing it.

A refusal that keeps happening

Nine refusals of the same tool means something expects to be able to do it. We find out what, and tell you.

A step a person always changes

If somebody rewrites the draft every time, the draft is wrong. That is a scope change, not a training problem.

A month with no refusals at all

Usually means the authority is too wide, not that the agents behaved well.

What keeps it running, and what moves the number.

One organisation rate

Not per seat. The whole team uses it for one agreed rate.

Quoted from your size

The monthly fee is quoted from the number of people and integrations in scope, and the monthly read shows both.

Connectors included

The connectors on the shelf are included. Anything custom is scoped and priced before it is built.

Agreed in writing, per phase

Running it starts from AUD $900 a month for the organisation. Your figure is in the written scope, before the pilot starts.

We report whether anybody was replaced.

The read states what changed about the people doing the work, because that is the question your team is actually asking. Where nothing changed, it says nothing changed: the same people answer the phone, and the agent covers the hours nobody was there.

If an agent ever does start doing somebody’s whole job, that is a conversation to have on purpose rather than a number to discover in a report.

Also in every read
  • What it cost, against the rate you agreed
  • Which refusals repeated, and what we think expects to do it
  • Anything we are recommending you stop

Ask what month seven looks like.

It is a fair question to put to anybody selling you AI, and the answer should be a document rather than a promise. Ours is the monthly read, and you can see one before you engage.

Request an evaluation
Talk to a person
Ask to see an example monthly read.