Online bulletin boards are still one of the highest-signal qualitative formats: asynchronous, multi-day, media-rich, and friendly to real life. The software market is crowded, and demos tend to look similar. This guide gives you a way to see past the demo: first decide what you are actually buying, then check the capabilities that matter, then ask RFP questions where you know what a good answer sounds like.
Step 1: Confirm the research object
Before comparing features, name the thing you need to run. A multi-day board or diary (people answering over several days with media) is different from a live focus group, a survey, or a long-lived community. Buying the wrong object is the most expensive mistake, because no feature set rescues it.
- Multi-day board or diary: asynchronous, day-structured, media-rich. CoLab is built for this.
- Live groups or interviews: synchronous video. A different tool class.
- Large-scale measurement: a survey platform.
- Long-term panel or community: relationship-first software.
Step 2: Must-have capabilities, and why each matters
Swipe to see all columns
| Capability | Why it matters |
|---|---|
| Day-based structure with unlock rules | Controls pacing and prevents respondents from skipping ahead and answering everything at once. |
| Mixed question types (rating, open-end, upload, camera photo, video, audio) | A single study often needs several evidence types; missing one forces workarounds. |
| Stimulus presentation | You must control what people see and when, especially for concept or creative testing. |
| Mobile UX without an app install | Install friction is one of the biggest causes of Day 1 dropout. |
| Live fieldwork visibility | Seeing who is on and how far along lets you nudge before people drift. |
| Transcripts for media | Without them, analysis means scrubbing video by hand. |
| Themes available before close | Lets you probe thin areas while respondents are still active. |
| Client-readable exports | Outputs must be usable by stakeholders who never log in. |
| Privacy, NDA, and data request paths | Required for legal comfort, especially in regulated categories. |
| Respondent help that is not only email | Media days fail quietly without help at the moment of need. |
Step 3: RFP questions, with what a good answer looks like
Each question below is followed by an explanation of why you are asking it and what separates a strong vendor answer from a vague one. Use them in your RFP, and score vendors on specificity, not enthusiasm.
RFP questions that separate marketing from product
Step 4: Understand the vendor landscape
Vendors fall into recognizable types. Knowing the type tells you what questions to press on, because each type has predictable strengths and gaps.
Swipe to see all columns
| Vendor | Type | What to probe for the board job |
|---|---|---|
| Recollective | Community-heritage platform | Study authoring speed, analysis timing, respondent experience on phones |
| Sago | Services network | How much control your team has over the board and who owns the methodology |
| Forsta QualBoard | Suite module with long history | Modern authoring, phone experience, and in-field analysis |
| Discuss.io | Live qual platform | Whether it supports multi-day diaries and in-home media at all |
| dscout / Indeemo | Mission or app-based capture | Install friction and fit for structured, guide-driven boards |
| CoLab | AI-native board software | Launch speed, completes, themes in field, and debrief readiness |
Step 5: Run a pilot, not a demo
- 1Choose a real, recent guide with at least one media task.
- 2Time the build from guide to a QA’d live board.
- 3Field to a small group on actual phones, including at least one older Android.
- 4Count support issues and daily drop-off.
- 5Check when a usable theme view first appeared, and whether the raw evidence was one click away.
- 6Ask the client-facing person on your team whether they would present the output as is.
FAQ