Opportunity discovery
We sit with the people closest to the work and map the repetitive jobs, the customer friction and the opportunities going missed.
You keepA written picture of how the work actually runs, in your team’s words.
AI strategy consulting
Every team has an AI idea. Find the ones worth funding, and build a clear roadmap.
A clear roadmap. A confident first step.
We rank every idea on value, effort and risk with the people who do the work, then hand you a one-page roadmap with the first pilot scoped and a baseline for every measure.
Where the conversation usually starts
Few businesses ask for an AI strategy. They ask about one of these, and the strategy is how it gets sorted out.
Everyone has a different AI idea
Operations wants the phones answered, accounts want invoices matched, and the director saw a demo last week. Nobody can compare them, so nothing starts.
A trial ran, and nobody can say if it worked
Licences were bought or a chatbot went live without a baseline. The bills keep coming, and nobody can point to what changed.
Someone has asked for your AI plan
A board member, an insurer or a large customer wants to know how you use AI and who controls it. Today the honest answer is a list of tools.
What’s included
Four parts, and each one leaves you something on paper
We shape the scope around your goals, the systems you already run and the people who will use the result.
Readiness assessment
We review your data, the tools you already pay for and your team’s skills, to find what is practical today and what needs fixing first.
You keepA readiness note: what is ready, what needs tidying, and what to leave alone.
Prioritised roadmap
We compare every use case on business value, effort and risk, map what each one depends on, then set a staged delivery plan.
You keepThe ranked list with the reasons, and the one-page roadmap.
Success measures
We agree a baseline, a few useful measures and an owner for each, so your team can judge every initiative on its own numbers.
You keepA measurement and adoption plan, with the date each baseline is taken.
The documents are yours, whether or not you build anything with us. They are written about your business, not about our product.
How we rank
Every idea answers the same three questions
What is it worth, what will it take, and what could go wrong? Scoring each idea on value, effort and risk turns a wish list into an order. Some ideas don’t survive it, and we say which.
A worked example, not a client
A facilities maintenance business of about 140 people runs on Microsoft 365, Simpro and Xero. It brings seven ideas to discovery. Here is how they might rank.
- Follow up quotes that went quietSimpro and Outlook. Drafts only, and a person sends. Value 4 of 5. Effort 2 of 5. Risk 1 of 5. Pilot first
- Sort the shared inbox and draft repliesOutlook. Sending waits for a person. Value 4 of 5. Effort 2 of 5. Risk 2 of 5. Next
- Weekly site report from job notesSimpro, read only. Value 2 of 5. Effort 1 of 5. Risk 1 of 5. Next
- Match supplier invoices to jobsXero and Simpro. Needs tidy job codes first. Value 5 of 5. Effort 4 of 5. Risk 3 of 5. Later
- Answer after-hours callsA phone line that gives only approved answers. Value 4 of 5. Effort 3 of 5. Risk 3 of 5. Later
- Predict which sites need reactive workNeeds job history the business doesn’t keep yet. Value 3 of 5. Effort 5 of 5. Risk 3 of 5. Fix the data first
- Approve purchase orders automaticallySpends money without a person deciding. Value 3 of 5. Effort 3 of 5. Risk 5 of 5. Not worth doing
Value: higher is better. Effort and risk: lower is better.Ranked overall: value, effort and risk together, plus what each one depends on.
Quote follow-ups go firstHigh value, low effort, and a person still sends every email. It is also the easiest one to measure.
Invoice matching is worth the most, and waitsIt depends on tidy job codes in Simpro. The roadmap puts that clean-up first and names who does it.
Automatic purchase orders come off the listIts risk outweighs its value, so a person keeps that decision. Saying so plainly is part of the job.
The deliverable
One page your board can read
The roadmap puts the ranked list in order of delivery, in a form your team can act on: what starts now, what follows, and what waits for something else to be true first.
Dependencies, written downEach later item names what it is waiting on and who is clearing the way, so nothing stalls without a reason.
A baseline before anything changesEach measure is typically taken before the pilot starts, so the week-six review compares like with like.
Controls agreed before anything connectsWhat runs on its own, what waits for a named person and what stays Off. When the build starts, those become the approval settings, and every request is recorded.
AI roadmapExample facilities business · one page
Sample
NowWeeks 1 to 6, the pilot
Follow up quotes that went quiet
- Owner
- Priya, operations
- Measure
- Days from quote to first follow-up. Baseline typically taken in week 1.
- Control
- Drafts run on their own. Sending waits for Priya.
NextAfter the pilot review
Shared inbox replies, then the weekly site report
- Owner
- Priya, then Tom, site supervisor
- Measure
- Drafts sent without changes. Baseline from the pilot.
- Control
- The report reads only. Replies wait for a person.
LaterOnce job codes are tidy
Match supplier invoices, then after-hours calls
- Owner
- Lena, accounts
- Depends on
- Job codes tidied in Simpro, by Lena’s team.
- Control
- Posting to Xero waits for Lena.
Fix first
Predicting which sites need reactive work. Revisit once the job history in Simpro is complete.
Not doing
Approving purchase orders automatically. Spending money stays a person’s decision.
Agreed by Sam, director, and Priya, operations
Agreed
Where it leads
Strategy is the first two of six phases. You decide on the rest.
In the usual shape, discovery and prioritising take about three weeks, and your timeline is confirmed in writing before they start. At the end, the first item on the roadmap is scoped as a pilot, and whether it goes ahead is your call.
- Weeks 1 to 2Discover
We sit with the people doing the work and write down what actually happens.
- Week 3Prioritise
Every opportunity ranked on value, effort and risk, with the pilot scoped.
- Weeks 4 to 5Connect
How SpeedOz reaches each of your systems, and who signs in how.
- Week 6Govern
Access starts closed, and a person on your side reviews it.
- Weeks 7 to 8Launch
Tested on realistic cases, then released to the people you nominate.
- Every monthImprove
Outcomes, exceptions and cost, typically read with you each month.
EvaluationFreeFive questions, read by a person. The reply says what looks worth ranking, and what doesn’t.
Discovery and roadmapFixed scopeQuoted in writing, with the time we need from your people, before anything starts.
Six-week pilotAUD $5,000One process, one team: the first item on the roadmap. Credited in full against setup if you continue.
Setup, then running itFrom AUD $5,000Then from AUD $900 a month for the whole organisation, not per seat.
Questions
Before we get started
Anything else, ask in the evaluation. A person answers within one business day.
With your goals and the work your people do every week, not with a tool. We shortlist the opportunities where the business value is clear and what it would take to deliver is known, then rank those.
Not necessarily. The assessment starts from the systems you already run. Often a connection or a targeted change does more than a replacement, and where a feature you already pay for does the job, the roadmap says so.
In the usual shape, discovery takes about two weeks and prioritising about one. Your timeline and the deliverables are confirmed in writing before the work starts.
Discovery runs on conversations and a workshop with the people closest to the work, plus whoever looks after the systems. The written scope states what we need from your people, in hours, before anything starts.
Then the roadmap says so, and says what would change the answer. Usually that is data that needs tidying or a process that needs settling first, and the roadmap names who would do it.
It is a good place to start. Discovery maps which AI apps are already in use and by whom, and the roadmap builds on them. Once anything connects to your systems, each app is approved per team by a named person.
Bring the list of ideas, or just the problem.
Tell us what you want to improve. A person reads it, replies within one business day and suggests a practical first step, even if that step isn’t us.