Frequently asked questions

Yes. Native Android in Kotlin, native iOS in Swift, and cross-platform in Flutter or React Native. We handle the full lifecycle including store submission, release management, crash reporting and post-launch analytics. Which approach we recommend depends on your performance needs and budget — we will explain the trade-off rather than defaulting to one.

Frequently — it is a large part of our work. We start with an audit of the codebase, data model and infrastructure, then recommend either incremental modernisation (replacing modules one at a time while the old system keeps running) or a phased rebuild. A full rewrite is occasionally right, but it is rarely the lowest-risk option and we will say so.

Both. For startups we usually run a tightly scoped MVP engagement to get something credible in front of users or investors quickly, built on an architecture that will not need throwing away when it works.

Indicatively: a focused web app or MVP runs 6–12 weeks; a mobile app 8–16 weeks; a mid-sized enterprise platform such as an ERP module 3–6 months; a full multi-department ERP 6–12 months. You get a stage-by-stage timeline after requirement analysis, and we release incrementally so value arrives before the final milestone.

Seven stages: requirement analysis, planning, UI/UX design, development, testing, deployment and maintenance. Development runs in two-week sprints with a working demo at the end of each one. You have access to the tracker throughout and a named project manager as your single point of contact.

They usually do, and that is fine. On time-and-material or dedicated-team engagements you simply re-prioritise the backlog. On fixed-scope contracts we assess the change, tell you the cost and schedule impact in writing, and you decide — nothing is added silently and then invoiced later.

More at the start, less later. Expect concentrated involvement during requirement analysis and design — typically a few hours a week from someone who knows the process deeply — then roughly an hour per sprint review. Projects where the client cannot spare that time are the ones most likely to disappoint everyone.

Three models. Fixed scope, fixed price when requirements are clear, with milestone-linked payments. Dedicated team billed monthly per allocated engineer. Time and material billed against detailed timesheets for evolving work. We will recommend the one that suits your project, not the one that suits us.

You do, in full, on final payment. That includes source code, database schemas, deployment scripts and documentation. We do not hold code hostage and we do not licence back to you something you paid us to build.

Yes, routinely, and usually before the first detailed discussion. We are happy to work under your NDA template or provide ours.

Yes. Our annual maintenance contracts come in three tiers covering monitoring, bug fixes, security patching, version upgrades and a pool of enhancement hours, with response-time SLAs from next-business-day up to one hour for critical issues on 24×7 cover.

Security is part of the build, not a phase at the end: OWASP-aligned code review, encryption in transit and at rest, role-based access control, audit logging, dependency vulnerability scanning in CI, and secrets kept out of source control. For regulated clients we also arrange third-party penetration testing before go-live.

Wherever your requirements dictate. We deploy to AWS, Azure and Google Cloud including their India regions, to your existing on-premise infrastructure, or to a private data centre. Data residency requirements are settled during planning, before architecture is finalised.

You leave with everything you need: code, documentation, credentials, deployment runbooks and a handover session with the incoming team. Building software that only we can maintain would be a poor way to earn repeat business.

Yes — user training sessions, role-based quick reference guides and recorded walkthroughs are part of every deployment. Administrator and developer training is available where your team will take over maintenance.