Turn spoken product ideas into researched concept notes

Why use this

1. A founder recording an idea may speak loosely about a user problem, possible features and assumptions about competitors. A clean written note can accidentally make tentative thoughts look like settled requirements or verified market facts.

2. A concept note could preserve the original idea while separating research evidence, open questions and a proposed first scope. The owner could decide whether the concept deserves more investigation without losing uncertainty during transcription and organization.

Why an agent / simpler alternative

Useful judgment

Structure an informal idea and distinguish the speaker’s intent from editorial interpretation.

Simpler alternative

Use a transcript and simple note template when no research or scope analysis is needed.

Unsuitable when

The concept relies on misunderstood audio or unsupported claims of market novelty.

Proposed inputs

1. Name

   Authorized voice-note transcript

   Owner

   Idea owner

   Minimum scope

   One idea with uncertain words marked

   Quality check

   Confirm important names, constraints and the speaker’s intended problem.

2. Name

   Research scope and supplied comparisons

   Owner

   Owner

   Minimum scope

   Approved competitor questions and relevant evidence excerpts

   Quality check

   Separate current observed features from the owner’s impressions.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only transcript and supplied comparison material; private draft note.

Compatibility unknowns

1. Unknown: exact runtime, transcription quality, research access and Obsidian write support.

External actions requiring approval

1. Uploading voice recordings, expanding research, sharing the concept or changing shared notes.

Expected deliverable and review checks

Proposed artifact

Tagged concept note with problem statement, comparison evidence and explicitly proposed MVP boundaries.

Critical checks

1. Uncertain transcription does not become a definite requirement.

2. Competitive facts and original hypotheses remain labelled separately.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A misheard product name points research at the wrong competitor.

   Why it matters

   The concept comparison could be irrelevant.

   Proposed response

   Confirm the name before using it as a research anchor.

2. Signal

   An absent feature in a small evidence sample becomes “nobody does this.”

   Why it matters

   The note may overstate novelty.

   Proposed response

   Limit the claim to inspected evidence and retain the broader question.

Effort and cost — unknown

Setup work

1. Clarify the idea and bound comparison questions.

Ongoing review

1. Review scope assumptions and refresh evidence before investment.

Unknowns

1. Unknown: market coverage, feasibility, research cost and demand.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

An invented transcript includes an ambiguous competitor name and a speculative feature list.

Acceptance checks

1. The name remains unresolved.

2. Features are proposed scope options rather than confirmed requirements.

Stop conditions

1. The owner’s intent or research authorization cannot be established.

Limits

1. Editorial concept development; no competitive advantage, feasibility or demand is established.