# Market Research Market Research Report - Global

**Generated on:** 2026-10-13 16:07:46.518337  
**Industry:** Market Research  
**Geography:** Global  
**Details:** # Deep Research Prompt: How Voxpopme could run diary studies for customers

## How to use this prompt

Paste the whole prompt into each model (ChatGPT Deep Research, Gemini Thinking, Perplexity, DeepSeek, Claude, Grok). For Grok, add this line first:

> I want you to be maximally contrarian about this topic. Challenge every assumption. Why do diary study features get built and then quietly abandoned? What do researchers secretly hate about diary platforms? What are the production failure modes nobody talks about? What wrong assumptions do product teams make when they try to add longitudinal research to a video survey platform?

---

## Context

Voxpopme is a video research platform. Customers (in-house UX and insights teams, plus research agencies) run video surveys where participants record self-filmed answers to questions, usually in a single sitting. The platform includes:

- **Video surveys**: asynchronous, one-off, self-recorded video responses to a set of questions.
- **AI moderator**: asks adaptive follow-up questions during a video response.
- **Sessions**: live, scheduled one-to-one video interviews run inside the platform.
- **Always On**: a continuously open project that keeps collecting responses over time.
- **Recurring Project toggle**: an existing setting that re-runs a project on a schedule.
- **Influence**: Voxpopme's participant community product, including "exclusive groups" (closed cohorts of participants that a customer owns).
- **Bring-your-own audience**: customers can invite their own participants rather than using a panel.
- **Panel supply**: most participants come from third-party panel suppliers under commercial agreements.
- **Compass**: an agentic AI research assistant that analyses responses and produces findings.
- **Research services**: a managed team that runs projects on the customer's behalf.

Voxpopme does **not** currently offer diary studies (multi-day or multi-week research where the same participants complete tasks repeatedly, with reminders and follow-up). The platform used to attempt them but stopped because of participant drop-off, heavy manual setup, and no reminder or re-invite mechanism. The research services team still runs diaries as fully managed, largely manual projects.

Customers keep asking for diaries. Recent examples include a large agency wanting 2 to 4 week studies, several consumer goods brands, a retail data business, and a maker-tools brand. One enterprise customer churned to dscout partly because diaries were missing.

**The decision this research informs:** should Voxpopme build diary studies into the product (self-serve), partner or integrate with a specialist diary platform, or keep diaries as a managed-service-only offer? No build decision has been made. This is discovery.

**Worked example to anchor on:** an agency client wants a study with 8 to 20 participants, 12 to 15 video tasks spread over 1 to 3 weeks, plus 2 live video interviews with each participant during or after the diary period.

---

## Research sections

Answer every section. Where you do not know, say so rather than guess. Prefer primary sources (vendor docs, help centres, pricing pages, published case studies, academic and practitioner literature) over marketing summaries.

### 1. Definitions and taxonomy
1. How do practitioners distinguish diary studies, longitudinal studies, mobile ethnography, in-the-moment research, experience sampling, and "always on" communities? Where do the boundaries blur?
2. What are the common diary formats (interval, signal, event-contingent, task-based, hybrid) and when is each used?
3. What is the typical shape of a diary study in UX and consumer insights: participant count, duration, number of entries, entry length, mix of video, photo, text, and survey questions?
4. What distinguishes a "diary study" from simply re-sending a survey to the same people every few days? What do researchers consider the minimum viable feature set?

### 2. What customers need
1. What do in-house UX teams and research agencies say they want from a diary study tool? Cite published reviews, G2/Capterra feedback, Reddit and research community discussions, conference talks, and job posts.
2. What tasks do they set participants (unboxing, daily usage, moments of friction, shopping missions, habit tracking, product trials)?
3. How often do they want to combine a diary with live follow-up interviews, and at what points (kick-off, mid-study, exit)?
4. What outputs do they expect at the end: per-participant timelines, cross-participant themes, highlight reels, journey maps, quant trends over time?
5. How do agencies' needs differ from in-house teams' (white labelling, client observers, multi-market, larger samples)?

### 3. Participant experience and retention
1. What are typical completion and drop-off rates for diary studies by length and cadence? Cite data where it exists.
2. What causes drop-off: task fatigue, unclear instructions, incentive structure, poor mobile experience, lack of reminders, feeling unobserved?
3. What reminder and nudge mechanics work (push, SMS, email, WhatsApp, in-app) and at what frequency before they become counterproductive?
4. How are incentives structured for multi-week studies (milestone payments, completion bonuses, per-entry payments) and what do participants say about them?
5. What does good participant onboarding look like for a diary (practice tasks, expectation setting, consent for repeated contact)?
6. What are the practical mobile capture challenges over multiple weeks: app versus web, offline recording, upload reliability, storage, battery, notification permissions?

### 4. Researcher workflow and setup burden
1. Walk through the end-to-end researcher workflow for a diary study on a mature platform: design, scheduling, recruitment, launch, monitoring, nudging, re-contact, analysis, reporting.
2. Where does setup effort concentrate, and which steps are typically automated versus manual?
3. How do platforms let researchers monitor progress mid-study (dashboards, per-participant status, alerts for non-responders) and intervene (re-invite, swap participants, adjust tasks)?
4. How do researchers handle changes mid-study (adding a task, extending the window, dropping a participant) without breaking the data?
5. What does the researcher need in order to schedule and run live interviews with the same participants during the diary window?

### 5. Competitive landscape
Cover at minimum: dscout, Indeemo, Recollective, Qualtrics (including any XM/video capabilities), UserTesting, Discuss.io, EthOS, Lookback, Maze, Dovetail (if relevant), and any newer AI-native entrants. For each:
1. What diary or longitudinal capability do they actually offer today (confirm from current documentation, not older reviews)?
2. How do they handle scheduling, reminders, re-contact, incentives, and live follow-up?
3. What is their pricing model and rough price points for diary studies?
4. What do customers praise and complain about in reviews?
5. Which of these are positioned as self-serve, managed, or both?
6. Produce a comparison table of features and a short note on where each is strongest and weakest.

### 6. Commercial and pricing models
1. How are diary studies priced in the market: per participant per day, per study, per seat, bundled into enterprise licences, managed-service day rates?
2. What are typical total costs to a customer for a study like the worked example (8 to 20 people, 12 to 15 tasks, 1 to 3 weeks, 2 live interviews)?
3. What margin and cost structures apply when panels are involved (per-entry incentives, re-contact fees, attrition replacement)?
4. What evidence is there on whether diary capability drives platform retention or expansion revenue?

### 7. Panels, recruitment and re-contact
1. How do major panel suppliers handle re-contacting the same participants over multiple weeks? What is typically allowed, restricted, or charged extra?
2. What are the consent and data protection requirements (UK GDPR, EU GDPR, CCPA, ESOMAR and MRS codes) for repeated contact, notifications, and storing video over time?
3. How do platforms handle attrition replacement mid-study without compromising the sample?
4. How do bring-your-own-audience and owned communities (exclusive groups) change the recruitment and re-contact picture compared with panel recruitment?
5. What identity and deduplication measures matter for multi-week studies (same participant, same device, fraud prevention)?

### 8. Product architecture and technical implementation
1. What are the core system components a diary study feature needs: participant cohort management, task scheduler, time-window logic, reminder engine, re-invite flow, progress tracking, per-participant timeline, data model linking entries over time?
2. How would a product that already has one-off video surveys, an always-on mode, a recurring project toggle, closed participant groups, an AI moderator, and live interviews combine those into a diary? Which gaps would remain?
3. What are the scheduling and time-zone edge cases (participants across time zones, daylight saving changes, missed windows, late entries, backfilling)?
4. What notification infrastructure is needed, and what are the trade-offs between email, SMS, push via a native app, and web push?
5. What is a credible MVP architecture versus a full build, with rough effort estimates and the biggest technical risks?

### 9. AI moderation and analysis of longitudinal data
1. How can an AI moderator adapt follow-up questions based on a participant's earlier entries in the same study?
2. What analysis is distinctive to diaries: change over time per participant, within-person comparison, event sequencing, sentiment trajectories, habit formation signals?
3. How are competitors and research teams using AI to synthesise multi-week qualitative data, and what are the known failure modes (over-generalising from sparse entries, losing the per-person thread)?
4. What visualisations and report structures work best for longitudinal qual (participant timelines, swimlanes, heatmaps of task completion, theme evolution)?

### 10. Blending diaries with live interviews
1. What is best practice for sequencing live interviews around a diary (pre, mid, post) and what does each add?
2. How do platforms let moderators review a participant's diary entries during a live interview?
3. What scheduling and no-show problems arise when booking interviews with diary participants, and how are they handled?
4. How much of the value of a diary comes from the live follow-up versus the asynchronous entries, based on practitioner accounts?

### 11. Build, partner or managed-only
1. What are the published examples of research platforms adding diary capability by building, by partnering or integrating, and by keeping it as a service? What happened afterwards?
2. What criteria should a product team use to decide between these options (demand depth, frequency of asks, strategic fit, differentiation, engineering cost, support load, margin)?
3. What is the realistic lead time and ongoing maintenance burden for each option?
4. If managed-only, what tooling would make the services team dramatically more efficient without a full self-serve build?
5. If partnering, which diary platforms have APIs, white-label options, or partnership programmes?

### 12. Edge cases, failure modes and risks
1. Why have diary features failed or been quietly deprecated on other platforms?
2. What happens when a participant drops out on day 3 of 21: data integrity, incentive disputes, replacement cost?
3. What support and operations load do diary studies create (participant tech issues, late-night reminders, chasing non-responders)?
4. What are the risks of building a diary feature on top of a one-off survey data model?
5. What assumptions in this brief should be challenged? Is the demand real and repeatable, or is it a handful of loud customers?

