When are SurveyMonkey or Typeform really not sufficient?
For a one-off survey with straightforward logic and non-sensitive data, those tools are usually perfectly adequate and cheaper. Custom software 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 tools, or you want answers to land directly in your own systems without manual exports. In the first conversation we give you honest advice. Sometimes an off-the-shelf SaaS tool with a custom integration is the smarter route.
How exactly does offline mode work?
With a well-built offline-first app, respondents or interviewers notice no difference between working with or without a network connection. Answers, photos, audio recordings and signatures are stored locally in encrypted form and sync automatically as soon as a connection is restored. For longer fieldwork sessions, the entire questionnaire, including any images, is cached in advance. A key requirement is thoughtful conflict resolution (what happens if the same respondent starts on several devices?) and testing against realistic scenarios: aeroplane mode, poor 4G, a basement or a metal building. For related offline use cases, you may also want to look at our
field service app page, which uses the same sync engine.
How does this work with GDPR, informed consent and data retention?
All communication is encrypted by default, both in transit and at rest, with an informed consent screen where respondents give explicit consent for each data category and can withdraw it 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 about research involving children or young people?
Research with minors is subject to additional GDPR rules on consent via a parent or guardian. Furthermore, the Code for Responsible Marketing of Food Products and the wider Children's Advertising Code impose strict rules on incentives and data use aimed at young people. We build the consent flow around this (digital signature from a parent or guardian), limit the number of fields we store, and take into account the age thresholds relevant to your research, for example 16 for GDPR consent and 13 for certain platform requirements.
Do you work with the EU AI Act for profiling?
If survey answers 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's provisions on profiling and automated decision-making. We help you assess whether this applies, document the logic transparently, and design the informed consent flow so that respondents know their answers are processed automatically. For sentiment analysis of open answers or intelligent routing, we sometimes draw on our
AI development expertise.
What compliance applies to research in healthcare?
For healthcare research, in addition to GDPR, the NEN 7510 standard for information security applies. Depending on the nature of the research, the WGBO (Dutch Medical Treatment Contracts Act), the WMO (Dutch 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-reported outcome measures (PROMs) and support the NEN 7510 requirements (logging, role-based access, encryption, physical and logical separation) as standard. We can connect to HiX or ChipSoft via HL7 or FHIR where your EHR allows it, and exports to REDCap for academic follow-up research are a frequently requested option.
Which integrations are available 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 are often also fed into a
customer data platform so that all customer signals come together in one place. For lesser-known systems, we build the integration based on their API or, where none exists, through an intermediate layer.
Native app or a web survey on a mobile site?
For pulse measurements among employees and NPS mailings, a web survey on a mobile site is often sufficient: low-threshold, no installation required, and the respondent clicks through from an email or Teams message. For fieldwork, patient PROMs, panel research with multiple measurement moments, and anything with an offline requirement, we almost always opt for a proper native app, because you need camera access, GPS, reliable offline storage and push notifications. In the first conversation we advise which combination works best; often it's a mix: native for the demanding use cases, web survey for the lighter 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 going live. A first working version of a clearly defined 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 spanning several sprints. We aim to get a first working version into the hands of real respondents as early as possible, because that is when you find out where the design needs adjusting.
What determines the cost?
Four factors define the scope: the number and complexity of the question types (a simple Likert scale is very different from a drag-and-drop ranking with geolocation), the number of integrations with existing systems, how much compliance layer is needed (standard GDPR versus NEN 7510 with a DPIA and penetration testing), and the rhythm of ongoing development afterwards (a one-off delivery or continuous maintenance with regular new waves). We work with fixed sprint budgets, so you know what you are spending each sprint and what it includes. In the first conversation we give an indicative estimate; after the discovery sprint, it becomes concrete.
Do you work alongside our own researchers or developers?
Yes, in many of our engagements that is the norm. Many clients have their own research team or methodologist who supply 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 pair-program where it helps knowledge transfer. By the end of the engagement, your own developers can maintain the codebase fully independently, with no lock-in to us as a supplier.
Who manages the app after it goes live?
You can do that yourselves 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 management contract, covering monitoring, OS updates (iOS and Android versions periodically require adjustments), security patches and further development for a fixed monthly fee. Combinations are also possible, for example your team handling the questionnaire content and us handling the mobile layer.