1. Where Machining Shops Actually Stand on AI
Taiwan has roughly 1,100 machine tool and key component makers, over 95% of them SMEs, with 2025 output around NT$89.89 billion, down about 10% year on year (Taiwan Association of Machinery Industry). Labour is equally tight: the Ministry of Labor vacancy survey (end of March 2025) counted 92,000 manufacturing vacancies, 33.5% of the national total and the largest of any sector, with machine operator roles taking 4.1 months on average to fill. Yet III MIC research shows only 28% of manufacturers have implemented AI, adopters spent an average of NT$2.09 million per company in 2024, and 80% are blocked by data quality. Fragmented orders plus slow quoting is where AI produces measurable results fastest.
2. Three Use Cases Worth Doing First
- Inquiry triage and first response. Extract material, spec, quantity and lead time from email, web forms and LINE, sort into prototype, production, price shopping and after-sales, and send a substantive reply within 10 minutes. Harvard Business Review research found firms replying within an hour are 7 times more likely to qualify a lead.
- Quote drafting engine. Match against similar part numbers, material grades, machining passes and finishing, then output a draft with cost breakdown so the plant manager reviews only the deltas.
- Multilingual technical Q&A. Turn manuals, tolerance tables and spare part numbers into a RAG knowledge base so overseas agents can ask in Chinese, English or Japanese without routing to engineering.
3. Two Real SME Deployments
Case A: a 22-person precision metal shop in Taichung. Each quote used to consume over an hour from both the salesperson and the plant manager, and complex specs ran from morning until closing. They structured two years of quotes for SUS304 and A6061, built a rule table covering material unit price, machining hours, anodising and laser engraving, and now generate a first version of a complex quote in about 90 seconds. The pitfall: feeding only PDF quotes left the model unable to learn why a job carried a 15% premium, and accuracy stabilised only after 80 annotated reason fields were added.
Case B: a linear guideway exporter in southern Taiwan (about 45 staff, anonymised). The pain was an overflowing inbox of overseas inquiries. They used n8n to connect email and a LINE Official Account for auto-classification, and drafted first replies in Chinese, English and Japanese. By month three, inquiries answered within one hour rose from 25% to 86% and sales saved about 9 hours a week. The lesson: letting the AI send directly produced one wrong lead time commitment, after which they moved to AI drafts with one-click human send.
4. Recommended Tool Stack
- Reasoning layer. Claude API at Sonnet tier for long spec documents and multilingual drafting, with classification downgraded to a smaller model; splitting the tiers typically cuts token spend by over 60%.
- Orchestration layer. n8n (Cloud Starter around US$24 per month, or self-hosted) connects email, LINE and ERP and handles retries — better than Zapier for shops needing on-premise deployment.
- Retrieval layer. LlamaIndex or LangChain for chunking, with vectors in pgvector or Qdrant so answers cite their source.
- Data layer. Keep pricing rules in PostgreSQL or Google Sheets so the plant manager edits unit prices himself. An SME shop has no MLOps team; if the stack cannot be maintained in a spreadsheet and debugged in a browser, it will not survive year one.
5. ROI Model (Shop Issuing 60 Quotes per Month)
| Item | Amount / Volume |
|---|---|
| One-off build (triage + quote drafting + document RAG) | NT$450,000 |
| Monthly LLM API | NT$3,000–6,000 |
| Monthly n8n + vector store + hosting | about NT$2,500 |
| Quoting hours before | 60 × 3.5 hrs = 210 hrs |
| Quoting hours after | 60 × 1.2 hrs = 72 hrs |
| Monthly labour saved (NT$450/hr) | about NT$62,000 |
| Net monthly benefit | about NT$54,000 |
| Static payback | about 8.3 months |
Revenue effects are excluded. With 60 inquiries a month and NT$40,000 average gross profit per won job, just 2 extra percentage points of win rate add roughly NT$570,000 a year. Measure your baseline before go-live, or the payback cannot be reconciled.
6. Rollout Phases 1 to 4 (About 18 Weeks)
- Phase 1, inventory and data prep (3–4 weeks). Audit two years of quotes and inquiry channels, annotate 80–100 records, fix success metrics and a baseline.
- Phase 2, single-scenario PoC (4 weeks). Triage and first-reply drafting only, in shadow mode against the live inbox, nothing sent externally.
- Phase 3, pilot (6 weeks). Add quote drafting and document Q&A, sales sends with one click, review error cases weekly and refill the rule table.
- Phase 4, launch and expansion (4 weeks). ERP write-back, monitoring and spend caps, and train an in-house owner to maintain the rules.
7. Failure Modes and How to Avoid Them
- Knowledge trapped in veteran heads. Unwritten pricing logic leaves the model guessing. Fix: annotate 80 records with an explicit reason field.
- Misaligned expectations. Assuming fully autonomous quoting. Fix: put it in the contract — AI drafts, humans approve; the goal is fewer hours, not fewer people.
- Drawing leakage concerns. Fix: an enterprise tier that does not train on customer data, a signed DPA, masked customer names and drawing numbers, on-premise models for sensitive parts.
- No baseline. Six months in nobody can say how much was saved. Fix: in Phase 1, measure hours per quote, median response time and win rate.
- PoC that never ships. Without ERP write-back staff copy-paste manually and abandon it. Fix: design the write-back path on day one.
8. Where AI Does Not Belong
- First-run prototypes of novel geometries with no comparable history in-house.
- Final release decisions in aerospace or medical devices carrying signed compliance liability.
- Engineering calls that depend on on-site measurement, fixture design and trial-cut feel.
- Strategic concessions to long-standing customers, where relationships dominate.
9. What ScriptWalker Delivers, and What It Costs
We build AI process integration for small and mid-sized factories. No hardware, no machine lock-in:
- AI inquiry triage plus multilingual first reply — from NT$120,000 (about 4 weeks)
- AI quote drafting engine — from NT$280,000 (about 8 weeks, rule table included)
- Multilingual RAG Q&A over technical documents — from NT$180,000
- Pre-project diagnostic (2 weeks) — NT$35,000, fully credited if you proceed
- Monthly operations — from NT$6,000 (API usage billed transparently)
10. FAQ
Q1: Our quoting relies entirely on veteran judgement. Can we still adopt AI?
Yes, but budget 3–4 weeks to turn that judgement into rules: pull 80–100 historical quotes and have your veteran add a reason field explaining how each number was reached. The model learns from that annotation, not from thin air. Skip it and accuracy rarely survives two months.
Q2: Will customer drawings leak if we send them to an AI?
Use an enterprise API tier contractually barred from training on customer data, and mask customer names and drawing numbers at the system layer. For defence or exclusive-project parts, run an on-premise open model — pricier, but data never leaves the plant.
Q3: What is a realistic minimum budget?
Triage plus multilingual first replies goes live for around NT$120,000, with NT$3,000–5,000 a month to run. It is the cheapest way to test whether your team will actually use the system. Run it three months, then decide on the quote engine.
Q4: How soon do results show?
Response-speed metrics move in weeks 6–8. Quoting hours stabilise late in the pilot, after the rule table has been revised two or three times. Overall payback under this model is roughly 8 months, depending on quote volume and labour cost.
11. Decision Checklist and Next Step
- ☐ Can anyone state our exact monthly inquiry and quote volume?
- ☐ How many hours does one quote take from receipt to send?
- ☐ What share of inquiries do we answer within one hour?
- ☐ Are two years of quotes stored in one system or folder?
- ☐ Can someone verbalise our markup and discount logic as rules?
- ☐ Do overseas inquiries get delayed by language or time zones?
- ☐ Does our ERP expose an API or a structured export?
- ☐ Is there an internal owner willing to spend 2 hours a week on the rule table?
- ☐ Do customer contracts prohibit putting data in the cloud?
Fewer than 5 checks means you need better base data before you buy AI. Bring your answers to a 30-minute call and we will say plainly whether it is worth doing:
- Email: [email protected]
- Phone: 0916-224-047
- LINE: @ufv9089p