---

## Output instructions

- Organise the response by the 12 sections above, in order.
- Be specific. Give numbers, feature names, price points, and dates where you can. Avoid ranges where a single evidenced figure exists.
- Cite sources for every factual claim about competitors, pricing, completion rates, and regulations. Include URLs. Flag any claim you could not verify.
- Clearly separate what is evidenced from what is your inference.
- Flag trade-offs explicitly, especially between participant experience, researcher effort, and engineering cost.
- Note anything surprising or counter-intuitive you found.
- Finish with three things:
  1. A one-page summary a product lead could read in five minutes.
  2. A recommended MVP feature list for the worked example (8 to 20 participants, 12 to 15 video tasks, 1 to 3 weeks, 2 live interviews), and a separate "later" list.
  3. Your provisional view on build, partner, or managed-only, with the three facts that would most change your mind.
- Write in UK English. No marketing language.

---

# A Practical Diary Study Strategy For Voxpopme

## Executive Summary

**Provisional recommendation: offer a better-instrumented managed diary service first, benchmark it against a specialist partner, and defer a broad self-serve build until repeat paid demand and delivery economics are demonstrated.** The most useful initial product investment is a reusable cohort, scheduling and follow-up layer, not another video question type.

Global scope; research cut-off **13 October 2026**. Voxpopme's product inventory, previous diary attempt, customer requests and churn example are supplied internal context. Product recommendations and planning estimates below are explicitly distinguished from published evidence.

- **The Market Is Larger Than The Opportunity**: ESOMAR reports **$153bn** in global insights-industry turnover in **2024**, up **8%**. This includes research software and business services, not just market research or diaries -> size Voxpopme's opportunity from customer demand, not that headline market. [48]
- **Continuity Is The Missing Product**: Dscout combines multiple activities with pacing, consent, payments and progress tracking -> recurring surveys alone are an inadequate competitive proposition. [5]
- **AI-Native Competition Is Already Here**: Outset announced diary studies on **13 August 2026**, including cohorts, rounds, invitations and analysis as sessions finish -> differentiate on reliable delivery and participant-level understanding, not simply AI summaries. [16]
- **Completion Benchmarks Are Easily Misused**: A large EMA meta-analysis reports **79.19% assessment compliance** and **10.58% participant dropout**, different measures from different reporting subsets -> do not promise a commercial video-diary completion rate from those figures. [22]
- **More Reminders Do Not Equal Better Retention**: Recollective documents extensive notification controls, yet reviewers still report missing reminders -> measure delivery, recovery and support, not just whether an email job ran. [6][39]
- **The Worked Example Includes Substantial Live Work**: The brief implies **96-300 diary submissions** and **16-40 live interviews**, calculated from its bounds -> budget moderator time, scheduling and participant incentives alongside diary software.
- **Prices Are Not Directly Comparable**: Recollective advertises Qual Live + Async from **$750/month with an annual commitment**; Lookback counts separate recordings as separate sessions -> compare the complete study bill and commitment, not a headline monthly price. [18][31]
- **Demand Is Plausible, Not Yet Proven At Scale**: The supplied requests and churn account justify paid discovery -> require repeat purchases, acceptable contribution and falling operational effort before committing to a full platform.

## 1. Definitions And Taxonomy

### The defining unit is a person over time

A diary study collects participants' accounts of experiences, behaviour and context over time. It is usually remote and asynchronous. NN/g distinguishes event-, interval- and signal-based logging, with combinations common. [10]

| Term | Practical distinction | Boundary that matters to Voxpopme |
|---|---|---|
| Diary study | Repeated self-reports from identifiable study participants over a defined period. [8] | Preserve the same person's sequence, including gaps and follow-up. |
| Longitudinal study | Broader design examining experience or change over time; diary-interview research is one example. [30] | A diary is one longitudinal method, not its synonym. |
| Mobile ethnography | Contextual capture through a participant's mobile device; Indeemo supports diaries, photographs, screen recordings and notes. [19] | Can be one-off or longitudinal; mobile capture does not itself create a diary. |
| In-the-moment research | Capture close to the experience, rather than a later reconstruction. [12] | A single shopping mission can qualify without being longitudinal. |
| Experience sampling / EMA | Repeated, frequent assessment in daily life; signal-based experience sampling prompts a response. [22][10] | Often shorter and more structured than video diaries. Academic EMA sometimes distinguishes itself from once-daily retrospective diaries. [22] |
| Always-on community | An ongoing participant relationship and research environment. Recollective distinguishes its Connect community offering from study-based async research. [18] | A community can supply diary cohorts, but continuous availability is not evidence of within-person continuity. |

**Takeaway:** classify the research design separately from the capture channel and the recruitment relationship.

### Formats and typical study shape

| Format | When to use it | Illustrative task |
|---|---|---|
| Interval-contingent | Regular reflection or comparable measurements. [10] | End-of-day product-use reflection. |
| Signal-contingent | Sample moments when prompted. [10] | Respond to an afternoon notification. |
| Event-contingent | Capture a defined occurrence. [10] | Record a failed attempt or purchase decision. |
| Task-based | Researcher-assigned activities across a study. Dscout supports multiple activities in one study. [5] | Unbox, try a feature, compare alternatives. |
| Hybrid | Combine scheduled and event-based entries; a published diary-interview study does this. [30] | Daily reflection plus optional friction incidents. |

**Takeaway:** the worked example is a task-based hybrid, not necessarily 15 identical daily surveys.

There is no single industry-standard sample or entry length. NN/g gives approximate saturation guidance of **5-12 participants** for small discovery projects, **12-30** for large discovery projects and **30-50** for large or academic projects. Dovetail's practitioner guide describes **one to four weeks** and **five to twenty participants** as common; these are guidance, not representative market statistics. [10][8]

**Design recommendation:** for this brief, start with short videos, photographs or text where appropriate, a small repeated rating, and an optional event log. Pilot a **two-to-three-minute video target** rather than treating that as an evidenced norm. NN/g recommends a short pilot and a pre-study briefing covering expectations, incentives and tools. [10]

**Case: NN/g's three-week diary.** NN/g describes asking UX professionals for an entry at the end of each working day for three weeks. The design connects a meaningful interval to an existing routine rather than demanding arbitrary continuous participation. [70]

That example also shows why reminders are not the whole method. A credible diary needs stable participant identity, clear entry rules, agreed contact, progress visibility and analysis across entries. Re-sending a survey can implement a diary method, but without those controls it leaves the researcher to supply the missing system manually.

**Decision:** define the MVP around continuity and fieldwork control, not around whether a project can be repeated.

## 2. What Customers Need

### Buyers want less coordination, not merely more video

Published feedback exposes specific operational needs. A Dscout reviewer values running both video diaries and in-depth research in one tool, but another reports substantial effort recruiting through bring-your-own links. An Indeemo reviewer praises analysis and client outcomes while reporting large-file upload failures. Recollective reviewers describe reminder-delivery problems and difficulty troubleshooting live sessions. These are individual accounts, not incidence estimates. [42][46][39]

A Reddit researcher discussion recommends Dscout and Lookback and describes UserTesting's diary approach as less refined during the author's evaluation. This is useful discovery evidence, but neither a current feature audit nor a representative buyer survey. No sufficiently specific diary-related job-post evidence was established; published talks and case studies are stronger evidence here. [57]

**Case: Fjord's combined diary and live programme.** Fjord used Dscout to build a cohort for a long-term client. Its researchers combined ranking, scaling and open questions in Diary with deeper Live interviews for a subset. Client stakeholders could attend every interview. [51]

The reported outcome includes an engaged panel, additional methods in the client's toolkit, and easily shareable clips for leadership presentations. The case does not disclose sample size, completion rate or financial return. What it reveals is a buying job broader than collecting entries: coordinate participants, involve clients and turn evidence into something stakeholders use. [51]

### Tasks and outputs to support

The following is a **recommended task catalogue**, not a measured ranking of market demand:

| Research question | Participant task | Expected output |
|---|---|---|
| First-use experience | Unboxing, set-up, first successful use | Baseline-to-later comparison; friction clips |
| Product trial | Use the product on agreed occasions | Participant trajectory; reasons for change |
| Shopping behaviour | Plan, shop, choose, explain alternatives | Purchase journey and decision moments |
| Habit and routine | Brief recurring check-in plus event notes | Repeated-use patterns, with missingness visible |
| Service friction | Capture an incident shortly afterwards | Incident sequence and live follow-up questions |
| Context of consumption | Show preparation, use and surroundings | Contextual themes and illustrated journeys |

Indeemo's published butter-and-spreads case directly demonstrates shopping and consumption tasks, rather than just retrospective opinion questions. [53]

**Takeaway:** outputs should include both a participant story and a cross-participant explanation. A highlight reel alone hides sequence; a timeline alone does not explain shared patterns.

For Voxpopme, provide participant timelines, cross-participant themes, evidence-linked clips, journey-map exports and descriptive repeated-rating trends. Quantitative trends from a small purposive cohort should not be presented as population estimates.

**Agency versus in-house requirements - inference:** agencies are likely to prioritise reusable study templates, separate client permissions, branding, observer access, exportability, multi-market coordination and predictable project quotations. In-house teams are likely to value owned-audience recontact, persistent participant history and connection to product decisions. These are hypotheses to test, not mutually exclusive segments. Fjord's case supports the importance of client access and shareable evidence; it does not prove agencies always need larger samples. [51]

Published guidance supports kick-off and exit interviews, but **no reliable market-wide percentage** was found for how often diaries include them. [21][10]

**Decision:** sell a coherent workflow and useful deliverables; validate each buyer segment's coordination requirements before building agency-specific complexity.

## 3. Participant Experience And Retention

### Three different completion measures must remain separate

