Our method
How we work
We start by understanding how you work, then analyze, design, build, and connect in stages. Each stage has a deliverable that you review before we move on to the next one.
01Our method
Five stages, from understanding the business to a working system
We follow Agile methodology across five stages, delivering in short Sprints, and at the end of each Sprint you review a working version.
Understand the business
We sit down with your team at your workplace and trace daily operations as they actually happen: who requests, who approves, where data is recorded, and where it gets lost.
Deliverable: The current process map, with weak points and opportunities
Process map
- Request
- Approval
- Execution
- Report
We map processes as they actually happen and identify where time is lost.
Analyze and design the solution
We turn what we have learned into numbered requirements and business rules, design the solution architecture and its modules, and arrange the priorities in a staged plan.
Deliverable: Requirements document, business rules, and module plan
Screen design
- Dashboard
- Mobile app
We review the screens with you before development starts.
Build in stages
We build the system module by module and deliver working releases at short intervals, which your team reviews and tests on real data.
Deliverable: Working releases, with a review log for each release
Sprint cycle
- Planning
- Development
- Review
- Improvement
We repeat this cycle in every Sprint until the system is complete.
Connect and launch
We connect the system to the existing systems, migrate the data, and train the users, then launch the system with a clear plan that limits interruptions to your work.
Deliverable: Integrations, data migration, launch plan, and handover
Launch checklist
- Acceptance tests
- Data migration
- User training
Ready to launch
We launch the system once the checklist is complete.
Improve and develop
After launch, we monitor usage and performance, gather the team’s feedback, and plan improvements and the next modules.
Deliverable: Support and continuous improvement plan
Operations cycle
- Monitoring
- Support
- Updates
We keep track of the system after launch and develop it in increments.
02Our commitments
What we commit to in every project
Practical commitments that we write into the contract and apply at every stage.
- You always own your data, and ownership of the code transfers to you at handover, as set out in the contract.
- We document the business rules and hand over the documentation with the system.
- We deliver in stages, and you review each stage before the next one.
- We stay with you after launch for a support period defined in the contract.
03Collaboration
How we collaborate and communicate
- At the start of each stage, we agree on its scope, its deliverable, and its estimated duration.
- Each side is represented by one person responsible for decisions, and we hold a weekly follow-up meeting.
- You review each stage on a working version, and we do not move on to the next one until it is approved.
- Any change in scope is documented as a change request, with its impact on time and cost, before it is carried out.
04Engineering
Engineering, security, and data
Practices we apply in every project to protect your data and your business continuity.
- Role-based access permissions: no one accesses data they do not need.
- Code review and testing before every release.
- Regular backups with a data recovery plan.
- Encrypted connections and protection of sensitive data.
- System documentation, and handover of the code and data when the project ends.
05Technologies
The technologies we work with
We choose the right technology for each project. Some of the technologies we work with:
06
Support and development after launch
Our work does not end when we hand over the system: we keep track of its day-to-day operation and develop it as your business grows.
- A post-launch support period to fix bugs and monitor stability, as set out in the contract.
- Keeping track of performance, backups, and security updates.
- Regular review sessions to rank improvements and the next modules by your priorities.
- Training for new users when the team grows or branches are added.
07
Questions about how we work
Who owns the code and the data after handover?
Your data is always yours. Ownership of the custom system’s source code transfers to you at handover, as set out in the contract, along with the documentation needed to run and develop the system.
Do you sign a non-disclosure agreement before we share the details of our business?
Yes. We sign a non-disclosure agreement before the discovery session if you request it, and in all cases we treat the procedures and data you share with us as confidential.
Can we start with just one stage?
Yes. You can start with a discovery session and an analysis stage, then decide on the next step based on its deliverable.
What happens after launch?
We stay with you after launch for a support period defined in the contract: we fix bugs, monitor performance, and plan improvements and the next modules with you, according to your priorities.
How long does a project take?
It depends on the project’s scope. After the discovery session, we divide the work into stages and set each stage’s deliverable and estimated duration, and you review them with us before we start.
Let’s start with how you work
Describe your operations and the problem you want to solve, and we will suggest a suitable first step.