When are SurveyMonkey or Typeform really not enough?
For a one-off study with straightforward logic and non-sensitive data, those tools are usually fine and cheaper. Custom development pays off when at least one of three things applies: you want data ownership (no respondent data on US servers), your routing or multi-wave logic doesn't fit the standard options, or you want answers to land directly in your own systems without manual exports. In the first conversation we give you honest advice — sometimes a SaaS tool with a custom integration is the smarter route.
How exactly does offline mode work?
With a well-built offline-first app, the respondent or interviewer notices no difference between working with or without a network. Answers, photos, audio recordings and signatures are stored locally in encrypted form and sync automatically as soon as a connection is available again. For longer fieldwork sessions, the entire questionnaire, including any images, is cached in advance. A key requirement is well-thought-out conflict resolution (what if the same respondent starts on several devices?) and testing in realistic scenarios: flight mode, poor 4G, in a basement or a metal building. For related offline use cases, take a look at our
field service app page, where the same sync engine is used.
What about GDPR, informed consent and retention?
By default, all communication is encrypted in transit and at rest, with an informed-consent screen in which the respondent explicitly consents per data category and can withdraw consent afterwards. We apply data minimisation (only the fields strictly necessary for the research) and automatic retention policies per data category (for example, anonymising free-text answers after six months while keeping scores for longer). For projects involving personal data of customers, employees or patients, we carry out a DPIA as standard and, in the final sprint, a penetration test by an independent security partner.
And what if it involves children or young people?
Research involving minors is subject to additional GDPR rules on consent from parents or guardians. Since the Code for Responsible Online Marketing of Food Products and the broader Code for Advertising to Children, there have also been strict rules on incentives and data use aimed at young people. We build the consent flow around these rules (a digital signature from a parent or carer), limit the number of fields we store, and take specific account of the age limits relevant to your research, for example 16 for GDPR consent and 13 for some platform requirements.
Do you work with the EU AI Act for profiling?
If the answers to a questionnaire are used to automatically place a respondent in a segment, give advice or calculate a score that affects a service or treatment, this quickly falls under the EU AI Act provisions on profiling and automated decision-making. We help you assess whether this applies, document the logic transparently, and build the informed-consent flow so that respondents know their answers are processed automatically. For sentiment analysis on open answers or intelligent routing, we sometimes bring in our
AI development expertise.
What compliance applies to research in healthcare?
Research in healthcare is subject not only to the GDPR but also to the NEN 7510 information security standard. Depending on the nature of the research, the WGBO (Dutch Medical Treatment Contracts Act), the WMO (Medical Research Involving Human Subjects Act) and the code of conduct of your ethics committee may also apply. We work with healthcare organisations that administer patient PROM questionnaires, and we support the NEN 7510 requirements (logging, role-based access, encryption, physical and logical separation) as standard. We build integrations with HiX or ChipSoft via HL7 or FHIR where your EHR allows it, and exports to Redcap for follow-up academic research are a frequently requested option.
Which integrations are possible as standard?
In practice, almost anything. For HR: AFAS, Visma, Personio, BambooHR. For CRM: HubSpot, Salesforce, Microsoft Dynamics, Pipedrive. For marketing automation: Marketo, ActiveCampaign, Mailchimp. For healthcare: HiX, ChipSoft, Redcap. For BI and analytics: Snowflake, BigQuery, Azure Synapse, Power BI, Tableau, Looker. NPS scores also often end up in a
customer data platform so that all customer signals come together in one place. For lesser-known systems, we build the integration using their API or, if there isn't one, via an intermediate layer.
Native app or a web survey on a mobile site?
For pulse surveys among employees and NPS mailings, a web survey on a mobile site is often enough: low threshold, no installation, and the respondent clicks through from an email or Teams message. For fieldwork, patient PROMs, panel research with multiple measurement points and anything with an offline requirement, we almost always choose a true native app, because you need camera access, GPS, reliable offline storage and push notifications. In the first conversation, we advise which combination works best. It is often a mix: native for the heavy use cases, a web survey for the light ones.
How long does a project take?
That depends heavily on the number of question types, the number of integrations, the compliance context and how many respondents need to be tested before production. A first working version of a clearly scoped pulse app with one integration can be ready within a few sprints. A larger implementation with multiple measurement waves, complex routing, EHR integration and phased pilots is a project of several sprints. We aim to get a first working version into the hands of real respondents as early as possible, because that is when it becomes clear where the design needs adjusting.
What determines the cost?
Four factors determine the scope: the number and complexity of the question types (a simple Likert scale is a different matter from a drag-and-drop ranking with geolocation), the number of integrations with existing systems, how much compliance is required (standard GDPR versus NEN 7510 with a DPIA and pen test), and the pace of ongoing development afterwards (delivered once, or continuous maintenance with regular new waves). We work with fixed sprint budgets so you know per sprint what you are spending and what is included. In the first conversation we give an indicative estimate; after the discovery sprint it becomes concrete.
Do you work with our own researchers or developers?
Yes, in a large share of our projects that is the norm. Many clients have their own research team or methodologist who supplies the questionnaire content, and possibly an IT team that manages the EHR, CRM or HRIS. We focus on the mobile layer and the integration APIs. We work in the same Git repository, use the same code conventions, and do pair programming where it helps with knowledge transfer. At the end of the project, your own developers can maintain the codebase completely independently, with no lock-in to us as a supplier.
Who manages the app after go-live?
You can do that yourself if you have in-house developers: we deliver the codebase, documentation and a runbook so your own team can maintain the app. Many clients opt for our maintenance contract: monitoring, OS updates (iOS and Android versions require periodic adjustments), security patches and ongoing development for a fixed monthly fee. Combinations are also possible, for example your team for the questionnaire content and us for the mobile layer.