| Evidence | Reported result | What it does not establish |
|---|---|---|
| EMA meta-analysis: 477 articles, 496 samples | **79.19% mean assessment compliance**; **10.58% mean dropout** where reported. Average scheduled duration **12.4 days**, median **7 days**. [22] | A completion benchmark for multi-week video diaries. Dropout was reported for only **28.2%** of samples. [22] |
| Prolific retention guidance, citing its testing | **80%** completed all sessions at one-week intervals versus **50%** at four-week intervals. [20] | The outcome of changing Voxpopme's video-task cadence. |
| Prolific examples | Reports **90% retention across 30 daily waves with 300 participants**, and **82% across four weekly waves with 2,500 participants**. [20] | Typical performance across all designs or audiences. |
| Indeemo vendor case | **25 registered respondents**, more than **256 video uploads**, and an **almost 90% completion rate**. [53] | A clearly defined all-participant/all-task denominator, study duration or independent benchmark. |

**Takeaway:** instrument entry compliance, cohort retention and complete-study completion separately. None can safely substitute for another.

A counter-intuitive finding: the EMA meta-analysis finds no association between total scheduled assessments and compliance or dropout. Prolific also reports that an **80% increase in effective hourly pay** produced less than a **three-percentage-point** retention difference in its testing. Neither result means burden or pay is irrelevant; both challenge simplistic claims that fewer tasks or slightly higher pay will solve retention. [22][20]

**Case: Indeemo's shopping diary.** Its butter-and-spreads study captured selection and consumption in context. Offline/online capture and real-time probes helped researchers collect evidence during supermarket decisions. [53]

The strong reported completion is encouraging, but the public case does not isolate whether technology, recruitment, incentives or researcher attention caused it. Treat it as evidence that the method can work, not as a service-level promise. Large-file upload complaints in independent feedback show that successful capture in one case does not remove production risk. [53][46]

### Recommended participant operating model

**Onboarding:** explain total tasks, duration, expected effort, contact channels, payment milestones, late-entry rules and interview obligations. Include a practice recording and upload, a notification test, accessibility needs, and agreement to repeated contact. NN/g recommends pre-study briefing and piloting; acknowledgement and simple thanks can help participants feel attended to. [10][70]

**Reminders:** use one invitation when a task opens, one reminder before its deadline and human outreach after a missed window as an initial policy to test. Suppress messages after completion or withdrawal; respect quiet hours and preferred channels. This is a proposed policy, not an experimentally proven optimum. No universal evidence establishes the best reminder frequency across email, SMS, push and WhatsApp.

**Payments:** favour transparent milestone or accepted-entry payments, with a modest completion bonus rather than making all earned compensation contingent on the last task. Competitor practice differs: Dscout's diary guidance says partial compensation is not generally expected for incomplete studies, while Prolific pays each wave separately and requires each wave to meet its minimum rate. [17][14]

**Mobile trade-off:** native apps can provide persistent drafts and notifications; installation adds friction. Indeemo explicitly saves entries on-device for later upload. Discuss warns unstable connections can break large-file uploads. Storage, battery, permissions and device changes therefore belong in onboarding and support testing. [49][11]

**Decision:** fund participant reliability and recovery before adding more task types or more aggressive nudging.

## 4. Researcher Workflow And Setup Burden

### A mature workflow is an operations system

| Stage | Researcher responsibility | Suitable automation |
|---|---|---|
| Design | Define change questions, cadence, burden and complete-study criteria | Templates; burden calculator; schedule preview |
| Recruitment | Confirm availability, eligibility, recontact rights and baseline quotas | Screening; stable IDs; consent records |
| Pilot and onboarding | Test instructions, capture, payments and notifications | Practice task; tech-check status |
| Launch | Approve cohort and task windows | Invitations; task release; time-zone handling |
| Monitor | Review early evidence and detect missing or weak entries | Participant-by-task dashboard; exception queue |
| Intervene | Clarify, extend, re-invite or remove participants | Targeted messaging; delivery logs; controlled overrides |
| Interview | Select evidence, book sessions and manage no-shows | Scheduling; reminders; linked participant briefing |
| Analyse and report | Compare within-person change and cross-person patterns | Transcription; evidence retrieval; timelines; exports |
| Close | Settle payments, archive and apply retention rules | Payment reconciliation; access expiry; deletion workflows |

This is a **proposed Voxpopme workflow**, informed by Dscout's documented scheduling, payment and progress controls and Recollective's participant-monitoring tools. [5][28][32]

**Takeaway:** automate repeatable coordination, but keep study design, quality judgements and participant welfare under researcher control.

**Case: Recollective's exception workflow.** Recollective's Response Summary table filters participants by completion status and segment. Researchers can bulk-message completed participants with thanks and follow-up instructions, or nudge incomplete participants. Its Activities Report can identify activities associated with poor participation. [28][32]

Importantly, removal from the study can retain responses already collected. That separates an operational decision - stop inviting this person - from an analytical decision about existing evidence. Voxpopme should preserve that distinction rather than deleting a participant's history when they stop participating. [28]

### Where effort actually concentrates

**Inference:** the heaviest set-up work is likely to be writing intelligible tasks, mapping releases and deadlines, checking recruitment feasibility, configuring incentives, translating materials and validating the complete participant journey. During fieldwork, effort moves to exceptions: ambiguous answers, upload failures, missed entries, participant questions and interview changes.

For mid-study changes, use explicit rules:

- Add a task as a new version and record who was eligible to receive it.
- Extend a window without silently changing the original deadline in the audit trail.
- Separate withdrawn, unreachable, excluded and replacement participants.
- Retain original answers; add corrections or annotations rather than overwriting evidence.
- Preview reminder consequences before applying a change.

These are architecture recommendations; the public documentation reviewed does not establish that every competitor implements all of them.

For live work, the researcher needs the same participant identifier, consent status, availability, time zone, interview stage, payment status and a linked evidence pack. Discuss already connects self-paced response pages to follow-up interview scheduling and participant availability collection. [11]

**Decision:** an internal diary control centre could remove substantial manual effort before Voxpopme exposes a self-serve study builder.

## 5. Competitive Landscape

The distinction below is between **documented functionality**, **documented workarounds**, and **not publicly confirmed**. The latter does not mean a capability is absent. Prices are as published; a platform subscription is not necessarily a complete diary-study quotation.

### 5.1 Capability and operational comparison

| Platform | Actual diary / longitudinal capability | Scheduling | Reminders | Re-contact | Incentives | Live follow-up |
|---|---|---|---|---|---|---|
| **Dscout** | Native multi-activity diary studies across mobile and web. [5] | Automated pacing and scheduling. [5] | Configurable pacing reminders. [5] | Multi-entry study continuity; panel or BYO recruitment. [5][23] | Researcher chooses amounts; payment support. BYO payout arrangements differ. [23][17] | Diary and Live combined in published customer use. [51] |
| **Indeemo** | Native mobile diaries; video, photos, text and screen capture; on-device saving. [19][49] | Tasks released together or drip-fed. [49] | New-task notifications, moderator reminders and probe notifications. [49] | Continued participation and dialogue in the study. [49] | Public payout mechanics not confirmed. | Native live booking was not established in the primary diary docs; confirm the interview/import workflow in a demonstration. |
| **Recollective** | Journal activities plus broader async and live research. [6][18] | Activity deadlines; interview scheduling workflow. [6] | Email digests; due, overdue and inactivity reminders. [6] | Private messages and group broadcasts to existing participants. [6] | Diary-specific payment processing not confirmed in reviewed docs. | Invitations, scheduling reminders, missed-meeting and rescheduling notifications. [6] |
| **Qualtrics** | Configurable repeated surveys, video responses and analysis; a turnkey diary workspace was not established. [4][24] | Recurring workflows with start/end dates. [24] | Email tasks and survey distributions can be configured. [24] | XM Directory supports survey distribution to contacts. [24] | Diary-specific payout workflow not confirmed. | Native diary-to-live workflow not confirmed. |
| **UserTesting** | Current help documents an orchestrated diary method using multiple tests, favourites and Live Conversations. [21] | Schedule tests or launch manually. [21] | Guidance says message before every touchpoint. [21] | Favourite-contributor list and invitations. [21] | Diary-specific public tariff not established. | Explicit first and final Live Conversations. [21] |
| **Discuss.io** | Self-Paced Activities explicitly support video diaries, pre-work and post-work. [11] | Activity end dates and response-count closure. [11] | Invites/reminders from respondent hub; cadence not established. [11] | Collect interest in further interviews from respondents. [11] | Public diary payout mechanics not confirmed. | Tech check, availability collection and booking from the response page. [11] |
| **EthOS** | Native diary/mobile ethnography app; multimedia entries and longitudinal fieldwork. [7][52] | Diary cadence controls not established; live self-scheduling is documented. [60] | Live email notifications documented; diary reminder rules not confirmed. [60] | BYO or assisted recruitment; same-person diary/live linkage should be demonstrated. [52] | Plans include panel participants; repeated-task reward terms not published. [7] | Native IDIs, rescheduling/cancellation, moderator dashboard and side chat. [60] |
| **Lookback** | Diaries as repeated SelfTest/Tasks sessions from the same participant. [2] | Researcher structures the sequence; automated diary scheduler not confirmed. | Diary-specific reminders not confirmed. | BYO participants supported; diary identity/reinvite details need demonstration. [31][2] | Panel recruitment and session charges are not a published diary incentive schedule. [31] | Moderated sessions available; diary-specific booking automation not established. [31] |
| **Maze** | Official diary guide supports repeat submissions or multiple studies; not equivalent to a dedicated diary workspace. [26] | Researcher sequences studies/prompts. [26] | Reach sends targeted email campaigns; diary deadline nudges not established. [33] | Reach maintains owned participant history; longitudinal use has restrictions. [33][26] | Diary-specific payout mechanics not confirmed. | Interview scheduling and moderated interviews listed separately. [15] |
| **Dovetail** | Repository and analysis layer for imported diary evidence; native diary fieldwork not established. [62] | No diary task scheduling established. | No diary reminder engine established. | Not established as diary cohort management. | Not established. | Calendar uploads/imports support analysis, not proof of a diary interview-booking system. [62] |
| **Outset** | Native AI-moderated diary rounds announced in August 2026. [16] | Cohort, cadence and rounds designed together. [16] | Invitation handling documented; channel and escalation rules not disclosed. [16] | Cohorts and rounds managed in-platform through panel integrations. [16] | Diary payout terms not publicly specified in launch material. | Platform includes interviews, but human-live diary follow-up was not established by the launch article. [16] |
| **Listen Labs** | AI interviews and analysis documented; native diary orchestration not established. [72][67] | Diary scheduling not confirmed. | Diary reminders not confirmed. | Panel or own-contact recruitment documented; repeated-cohort rules not confirmed. [72] | Diary-specific payment terms not confirmed. | AI interviews are documented; a human-live diary workflow is not established. [72] |

