Following our discussion, here is how we would like to take this forward. A few questions about your fieldwork, a phased delivery plan shaped by your answers, and the security and compliance measures that protect your data and your clients' data from day one. Treat the plan as our starting point. We will refine it once we hear from you.
Data stays in India DPDP Act ready Encrypted on phone and server Independent security auditThis survey runs the way your field app will. One question at a time on the phone, a running interview timer, and each answer reaching the supervisor view the moment it is given. Every question says why we ask it.
In Phase 2 this becomes a dashboard for all your surveyors at once, on a map, with progress against quotas.
Each phase ends with something your team uses in real surveys. Later phases add to a working system, so nothing waits on the full build.
Most of this time is spent waiting on Apple, Google and the security auditor, not on building. Starting these in week 0 is what keeps launch at week 12. To publish the app under MSR's own name, Apple and Google first verify that MSR is a registered company. This uses a free business ID called a D-U-N-S number, which we apply for on your behalf. No app goes public before it passes the independent security audit.
Outcome: a pilot survey on your own app in week 6
Outcome: catch bad interviews the same day
Outcome: full launch on every device your team carries
Timelines and scope will be confirmed after we review your answers in Step 1. For example, phone surveys or a large surveyor team would change Phase 1.
Opinion data that can include caste, religion and voting intent is among the most sensitive data a firm holds. These protections are part of Phase 1, not added later.
Consent wording and contracts will be reviewed by a lawyer before go-live.