Plans
Quoted by scope and by where it runs
No price list, because no two customers connect the same systems or run on the same machines. You get a firm number after we have talked.
Start here
One process
Connect the single process that costs you the most hours.
- One process, one department
- One existing system, read-only
- Runs on our Taiwan nodes
- Full audit record
- An engineer of ours stays with it through rollout
For teams that want proof before scope.
Talk about thisMost common
Operations team
Booking, rostering, dispatch and customer messages, connected end to end.
- Several processes, shared across departments
- Connects booking, roster and dispatch back ends
- Our Taiwan nodes or a dedicated GPU
- Set who can see what, and who has to approve what
- Document and image recognition
Where service businesses, chains, clinics and fleets usually start.
Talk about thisManufacturing and regulated
Enterprise
Data never leaves the plant; the model runs on hardware you choose.
- Connects ERP, MES, drawings and specification libraries
- Reads drawings, compares specs, checks QA records
- Dedicated GPU, your own server room, or hybrid
- SSO, audit export, and a retention policy you set
- Named contact and a service level agreement
- A process walkthrough on site before anything is built
- NDA and data processing agreement available
Precision manufacturers, job shops, and anyone whose data cannot leave the building.
Talk about thisNot sure where to start?
- Still deciding if this is usefulOne process. Just the one.
- You know which problem to solveOperations team — connect the whole message flow at once
- Data cannot leave the companyEnterprise — your own server room or a dedicated GPU
- Not sure which process to pickBook a conversation and we will work it out with you
Common questions
The five questions we hear in every conversation
They come up in the first ten minutes, every time. The answers are written down here.
- Our IT team is one or two people. Who does the work?
- Our engineers do. We walk the process, connect the systems and stay with it through rollout; your IT grants access and checks that what we connected is right. It is why we start with a single process — we can finish that, so we can promise it.
- Our data cannot leave the plant. Does this still work?
- Yes. The software installs on your own servers and neither your data nor the model leaves your network. Hybrid works too: sensitive work stays on site and peak load borrows our nodes. The agent, the permissions and the audit trail are identical across all four deployment options.
- Could it change something in our systems by mistake?
- It cannot. In the first phase it holds read access only, so it has no write capability at all. Write access is granted later one action at a time, each behind an approval rule you set — it writes what it intends to do and leaves it there until you say yes.
- We tried AI before and it failed. What is different?
- Most failures come from handing staff a second system to learn, or from something that answers fluently but is not connected to the real data. Our agent lives inside the interface they already use, every answer links back to the screen it came from, and when it cannot answer it says so rather than inventing one.
- How long before we see anything?
- One process first, usually running within weeks. Prove one works, then widen — every rollout we have seen succeed went in that order.
Next step
Thirty minutes, three answersWhich process first, what it connects to, how soon it runs
Online or at your site. Nothing to prepare.