**Takeaway:** Dscout, Indeemo and Recollective are the most relevant operational benchmarks. Outset is the clearest newly documented AI-native diary threat. The remaining products should not be described as equivalent merely because they can collect or analyse repeated responses.

### 5.2 Pricing, delivery model and customer feedback

Strengths and weaknesses below are **assessment for this worked example**, not overall vendor rankings. Review evidence is anecdotal and sometimes historical; missing evidence is stated rather than filled with generic complaints.

| Platform | Delivery model | Published price / model | Customer praise | Customer complaints | Strongest fit | Main limitation for this brief |
|---|---|---|---|---|---|---|
| **Dscout** | Software plus project design/delivery services. [23] | Customised subscription; no public diary price. [23] | Variety of qualitative methods and intuitive use. [42] | BYO recruiting effort. [42] | End-to-end diary/live benchmark | Commercial terms require a quote; BYO is not automatically effortless. |
| **Indeemo** | Researcher-operated software with guided onboarding; full managed diary scope needs quotation. [49] | Public primary-source amount not established. | Analysis and client outcomes. [46] | Large-media upload issues; AI improvement requests. [46] | Contextual mobile capture, including delayed upload | Native live workflow, integration rights and commercial terms need confirmation. |
| **Recollective** | Self-serve platform with service/recruitment partners. [47] | Qual Live + Async from **$750/month**, annual commitment; per-project pricing available. Public estimator shows **$4,475 for 50 participants/four weeks**, guidance only. [18] | Specific independent praise was not established in the review excerpts; the platform documentation establishes its analysis offering. [18] | Independent reviews report reminder and live-support issues. [39] | Branded async/live studies and community operations | Do not interpret the entry licence as all-in fieldwork, incentives and live usage. |
| **Qualtrics** | Configurable research platform; managed diary scope unconfirmed. [4][24] | Diary-specific price not publicly established. | Diary-specific praise was not established in the reviewed evidence. | Review excerpts request clearer menus and guided set-up. [41] | Existing XM users needing structured repeated surveys | More configuration; turnkey diary operations not established. |
| **UserTesting** | DIY orchestration plus explicitly recommended Professional Services. [21] | Diary-specific public quote not established. | G2 summary praises speed and ease of set-up. [38] | A reviewer criticises panel professionalism/quality; not diary-specific. [38] | Product-use tests combined with live interviews | Multiple tests and manual touchpoint management remain visible in official guidance. |
| **Discuss.io** | Software plus support; complete managed diary package not confirmed. | Public diary price not established. | Reviewers praise visible discussion guides, observers and support. [65] | Translation-tab clutter, audio-noise concerns and saved-clip organisation. [65] | Diary/pre-work flowing into interviews | Automated longitudinal pacing and diary economics need demonstration. |
| **EthOS** | Software plus recruitment/support options; full management scope needs quotation. [52][7] | Custom plans: Essential includes **one manager/admin and ten panel participants**; higher plans increase these allowances. No public amount. [7] | Relevant independent diary-specific reviews not established. | Relevant independent diary-specific reviews not established. | Mobile diaries plus native one-to-one interviews | Confirm diary reminders, incentive coverage and longitudinal identity linkage. |
| **Lookback** | Self-serve software; managed diary service not confirmed. | **$1,782/year Team**, 100 sessions; **$4,122/year Insights Hub**, 300 sessions. Annual commitments. [31] | BYO users and recording storage. [45] | A **2022** review mentions bugs and plug-in friction; not proof of today's implementation. [45] | Repeated product-use recordings | Each separate recording consumes a session; operational diary controls need checking. |
| **Maze** | Self-serve research platform; managed diary delivery not confirmed. | Current reviewed page lists seats/studies and enterprise features but does not establish a reliable diary-specific amount. [15] | G2 summary praises ease of use and Figma integration. [40] | Specific diary complaints not established. | Existing Maze customers and owned participant database | Repeated prompts and Reach require careful multi-study configuration. |
| **Dovetail** | Self-serve analysis; not established as diary delivery. | **$0** Free with one project; Enterprise custom. [62] | Clips improved stakeholder engagement. [43] | Portuguese transcription correction and AI-control frustrations. [43] | Repository and evidence sharing | Does not replace recruitment, scheduling, reminders or payments. |
| **Outset** | Platform-operated AI research; managed diary terms undisclosed. | No separate public diary price in launch article; round-by-round analysis described as at no extra cost. [16] | Independent diary-specific review evidence not established. | Independent diary-specific review evidence not established. | AI-moderated longitudinal conversations | Published launch claims do not prove retention, cross-round memory or operational maturity. |
| **Listen Labs** | Platform plus Research Partners. [72] | Diary-specific price not established. | Diary-specific review evidence not established. | Diary-specific review evidence not established. | Adjacent AI interviewing and deliverables | Native diary functionality should not be inferred from repeated interview capability. |

**Takeaway:** request the same priced study and live demonstration from shortlisted vendors. Include two interviews per person, actual video minutes, BYO recruitment, attrition handling, exports and support coverage.

**Case: Outset changes the competitive baseline, not the evidence standard.** Its launch makes cohorts, rounds and invitations first-class concepts and generates summaries from the first round. That is materially closer to a diary product than a generic AI interview tool. [16]

However, an AI-moderated conversation in each round does not establish that the moderator retrieves and reasons correctly over earlier rounds. The public launch article also does not disclose diary completion rates. Voxpopme should test cross-round continuity and operational recovery directly, rather than compete against an assumed feature set.

## 6. Commercial And Pricing Models

### The market uses several incompatible billing units

Published examples show customised subscriptions at Dscout, participant/study-length pricing at Recollective, annual session allowances at Lookback, and user/participant/support configuration at EthOS. A universal per-participant-per-day diary price was not established. [23][18][31][7]

For the worked example, distinguish **participant compensation**, **sample supplier charges**, **software**, **research labour**, **media/AI/translation**, and **contingency**. No sufficiently comparable set of public quotations establishes a defensible market-average all-in price.

### Transparent participant-cost model

**Assumptions:** each video task is a separate activity; two live interviews last **30 minutes each**; use Dscout's published baseline of **$10 per activity** and **$50 per 30-minute interview**. These are one supplier's guidance, not mandatory market rates. Its guidance prices additional entries within an activity differently, at **$5**. [1]

| Scenario from the brief | Diary entries | Live interviews | Incentive per person, calculated | Total incentives, calculated |
|---|---:|---:|---:|---:|
| 8 people, 12 tasks | 96 | 16 | $220 | **$1,760** |
| 16 people, 14 tasks | 224 | 32 | $240 | **$3,840** |
| 20 people, 15 tasks | 300 | 40 | $250 | **$5,000** |

**Takeaway:** even before recruitment and researcher labour, participant compensation is material. Do not use a short-survey incentive model for this bundle.

If those 14 diary entries belong to one multi-entry activity rather than 14 separate activities, applying Dscout's formula mechanically gives **$75 for the diary component**, not $140. That difference illustrates why scope and participant effort matter more than a label. Longer interviews, specialist audiences, product purchases and shipping require separate allowances. Dscout explicitly excludes some partner-panel recruits from its general guidance. [1]

**Case: Lookback's annual session arithmetic.** With one recording per diary task and interview, the 16-person scenario consumes **256 sessions**, calculated. Lookback treats distinct recordings from the same participant as separate sessions. [31]

Team's 100 included sessions plus sixteen ten-session packs cost **$4,630/year**, calculated from $1,782 plus 16 x $178. Insights Hub's **$4,122/year** includes 300 sessions, so it is cheaper for this particular session volume. Neither calculation includes incentives or recruitment, and the commitment remains annual. [31]

### Illustrative managed quotation, not a market benchmark

For the 16-person case, assume:

- Incentives: **$3,840**.
- An illustrative supplier uplift using Prolific's published **42.857% corporate fee**: approximately **$1,646**. This is not a Voxpopme supplier quote or confirmation that Prolific permits this exact workflow. [55]
- Software allocation: **$1,000**, assumed.
- Design, operations, moderation, analysis and reporting: **70 hours at $125/hour = $8,750**, assumed.

That produces approximately **$15,236 before tax, shipping, specialist recruitment, translation and contingency**. An existing-licence, BYO, self-run customer may face much lower incremental cash costs while still supplying substantial staff time.

**Margin model:** calculate contribution after incentives, supplier fees, replacements, software allocation, communications, AI/media processing and direct delivery labour. Public evidence does not establish Voxpopme's margins, supplier recontact charges or a causal diary-driven retention/expansion effect. The supplied churn account is a signal, not an attributable revenue estimate.

