One-time implementation
- Discovery and process/data mapping
- Architecture and security controls
- Integrations, rules and model prompts
- Happy-path, failure-path and acceptance testing
- Training, account handover, documentation and rollback runbook

Three transparent planning examples, from one focused workflow to an operational system, with implementation and monthly costs separated.
Request a workflow estimateiReadCustomer planning examples range from THB 70,000–105,000 for one focused workflow, THB 126,000–210,000 for multiple integrations, and start at THB 252,000 for an operational system with stronger monitoring, staging, recovery and human-review paths. These ranges use our published THB 7,000 per man-day rate; they are not market averages or fixed quotes.
Implementation is not the entire TCO. Add model and API usage, cloud and databases, monitoring, maintenance, and the people who review exceptions. This page makes the first-year formula and every illustrative assumption visible so you can replace them with your organization’s data.
Three workflow sizes
Scope from risk, integration count and the path used when automation cannot decide—not screen count. Every example below is a planning scenario with disclosed assumptions.
| Size | Best fit | Illustrative scope | Effort | One-time implementation | Monthly operating cost | First-year TCO |
|---|---|---|---|---|---|---|
| Focused workflow | One repetitive process with low-to-moderate risk |
| 12 man-days | THB 84,000 | THB 7,900 | THB 178,800 |
| Connected automation | Multi-step data flow across teams with staging |
| 24 man-days | THB 168,000 | THB 19,000 | THB 396,000 |
| Operational system | High-volume or customer-facing critical processes |
| 48 man-days | THB 336,000 | THB 48,500 | THB 918,000 |
First-year TCO = one-time implementation + (monthly operating cost × 12). The examples exclude VAT where applicable, licenses already held, scope changes and 24/7 SLAs.
Complete cost model
A comparable proposal should separate these eight components instead of hiding everything inside “bot development,” so the buyer can see the obligations after go-live.
| Component | Timing | What it covers | How to estimate it |
|---|---|---|---|
| Discovery | One-time | Workflow map, data owners, volume, risk, acceptance criteria and failure paths | Workshops plus the time needed to validate data and scope |
| Integrations and build | One-time | APIs, webhooks, mapping, authentication, retries, idempotency and business rules | System count × API readiness × data complexity |
| Model / API usage | Recurring | LLM, OCR, speech, search, messaging or usage-priced third-party APIs | Transactions × usage per transaction × current provider rate |
| Infrastructure | Recurring | Runtime, database, storage, queue, network, backups and environments | Average/peak load + retention + recovery requirements |
| Monitoring | Recurring | Logs, metrics, alerts, traces, dashboards and history retention | Log volume × retention plus tooling and alert-response time |
| Maintenance | Recurring | Dependency/API changes, bug fixes, prompt/rule tuning, backup checks and release support | Reserved man-days per month or an agreed support scope |
| Exception handling | One-time + recurring | Retries, dead-letter queue, fallback, rework and ownership when automation stops | Exception rate × handling time × loaded labor cost |
| Human review | Recurring | Approvals, quality sampling, escalation and decisions AI should not make alone | Reviewed cases × minutes per case × loaded hourly cost |
Separate CapEx and OpEx
Implementation makes a workflow ready. Recurring spending keeps it running, observed and owned when exceptions occur. Both belong in the same business case.
Auditable planning formula
First-year TCO = implementation + 12 × (APIs + infrastructure + monitoring + maintenance + exception/human review)
These values expose the arithmetic. They are not a provider-price guarantee or a customer outcome. Replace them with live quotations and usage data before making an investment decision.
| Monthly item | Focused | Connected | Operational |
|---|---|---|---|
| Model/API usage | THB 1,000 | THB 4,000 | THB 12,000 |
| Infrastructure | THB 1,500 | THB 3,000 | THB 8,000 |
| Monitoring | THB 500 | THB 1,500 | THB 4,000 |
| Maintenance at THB 7,000/man-day | 0.5 day = THB 3,500 | 1 day = THB 7,000 | 2 days = THB 14,000 |
| Exception + review at THB 350/hour | 4 hr = THB 1,400 | 10 hr = THB 3,500 | 30 hr = THB 10,500 |
| Monthly total | THB 7,900 | THB 19,000 | THB 48,500 |
The THB 350/hour loaded labor cost is an example for human-review time, not a Thai wage benchmark. The 12/24/48 man-day values are midpoint scenarios inside planning bands, not guaranteed delivery durations.
Before requesting a quote
If these are unknown, use a small discovery phase before committing to a full build.
Name its trigger, input, output, owner and reason to automate now.
List systems, API documentation, account owners, authentication and rate limits.
Capture transactions per day/month, current handling time, rework and loaded hourly cost.
Decide what retries, what stops, who approves and which decisions AI must not make alone.
Set task completion, error, latency, unit cost, review-rate and rollback thresholds before build.
We do not present changeable platform fees as a permanent “market price.” Verify quotations and usage tiers directly when approving the SOW.
Review production workflow, AI and integration scope.
Compare n8n Cloud, self-hosting and queue mode with transparent pricing.
Use your labor, coverage, review and cost inputs to estimate payback.
Verify the THB 7,000/man-day rate and estimating approach.
Share a workflow and integration list for an auditable scope.
Direct answers for teams preparing a budget or comparing vendors
iReadCustomer planning ranges start at THB 70,000–105,000 for one workflow, based on THB 7,000/man-day. Multi-integration work is THB 126,000–210,000 and operational systems start at THB 252,000. These are initial planning bands, not market averages or fixed quotes.
The system still consumes model/API, hosting, database, monitoring and maintenance resources, while people handle exceptions each month. Comparing development fees alone hides the cost after go-live.
Not automatically. The customer should own provider accounts and pay actual usage. The SOW should name the model, volume assumption, spending limit and cost owner.
No. n8n can reduce effort for supported workflows and connectors, but cost still depends on API readiness, data mapping, scale, security, error handling and operations. Some systems use n8n for orchestration and custom code for critical parts.
Yes. AI-assisted workflows often need people to review riskier cases. This guide models that time monthly; omitting review and rework can overstate ROI.
Choose one workflow, document source and destination systems, volume, labor, exceptions and acceptance criteria, then run discovery to separate known scope, experiments and exclusions.
Send one workflow, monthly volume, connected systems and the human-review path. We will respond with explicit assumptions, scope and arithmetic you can inspect.
Request an AI automation estimate