Discovery
Understand your goals, users, workflows, and requirements.
The Rakmyat approach
How we work
From your first idea to a working software solution.
We follow a structured process that connects business understanding, clear requirements, design approval, development, testing, and launch.
Discuss your projectFrom first conversation to handover
The process at a glance
We follow a structured process that connects business understanding, clear requirements, design approval, development, testing, and launch.
01 02 Business analysis
Study the business context and identify what the solution must support.
03 BRD & PRD
Document the business requirements and product expectations.
04 Flows & SRS
Map the application experience and define the software specification.
05 Agreement
Confirm deliverables, milestones, costs, and contractual terms.
06 UI/UX design
Design the experience and obtain client approval.
07 Development
Build the approved solution and its integrations.
08 Staging & QA
Test the complete solution in a realistic staging environment.
09 Launch & handover
Deploy to production, verify the release, and complete handover.
Activities, outputs, and collaboration
What happens at each stage
Discovery
Understand your goals, users, workflows, and requirements.
We start with the business context and the people who will use the software, then capture what the project needs to support.
Key activities
- Discuss the current situation, goals, and challenges
- Map users, workflows, tools, constraints, and expectations
- Record initial needs and open questions
Deliverable
Initial requirements and discovery notes
Your role
Share context, explain current workflows, and clarify priorities.
Business analysis
Study the business context and identify what the solution must support.
The initial information is examined to understand operational needs, roles, dependencies, and potential improvements.
Key activities
- Review current workflows and pain points
- Identify users, roles, business rules, and dependencies
- Develop an initial solution direction
Deliverable
Business analysis findings and an initial solution direction
Your role
Validate the findings and confirm that the business context is represented accurately.
BRD & PRD
Document the business requirements and product expectations.
Requirements are organized into business objectives and product behavior, reflecting the scope agreed for the project.
Key activities
- Define objectives, scope, stakeholders, and requirements
- Describe expected functionality and user journeys
- Set acceptance expectations appropriate to the work
Deliverable
BRD and PRD, with depth adapted to the project
Your role
Review the documents and resolve scope questions before the technical plan proceeds.
Flows & SRS
Map the application experience and define the software specification.
Agreed requirements are translated into user and application flows with relevant functional and technical considerations.
Key activities
- Map screens, user flows, and core workflows
- Define functional and relevant non-functional requirements
- Consider integrations, data, and permissions
Deliverable
Application flows and SRS
Your role
Review the flows, dependencies, and important requirements.
Agreement
Confirm deliverables, milestones, costs, and contractual terms.
The proposal and agreement state what will be delivered and how the work will be reviewed and accepted.
Key activities
- Describe approved scope and deliverables
- Set milestones and an estimated schedule
- Agree cost, responsibilities, acceptance, and change handling
Deliverable
Approved proposal and signed contract
Your role
Review and agree the terms before implementation begins.
UI/UX design
Design the experience and obtain client approval.
The interface and user experience are designed around the approved requirements, with appropriate responsive considerations.
Key activities
- Prepare relevant wireframes and interface designs
- Review user journeys and responsive states
- Incorporate feedback within the agreed scope
Deliverable
UI/UX design approved for development
Your role
Review the design and approve it before development starts.
Development
Build the approved solution and its integrations.
The implementation follows the approved requirements and design. The work may include front end, back end, data, access rules, integrations, and ongoing testing as relevant.
Key activities
- Implement agreed interface and business behavior
- Connect the required data and systems
- Test the solution during development
Deliverable
Implemented software ready for staging validation
Your role
Review progress at the agreed milestones and clarify project decisions.
Staging & QA
Test the complete solution in a realistic staging environment.
The candidate release is checked in a staging environment configured to represent intended production behavior as closely as practical.
Key activities
- Test workflows, responsiveness, integrations, and access
- Check validation, errors, performance, security, and regressions as relevant
- Resolve issues and complete agreed acceptance checks
Deliverable
Tested release candidate ready for client review
Your role
Review staging, provide feedback, and confirm acceptance against the agreed criteria.
Launch & handover
Deploy to production, verify the release, and complete handover.
After acceptance, production preparation and deployment are coordinated with the client's hosting environment or another agreed provider.
Key activities
- Prepare production configuration and coordinate deployment
- Verify key workflows after release
- Provide agreed access, documentation, or guidance
Deliverable
Live production solution and project handover
Your role
Coordinate hosting access, participate in release checks, and receive the agreed handover.
Documentation shaped to scope
Documents that make decisions clearer
We choose the depth of documentation to fit the agreed scope. A smaller engagement may use concise records; a complex solution may need more detailed specifications.
Business Requirements Document
Business objectives, scope, stakeholders, requirements, and intended business outcomes.
Product Requirements Document
Expected functionality, features, user journeys, and acceptance expectations.
Software Requirements Specification
Functional and relevant technical requirements used to guide implementation.
Other useful project records
- Application and user flows
- Approved UI/UX design
- Proposal, contract, and milestones
- Test results and acceptance notes
The documents describe the project as agreed. They are reviewed with the client at relevant checkpoints.
Client collaboration
Review and approval checkpoints
Client feedback helps confirm direction before the next major stage. The number and timing of review rounds depend on the agreed project scope.
- 01
Requirements and scope
Align on goals, users, workflows, constraints, and what the solution is expected to cover.
- 02
Documentation review
Review relevant requirements, product expectations, application flows, and technical specifications.
- 03
Proposal and contract
Agree on scope, deliverables, milestones, schedule estimate, cost, responsibilities, and acceptance conditions.
- 04
UI/UX design approval
Review the proposed experience and approve the design before development starts.
- 05
Staging review and acceptance
Validate the release candidate and resolve identified issues against agreed acceptance checks.
- 06
Production and handover
Coordinate launch, verify key workflows, and hand over agreed access and documentation.
Before and after release
From development to handover
Staging gives the team and client a place to validate the agreed workflows before production release.
- 01Development
- 02Staging
- 03Testing
- 04Approval
- 05Production
- 06Handover
Staging is used for testing before launch. Identified issues are addressed before final acceptance.
Production deployment is coordinated with the client’s hosting environment or an agreed provider. Handover follows the agreed project scope.
Practical answers
Questions about the process
When do we receive the project scope and cost?
The business context and requirements are discussed first. A proposal can then describe the agreed scope, deliverables, milestones, estimated schedule, and cost for review before any contract is signed.
What are BRD, PRD, and SRS?
They are documents for business requirements, product expectations, and software requirements. Which documents are useful, and how detailed they need to be, depends on the project.
Can requirements change after the contract?
A requested change is reviewed for its effect on scope, deliverables, schedule, and cost. Any change is handled according to the change process agreed in the contract.
When does development begin?
Development begins after the agreed requirements and scope are understood and the UI/UX design has been approved for the project.
Will we review the design before development?
Yes. The design is shared for client review and approval before implementation proceeds.
Can we test the software before launch?
The release candidate is placed in a staging environment for agreed functional, workflow, responsive, integration, and other relevant checks. Issues found are addressed before acceptance.
Can Rakmyat deploy to our existing hosting?
Deployment is coordinated with the client and can use the client's hosting environment or another provider agreed for the project.
What happens after launch?
The team verifies the agreed production workflows and completes handover. Any continuing support or maintenance follows the project agreement.
Ready to turn your requirements into working software?
Tell us what you’re building, and we’ll start by understanding your business and the outcome you need.
Discuss your project