Starting ranges help you assess fit before a conversation. The final scope still follows the workflow, risk, and outcome.
For brand sites, content platforms, and digital journeys that need custom strategy, design, and development.
For internal tools, portals, and workflows designed around the way a team actually operates.
For retrieval, automation, and assisted decisions connected to real data, rules, and human review.
VND 1–3M for a workflow map, priorities, scope, delivery plan, and estimated investment.
Reference ranges exclude VAT, infrastructure, API usage, content production, and out-of-scope integrations.
Confirm scope, working rhythm, and decision owners.
Agree the experience, architecture, or prototype before engineering.
Test the real system with relevant data and users.
Deploy, document, and transfer operational ownership.
How many people, roles, decisions, exceptions, and operating rules the system must support.
The amount, quality, migration needs, permissions, and structure of the information involved.
The external tools, APIs, legacy systems, authentication, and reliability requirements we need to connect.
Security, privacy, evaluation, auditability, accessibility, and human oversight requirements.
After launch, support can cover maintenance, monitoring, continuous improvement, and new capability.