Skip to main content
This example connects the main DeepField workflows in the order you use them. Meridian Coffee is a fictional brand, and the sample content contains no client or participant data. Research brief: Meridian wants to measure appeal for a ready-to-drink cold brew in France. The analysis demo is “Meridian Coffee — Cold Brew Concept Test”; the editable demo is “Meridian Coffee — Packaging exploration.” Both begin with cold-coffee habits and one cold-brew concept at €3.50. The screenshots show synthetic demonstration data, not a completed commercial sample.

​
Before you start

Use the two fictional Meridian studies as orientation. For your own launch, define eligibility and sample targets from your brief; do not treat demonstration response counts as a sample recommendation.

​
Build the questionnaire

In New study, the researcher describes the audience, decision, and required outputs, then attaches the concept brief. The assistant asks for missing details before creating the first questionnaire draft. In Create, the researcher reviews every section and question. The saved example asks about drinking frequency, purchase location, monthly spend, concept appeal, reasons to buy, purchase intent at €3.50, and barriers. Check that each answer structure fits that measure. Add eligibility screening only when the research brief requires it. The researcher opens Fix problems, resolves an empty option list and a missing question label, then saves the questionnaire. See Start a study, Show stimuli and concepts, and Fix survey problems.

​
Configure the sample

In Quotas, panels & links, the researcher sets the agreed respondent target. The brief, provider instructions, and screening rules define geographic eligibility. Screening rules end the survey for people outside the intended category audience. For a real launch, add quotas only for screening categories actually collected by the questionnaire. The sample-size estimate in Quotas, panels & links and the cost summary on Fieldwork reflect the audience configuration. The researcher checks the smallest reporting group before confirming the total target. See Configure your audience, Screen participants, Set quotas, and Choose a sample size.

​
Test and launch

In Test, the researcher runs Flow coverage and generates a test link. Two manual test sessions cover a qualifying path and a screen-out path. If a route skips an intended question, the researcher returns the study to Draft, fixes the rule, and generates a new test link. After the repeated tests pass, the researcher selects Publish on Fieldwork. Confirmation changes the study directly to Published. See Test and publish a study.

​
Monitor fieldwork

The Fieldwork and Responses views show recruitment progress from different perspectives. Fieldwork compares live fills with the panel and quota targets. Responses shows the individual submissions and their statuses. The researcher filters to completed responses, reviews the first records and their quality results, and checks whether the quota cells are filling at a usable pace. See Monitor responses and Review response quality.

​
Analyze the results

Before generating, the researcher decides whether weighting is required and selects the scheme in the analysis plan. Save and generate builds the plan folder in Charts with that weighting, and the researcher steps through it question by question, reading each base before the values. To compare concept appeal by purchase intent, the researcher builds a crosstab, checks the raw bases, and reads the column-proportion markers. The data assistant is used for a focused follow-up: “Show the main reasons participants hesitated at the stated price and include supporting responses.” See Generate a report, Build a crosstab, Interpret significance, and Ask questions about your data.

​
Prepare and share the output

The researcher files the verified charts in a story folder and selects Generate slides from this folder. After reviewing and approving the proposed storyline, they check each slide’s headline against its chart, replace broad statements with claims supported by the tables, and resolve reviewer comments. The deck is exported to PowerPoint for its final delivery check. A guest link is created with access limited to the intended result surfaces. See Build a slide deck, Export results, and Share a study.

​
Check the result

Trace each delivered claim to its source question, base, and supporting responses. Open the exported files and test the guest view before sharing them.