**Decision:** sell scoped study packages initially; measure actual delivery contribution before creating bundled unlimited diary access.

## 7. Panels, Recruitment And Re-contact

### Access to respondents is not ownership of a reusable cohort

Toluna's published sample documentation supports recontacts and repeated-wave research. It also describes unique respondent controls and consistent sourcing methodology across waves. That does not mean a buyer can export contact details, send off-platform reminders or reuse every respondent indefinitely. Those permissions and charges depend on the supplier agreement. [29]

**Case: Prolific exposes a hidden attrition mechanism.** Prolific warns that participants can be banned between parts of a longitudinal study. It recommends messaging missing participants and contacting support with their IDs after five days without a response. [69]

Consequently, a missing diary entry is not necessarily fatigue or a failed reminder. Supplier account state can make a participant unreachable. The operational model needs a supplier escalation route and reason codes rather than repeatedly chasing someone who cannot return.

Prolific's payment documentation also says each wave is paid separately, and approval of one wave controls eligibility for the next in its longitudinal setup. Slow approval can therefore become a researcher's own recruitment bottleneck. [14]

### Privacy, consent and video retention

| Regime | Evidenced requirement | Practical diary implication |
|---|---|---|
| **EU GDPR** | Article 5 requires purpose limitation, minimisation, storage limitation and security; Article 6 provides several lawful bases, not consent alone. [61] | Document controller/processor roles and lawful basis; do not assume the word research supplies an exemption. |
| **EU GDPR: sensitive data and transparency** | Article 9 adds conditions for special-category data. Article 13 covers purposes, recipients, retention, transfers and rights, including withdrawal where processing relies on consent. [61] | Explain repeated contact, recordings, observers, AI processing, recipients and retention before collection. |
| **EU GDPR: processors** | Article 28 requires a binding processor arrangement and controls on subprocessors. [61] | Cover panel suppliers, messaging providers, transcription/AI processors and specialist partners. |
| **UK GDPR / ICO** | Ordinary photos are not automatically special-category biometric data; specific technical processing and unique-identification purposes matter. Biometric recognition requires a lawful basis and separate special-category condition. [36][35] | Do not add facial identity matching casually. A diary may also reveal health or other sensitive information through its content. |
| **CCPA, as applicable** | California residents have rights including access, deletion, correction and opt-out/limitation rights in relevant circumstances. [34] | Support requests across raw media, transcripts, contact records and derived outputs, subject to applicable exceptions and business coverage. |
| **ICC/ESOMAR 2025 Code** | Inform participants about recontact and seek agreement; state retention period/purpose; obtain consent before publishing identifiable personal data. [50] | Capture contact and media-sharing permissions explicitly. |
| **MRS observer guidance** | Inform participants about recording/observation and observer capacity; observers should not make their own recordings or disclose identities. [13] | Use controlled client access and explicit observer instructions, not unrestricted media circulation. |

**Takeaway:** agreement to repeated research contact, the legal basis for processing, and permission to share identifiable clips are related but distinct decisions. Country-specific notification, transfer and recording rules need legal review for each rollout.

### Recruitment and replacement policy

**Recommendation:** obtain written supplier terms for persistent IDs, re-invites, permitted channels, minimum wave payments, late entries, replacement charges, exclusions, media consent and retention. Public Cint or Voxpopme supplier-specific commercial terms were not established.

For BYO and Influence exclusive groups, the recruitment relationship may be simpler, but owned access does not remove privacy duties or guarantee willingness to participate. Use pseudonymous study IDs and separate contact information from research evidence. Device fingerprinting can detect duplicate participation, as Toluna documents, but a device is not the same thing as a person. [29]

Recruit an agreed reserve where feasible. A participant joining after day three is a **new trajectory**, not a replacement baseline. Preserve original attrition and report staggered entry separately.

**Decision:** start pilots with BYO or owned cohorts where contact permissions are clear; do not launch panel-based self-serve diaries before supplier-specific recontact feasibility is settled.

## 8. Product Architecture And Technical Implementation

### Add a study-level orchestration layer

**Proposed model:** `Study -> CohortMembership -> TaskAssignment -> Entry`, with linked `Interview`, `Consent`, `NotificationAttempt` and `PaymentLedger` records. Keep persistent participant identity separate from project-specific membership and supplier identifiers.

| Existing Voxpopme component, from the brief | Reuse | Remaining gap |
|---|---|---|
| Video surveys | Capture questions and media | Repeated entries linked to a person and task occurrence |
| AI moderator | Clarify the current response | Controlled prior-entry retrieval and probe limits |
| Sessions | Run live interviews | Two bookings linked to the diary participant and evidence |
| Always On | Keep collection available | Finite cohort, start/end rules and expected participation |
| Recurring Project toggle | Potential scheduling primitive | Participant-level assignments, missed windows and deduplication |
| Influence exclusive groups | Candidate cohort source | Study-specific eligibility, consent and progress |
| BYO audience | Invitation route | Persistent access, re-invite and contact preferences |
| Compass | Analysis and evidence retrieval | Within-person chronology and missingness-aware reporting |

**Takeaway:** reuse capture and analysis services, but do not disguise a new longitudinal data relationship as repeated independent projects.

**Core components:** cohort roster; task scheduler; local-time windows; participant task list; reminder orchestration; re-invite/access recovery; progress dashboard; participant timeline; versioned instructions; payment ledger; audit trail; support and delivery observability. Notification jobs should be idempotent and check current completion/withdrawal state at send time.

**Case: daylight saving is a product policy, not a cron setting.** AWS EventBridge Scheduler supports named time zones, but its documented spring-forward behaviour skips a non-existent local invocation, while autumn repetition runs only once. [27]

A daily diary scheduled at a skipped local time still needs a product decision: release at the next valid time, use a participant-relative day window, or alert an operator. Buying scheduling infrastructure does not determine what the research protocol means. Store the intended local time, IANA zone and resolved UTC time; explicitly decide whether travel changes a participant's schedule.

Distinguish event time, recording time and upload time. Label late and backfilled entries rather than silently treating them as in-the-moment. Record missed windows, time-zone changes and manual overrides. A failed upload must not immediately become an automatic non-completion or non-payment decision.

### Notification choices

| Channel | Proposed role | Trade-off |
|---|---|---|
| Email | MVP default and recovery | Low participant set-up, but delivery and attention need monitoring |
| SMS | Opted-in escalation | Additional cost, country-specific delivery and contact requirements |
| Native push | Later, or specialist-partner route | Better app integration, but installation and permission friction |
| Web push | Supplementary, not sole channel | On iOS/iPadOS, documented support requires a Home Screen web app and a permission request following direct interaction. [58] |
| WhatsApp | Optional managed workflow | Familiar for some cohorts, but creates consent, number handling, integration and evidence-export questions; messaging-app export limitations are noted by NN/g. [10] |

**Takeaway:** use one channel preference and suppression policy across the whole study, including live interviews, rather than independent reminder systems that compete for attention.

**Planning estimates, not engineering commitments:** internal operations tooling **2-4 weeks**; a bounded web pilot with two engineers and shared design/QA **8-12 weeks**; broad self-serve capability with richer scheduling, payments, permissions and resilience **6-9 months** for a larger cross-functional team. Existing code quality, capture reliability and supplier integration could materially change these estimates. Native offline capture is not included in the bounded web pilot.

**Decision:** build a thin cohort-and-task layer behind managed delivery first. If offline contextual capture is essential, partner rather than pretending a web-only MVP is equivalent.

## 9. AI Moderation And Analysis Of Longitudinal Data

### Preserve the person before summarising the cohort

The **Framework Method**, described by Gale and colleagues, uses cases as rows, codes as columns and summarised evidence in cells. It supports comparison across cases without disconnecting an individual's statements from their wider account. Adapt that structure to person x time x theme rather than flattening all diary entries into a single transcript pile. [64]

**Proposed moderation approach:** retrieve only the participant's earlier entries from the same study, with source references and time boundaries. Supply a compact factual context, not an unqualified AI personality profile. Ask neutral comparisons such as, "Earlier you described difficulty setting this up. What happened on this occasion?" Permit the participant to reject the premise.

Keep core repeated questions stable. Version adaptive probes and impose a burden cap. Otherwise AI can create unequal task loads, lead participants towards a change narrative, and make later comparisons less interpretable. These are design risks and recommendations, not measured failure rates for Voxpopme.

**Case: speed and interpretation diverge in a published AI comparison.** A JMIR study analyses **40 short SMS prompts**, not diary videos. GenAI took **20 minutes on average**, compared with **567 minutes** for human coders, and matched **71%** of human inductive themes. [63]

The authors nevertheless find human coders better at nuanced interpretation and recommend hybrid approaches. Its dataset and older model context do not establish equivalent accuracy for multi-week video diaries. The transferable lesson is narrower: faster coding is not evidence that the system preserves longitudinal meaning. [63]

Outset produces summaries and themes as rounds complete. Indeemo documents evidence-linked thematic analysis and journey mapping. Neither capability, on its own, proves reliable inference about individual change or causal habit formation. [16][19]

### Required analysis and visualisation

| View | Analytical use | Required safeguard |
|---|---|---|
| Participant timeline | Sequence of events, entries and interviews | Preserve actual dates, late uploads and gaps |
| Participant x task heatmap | Completion and support monitoring | Do not interpret missing as negative sentiment |
| Journey swimlane | Actions, context, friction and workarounds over time | Distinguish observation from retrospective explanation |
| Within-person comparison | What changed for the same person | Compare matched participants and comparable tasks |
| Theme evolution | Whether themes emerge, persist or resolve | Show participant counts, not just entry counts |
| Repeated-rating chart | Descriptive direction over the study | Show changing denominators and avoid population claims |
| Evidence-linked reel | Communicate a change narrative | Include contradictory cases, not only compelling clips |

