AX Consulting & Build — From Assessment to Adoption
AX (AI Transformation) is the work of redesigning a company's workflows and decision-making structure around AI, and embedding that design in its actual systems and day-to-day operations. TECH2030 runs this in four stages — assess → design → build (pilot) → operate & embed — and the assess and design stages are the AX consulting part. Every stage leaves documented deliverables such as a task inventory, a transformation roadmap and an architecture design.
- 4
- StepsAssess · Design · Build (pilot) · Operate & embed
- KRW 3M
- Starting costAssess & design (AX consulting)
- 7
- Sub-services
- 17
- Related insights
What is AX (AI transformation)?
AX is not the adoption of a single tool. It is the work of finding where — among repetitive tasks, documents, inquiries, and decisions — putting AI in changes the outcome, and embedding LLMs, retrieval (RAG), automation, and agents there as part of the actual workflow. The result should show up not as a new screen but as a changed way of working.
That is why the success of AX depends less on model selection than on three things: which tasks are targeted, how well organized the data for those tasks is, and whether there is an operating structure that keeps the organization using what was built.
How DX and AX differ
If DX (digital transformation) moved paper and manual work into systems and data, AX redesigns work so that AI takes on judgment, generation, and response on top of the data and systems built up along the way. Some degree of DX is needed before AX can begin, but there is no need to wait for perfect DX — it can start with a single task.
| DX (digital transformation) | AX (AI transformation) | |
|---|---|---|
| Goal | Move work into systems and data | Redesign work so AI handles judgment, generation, and response |
| Core assets | Systems, databases | Organized documents and data, business rules, evaluation criteria |
| Typical outputs | ERP, groupware, portals | Internal knowledge search, document automation, AI agents, response automation |
| Success conditions | Process standardization | Target task selection, data quality, operations and adoption structure |
| Failure pattern | The system exists but nobody uses it | The demo works but never makes it into day-to-day work |
Process — assess → design → build (pilot) → operate & embed
The four stages run in order, and each stage's deliverables become the input to the next. Assessment and design can be contracted on their own as AX consulting, so you can start with consulting and decide on the build after reviewing the deliverables.
STEP 1Assess
Assess & design 2–6 weeksThrough frontline interviews and observation of work, we inventory repetitive and bottleneck tasks, evaluate each task's data readiness and expected impact, and set priorities.
- task inventory
- priority matrix
- data readiness assessment
STEP 2Design
Assess & design 2–6 weeksFor the top-priority tasks, we set the transformation roadmap and architecture (models, retrieval, integrations, permissions, security), and agree in advance on the evaluation criteria that will determine success.
- transformation roadmap
- architecture design document
- evaluation criteria
STEP 3Build (pilot)
4–8 weeksWe build one target task with real data and real users and validate it in the production environment. Based on the evaluation criteria, we decide whether to expand, revise, or stop.
- pilot system
- evaluation results
- rollout plan
STEP 4Operate & embed
MonthlyWe widen the scope of internal adoption and embed it in the organization by setting how it is used, the rules, and who owns it. We keep improving against monitoring, cost, and quality metrics.
- security and governance guide
- training materials
- operations dashboard
The solid part is the minimum and the faded part runs to the maximum. Based on one task; the same durations as the cost table below.
| Assess & design (AX consulting) | 2–6 weeks |
|---|---|
| Build (pilot) — one task | 4–8 weeks |
| Scale-out build — production rollout & integration | Depends on scope |
| Operate & embed | Monthly |
Common types of adoption
- Internal knowledge search and Q&A (RAG)a system that searches policies, manuals, contracts, and technical documents and answers with sources. Permission-based access control is essential.
- Document automationautomating document work with a fixed format, such as reports, summaries, translation, classification, and extraction.
- AI agentsperforming multi-step work (look up → judge → execute) on your behalf within rules and approval procedures.
- Customer response automationautomating inquiry classification, first-line replies, and conversation summaries, and defining the criteria for handing off to a person.
- Data analysis assistantask questions of your data in natural language and get visualizations and summaries back.
AX consulting cost — estimated ranges by stage
These are estimated ranges for a single task, excluding VAT. We confirm the final amount stage by stage after reviewing company size and data readiness. Companies with 300 or more employees, or programs covering several tasks at once, are quoted separately.
| Under 50 employees | 50–300 employees | |
|---|---|---|
| Assess & design (AX consulting) | KRW 3M~KRW 10M | KRW 15M~KRW 40M |
| Build (pilot) — one task | KRW 7M~KRW 20M | KRW 20M~KRW 60M |
| Scale-out build — production rollout & integration | KRW 10M~KRW 30M | KRW 30M~KRW 100M |
| Stage | Typical duration | Under 50 employees | 50–300 employees |
|---|---|---|---|
| Assess & design (AX consulting) | 2–6 weeks | KRW 3M–10M | KRW 15M–40M |
| Build (pilot) — one task | 4–8 weeks | KRW 7M–20M | KRW 20M–60M |
| Scale-out build — production rollout & integration | Depends on scope | KRW 10M–30M | KRW 30M–100M |
| Operate & embed | Monthly | KRW 1M–2M per month | KRW 2M–5M per month |
What changes the amount
- Data readiness — if records are scattered across spreadsheets, paper or personal PCs, a separate data-preparation stage comes before the build.
- Data volume — the longer records have been accumulated and the more documents and systems there are, the larger the search and integration build.
- Model API fees and infrastructure such as GPUs and servers are not included above and are billed separately by usage.
- Pairing the work with government or local AI adoption support programs can reduce the company's share. Support limits and co-payment ratios differ by program.
What drives timeline and cost
Within the ranges above, the following variables set the actual timeline and amount.
- Scope and number of target tasks — a pilot on one task and a company-wide rollout are different projects.
- Data readiness — whether document formats are unified, the permission structure, and the share of duplicate or outdated documents.
- Number of internal systems to integrate — groupware, ERP, CRM, file storage, and so on.
- Security requirements — on-premises or VPC setup, restrictions on data leaving your environment, logging and audit requirements.
- Extent of adoption support — number of people to train, how operations are handed over, and whether there is a continuous improvement contract.
Security and governance
Because AX handles the company's documents and data, we set the security boundary first, in the design stage. Before building, we agree in writing on which data may leave your environment and how far, whether model calls are processed inside your own infrastructure (on-premises or VPC) or through external APIs, who may access which documents, and how logs of generated output are kept.
In the operations stage, we set usage rules (what may be entered, where the output may be used) and owners, distribute them to the organization, and include them in adoption training.
Ten things to confirm before adopting
- Can each team name the repetitive tasks that consume the most time?
- Do the inputs and outputs of those tasks exist as documents or data?
- Do you know where the documents are scattered and who can access them?
- Can you define the point where a person checks the output when the AI gets it wrong?
- Can you decide how success will be judged (processing time, accuracy, rework rate, etc.)?
- Is there a list of data that must not leave the company?
- Can you secure the owners and permissions for the internal systems that need integration?
- Is a frontline owner designated to actually use the pilot?
- Is there someone to own operations and improvement after adoption?
- Have you checked the requirements of government and municipal AI adoption support programs?
Sub-services







