EARLY MARKET RESEARCH · Workflow idea

Find recurring problems people discuss and turn them into questions worth testing.

Review selected public community discussions, organize recurring frustrations, and prepare early product hypotheses with rough cost and revenue assumptions for later investigation. Respect source rules and participant privacy, avoid copying posts or identifying details, and treat each idea as an unvalidated research prompt—not evidence of demand or a business forecast.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A research topic is selected
Produces
A reviewable list of early product hypotheses, problem themes, and clearly labeled assumptions for further research.
Category
Research & strategy

01 / The starting point

A clear request.
A useful direction.

Public community discussions selected for an appropriate and permitted research purpose

“Organize public discussion themes into tentative product ideas for human assessment, preserving source context and respecting privacy and use restrictions.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps researchers turn recurring public conversations into organized questions for product discovery and validation.

  1. Choose communities and a research question

    Select public discussion spaces and topics that are relevant to a clearly defined research purpose.

  2. Review permitted posts and discussion themes

    Use information in ways allowed by the source and focus on recurring problems rather than identifying individual participants.

  3. Organize possible unmet needs

    Group similar concerns with enough context to understand them without copying personal or distinctive post content.

  4. Prepare early product hypotheses

    Describe a possible solution and label market size, costs, revenue, and feasibility as assumptions that still need evidence.

  5. Review sources, privacy, and next research

    Have a researcher check source permissions and limitations, remove unnecessary personal details, and plan independent validation.

03 / The result

Something useful.
Something to build on.

A reviewable list of early product hypotheses, problem themes, and clearly labeled assumptions for further research.

AmbactiWorkflow folio · 5 steps

Explore startup ideas from community discussions

Research & strategy · Example outcome

The handoff

A reviewable list of early product hypotheses, problem themes, and clearly labeled assumptions for further research.

Keep in mind

Public posts still have context, privacy expectations, and applicable use restrictions. Follow source rules, minimize or remove personal details, avoid reproducing distinctive text, and do not treat discussion volume as representative demand. Cost and revenue figures are hypotheses only; validate them independently before making business decisions.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Define the research purpose and source scope

Choose the communities, topics, and time period that are appropriate for the project.

Follow source rules and privacy expectations

Set limits on collection and reuse, avoid unnecessary identifiers, and define when material should be excluded.

Set a consistent idea and assumption format

Separate observed discussion themes from proposed solutions and unverified cost or revenue estimates.

Assign research and decision reviewers

Name who checks source context and who validates any idea before it informs investment or product decisions.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