intesol.kr
Free diagnostic
Home / Services / AI Workflow Automation
SERVICE 02 Running in-house

Repetitive work goes
over to the system

Reporting, research, email drafts, data processing — automated with the Claude API. Built in four to eight weeks and handed over with the documentation. A transfer of ownership, not an outsourced retainer.

PROGRAM SPEC
Build duration 4–8 weeks
Time to start Within 1 week of signing
Tasks in scope 3–5
Outcome System + documentation
Code ownership 100% client
Project cost ₩8M–24M
01 · If you see these signs

The problem is not headcount —
it is how the work is structured

SIGNAL 01
The same document gets rebuilt every week
The format is fixed and only the content changes. There is less reason than anywhere else for a person to sit on it, and it reliably eats hours every week.
SIGNAL 02
Someone retypes it and gets it wrong
If you are filling the gaps between systems by hand, errors are a matter of probability. A layer of reviewers gets added and the cost doubles.
SIGNAL 03
It stops when that one person is away
The work lives in one person head, not in a document. A side effect of automating it is that it finally gets written down.
02 · How the 8 weeks run

Starting with the most expensive work,
we take it off your hands

We do not automate everything. We measure time spent and error rate first, then attach automation only to the three to five with the biggest return.

PHASE 01
Weeks 1–2
Measurement
→ Collect task logs, interview the people doing the work
→ Time per item and error rate measured
→ Rank automation priority by hours recovered
PHASE 02
Weeks 3–4
Design
→ Workflow design with human review points
→ Fix data access rights and the security perimeter
→ Define prompts and validation rules
PHASE 03
Weeks 5–7
Build
→ Claude API pipeline implementation
→ Two weeks running in parallel with the current process
→ Side-by-side review of real output
PHASE 04
Week 8
Handover
→ Re-measure error rate, compare before and after
→ Write the operations and incident manual
→ Two training sessions and account handover
03 · Deliverables

After the contract ends
What remains

Both the code and the accounts are yours. Take Intesol out and the system keeps running.

✓ Task measurement report (time and error rate)
✓ Full source code for the automation pipeline
✓ Prompt and validation rule documentation
✓ Operations and incident manual
✓ Two training sessions
✓ 30 days of stabilization support after handover
CASE #0 · INTESOL.KR
The first client of this service
was us
Report publishing, conversation archives, intelligence pipelines — every internal operation at Intesol runs this way. It is why two people are enough.
Workflow baseline Time and errors measured
Automation check Before and after compared
Human review Placed at risk points
Operations handover Manual and training
04 · Questions we get

Before you sign
What you get to check

Does our data leave the building?
Only the minimum data an API call needs is sent, configured so none of it is used for training. Which field goes where is fixed in writing at the design stage, in a form you can hand straight to your security reviewers.
Which tasks are a good fit?
Work whose criteria you can write down, that repeats at least weekly, and whose output has a fixed format. Decision work where the criteria change every time is better left out.
Will it integrate with our existing systems?
If a system has an API or a file export, we integrate with it. Closed internal systems get worked around with intermediate files, and that call is settled during the week 1–2 measurement stage.
How does maintenance work?
Intesol covers the first 30 days after handover. After that the manual is enough for your team to run it, and you can put a separate monthly check-in in place if you want one.
No sales call
We measure which work qualifies
before anything else.
Free workflow audit — we measure the time and error rate on three to five repetitive tasks and calculate the hours automation gives back.