Latest on AX (AI Transformation)
MoreFrequently asked questions
In what order does an AX program proceed?
Assessment confirms target tasks and data; design fixes the roadmap and architecture; a pilot is built and validated in real work; and it ends with rollout, in-house adoption, and training. Each stage leaves a deliverable.
How much does AX consulting cost?
For a single task, assessment and design (AX consulting) runs KRW 3M–10M for companies under 50 employees and KRW 15M–40M for companies with 50–300 employees, excluding VAT. The pilot build and operations are separate, and we quote each stage after reviewing data readiness and the number of systems to integrate.
Can we engage you for AX consulting only?
Yes. You can contract assessment and design first, receive the task inventory, priority matrix, transformation roadmap and architecture design, and then decide whether to proceed with the build.
Can small and mid-sized companies do AX?
Yes. A pilot on a single task is a valid starting point. We also review options to combine it with government AI adoption support programs.
Can we start even if our data is not organized?
Yes. In the assessment stage we evaluate data readiness and include the scope that needs organizing in the pilot plan. The usual order is to start with the tasks whose data is already organized.
Can everything be processed on our own infrastructure instead of external APIs?
Yes. On-premises or VPC setup and restrictions on data leaving your environment are set as security requirements in the design stage, and we select a model and infrastructure combination that meets them.
Can you also run operations after the build?
Yes. In the operate & embed stage we continue monitoring and improvement, and we also plan the handover to your internal team.