Workshop
$5k–$18kLeadership, functional or multi-team sessions connected to real work and a practical next step.
EXPLORE WORKSHOPSA practical guide to how Identify prices the work it can price honestly, what drives Production Build scope, and what Australian leadership teams should understand before approving an AI implementation budget.
There is no credible single price for “AI implementation”. The cost depends on the business workflow being changed and what it takes to make that workflow survive real data, real systems, real users and real exceptions.
Identify publishes fixed ranges where the work can be standardised. Production implementation is scoped after the operating constraints are understood.
Leadership, functional or multi-team sessions connected to real work and a practical next step.
EXPLORE WORKSHOPSMap the opportunity, prioritise the roadmap, define business cases and choose what should move into Build.
EXPLORE THE SPRINTScoped around the workflow, systems, data, governance, evaluation and integration required to move into production.
DISCUSS THE BUILDOngoing opportunity portfolio, optimisation, governance, adoption and the next useful deployment.
EXPLORE EMBEDDED PARTNERThe model is rarely the expensive part. The operating environment around it is what makes one implementation materially different from another.
How many steps, exceptions, approvals and user roles sit inside the current process.
Whether the workflow touches one source or several systems such as CRM, finance, document management or operational platforms.
How accessible, reliable and permissioned the required business context is.
Identity, access, privacy, vendor controls, auditability and human-accountability requirements.
How the business will test quality, accuracy, exceptions and safe failure before production.
Training, process redesign, manager ownership and whether the new workflow becomes the default way of working.
Whether the build is a one-off workflow or a reusable pattern intended to spread across teams, sites or functions.
Whether the business needs a contained build, post-launch optimisation or an ongoing embedded transformation partner.
A serious implementation should leave behind more than a working demo. The engagement scope should make ownership, documentation and operating responsibility explicit.
Know how the workflow performs now: time, volume, cost, service, quality or another operating measure.
Confirm the value case, systems, data, governance and implementation constraints before committing to Build.
Fund one production workflow with real users and exceptions rather than spreading budget across disconnected pilots.
Use measured evidence and reusable patterns to decide where the next dollar of AI investment should go.
Practical AI workflows, implementation lessons, Australian market signals, governance notes and upcoming Identify events for leadership teams.
The honest answer depends on the workflow, systems, data, security, governance and adoption requirements. Identify publishes Workshop pricing of $5k–$18k and AI Transformation Sprint pricing of $8k–$30k. Production Build and Embedded AI Partner work is scoped with the team because integration and operating complexity vary materially.
A workflow that reads one governed document set is materially different from a production system that touches CRM, finance, customer data, approvals and multiple user roles. Fixed pricing before those constraints are understood usually hides assumptions rather than reducing risk.
The biggest cost drivers are usually system integrations, data preparation, security and permissions, evaluation requirements, exception handling, number of user groups, governance, change management and the amount of reusable engineering required.
You should leave with clear documentation of the workflow, system design, operating ownership, governance, measurement approach and the agreed deliverables. Commercial and IP terms are confirmed in the engagement scope.
A contained workflow can move far faster than a multi-system program. Identify does not publish a blanket production timeline because the right duration depends on data access, integrations, testing, governance and adoption. The first step is to scope the workflow and baseline the current state.
Start by mapping the opportunity portfolio and choosing a workflow with clear friction, an accountable owner and a measurable baseline. That is the purpose of the AI Transformation Sprint and the AI Readiness Benchmark.