The brief and user roles
Describe the current task, the problem, the people using the system and each role’s permissions. Compare adapting an existing tool with a custom build before choosing the approach.
Custom software
Custom software development
Build a tool around how your team in Vietnam handles work, information and customer enquiries across the languages it uses.
AT A GLANCE
Define a first release around your team's roles, data and complete working flow.
- Start with
- Your workflow, user roles, existing systems and essential first-release requirements.
- Deliverable
- The agreed working release, source code, accounts and operating guidance.
- Agree first
- Integrations need feasibility checks; later features and support are scoped separately.
What this starting fee covers
- Hourly work for an agreed analysis, development or testing task.
- Estimated hours, deliverables and a budget cap agreed before each stage.
- Time records, with source and documentation as defined in the scope.
Separate costs / conditions: This is an hourly rate, not a complete software-project price. Infrastructure, external services and complex integrations are estimated separately.
Compare service prices →Cost depends on the amount and complexity of the work. A smaller scope may reduce the total; we confirm this after reviewing your requirements. Work fees exclude any applicable taxes; domains, hosting, paid tools/APIs and advertising are separate. The final quote confirms scope, total, taxes and timing before work begins.
First release
From the problem to the first release
Choose essential functions and the criteria users will check before acceptance.
One complete workflow
A workflow to discuss might cover receiving a request, assigning an owner, updating its status and finding the record later. Review screens and sample records with users before development.
A first release with acceptance criteria
Agree essential functions, required data, approvers and completion criteria. List features deferred to later phases, then expand based on actual use and an approved scope.
Connections
Connect systems and information
Identify the system of record, permissions and handling of failed operations.
Data sources and responsibilities
Identify which system holds the authoritative data, who is responsible for it and which fields need to be exchanged. Agree permissions to view, edit, export and delete records for each role before designing the connections.
Check integrations and plan for errors
Review API documentation or import and export options, access permissions and provider limits. Define how errors are reported, when to retry and how to avoid duplicate records if a request is submitted more than once.
Check migrated data
Check sample records, formats and missing information. Where migration is needed, agree record-count reconciliation, handling of failed records and recovery before replacing the working system.
Acceptance
Clear acceptance and handover
Test each role and hand over the agreed assets and operating guidance.
Tests for roles and real workflows
Test the main flow, denied permissions, invalid data, duplicate requests and connection failures. Record results against approved criteria; defects in agreed features and new requests are tracked separately.
Source code, accounts and guidance
The handover list covers source code, data, accounts, operating guidance and necessary configuration. Agree ownership, third-party licences and who will maintain each part.
Costs and changes after handover
The proposal separates discovery, development, migration and integrations from hosting, tools and recurring maintenance. Agree how defects are reported and how changes to scope, cost and timing are approved.
Explore the next step.
HOW WE WORK
Clarity at every step.
Discover and define the scope
Prepare the brief: roles, the main workflow, data, first-release scope and acceptance criteria.
Design and confirm
Review proposed journeys, interfaces and data structures with the people who will use the software, resolving unclear requirements before development progresses.
Develop and test
Build the agreed functions in reviewable stages. Users check practical scenarios, and defects are addressed against the documented acceptance criteria.
Deploy and hand over
Deploy the approved release, migrate agreed data and check the result. Hand over access, documentation and guidance, with open work and support arrangements recorded.
ILLUSTRATIVE SCENARIO
One request. One working record.
An example of defining requirements and checking the output. This is an illustrative scenario, not a deployed project or a measured client result.
- Scenario
- Staff receive a website enquiry and track its status in an internal tool. A connection retry may deliver the same request again.
- Test boundaries
- Use sample records. Staff and managers have different permissions; no live CRM or customer data is connected in this scenario.
- Expected output
- One record per request ID, with an owner and status. Duplicate deliveries are recognised and connection failures remain visible for follow-up.
- Acceptance checks
- Replaying the same ID creates no extra record; unauthorised users cannot edit; a connection failure preserves the record without reporting false completion.
FAQ
Before we begin.
A few useful answers to help define the right scope.
Should we buy existing software or commission a custom system?
Compare workflow fit, ongoing costs and integration needs. If an existing product meets your requirements well, a custom build may not be necessary.
Can the software connect to systems we already use?
Each connection needs assessment. Feasibility depends on available APIs or import and export options, permissions and cooperation from the relevant provider.
Can requirements change during development?
Changes can be discussed. We assess their effect on scope, cost and schedule before they are approved and added to the work.
How long does custom development take?
Timing depends on functionality, integrations, data readiness and review cycles. A staged schedule is prepared after discovery.
LET’S DEFINE THE REQUIREMENTS
Discuss the software you need.
Describe your workflow and the problem to solve so we can define a suitable scope.