Discover
We sit with your team, walk the actual process, and write down what the system must do — in your language, not ours.
About Nirvok
We build the systems
We build the systems
organisations actually run on.
Not demos. Not pilots that quietly die. The software the office opens at nine in the morning and closes at seven — for schools, hospitals, hotels, complexes and companies.
Our approach
Software is an operations problem before it is a coding problem.
Most failed projects were coded correctly. They failed because nobody spent enough time understanding the fee counter at the end of the month, the ward at shift change, or the front desk at 2 PM check-in.
So that is where we start. We walk the process, meet the people who will use the system every day, and design around their reality — the exceptions, the rush hours, the audit that arrives in March. The code comes after, and it comes out simpler because of it.
A typical engagement16 weeks
1
Discovery on siteWeek 1–2 · Process mapping with your team
Done2
Clickable designWeek 3–4 · Every screen approved before code
Done3
Build sprintsWeek 5–12 · Demo at the end of each sprint
Running4
Migration & trainingWeek 13–15 · Parallel run with old system
Planned5
Go-live & supportWeek 16 · Warranty and named support channel
Planned
How we work
Five steps, no surprises
Fixed scope, fixed date, and something working to look at every two weeks.
Design
Screens and flows before code. You approve a clickable design, so there are no surprises at delivery.
Build
Two-week sprints with a working demo at the end of each. You see progress, not status reports.
Deploy
Data migration, training, parallel run, and go-live on a date we commit to in the contract.
Support
Named support channel, fixes under warranty, and a roadmap for what you want next quarter.
Principles
What we hold ourselves to
Understand before building
We spend the first days watching how the work is actually done — including the workarounds people invented. That is where the real requirement lives.
Ship in small pieces
A working demo every two weeks. You correct the direction early, when correcting is cheap.
Design for the slowest phone
Our users are clerks, teachers, nurses and cashiers on mid-range devices and patchy networks. If it is not fast there, it is not finished.
Write it down
Documented code, documented data model, documented handover. The system should outlive whoever built it — including us.
No lock-in
You get the source, the database and the hosting accounts. Staying with us should be a choice, not a constraint.
Answer the phone
Support is a named channel with a committed response time, not a ticket that disappears.
Technology
Proven tools, chosen for your context
We pick the stack that fits your team, your budget and your hosting reality — not the one that is fashionable this year.
FrontendReact, TypeScript, responsive HTML/CSS, progressive web apps
BackendNode.js, Python, PHP (Laravel), REST and GraphQL APIs
MobileReact Native and native Android/iOS where it matters
DataPostgreSQL, MySQL, MongoDB, Redis, reporting warehouses
InfrastructureAWS, Azure, DigitalOcean, on-premise Linux, Docker, automated backups
IntegrationsPayment gateways, WhatsApp and SMS, biometric devices, Tally, GST, couriers, HL7
Start with a conversation.
Tell us about your organisation and what you are trying to fix. We will tell you honestly whether we are the right team for it.
+91 98087 34217