Consumer Research
Research engagements where methodology, evidence quality, and defensible findings determine what gets acted on.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Outcome Discovery
Align on the precise research question, target segments, timeline, decision gate, and success signals so the study will produce specific evidence.
Discovery Questions
Quick orientation: where we start
- Tell me briefly which product concept or business decision prompted this research request?
- Who on your team will be the day to day owner of this study, and who will sign the final recommendation?
- When do you need findings in hand to influence your next development or budget gate?
- What metrics or decision rules will you use to say this study changed the plan?
- How confident are you today that the target sample can be recruited within your timeline?
Pin down the one question that changes everything
- Imagine you need to write a single, decision-triggering question for leadership, what is that question?
- Describe the consumer segment and the purchase or usage context that must be present for results to feel credible to your team
- Walk me through the last time you ran a study like this, what went right and what most undermined confidence in the outcomes?
- What would have to be true about the measured lift or effect size for leaders to change a product, price, or go to market plan?
- What single finding, if it does not appear, would make you cancel or delay the initiative?
Where your current knowledge leaves you exposed
- What's the biggest assumption about your customers that this study could prove wrong?
- How often do teams rely on internal surveys or anecdote instead of fresh, recruited samples for decisions like this?
- Point to the internal dataset or metric that most shapes current beliefs and say who maintains it
- When those internal metrics point one way and in depth interviews point another, which do leaders typically trust and why?
- Suppose recruitment misses your core segment by 25 percent, what would cause you to pause or stop the study?
The real consequences if this study misses the mark
- What broken decision or lost opportunity will you be held accountable for if this research does not deliver?
- How much budget or development time is explicitly tied to the outcome of this study?
- List the stakeholder groups who will push back hardest if results contradict current plans
- Tell a recent story when research was dismissed in your organization, what happened and who won the argument?
- Should the timeline slip by more than two weeks, what happens to the product gate or budget decision?
Who else is on your short list
- Identify the suppliers, internal teams, or incumbent approaches you are actively considering instead of engaging an external research partner
- What would have to be true about your current approach for you to stick with it rather than change?
- Has anyone on your team proposed solving this with internal surveys or analytics instead of commissioning field recruitment?
- Select vendor capabilities that would make you switch today
- Assuming an incumbent matches the quota and timeline we propose, what would make you still change vendors?
Constraints that will gate fieldwork
- Select the legal, privacy, or compliance approvals that must be obtained before we can start recruiting
- Do you have sample lists, CRM segments, or first party identifiers we must connect to for recruitment and if so in what formats?
- Name the internal owner who will coordinate logistics, approve screener language, and clear participant incentives
- If an API or secure SFTP is required for data exchange, who owns that system and can they provision access within your target timeline?
- What single operational constraint would force us to pause or cancel fieldwork before it starts?
How this project earns a yes from your leaders
- Beyond p values and surface metrics, what specific evidence would convince leaders to change the plan based on this study?
- Point to the decision gate that will accept our recommendations and tell us who signs that gate
- Upon meeting your target metrics, how quickly could procurement or budget be released?
- What specific acceptance criteria do you require for a 'go' recommendation, for example minimum conversion lift or minimum reachable segment size?
- When the study produces a recommendation you agree with, what internal obstacles could still prevent action and who must be convinced for the change to happen?
-
Research Approach
Translate the buyer's decision needs into a mixed-method design, explaining how quantitative scale and qualitative depth combine to produce usable recommendations.
Solution Experience
- Research Approach Solution Experience
- Confirm the current state and its cost to your team
- You confirm the proposed mixed-method design will produce the segment-level evidence required for the funding decision.
- Deliver a written mixed-method design and sample forecast with screening logic and quota plan within 3 business days.
- You accept the recruitment and quota plan as sufficiently representative to withstand internal review.
- Show the mixed-method design mapped to your decision
- Run a sample feasibility check against proposed recruitment sources and share expected completion dates for fieldwork.
- You agree the timeline meets the development gate or identify the specific adjustments needed to do so.
- Prove the recruitment and quota approach
- Provide the confirmed development gate date and the success signals that will be used to judge recommendations.
- Map the timeline to your development gate and surface risks
- Share any existing screening criteria, segmentation rules, or known exclusionary constraints used in prior studies.
- Validate the design against your needs
- Research Approach Solution Experience
- Research Approach Deck
- Research Approach Brief
- meeting
- slides
- document
-
Study Scope
Define deliverables, recruitment quotas and screens, methodologies (surveys, interviews, ethnography), timelines, and the acceptance criteria for specific recommendations.
Scope Configuration
- Recruit and Screen Target Respondents
- Program and QA Online Survey Instrument
- Field Quantitative Survey
- Tabulate, Weight, and Statistical Test Survey Data
- Code Open-Ended Responses and Thematic Analysis
- Conduct In-Depth Qualitative Interviews
- Moderate Remote Focus Groups
- Conduct Ethnographic Field or Home Visits
- Run Conjoint and Price-Optimization Analysis
- Build Behavioral Segmentation Model
- Integrate and Analyze Third-Party Behavioral Data
- Deliver Executive Findings Deck and One-Page Brief
- Run Cross-Functional Recommendations Workshop
- Provide Raw Data, Codebook, and Analysis Files Export
Scope Questions
Recruit and Screen Target Respondents
- Provide the exact target segments by SKU purchase behavior or loyalty tier you want represented in the sample (for example: weekly buyers of SKU A, lapsed members of loyalty tier Gold)
- How many completed interviews or survey completes do you require per target segment (specify numeric value per segment)
- Specify the inclusion and exclusion screener rules tied to purchase frequency, household size, or payment method (for example: at least two purchases of SKU A in past 90 days; exclude employees of your company)
- List the verification artifacts you will accept for recruitment (for example: recent receipt image, loyalty ID match, POS transaction ID)
- Indicate the geographic and channel constraints for the sample (for example: urban grocery shoppers in Northeast region; online-only shoppers from your e-commerce channel)
- Estimate the expected recruitment lead time for the strictest segment you named (in calendar days)
- Identify any regulatory or privacy constraints that affect recruitment in your category (for example: minors excluded for alcohol, GDPR consent for EU respondents)
- State the minimum sample representativeness threshold you will accept (for example: margin of error at +/- 5%, demographic match to CRM within 5%)
Program and QA Online Survey Instrument
- Provide the final list of product stimuli and packaging images to be used in the survey instrument (file types accepted: PNG, JPG, PDF)
- How long do you want the median respondent experience to be (in minutes) for the online survey to avoid fatigue with choice tasks or concept testing?
- Specify mandatory QA checks we must run before launch tied to question types (for example: minimum 100ms response time per item, attention check on concept slider, forced-choice validation on price tradeoffs)
- List any third-party tracking or tag blockers that must be respected in the survey (for example: no pixel tracking, disable browser fingerprinting for privacy), and whether your legal team requires a consent script
- Indicate the languages and localized phrasing required for item text and response options (for example: English US, Spanish for California sample)
- Identify the data export format you prefer for raw survey responses (for example: CSV with timestamp and panel ID, JSON payload matching codebook)
- Describe any banned question types or sensitive attributes you want removed from the instrument (for example: income band above $200k, health conditions explicit questions)
Field Quantitative Survey
- Provide the fieldwork start and end dates or the acceptable fielding window tied to your product development gate
- Estimate the maximum allowable time-to-complete for fielding the full quota set (for example: all quotas filled within 3 weeks)
- List the panel sources or recruitment partners you prefer or require (for example: loyalty panel, POS recontact list, retailer panel)
- Describe quality-monitoring signals you want tracked in field (for example: soft-launch N=50 review, percent straightliners, attention-check pass rate)
- Identify any quota overflow rules or soft caps you will allow when a segment is hard to fill (for example: allow +/- 10% overflow on age quotas)
- Supply the incentive approach you prefer for this category to hit retention (for example: e-gift card, loyalty points, higher incentive for low-incidence segments)
- Identify your required evidence of completed fieldwork for acceptance (for example: respondent metadata with receipt verification, timestamped screener logs)
Tabulate, Weight, and Statistical Test Survey Data
- Provide the weighting targets and source (for example: CRM purchase distribution by age and region, national census benchmarks) you expect applied to tabulations
- Specify the primary cross-tab breakouts you need in the deliverable (for example: household grocery spend deciles, channel of purchase, SKU choice)
- Identify which statistical tests you require for inference by recommendation (for example: chi-square for choice differences, t-test for mean hedonic scores, ANOVA for multi-group comparisons)
- List the significance thresholds that will define specific differences for your team (for example: p < 0.05, difference > 5 percentage points)
- Describe any post-stratification grouping rules or combined-category logic you want applied (for example: combine low incidence SKUs under "other", collapse age to 18-34/35-54/55+)
- Indicate whether you require documented reproducibility (analysis script and seed) for statistical tests as part of acceptance
Code Open-Ended Responses and Thematic Analysis
- Provide the open-ended prompts that will require coding and note whether verbatim quotes will be attributed to respondent segments (for example: verbatim quotes allowed for loyalty members only)
- Describe the codeframe approach you prefer (for example: inductive initial pass then deductive mapping to brand attributes like taste, packaging, price)
- Specify the minimum inter-coder agreement threshold you require for acceptance of coded themes (for example: Cohen kappa > 0.7)
- List the verbatim output formats you need (for example: top 10 themes with example quotes per segment in XLSX, coded CSV with code IDs)
- Indicate any categorical mappings to business KPIs required (for example: map "taste" mentions to NPS drivers or purchase intent lift)
- Identify any confidentiality rules governing quote use in deliverables (for example: remove retailer names, anonymize city-level data)
Conduct In-Depth Qualitative Interviews
- Provide the interview target profile tied to product use cues (for example: primary grocery shopper, purchaser of premium SKU B in past 60 days)
- Estimate preferred interview length for concept depth and product walkthroughs (for example: 45 minutes with product usage probe)
- Specify whether you require video capture of usage during remote interviews and any consent wording that must appear in the screener
- List stimulus materials you will provide for interviews (for example: physical prototype shipped, high-fidelity mockup, claim language) and shipping constraints
- Indicate whether interviews should be exploratory or semi-structured with a fixed discussion guide and whether you need timestamps mapped to guide sections
- Name the stakeholder who will attend interim interview readouts and the cadence for those check-ins (for example: weekly snapshot during first 10 interviews)
Moderate Remote Focus Groups
- Provide the group composition rules you require (for example: separate sessions by heavy vs light purchasers, max 8 participants per group)
- Estimate the number of sessions and the total participant count you expect for adequate cross-segment coverage
- Specify the stimulus presentation order and whether you require randomized exposure to concepts or price options during groups
- List any recruitment screens unique to focus groups (for example: no prior participation in last 6 months in similar research, must have household grocery spend > $X)
- Indicate the moderator style you prefer (for example: directive elicitation for product attributes, open discussion for attitudinal insight)
- Describe any recording, transcription, or CLT (closed-loop testing) needs for group output and whether verbatim transcripts are required
Conduct Ethnographic Field or Home Visits
- Provide the exact activities you want observed in-home or in-store (for example: unboxing and first use, shopping trip from shelf selection to checkout)
- Estimate the number of visits and geographic spread required to capture behavior across channels and store formats
- Specify any safety, compliance, or retail permissions we must secure prior to visits (for example: retailer filming consent, in-store brand reps approval)
- List the artifacts you require from each visit for acceptance (for example: timestamped video clips, annotated shopper journey maps, photographed receipts)
- Indicate whether you want ethnographers to collect packaging, shelf-position photos, and price tags during in-store visits
- Describe any constraints on participant contact before visits (for example: do not reveal brand name, send neutral scheduling messages)
Run Conjoint and Price-Optimization Analysis
- Provide the attribute list and levels you want tested in conjoint (for example: pack size 8/12/16, price points $2.49/$3.49/$4.49, flavor A/B/C)
- Specify the pricing range and anchor points for price-optimization modeling tied to current list prices or test price ladders
- List the demand curve or revenue objective that defines success for price tests (for example: maximize revenue vs maximize volume)
- Indicate the sample size per conjoint cell you are willing to fund to achieve stable utility estimates
- Describe any simulated market constraints that must be modeled (for example: shelf share caps, competitor price floor, bundle discounts)
- Identify whether you require willingness-to-pay calibration to real purchase data from your CRM or POS for anchor alignment
Build Behavioral Segmentation Model
- Provide the behavioral data fields available for segmentation (for example: purchase frequency, SKU mix, average basket spend, recency days)
- Specify the desired number of segments or the business rule for segment granularity (for example: 3 strategic segments for GTM, or up to 8 micro-segments)
-
Mutual Commit
Finalize commercial terms, data and consent requirements, recruitment guarantees, timelines, and mutual obligations before fieldwork begins.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Data Processing Agreement (DPA)
- Participant Consent & Data Use Agreement
- Recruitment Guarantee Addendum
- Commercial Terms & Payment Schedule
- Timeline & Mutual Acceptance Criteria
- Confidentiality Agreement (NDA)
- Regulatory Compliance Addendum
- Participant Incentive & Disbursement Terms
-
Delivery
Operationalize research fieldwork, recruitment, analysis, and final delivery with readiness checks and configuration locks.
-
Pre-Deployment Readiness
Confirm concrete readiness facts—named stakeholders, recruitment sources, regulatory or legal approvals, and timing constraints the fieldwork depends on.
Pre-Deployment Questions
Environment and access
- Which recruitment sources have been confirmed for this study? (select all that apply — so we know where to route quotas)
- If you selected 'Buyer-provided customer list' or 'Other', who is the named owner responsible for delivering or coordinating that source? (name and role — so we can schedule handoff)
- Are any in-person site visits, facility access, or on-location observations required? (if yes, we will need a site contact and access window)
Data, scripts and acceptance
- Has the final screener, quota plan, and survey/interview script been approved for deployment, or is approval pending?
- Who is the named buyer approver for screener/scripts/incentives (name, role, and preferred contact) — this person will be the sign-off on final materials
- Are there data privacy, consent, or regulatory approvals required for this study (select all that apply)?
- For any approval selected above, what is the current status and expected sign-off date? (brief status and date for each approval) — we schedule fieldwork after these clearances
People and operational ownership
- Please confirm the single primary point of contact (POC) for deployment decisions and the named backup approver (name and role) — this POC will receive daily readiness checks before launch
- Who will own recruitment monitoring and quality control during fieldwork, and who will own incentive procurement/distribution? (name, role, seller or buyer)
Timing, constraints and acceptance
- What is the earliest fieldwork start date the buyer can commit to? (we will not schedule fieldwork before this date)
- Are there blackout windows, embargoes, product launches, or internal decision gates that block fieldwork or delivery? If yes, list date ranges and brief reason so we can avoid scheduling conflicts
- Are minimum recruitment guarantees required (minimum completes per quota)? And will the buyer accept partial quota substitutions if a segment underperforms? (select the single applicable policy)
-
Configuration Details
Lock the exact instruments and execution parameters the team will use—screener logic, quota caps, survey scripts, interview guides, and data export formats.
Configuration Details
Configuration Details — Lock the instruments & execution parameters
- Select the fieldwork data storage region (Default: US-East)
- Select the primary data export format for deliverables (Default: CSV (comma-separated))
Survey Instrument & Screener
- Enter the canonical survey instrument name (format: short filename, e.g., 'PriceConcept_V1')
- Provide the primary screener pass rule as a single Boolean clause (format guidance: use AND/OR, e.g., 'age>=18 AND age<=54 AND purchased_category_last_12mo = true')
Quotas, Recruitment & Interviewing
- Total completed survey target (numeric). Default: 1000 — confirm or specify another value
- List quota cells with their target counts as comma-separated pairs (single value). Example: 'M18-34:250,F18-34:250,HeavyUser:200'
- Enter the canonical interview guide name for qualitative work (format: short filename, e.g., 'IDIs_Pricing_v1')
Consent, Recording & Data Quality
- Select the consent + recording policy to apply to all interviews (choose one). Default: 'Recording allowed; verbal consent recorded'
- Minimum median seconds per question to mark a survey response as valid (numeric). Default: 3 — confirm or specify another value
- Select the data delivery cadence for exports and analytics (Default: Final deliverable only)
-
Fieldwork & Analysis
Execute recruitment and fieldwork, monitor data quality, run analysis, and deliver prioritized findings and recommendations ready for decision gates.
-
-
Success
Review findings against the agreed success signals, capture adoption actions and owners, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Findings Acceptance Review
- Roadmap Endorsement Workshop
- Implementation Readiness Check
- Realization and Follow-up Review
Issues & Enhancements
- Document the go/no-go conditions for the first milestone and distribute to all roadmap stakeholders.
- Schedule the Implementation Readiness Check and share the milestone tracker for status updates.
- Status of implementation blockers
- Implementation blockers resolved count is updated and clearly documented.
- Client-side owners confirm they have the required access and resources to begin the first milestone.
- A clear go/no-go condition for the first milestone is agreed and recorded.
- Update the blocker registry with resolved items and publish the remaining blocker list with resolution dates.
- Confirm data access and measurement artifacts are available and share access details with the tracking owner.
- Reconfirm acceptance criteria from Study Scope
- The count of prioritized initiatives implemented and their early outcome signals are recorded for the quarter.
- Report on implemented initiatives and early outcomes
- Remaining implementation blockers and their planned resolution dates are documented.
- A short list of enhancement requests or follow-up analyses is agreed for the next quarter.
- Publish the quarterly realization report that lists implemented initiatives, outcome evidence, and remaining blockers.
- Log enhancement requests with scope descriptions and estimated effort for prioritization in the next roadmap cycle.
- Set the date and objectives for the next realization review and share the updated milestone tracker.
- The study's findings acceptance rate is documented and linked to the acceptance criteria recorded in Study Scope.
- The count of prioritized initiatives accepted, conditionally accepted, and rejected is recorded.
- A remediation plan for any evidence gaps is agreed with tasks and completion dates.
- Publish the findings acceptance log that records acceptance status for each recommendation and link it to Study Scope acceptance criteria.
- Run the agreed supplementary analyses or sample checks to close identified evidence gaps and report results within the agreed timeframe.
- Circulate a one-page summary of accepted recommendations for internal stakeholder review prior to the roadmap workshop.
- Recap accepted recommendations
- A finalized list of prioritized initiatives is recorded with an agreed count for execution.
- Each prioritized initiative has a named client-side owner assigned and an initial target date.
- Resource gaps that could prevent implementation are identified and have mitigation tasks.
- Publish the prioritized roadmap that lists initiatives, assigned client-side owners, and target completion windows.
- Document identified resource or data gaps and propose mitigation steps with dates for resolution.
- Confirm owner readiness and access
- Present summary of key findings and confidence levels
- Review blocker burn-down since last meeting
- Prioritize initiatives by impact and feasibility
- Assign client-side owners and target dates
- Record acceptance status per recommendation
- Re-check critical data and measurement plans
- Capture enhancement requests and scope changes
- Identify resource or data gaps
- Agree next quarter milestones and tracking cadence
- Agree go/no-go conditions for first milestone
- Surface evidence gaps and remediation plan
- Finalize short-term milestones
- Agree next steps toward roadmap workshop
- Record unresolved risks and mitigation owners