AX CONSULTING
AX consulting: a diagnosis decides where AI goes
The most expensive mistake in enterprise AI adoption is holding on to the wrong initiative for too long. We look at your workflows and data directly, narrow the candidates, and produce the evidence you need to decide.
- Organisations that have committed to AI but have not settled on a starting point
- Organisations receiving requests from the business with no way to prioritise them
- Organisations preparing an application for government support such as the AX voucher
This page covers only diagnosis and consulting, the first stage of the AX journey. The full journey including training, build, and operations is on the parent page.
See all four AX stagesHow the diagnosis runs
This is not a template to fill in. We look at how work actually flows and what state your data is in, then build something that runs so the decision rests on evidence.
- 01
Agree the scope and the criteria
We put in writing who gets interviewed, how far the data review goes, and what the diagnosis will be judged against. If this step is off, every step after it is off.
Involved: business owner, data access owner
- 02
Review workflows and data
We map where manual effort actually goes per team and what repeats, then look at what data you hold, in what form, and where. Including the exception handling that never made it into a document.
Involved: interviews with the people doing the work
- 03
Place the candidates and prioritise
Candidate initiatives are placed on two axes: business impact and implementation conditions. We separate what to touch first, what to revisit once the data is ready, and what not to do now.
Output: draft priority map
- 04
Build and demo a PoC on real data
We pick one initiative from the top of the list and make it run on your data. You see the screens and the results, then decide the next step.
Format: run in an environment that matches your security policy
- 05
Set out the roadmap and conditions
We define the scope and order of the build, and the data, access, and infrastructure conditions to prepare beforehand. If you are applying for government support, this document is the backbone of the application.
Output: build execution plan, validation plan
What you have when the diagnosis ends
It does not end with one deck. It ends in a form your next decision and your next build can use directly.
Initiative priority map
Candidate initiatives placed by business impact and implementation conditions. Which to do first, which to defer, and the reasoning behind each call.
PoC on real data, with a record of the demo
What ran on your data, and the screens it ran on. Written up in a form you can take straight into internal reporting and budget discussions.
Validation plan
The metrics and measurement method for what to check before and after adoption. Agreeing the criteria up front cuts down the arguments about results later.
Build execution plan
Scope and sequence, plus the data, access, and infrastructure to prepare. Written at a level your own engineering team can pick up and run with.
Deployment assessment
Whether cloud, VPC, or on-premise is viable given your data export policy and security review conditions, decided in advance.
Working with the AX voucher
The AX voucher is a Korean government programme that covers part of an adopting company's AI costs. Having the initiative and scope settled by a diagnosis makes the application considerably easier to prepare.
- 01
Check the announcement and eligibility
We go through the schedule and eligibility requirements together and pick a viable application window.
Prepare: company details, background to the adoption
- 02
Write up the initiative definition
We help move the initiative and scope from the diagnosis into the form the application requires.
Basis: priority map, validation plan
- 03
Confirm scope and quote
We fix the scope, deliverables, and schedule we will carry out as the supplying company and prepare the submission materials.
Output: execution plan, quote
- 04
Start once selected
We set a start date based on the outcome and prepare the evidence and reporting the programme requires during delivery.
Next: continues into the build stage
The support ratio, eligibility, and application window change with each year's announcement. If selected, up to 75% of the adopting company's cost is covered per the announcement, and the selection decision rests with the administering agency. Alphaca Labs supports the application and the delivery, and does not guarantee selection.
How we build the PoC
We do not build demos for the sake of demos. Only the minimum scope the adoption decision needs is made to actually run.
We narrow to one thing
Run several initiatives at once and you cannot tell what worked or why. We take the one the decision depends on and carry it all the way through.
Data stays inside your boundary
Material that cannot leave your organisation is handled in a working environment inside it. We confirm the security review conditions first, then decide the format.
We start from something already built
If an implementation exists for a similar industry, we start on top of it. Not building from the floor means you see results sooner.
Browse the industry PacksIf the data structure is the bottleneck, we start there
Often search and reasoning are blocked because terminology and relationships were never organised. In that case we propose candidate knowledge structures alongside.
See how Ontokit worksWe write down the limits too
We do not only show you what worked. What did not work, and what would have to change for it to work, goes into the document as it is.
자주 묻는 질문
Start with a diagnosis
Tell us what you are considering and where your organisation stands, and we will propose the scope and schedule first.