Karabox
In operation
Bookings and operations in one place
A system supporting bookings, customer data and operations across multiple service locations.
- Booking workflow
- Operations dashboard
- Customer data
Custom software development
When information lives across spreadsheets and staff move it manually between steps, Cyno helps build software around the actual workflow. Start with the most important process, review working versions and agree acceptance criteria before expanding.
Review where data originates and is used, then design shared flows, permissions and connections between separate steps.
Bring statuses, responsibilities and transition rules into a system that gives the team a shared view of the workflow.
Assess configuration and integration options before deciding which functions need custom development.
The proposal turns these work areas into agreed deliverables, responsibilities and acceptance criteria for your project.
Clarify user roles, business rules, inputs and exceptions. Agree how each feature will be checked.
Present screens and task journeys so the people doing the work can give feedback before development.
Build agreed features, permissions and integrations. Scope, reconcile and test data migration before operational use.
Test business scenarios with the responsible users, provide guidance and hand over documentation with the support arrangement.
Explore the scope and implementation approach in projects Cyno has introduced.
In operation
Bookings and operations in one place
A system supporting bookings, customer data and operations across multiple service locations.
In development
ERP around the production workflow
A modular system in development for orders, inventory and operational reporting.
Scope & investment
Start with an important workflow, define the deliverables and phase your investment. Cyno separates discovery, development and operating costs so you can decide what to build first.
Define the problem
Indicative budget
10 – 20 million
VND / discovery engagement
For a known business problem where features, cost and delivery approach still need definition.
1–2 weeks once business inputs are available
Request a discovery proposalFor one core workflow
Indicative budget
60 – 120 million
VND / development phase
For solving a core workflow and gathering user feedback before expanding.
8–12 weeks after specifications are agreed
Discuss your first releaseFor an existing system
Indicative budget
40 – 100 million
VND / expansion phase
For adding management tools, reports, data connections or automation to an existing system.
4–8 weeks after the system review
Review an existing systemIndicative prices apply to the scope described. Your quote follows clarification of workflows, data, integrations and acceptance criteria. Applicable taxes, hosting, licences, third-party services and additional work are specified in the quote.
On smaller screens, swipe across to see all three options. You can also focus the table and use the arrow keys.
| Scope | Discovery & specifications | First software release | Expansion & integration |
|---|---|---|---|
| Business need | Define features and cost before investing | Build a first release for use and feedback | Extend or connect an existing system |
| Platform | Assess existing tools, integration or custom development | One responsive web app for one business | Existing platform, subject to review |
| Business workflow | Review one core workflow and its exceptions | Implement one specified core workflow | One agreed feature group or API connection |
| Roles & permissions | Define up to 3 role groups | Up to 3 fixed roles; server-side permission checks | Agree the permission matrix for affected work |
| Screens | Prototype of 5–8 main screens | 5–8 main business screens as specified | Screen count and flows defined in the quote |
| Reports | Define the measures and report templates needed | Up to 2 agreed report templates | Agreed additions using identified data |
| Initial data | Review anonymised samples and propose an import approach | One agreed CSV format; row count and import runs specified | Define sync direction, volume and reconciliation criteria |
| Integrations | Assess feasibility and dependencies; no implementation | Third-party integrations quoted separately | One documented API with a test environment, if integration is selected |
| Testing | Test scenarios and acceptance criteria | Scoped workflow, permission, data and recovery checks | New functionality, reconciliation and regression checks |
| Handover | Specifications, prototype and phased estimates | Software, source code and documentation as agreed | Changed source, documentation and deployment record |
| Warranty & support | Clarification of in-scope documentation | Defect warranty under agreed terms; operations support separate | Warranty for the changed scope under agreed terms |
| Outside the scope | Software development and deployment | Native mobile apps, multiple workflows, full ERP or complex integrations | A full rebuild, multiple connections or an API that is not ready |
Screen counts indicate scale; pricing also depends on business rules, exceptions, load and testing. Concurrent users, imports, revision rounds and responsibilities are specified before development. Third-party components retain their respective licence terms.
When discovery and development are quoted separately, the indicative total is VND 70–140 million. Existing equivalent specifications are reviewed for gaps; discovery work is not billed twice. Expansion is a separate phase when needed.
Separate warranty defect fixes, operational support and new development. Hosting, domains, licences and usage-based API/SMS/AI costs are budgeted separately. Warranty duration, support hours and payment milestones are agreed in the quote.
New requests are assessed for cost, data and schedule impacts before implementation. Multi-department systems, ERP/MES, native mobile apps and complex integrations need a separate scope and budget.
An example for one core workflow, manageable data and few integration dependencies, including discovery and development. The actual schedule follows agreed specifications, resources and feedback timing.
Weeks 1–2
Workflow map, prototype, acceptance criteria, estimate and a clear list of exclusions.
Weeks 3–4
Data design, authentication and permissions; a preview to confirm roles and user flows.
Weeks 5–8
Features, reports and key activity history; demos every two weeks for in-scope feedback.
Weeks 9–10
Business owners check real scenarios and trial imports, then verify fixes for issues blocking use.
Weeks 11–12
Small-group pilot, training, documentation, access and a backup/recovery approach.
After launch
Track handling time, repeated data entry and errors; choose expansion work based on actual use.
This example assumes an available business decision-maker, ready data and feedback within two working days. Third-party dependencies or scope changes may affect timing. Payment milestones are agreed against deliverables.
Start with your workflow, forms and current problems. Indicative budgets are VND 10–20 million for discovery and VND 60–120 million for a first release within the described scope. When quoted separately, the combined range is VND 70–140 million, without billing discovery work twice. Expansion of an existing system is VND 40–100 million per phase. The final quote defines features, integrations, acceptance criteria, taxes and operating costs.
Allow an indicative 1–2 weeks for discovery and 8–12 weeks for development after specifications are agreed. The 12-week roadmap on this page is an example including discovery for a focused workflow with ready data and few integration dependencies. The operational date follows the agreed scope and both teams' availability.
The agreement clarifies rights to source code, documentation, data and third-party components. Handover items, hosting accounts and access are agreed for your project so the business can manage and continue operating or developing the system.
Issues within the accepted scope are handled under the warranty terms. Maintenance, operational support and new business requirements are agreed separately. Changes are assessed for cost, data and schedule impact before development.
Involve a process decision-maker and the people who will use the software. Prepare workflow notes, forms, current tools and anonymised sample data. System access is discussed within the discovery scope.
Choose relevant measures such as processing time, repeated data entry or status visibility. Review the first release with users before expanding. Actual savings depend on data, workflows and team adoption.
Agree on monthly monitoring, backup checks, updates and support. Response windows, included work and additional changes are defined before the service starts.
Explore the concepts, approaches and preparation that can help you define your project. These articles are in Vietnamese.
Cách xác định phạm vi ERP theo quy trình doanh nghiệp, chọn phần việc ưu tiên và nghiệm thu trước khi mở rộng hệ thống.
Read article
Tìm hiểu cách hệ thống CRM vận hành, quản lý dữ liệu khách hàng tập trung và những nền tảng cần có khi triển khai.
Read article
Phân biệt chuyển đổi số và tự động hóa, xem ví dụ trong doanh nghiệp, cách chọn quy trình ưu tiên và lộ trình triển khai gắn với chỉ số đo hiệu quả.
Read articleCustom software development
Tell us what your team does, which tools it uses and where work gets stuck. We will identify priority functions and a practical discovery step.
+84 779 699 996Describe a time-consuming workflow, the tools your team uses and the change you want to make. We will identify what to address first and how to phase delivery.
