How we work
Discovery first. A fixed scope. Then working software, early and often.
Custom software fails when the scope is vague and progress is invisible. Our process is built to prevent both.
The six steps
From first visit to support
- 01
Discover
We visit your site or run structured calls to map how work actually moves today: who does what, which spreadsheets matter, where the delays are.
You getRequirement map and process notes you can keep
- 02
Scope
You get a fixed-price proposal with the modules, deliverables, timeline and payment milestones written down before the build starts.
You getScope document and fixed-price proposal
- 03
Build
We work in short sprints and demo working software at the end of each one, so you see progress and can change direction early.
You getSprint demos on a staging system
- 04
Migrate
Opening balances, masters and history move across from Tally, Excel or your current system, checked with your team.
You getVerified data migration
- 05
Go live
User acceptance testing with your team, then go-live with our engineers on standby for the first days of real use.
You getUAT sign-off and go-live plan
- 06
Train & support
Role-based training in Hindi and English, then 12 months of post-go-live support for custom ERP projects.
You getTrained users and a support channel
Engagement models
Choose how the work is structured
Fixed-price project
Best for: a defined scope: one ERP, one portal, one app
Discovery first, then a written scope with deliverables, timeline and payment milestones. The price is agreed before the build.
Phased rollout
Best for: large systems that touch several departments
Start with the modules that hurt most today. Each phase is scoped and priced on its own, on the same system.
Ongoing development
Best for: products and systems that keep changing
After go-live, the same engineers keep improving the system from a shared backlog, with a demo at the end of each sprint.
During the project
You always know where things stand.
Sprint demos
Working software on a staging system at the end of every sprint, so you see progress rather than status reports.
Process questions
What happens in discovery?
We visit your site or run structured calls to map how work moves today, who does what, and which spreadsheets and tools matter. You keep the requirement map whatever you decide next.
What if our requirements change mid-project?
Sprint demos exist so changes surface early, when they are cheapest to make. Any change to the agreed scope is discussed with you before we build it.
Who owns the software at the end?
You do. We hand over full source code ownership once the project is complete, so there is no dependency on us to run or change it.
Will you sign an NDA?
Yes. Everything you share with us stays confidential, and we are happy to sign an NDA before you share details.