**Takeaway:** separate analytical views from persuasive reporting. The most quotable participant is not necessarily the most representative.

Failure modes to test include prolific contributors dominating themes; conflating different participants; interpreting silence as improvement; inventing transitions between sparse entries; translation shifting meaning; and carrying a false AI summary into every subsequent interview. Dovetail reviewers' transcription and AI-control complaints reinforce the need for editable outputs and researcher control, although they are not diary-specific error measurements. [43]

**Decision:** make Compass's initial diary output a source-linked participant timeline and within-person comparison, then add cohort synthesis. Do not begin with an automated journey story that cannot expose its gaps.

## 10. Blending Diaries With Live Interviews

### Each interview stage answers a different question

| Stage | What it adds | Risk / trade-off |
|---|---|---|
| Kick-off | Expectations, baseline context and technology check | More scheduling work; discussion may prime later reporting |
| Mid-study | Clarifies an emerging contradiction or repeated problem | Can alter subsequent behaviour and increase burden |
| Exit | Explains patterns and contradictions using actual entries | Recall and retrospective rationalisation still require scrutiny |

UserTesting explicitly recommends a first Live Conversation and a final one; NN/g recommends reviewing each participant's diary before a follow-up interview. These are best-practice recommendations, not evidence that every diary needs all three stages. [21][10]

**Takeaway:** decide interview timing from the research question rather than adding live sessions as a default premium feature.

**Case: the diary-interview method in practice.** Thille and colleagues describe a study using twice-weekly diaries over **12 weeks**, with additional entries when something noteworthy happened. Participants submitted audio diaries by email, which researchers transferred to secure university storage. [30]

This shows that the method does not depend on video or a specialist app. The authors identify the time commitment for participants and researchers as a major limitation. Its value lies in combining a sequence of experiences with later sense-making, not in maximising recorded minutes. The paper does not quantify what percentage of insight comes from diaries versus interviews. [30]

Fjord provides a commercial contrast: it used deeper Live interviews with a subset of diary participants rather than necessarily interviewing everyone. It also enabled client participation and reusable clips. [51]

### Recommended sequence for the worked example

**Proposal:** keep onboarding/practice lightweight, then run the two substantial interviews as a mid-study clarification and an exit interview. If baseline motivations are central, use baseline plus exit instead. Do not quietly add a third paid research interview because onboarding was poorly designed.

Before each live session, provide a participant-specific briefing: timeline, recent entries, outstanding questions, selected clips, repeated ratings and contact/consent status. The moderator should be able to open source entries alongside the interview. Public material establishes Discuss's response-to-live scheduling and EthOS's session dashboard/side chat, but not a universally available synchronised diary viewer across vendors. [11][60]

Book the two interview windows early, while leaving specific slots reschedulable. Use local time plus calendar invitations, a tech check, a clear lateness policy and separate interview payment milestones. Recollective documents reminders to schedule, missed meetings and rescheduling notifications; EthOS documents participant-controlled rescheduling/cancellation and calendar files. [6][60]

**Value split:** no defensible percentage allocation between async and live was established. Test it in pilots: record what decisions can be supported from diary evidence alone, then what additional explanations or changes arise during live follow-up. This evaluates marginal value without claiming that two methods are interchangeable.

**Decision:** support diary-to-live continuity in the MVP, but challenge whether every participant needs both interviews in every future study.

## 11. Build, Partner Or Managed-only

### Published precedents show different routes, not comparable returns

**Build:** Outset's dated diary launch is a clear example of an AI interview platform extending into longitudinal research. Its published outcome is feature availability and integrated operation, not disclosed retention or expansion revenue. [16]

**Managed orchestration:** UserTesting's current documentation says customers historically use Professional Services and recommends involving them because diary stages and dropout create variability. It still documents researcher-managed tests, contributor lists and messages. This is evidence that a large research platform can support the method without making every step a turnkey diary product. [21]

**Case: Recollective demonstrates a partnership-compatible boundary.** Recollective publishes an SSO API for creating/authenticating users, webhooks for participant events, and a no-code Qualtrics integration mapping survey data to participant properties. It also lists Studio by buzzback within its partner ecosystem for communities, diaries and mobile ethnography. [54][47]

That is useful evidence of a real integration route, but not proof of an unrestricted task/media API or an OEM resale licence. Custom branding, SSO and full white-labelling are different commercial and technical propositions. A partnership must settle media export, rights, deletion, support ownership and participant experience, not just login.

### Decision framework

| Criterion | Build | Partner | Managed-only / managed-first |
|---|---|---|---|
| Demand | Best if frequent and repeatable across customers | Useful for irregular or specialist demand | Suitable while scope and willingness to pay remain uncertain |
| Differentiation | Maximum control over video/live/Compass continuity | Borrow mature fieldwork; differentiate analysis/service | Research design and delivery quality |
| Engineering | Highest initial and ongoing burden | Integration, data mapping and vendor-change burden | Smaller internal tools; more delivery labour |
| Participant experience | Can be coherent, but must be built and supported | Mature capture, potentially fragmented accounts | Human recovery can compensate for gaps, not unlimited scale |
| Economics | Potential operating leverage at sufficient volume | Licence/resale costs and margin sharing | Labour-sensitive; straightforward to measure by project |
| Control | Roadmap, data model and UX control | Supplier dependency and contract constraints | Operational control; less product automation |

**Takeaway:** partnership is not automatically cheap, and managed delivery is not automatically unscalable. Both depend on the boundary between reusable software and human exception handling.

**Planning estimates:** a managed offer with basic internal tooling could be readied in **2-4 weeks**, plus recruitment and the diary period. A partner-led pilot might require **4-8 weeks**, subject to contracting and configuration. Deeper integration could take longer; no implementation estimate is credible before confirming API scope and media rights. These are planning assumptions, not vendor commitments.

**Partner shortlist:** Recollective for documented integrations and branded async/live research; Indeemo for contextual mobile/offline capture; EthOS for diaries plus native IDIs. Public task/media APIs, sublicensing and complete white-label rights were not established for all three. Dscout should be the benchmark even if no partnership is pursued. [54][18][49][60]

For managed-only delivery, prioritise roster import, batch task creation, schedule templates, contact logs, exception queues, payment reconciliation, linked interview briefs and exportable timelines.

**Decision:** pursue managed-first with a parallel partner evaluation. Keep the native build modular so the same cohort layer can eventually orchestrate Voxpopme capture or a partner.

## 12. Edge Cases, Failure Modes And Risks

### The strongest failure case is already in the brief

The supplied account says Voxpopme previously stopped diary attempts because of drop-off, manual set-up and missing reminders/re-invites. That is an internal operational failure case, not evidence that customers do not value longitudinal research.

The danger is rebuilding the visible feature while leaving the same failure mechanisms intact. Adding recurring invitations without persistent identity, recovery workflows and support ownership can reproduce the original service burden behind a new interface. A credible relaunch needs evidence that those mechanisms have changed.

No sufficiently documented named case of a competitor quietly deprecating diary features was established. It would be misleading to present plausible reasons as proven vendor history. Current UserTesting guidance and Recollective reviewer complaints do, however, show that orchestration and notification/support problems persist even on established platforms. [21][39]

### Production failure register

| Failure | Research consequence | Recommended response |
|---|---|---|
| Participant leaves on day 3 of 21 | Shortened trajectory; possible attrition bias | Retain valid early evidence, record reason, pay according to agreed milestones; do not fabricate later observations |
| Replacement starts on day 4 | Different exposure and baseline | Flag a new/staggered cohort; exclude from incompatible matched comparisons |
| Video recorded but not uploaded | Event exists but is operationally invisible | Save/retry where supported; distinguish capture from server receipt; offer support |
| Reminder sent after submission | Loss of trust and support traffic | Check current state at send time; suppress duplicate messages |
| Task edited mid-fieldwork | Responses no longer directly comparable | Version the task and preserve which version each person saw |
| Survey anti-duplication blocks repeat entry | Legitimate diary participant is rejected | Deduplicate per task occurrence, not once per entire study |
| Panel account becomes unavailable | Apparent unexplained attrition | Supplier escalation and account-status reason code; Prolific documents this risk. [69] |
| Sensitive people or locations appear in video | Privacy exposure beyond the recruited person | Clear capture instructions, restricted access and redaction workflow |
| AI repeatedly probes poor or sensitive answers | Unequal burden and participant discomfort | Probe caps, opt-out and researcher escalation |
| Live interview no-show | Lost moderator slot and incomplete study bundle | Booking confirmation, reminders, rescheduling and separate diary/interview completion status |

**Takeaway:** the product needs a visible exception state for each failure. Otherwise every exception becomes a private spreadsheet, an unanswered email or a misleading metric.

The support load includes app/browser permissions, device changes, storage, low bandwidth, confusing prompts, payment questions, weekend deadlines, client observers and late interview cancellations. Indeemo's documented local saving and Discuss's upload warning show why reliability cannot be treated as a marginal UI issue. [49][11]

**Contrarian inference:** the most dangerous commercial assumption is that every diary request represents recurring software demand. An agency may need one bespoke study; a brand may primarily want a managed product trial; a churned customer may have needed Dscout's recruitment and operational maturity as much as its diary label. The brief does not establish the counterfactual.

Measure paid study conversion, repeat bookings, eligible task completion, full bundle completion, reminder delivery failures, support minutes per participant-week, researcher administration hours, incentive disputes, direct contribution and incremental decision value from live follow-up. Keep launch denominators fixed and report withdrawals rather than removing them to improve apparent completion.

**Decision:** make operational effort and repeat purchase co-equal success metrics with participant completion. A service that completes only because researchers chase everyone manually has not yet demonstrated a self-serve product.

