AI Implementation Checklist: A One-Page Guide for Australian SMBs

If you only have time to do one thing before starting an AI project, work through this checklist. It is the same six-section checklist we use at Waymouth Tech with new Australian SMB clients. Designed to fit on a page, answer in plain English, and force the awkward conversations early — when they are cheap.

Section 1: Readiness

Tick these before you bother scoping.

• A single executive sponsor is named and accountable (usually COO, CIO or ops director).
• A delivery owner is named (single person, not a committee).
• Budget envelope agreed for the next 12 months (planning range, not a hard number).
• Board or leadership team has agreed AI implementation is a current priority, not a "someday" item.
• At least one repetitive, high-volume workflow is a candidate (you can name it in a sentence).
• Willingness to run a 4–8 week pilot before larger commitments.
• No expectation of magic — leadership understands AI augments workflows, not replaces them wholesale.

If any are missing, fix those first. AI implementation by committee, or without a budget, or with unrealistic expectations, almost always stalls.

Section 2: Scope

The scope conversation is where most projects are won or lost.

• One specific workflow is named (e.g. "first-pass quote drafting for inbound enquiries").
• Trigger, inputs, steps, decisions and outputs of the workflow are documented.
• Volume is known (cases per week).
• Time per case today is measured, not guessed.
• At least one success metric is defined (cycle time, cost per case, throughput, error rate).
• A target number is set (e.g. "reduce cycle time from 3 days to 4 hours").
• Out-of-scope items are written down explicitly to prevent drift.

For more on framing scope, see how to start AI implementation in your business. For a fuller plan, see AI implementation roadmap template.

Section 3: Data

The single biggest source of slippage in AI projects. Get ahead of it.

• All required data sources are listed.
• Each source has a known owner inside the business.
• Access is technically feasible (API, export, or supported integration).
• Data freshness is known and acceptable.
• Quality is assessed honestly — clean, messy or unusable.
• Sensitive fields are identified (PII, health, financial, legal).
• Data residency requirements are documented (AU-region by default unless there is a reason not to).
• Retention requirements are documented for inputs, outputs and logs.
• A "minimum data" version of the workflow is defined, so you can build something useful even if some data is not yet accessible.

If you cannot tick the data box, do not skip ahead. Fix it. AI cannot reason its way around bad or missing data.

Section 4: Build

The technical-readiness portion.

• Architecture is sketched on one page (data flow, model usage, integrations, user interface).
• Foundation model choice is justified (which provider, which model, why).
• AU-region endpoints are used where available.
• Zero-retention model configuration is in place where supported.
• Identity, access and audit logging plan is documented.
• Integration list is defined with effort estimates.
• Build team is named with capacity confirmed.
• Fixed-scope pilot is agreed with timeline and acceptance criteria.

Resist over-engineering. The first version should be the smallest thing that solves the workflow end-to-end.

Section 5: Evaluation

The piece most teams skip and most regret skipping.

• A test set of 30–100 real cases with known good outputs is collected.
• Acceptance thresholds are defined (e.g. ≥85% of cases acceptable to a reviewer).
• Automated evaluations run on every change to prompt, model or data source.
• A weekly failure-case review is scheduled with the workflow owners.
• A rollback path is defined and tested.
• Monitoring and alerting are in place for output quality, latency and cost.

Without this, you will not know when the system has regressed until users complain — by which point trust is gone.

Section 6: Operations

The bit that determines whether the system is still working in six months.

• On-call coverage is defined (internal or partner).
• A runbook covers common issues, escalation and rollback.
• Prompt and configuration are version-controlled in a repo you own.
• At least one internal person can make minor updates without external help.
• A monthly cost review covers model usage, cloud and partner fees.
• A quarterly review covers business outcomes against the success metric.
• Risk register aligned with the Voluntary AI Safety Standard is kept current.
• Change management plan covers training, internal champions and feedback channels.

Why this matters in Melbourne and Australia

A few items on this checklist are uniquely Australian:

• Voluntary AI Safety Standard alignment. The ten guardrails (accountability, risk management, human oversight, data governance, testing and evaluation, transparency, contestability, record-keeping, stakeholder engagement, compliance) are now a de facto expectation in tenders, especially for government and regulated sectors. Even if you sell only to SMBs today, aligning early is cheap insurance.
• Privacy Act and APPs. The current and proposed reforms to the Privacy Act change what counts as reasonable handling of personal data through AI systems. Document what data leaves Australia, how long it is retained, and your basis for using it.
• Sector frameworks. APRA's CPS 230 and CPS 234 for financial services, My Health Record for health, and education and legal sectoral frameworks all overlay additional requirements. Check yours and bake the controls in.

These are not bureaucratic checkboxes. They are the same controls that prevent the avoidable incidents — and they are far cheaper to design in than to retrofit.

How to use the checklist

There are three ways we see Melbourne SMBs use this checklist:

1. Self-assessment before talking to anyone. Run through it internally. Where you cannot tick, that is your homework.
2. Pre-procurement. Send the checklist to potential partners and ask how they would help close each gap. The quality of the answer tells you a lot about who you are dealing with.
3. Mid-project audit. Halfway through a project, run the checklist. Gaps are signs of where the project is likely to slip in production.

You can find a fuller treatment of partner selection at choosing an AI implementation partner, and the broader landscape at AI implementation consulting Melbourne.

What to do next

Print the checklist. Fill it in honestly. Anywhere you cannot tick a box, that is the next action. Most stuck AI projects we are asked to rescue would never have stuck if their teams had run this six-section sweep before signing.