Our method
One clear loop, from first conversation to years of support.
We listen, write it all down, show you working software every week, and you pay only for the parts that work. Then we stay, and keep improving it.
The delivery loop
Step by step, with something to see every week.
The same path for a startup, a hospital or a government office. Every release teaches us something that shapes the next.
DiscoverFirst week
We listen and ask how the work happens today: who does what, where it gets stuck, which systems are involved. The first conversation is free.
Behind the scenes: Notes on users, roles, current process and systems to connect to.
DesignAbout 1 to 3 weeks
A written plan in plain words, split into milestones with dates. You click through the screens before any code is written. Nothing starts until you agree.
Behind the scenes: Written scope, acceptance criteria per milestone, clickable prototype.
BuildUsually 4 to 12 weeks
A short demo every week on your own phone or computer. When a milestone works the way the plan says, you approve it and pay for it. Not before.
Behind the scenes: Weekly builds on a test link; code in your Git repository from week one.
Launch1 to 2 weeks
We put it live, train your people and hand over everything: the code, the credentials and a clear manual.
Behind the scenes: Go-live checklist, user manuals, handover pack.
EvolveFor as long as you need
Fixes, updates and improvements, with daily backups and response times written into the contract. What we learn in use feeds the next release.
Behind the scenes: Monitoring, backups, security updates and a monthly report.
Four promises, written into every agreement
Everything in writing
What we build, by when and on what terms is written down and signed before we start.
Pay only for parts that work
The work is split into milestones. You pay for each one after you have seen it working and approved it.
You own it, fully
Code, domain, app-store accounts and data are in your name. If you change vendor, you take everything with you.
Your data stays in India
Hosted on infrastructure in India, backed up every day, visible only to the people you choose.
Cost and engagement
Ways to work with us
A clear, fixed quote after a free first conversation, split into milestones you pay for only once they work. Not sure which fits? We will suggest one in the first conversation; a pilot is a good first step.
- A good first step
Pilot
Start small: one useful module, live with real users.
- One module, live with real users
- Typically 4 to 8 weeks
- Fixed scope, written acceptance test
Good for: A first project with us, a new idea, or a department trying something new.
Fixed-scope project
The whole job, scoped and agreed in writing.
- Written scope and terms
- Three to five milestones
- Pay as each milestone is accepted
Good for: When you know what you need and want one clear agreement.
Monthly product team
Our team works through your list, every month.
- A set number of hours a month
- Your priorities, our team
- Billed monthly
Good for: Software that keeps growing, with new requests every month.
Support and AMC
We look after it once it is built.
- Essential, Standard and Priority plans
- Response times in the contract
- Daily backups and security updates
Good for: Any live website, app or system, even one someone else built.
When we'll say no
If a ready-made product fits, if the budget can't deliver the scope, or if AI isn't the right tool, we'll tell you.
Buying for government?
See how departments and PSUs can buy from us, and where our registrations stand.
The stack we build on
Proven tools, chosen for the job.
Mainstream, well-supported technology, so any good team can maintain what we hand over. Everything runs in accounts in your name.
Mobile
- React Native
- Flutter
- Expo
- Kotlin
- Swift
Web
- React
- Next.js
- TypeScript
- Astro
Back end & data
- Node.js
- Python
- PostgreSQL
- Supabase
- Firebase
- Power BI
AI
- Claude
- OpenAI
- Gemini
- Bhashini
Cloud & India Stack
- AWS Mumbai
- Cloudflare
- UPI
- WhatsApp API
Who it's for
One method, shaped for each sector.
The loop stays the same; the rules, languages and ways of buying change. Each sector page shows what that means for you.
- GovernmentFaster, simpler public services in Hindi and English, with every line of code owned by the department.
- PSUsSystems that connect plants, offices and vendors, built to your security and audit rules.
- HealthcareShorter queues and fewer missed appointments, with patient data kept safe.
- EducationAdmissions, fees and results in one place, with parents kept informed.
- BusinessesSoftware that pays for itself: more orders, faster payments, less paperwork.
- StartupsFrom idea to a product in users’ hands, with engineers who have shipped live apps before.
The agreement, and the standards we build to
What's in our agreement
- IP assigned to you on payment
- Code in your repository from week one
- NDA on request
- Payment by milestone, split agreed in writing
- A warranty period on defects, written into the contract
- Written acceptance criteria for every milestone
- Handover pack, no exit fees
- GIGW 3.0
- Bilingual, accessible, audit-ready government websites.
- WCAG 2.1 AA
- Screen readers, keyboard use, contrast and text resizing, tested with tools and by hand.
- DPDP Act 2023
- Minimum fields, encryption, masked IDs, role-based access, retention rules.
- OWASP ASVS and MASVS
- ASVS for web and MASVS for mobile. Every change is reviewed and tested before release.
- Data hosted in India
- NIC, your State Data Centre, or a MeitY-empanelled cloud (AWS, Azure or Google Cloud India regions).
- Code in your repository
- Domains, cloud and store accounts are registered in your name too.
'Built to' means we design and test against the standard. It is not a certification.
Frequently asked questions
How much does custom software cost?
It depends on what you need: the number of users, screens, reports and connections to other systems. After a free first conversation we send a written scope and a quote, split into milestones. You pay for each part only after it works.
How long does it take?
A pilot goes live in 4 to 6 weeks. A multi-module system usually takes 3 to 6 months. We release it in stages, so staff use the first module while we build the next.
Who owns the code?
You do. The code goes into a Git repository in your organisation's name from the first week, and the IP is assigned to you as each milestone is paid. Domains and cloud accounts are registered in your name too.
Do you build in Hindi?
Yes: proper Unicode Hindi (no images of text), a language switch on every page, Hindi fonts that load fast, and separate Hindi titles for search engines. We don't publish machine translation without a fluent person reviewing it.
Where is your team?
Our office is in Patna, India. We work with clients remotely and on site.
Start with a conversation.
Tell us the problem. A founder replies within one working day.