## Synthesis: What The Different Approaches Reveal

| Approach / major examples | Mechanism | Scope | Main trade-off | Evidence and time horizon |
|---|---|---|---|---|
| **Specialist diary operations: Dscout, Indeemo, Recollective** | Cohorts, repeated activities, prompts and researcher intervention. [5][49][6] | Longitudinal collection and fieldwork; live capability varies | More complete operational model, but price/integration dependence | Current product documentation and cases; commercial retention effects undisclosed |
| **Configurable research platforms: Qualtrics, UserTesting, Maze, Lookback, Discuss, EthOS** | Different combinations of repeat surveys/sessions, task workflows, participant management and live interviews. [24][21][26][2][11][60] | From DIY longitudinal sequences to native diaries | Reuse existing licences, but operational completeness differs materially | Current documentation; do not generalise one platform's workflow to the whole group |
| **Repository: Dovetail** | Import, organise and analyse evidence. [62] | Downstream synthesis and sharing | Stronger evidence access does not solve fieldwork | Current product/pricing documentation |
| **AI-native: Outset; Listen Labs as an adjacent interview platform** | AI conversations and rapid synthesis; Outset additionally documents diary cohorts/rounds. [16][72] | Faster moderation and analysis | New capability does not establish long-term participant retention or safe memory | Recent launch evidence; independent diary outcome evidence limited |
| **Voxpopme managed-first proposal** | Human-led delivery supported by reusable cohort/task controls | Bounded diary/live studies for existing buyers | Lower initial commitment but continued delivery labour | Must be tested through paid pilots rather than assumed |

**Takeaway:** this is not a choice between old diaries and new AI. It is a choice about who owns longitudinal coordination, participant recovery and the interpretation of change.

Three tensions determine the strategy.

First, **research validity and participant convenience can diverge**. More flexible late entries improve apparent completion but weaken in-the-moment claims. More probing improves individual depth but changes burden and comparability. The right response is explicit provenance and controlled flexibility, not maximal automation.

Second, **owned audiences reduce one dependency while increasing another**. They can simplify recontact permissions and recruitment logistics, but success may rely on the customer's existing relationship with participants. A successful owned-cohort pilot does not automatically prove feasibility for third-party panel traffic.

Third, **AI reduces one cost centre while exposing another**. Even if analysis becomes faster, recruitment, support, payment disputes and live scheduling remain. The published AI comparison's speed/interpretation divergence is a reason to redirect saved effort towards better fieldwork and participant-level checking, not assume the whole study becomes nearly free. [63]

The strongest strategic position is therefore selective: retain Voxpopme's existing video, live and analysis workflow where it adds value; use a specialist when offline capture or complex fieldwork matters; and build only the reusable coordination layer that paid studies demonstrate customers need.

## Five-Minute Product-Lead Summary

**The opportunity.** Customers are asking for a coherent longitudinal service, not necessarily a new survey format. The supplied requests and churn example justify action, but do not yet establish a large recurring software market. The broad global insights industry is substantial, while the diary-specific addressable market remains unquantified. [48]

**The product insight.** A diary's defining asset is a stable participant thread: what happened, when, under which task, with which missing periods and follow-up. Video capture already exists in the brief. Cohort membership, assignments, re-invitation, progress and exception handling are the more important missing capabilities.

**The competitive bar.** Dscout provides configurable pacing and operational controls. Indeemo demonstrates contextual capture with saved on-device entries. Recollective documents detailed notifications and participant intervention. Outset has now added AI-moderated diary rounds. Repeating a Voxpopme project without equivalent continuity would be a weak relaunch. [5][49][6][16]

**The participant insight.** There is no defensible universal completion benchmark for this video study. EMA assessment compliance, panel wave retention and a vendor's project completion claim measure different things. Good instructions, tested capture, appropriate payments and real researcher attention matter; the ideal reminder frequency remains a pilot question. [22][20][53][70]

**The economics.** The central 16-person scenario contains **224 diary entries and 32 interviews**, calculated. Applying published Dscout baselines to separate activities and 30-minute interviews produces **$3,840 in incentives**, before recruitment and software. A transparent managed planning example totals approximately **$15,236**, but this is an assumption-based estimate, not a market quotation. Live interview duration and actual supplier terms are major sensitivities. [1]

**The implementation risk.** A one-off survey data model can block legitimate repeats, duplicate payments, erase task versions and lose the participant's history. A scheduling service does not resolve research-specific time-zone rules. Upload failure, missed reminders and account-access problems need observable recovery paths. [27][69]

**The near-term action.** Run paid managed pilots using a common study template and record actual operational work. In parallel, price the same study with Recollective, Indeemo and EthOS, with Dscout as the benchmark. Ask for a participant-side demonstration, not just a researcher dashboard.

**Suggested discovery gate, not a market benchmark:** secure prepaid pilots from at least **three independent customers**, with at least **two placing a second diary order**, before authorising broad self-serve work. Set a minimum contribution requirement with finance and measure whether administration hours fall across repeated studies. A paid first study proves interest; a second purchase with acceptable delivery effort is stronger evidence of a product opportunity.

**The decision to avoid.** Do not choose permanent managed-only because the old implementation failed, and do not choose full build because several large customers asked. First determine whether the repeatable value sits in native workflow continuity, specialist capture, or the research team's delivery expertise.

## Recommended MVP For The Worked Example

**Scope:** 8-20 participants; 12-15 tasks; one-to-three-week fieldwork; two live interviews per participant. These are the supplied requirements, not proposed expansion targets.

### MVP: reliability and continuity first

1. **One study and one cohort.** Persistent participant ID; supplier/BYO identifiers; consent and contact preferences; explicit enrolled/active/withdrawn/excluded states.
2. **Template-based task plan.** Create 12-15 assignments with opening times, deadlines, participant-local time zone, expected effort and a schedule preview. Support one simple interval/task-based design before complex branching.
3. **Participant home.** See current tasks, due dates, completed entries, interview bookings, payment milestones and a clear support route.
4. **Existing video capture plus lower-burden alternatives.** Permit photo/text where the research question allows; use a practice upload. Preserve drafts and show upload state wherever technically feasible.
5. **Reliable invitations and reminders.** Email initially, opted-in SMS where operationally appropriate; delivery logs, quiet hours, completion suppression, manual resend and access recovery. Never rely solely on push.
6. **Researcher exception dashboard.** Participant x task status; failed uploads; bounced invitations; late entries; non-response; manual extension and audited removal.
7. **Explicit partial-completion and payment rules.** Milestone ledger; reconciliation/export; no duplicate payment for retried uploads; separate live and diary obligations.
8. **Two linked Sessions bookings.** Stable identity, calendar invitation, rescheduling, tech check, interview status and participant evidence briefing.
9. **Participant timeline and evidence export.** Entry/task/date links, source video, transcript, missingness and interview links. Compass can summarise within-person patterns with traceable evidence; Voxpopme already positions AI analysis and searchable insights as core capabilities. [73]
10. **Basic governance and observability.** Role-based client access, retention controls, consent records, task versions, event logs and documented support ownership.

**MVP trade-off:** this should initially be an assisted product used by the services team and selected customers, not an unrestricted self-serve launch. If a pilot depends on offline supermarket or workshop capture, use a specialist rather than treating unsupported offline behaviour as an acceptable edge case. Indeemo documents on-device saving for precisely this situation. [49]

### Later: only after the core workflow earns its complexity

- Native/offline-first capture and background upload recovery.
- Event-triggered tasks, branching and complex rolling cohorts.
- More markets, languages and notification channels.
- Automated supplier recontact and payout integrations.
- Agency multi-client administration and deeper branding.
- Participant-aware AI moderation across rounds, with controlled memory and probe budgets.
- Advanced journey maps, theme evolution and matched repeated-measure views.
- Broader APIs, partner orchestration and reusable study programmes.

## Provisional View And The Three Facts That Would Change It

**Choose managed-first, with selective internal build and a parallel specialist-partner trial. Do not yet commit to full self-serve, and do not make managed-only a permanent strategic constraint.**

Build the reusable cohort, task, reminder, progress and timeline layer because it addresses the failures described in the brief and can improve managed delivery immediately. Reuse existing capture, Sessions and Compass. Compare partner delivery before investing in native offline apps, complex scheduling or cross-supplier recontact. Recollective's published integrations make it a practical technical discussion; Indeemo's capture model and EthOS's native IDIs offer different useful benchmarks. [54][49][60]

The **three facts most likely to change this view** are:

1. **Repeat paid demand and attributable account value.** If several customers repeatedly buy substantially the same diary workflow, and renewal/win-loss evidence shows native integration materially changes buying decisions, accelerate a bounded self-serve build. If demand remains occasional and highly bespoke, favour service delivery.
2. **Actual unit economics and support intensity.** If pilots show acceptable completion without sustained manual chasing, declining administration hours and attractive contribution after all direct costs, building becomes more credible. If exceptions remain high, a partner or explicitly premium managed model is more defensible.
3. **Supplier and partner feasibility.** Written permission for affordable repeated contact, persistent identity and consented media use would remove a major constraint. Conversely, an attractive partner offer with adequate data access, support and participant continuity could make a large native build unnecessary. Public integration documentation alone does not settle those commercial rights. [54]

**Bottom line:** prove that Voxpopme can deliver a repeatable longitudinal relationship, not merely repeat a video survey. That is the capability customers will experience and the cost the business will carry.

## References

