A staged engagement model
AgentTech separates fit, paid diagnosis, a single-workflow pilot, implementation, and ongoing operations so a large system is not promised while requirements remain ambiguous.
Start a fit checkConfirm that the problem is real, a decision-maker can participate, budget and timing are plausible, and AgentTech is a relevant fit.
Core deliverables
Timing
15–20 minutes
Reference
No fee
This stage does not include complete process design, architecture, or a formal estimate.
Use interviews, workflow mapping, and data inventory to identify cost, priority, and the smallest testable scope.
Core deliverables
Timing
About 1–2 weeks
Reference
Test range TWD 30,000–60,000
This is a market-validation reference range and varies by workflow complexity and number of interview roles.
Address one workflow tied directly to revenue or operating efficiency, with functional and operating metrics.
Core deliverables
Timing
About 4–8 weeks
Reference
Test range TWD 120,000–300,000
Concurrent pilots are capacity-limited. Out-of-scope requests use a formal change process.
Expand proven workflows into CRM, orders, members, bookings, permissions, reporting, AI, or third-party integration.
Core deliverables
Timing
Planned by scope
Reference
Reference TWD 300,000–1,200,000+
Formal pricing reflects business rules, integration, migration, security, and launch responsibility.
Carry responsibility for reliability, data, SEO, conversion, and workflow improvement—not only defect fixes.
Core deliverables
Timing
Minimum term by plan
Reference
Priced by responsibility and allowance
A monthly plan is not unlimited development. New features, third parties, and overage are defined separately.
Trust through operating discipline
Discovery, architecture, implementation, and critical acceptance stay in direct communication, supported by versions, previews, documents, and client-owned accounts.
Discovery, architecture, major changes, and critical acceptance are not lost across layers.
Source code, cloud environments, and third-party accounts remain within client control.
Versions, previews, documents, and decision records demonstrate progress.
Versioning, environment notes, deployment, and recovery documentation support continuity.
Capacity boundaries
FAQ
No. The first 15–20 minute fit check covers the problem, budget, timing, and potential fit. Deeper workflow analysis and recommendations begin with paid diagnosis.
No. The diagnosis should remain useful for internal decisions, comparing proposals, or handover. A pilot follows only if both sides fit.
When workflows and acceptance criteria are already clear, we can assess it. When several roles, tools, and exceptions are involved, diagnosis avoids hiding risk behind an inaccurate quote.
No. Each plan defines hours or tasks, response windows, emergencies, new-feature estimates, third-party cost, and overage.
Start with clarity
Bring your site, audience, core workflow, and desired outcome. We will identify whether SEO, conversion, CRM, orders, or automation is the strongest starting point.