1. *Recommended study incentives*. https://help.dscout.com/study-basics/design-a-study/recommended-study-incentives
2. *Diary Studies in Lookback | Lookback Help*. http://help.lookback.io/en/articles/3156562-diary-studies-in-lookback
3. *Diary Studies (Video) - NN/G*. https://www.nngroup.com/videos/diary-studies/
4. *Qualitative + Quantitative Research & Analytics Software*. https://www.qualtrics.com/en-au/strategy/research/qualitative-quantitative
5. *Diary Studies For Longitudinal UX Research | Dscout*. https://www.dscout.com/platform/methods/diary-studies
6. *Overview of Automatic Notifications for Participants - Recollective Knowledge Base*. https://helpdesk.recollective.com/article/367-overview-of-automatic-notifications-for-participants
7. *EthOS Pricing Plans | Tailored Subscription Options for All Organization Sizes*. https://ethosapp.com/pricing
8. *Diary Study: Definition, Methods, and How to Run One*. https://dovetail.com/research/diary-study
9. *Diary Methods — Sage Research Methods Community*. https://researchmethodscommunity.sagepub.com/blog/diary-methods
10. *Diary Studies: Understanding Long-Term User Behavior and Experiences - NN/G*. https://www.nngroup.com/articles/diary-studies
11. *Self-Paced Activities: A Guide for Researchers – Discuss Help Center*. https://discussio.zendesk.com/hc/en-gb/articles/4625013220753-Self-Paced-Activities-A-Guide-for-Researchers
12. *Evaluation of Pressing Issues in Ecological Momentary Assessment | Annual Reviews*. https://www.annualreviews.org/content/journals/10.1146/annurev-clinpsy-080921-083128
13. *MRS Guide to Observers’ Legal & Ethical Responsibilities (For those viewing or listening to research) & Viewing Facilities - Commitments*. https://www.mrs.org.uk/pdf/Guide%20to%20Observers%20Legal%20%20Ethical%20Responsibilities%20%28with%20Committments%20to....pdf
14. *Prolific's payment model | Prolific Research*. https://researcher-help.prolific.com/en/articles/445230-prolific-s-payment-model
15. *Maze Pricing & Plans | Consolidate product research*. https://maze.co/pricing?source=comparison_pages
16. *Introducing Diary Studies | Outset*. https://outset.ai/resources/blog/diary-studies
17. *How much should I pay for diary studies?*. https://help.dscout.com/diary-studies/what-are-diary-studies-in-dscout/how-much-should-i-pay-for-diary-studies
18. *Pricing | Recollective*. https://www.recollective.com/pricing
19. *Indeemo | AI-Powered In-the-Moment Video Research Platform*. https://indeemo.com/
20. *How to retain participants in longitudinal studies | Prolific*. https://www.prolific.com/resources/how-to-maximise-retention-in-longitudinal-studies-reducing-attrition-and-dropout-across-multi-wave-studies
21. *Diary studies with UserTesting – Knowledge Base Home*. https://help.usertesting.com/hc/en-us/articles/11880443395997-Diary-studies-with-UserTesting
22. *Ecological Momentary Assessment: A Meta-Analysis on Designs, Samples, and Compliance Across Research Fields*. https://journals.sagepub.com/doi/pdf/10.1177/10731911211067538
23. *Dscout Pricing | Flexible Plans for Powerful UX Research*. https://dscout.com/pricing
24. *Building Workflows - Qualtrics*. https://www.qualtrics.com/support/survey-platform/actions-page/building-workflows
25. *Survey Response Task - Qualtrics*. https://www.qualtrics.com/support/survey-platform/actions-page/tasks/survey-response-task
26. *Conducting diary studies with Maze | Maze Knowledge Base*. https://help.maze.co/articles/7194288697-conducting-diary-studies-with-maze
27. *Schedule types in EventBridge Scheduler - EventBridge Scheduler*. https://docs.aws.amazon.com/scheduler/latest/UserGuide/schedule-types.html
28. *Tracking Participant Progress - Recollective Knowledge Base*. https://helpdesk.recollective.com/article/181-tracking-participant-progress
29. *ESOMAR 37*. https://tolunacorporate.com/wp-content/uploads/2025/08/ESOMAR-37_v2_20250715.pdf.pdf
30. *Diary-interview studies: longitudinal, flexible qualitative research design | Family Practice | Oxford Academic*. https://academic.oup.com/fampra/article/39/5/996/6574305
31. *Lookback Pricing*. https://lookback.io/pricing
32. *Activities Report - Recollective Knowledge Base*. https://helpdesk.recollective.com/article/73-activities-report
33. *Participant Management | Maze*. https://maze.co/platform/reach
34. *California Consumer Privacy Act (CCPA) | State of California - Department of Justice - Office of the Attorney General*. https://oag.ca.gov/privacy/ccpa
35. *How do we process biometric data lawfully? | ICO*. https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/biometric-data-guidance-biometric-recognition/how-do-we-process-biometric-data-lawfully/
36. *Biometric recognition | ICO*. https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/biometric-data-guidance-biometric-recognition/biometric-recognition/
37. *Discuss Reviews 2026: Details, Pricing, & Features*. https://www.g2.com/products/discuss/reviews
38. *UserTesting Pros and Cons | User Likes & Dislikes*. https://www.g2.com/products/usertesting/reviews?qs=pros-and-cons
39. *Recollective Reviews 2025: Details, Pricing, & Features | G2*. https://www.g2.com/products/recollective/reviews
40. *Maze Reviews 2026: Details, Pricing, & Features*. https://www.g2.com/products/maze-maze/reviews
41. *Qualtrics Market Research Reviews & Product Details*. https://www.g2.com/products/qualtrics-market-research/reviews
42. *Dscout Pros and Cons | User Likes & Dislikes*. https://www.g2.com/products/dscout/reviews?qs=pros-and-cons
43. *Dovetail Pros and Cons | User Likes & Dislikes - G2*. https://www.g2.com/products/dovetail-research-pty-ltd-dovetail/reviews?qs=pros-and-cons
44. *ethos Software Pricing, Alternatives & More 2026 | Capterra*. https://www.capterra.com/p/10020044/ethos
45. *Lookback Products | Read 21 Reviews on G2*. https://www.g2.com/sellers/lookback
46. [
      Indeemo Pricing, Reviews & Features - Capterra New Zealand 2026
    ](https://www.capterra.co.nz/software/205445/indeemo)
47. *Partners | Recollective*. https://www.recollective.com/partners
48. *Global Market Research 2025*. https://www.esomar.org/publications/global-market-research-2025
49. *The Respondent Experience: A Guide for Researchers*. https://help.indeemo.com/moderator-resources/the-respondent-experience-walkthrough
50. *on Market, Opinion and Social Research and Data Analytics*. https://standards.esomar.org/assets/documents/icc-esomar-code-2025.pdf
51. *How Fjord Mixed Diary and Live for Iterative Insights - Dscout*. https://dscout.com/customers/fjord-case-study
52. *Insights On-the-Go: Mobile Diary Studies by EthosApp*. https://ethosapp.com/mobile-diary-studies
53. *Path to Purchase Research via a Mobile Diary Study — Indeemo*. https://indeemo.com/mobile-diary-case-study
54. *Integrations | Recollective*. https://www.recollective.com/integrations
55. *What is your pricing? | Prolific Research*. https://researcher-help.prolific.com/en/articles/445239-what-is-your-pricing
56. *Diary studies, a double‐edged sword? An experimental ...*. https://onlinelibrary.wiley.com/doi/full/10.1002/job.2633
57. *Longitudinal Diary Study - best tools and recruitment ...*. https://www.reddit.com/r/UXResearch/comments/1al17mo/longitudinal_diary_study_best_tools_and/
58. *  Web Push for Web Apps on iOS and iPadOS | WebKit*. https://webkit.org/blog/13878/web-push-for-web-apps-on-ios-and-ipados
59. *Does anyone else prefer to *only* do live over diary ...*. https://www.reddit.com/r/dscout/comments/1sd6l4x/does_anyone_else_prefer_to_only_do_live_over/
60. *In-Depth Interview (IDI) Software & Platform | EthOS*. https://ethosapp.com/in-depth-interviews
61. *REGULATION  (EU)  2016/  679  OF  THE  EUROPEAN  PARLIAMENT  AND  OF  THE  COUNCIL  -  of  27  April  2016  -  on  the  protection  of  natural  persons  with  regard  to  the  processing  of  personal  data  and  on  the  free  movement  of  such  data,  and  repealing  Directive 95/  46/  EC  (General  Data  Protection  Regulation)*. https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0679
62. *Pricing | Dovetail*. https://dovetail.com/pricing
63. *JMIR AI - Comparing the Efficacy and Efficiency of Human and Generative AI: Qualitative Thematic Analyses*. https://ai.jmir.org/2024/1/e54482
64. *Using the framework method for the analysis of qualitative data in multi-disciplinary health research | BMC Medical Research Methodology | Springer Nature Link*. https://link.springer.com/article/10.1186/1471-2288-13-117
65. *Discuss Reviews 2026: Details, Pricing, & Features | G2*. https://www.g2.com/products/discuss/reviews?sort=lowest_rating
66. *Consent | ICO*. https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/consent?patch=8&template=pdf
67. *Best AI Research Platforms for 2026: 14 Platforms Compared*. https://listenlabs.com/blog/top-ai-research-platforms
68. *Using the framework method for the analysis of qualitative ...*. https://pubmed.ncbi.nlm.nih.gov/24047204
69. *Why participants get banned | Prolific*. https://www.prolific.com/resources/why-participants-get-banned
70. *6 Tips for Better Participant Engagement in Diary Studies - NN/G*. https://www.nngroup.com/articles/better-diary-studies
71. *Sony Music Entertainment: using Indeemo as an alternative to online research communities — Indeemo*. https://indeemo.com/video/sony
72. *Listen Labs • Trusted AI Research for Leading Brands*. https://listenlabs.com/
73. *Consumer Intelligence Platform | Voxpopme*. https://www.voxpopme.com/