Use case 1: founders explaining product judgment
Good source material: a product page, launch post, roadmap note, customer-safe objection, demo, architecture decision, or founder memo.
A founder session should reveal why a product works the way it does. Questions might include: which option did you reject, what evidence changed the roadmap, what trade-off did the team accept, what does the product deliberately not do, what would make you reverse the decision, and which buyer objection is reasonable?
Example output: a founder explains why the team removed an automated recommendation feature. The useful clip is not "we put users first." It is the answer that names the pilot observation, rejected alternative, current product mechanic, and remaining limitation.
Limitation: founder authority is interested authority. Product claims still need documentation, accurate dates, and appropriate company review. A founder's confidence is not independent validation.
Use case 2: operators preserving decision principles
Good source material: a postmortem, process map, project brief, internal playbook, incident timeline, before-and-after workflow, or retrospective notes.
Operators often hold knowledge that disappears into delivery. The interview should surface the principle behind a choice. Questions might include: what broke first, what signal did the dashboard or workflow miss, which workaround became too expensive, what does an experienced operator notice earlier, when does the standard process fail, and what changed after the incident?
Example output: an operations lead explains why a team replaced a single approval queue with risk-based routing. The clip shows the bottleneck, decision criterion, and exception rather than presenting "move faster" as advice.
Limitation: operational stories often contain customer data, colleague mistakes, security details, or confidential metrics. The most specific version is not always safe to publish. An internal source trail and a public clip may need different levels of detail.
Use case 3: consultants making diagnosis visible
Good source material: a diagnostic framework, workshop notes, published essay, proposal structure, recurring prospect question, client-safe pattern, or teaching deck.
A consultant's value is often in the frame they use before giving advice. Questions might include: what does the client think the problem is, what pattern do you see instead, which two legitimate needs are in tension, what evidence changes your diagnosis, when does your framework mislead, and what should a buyer ask before hiring help?
Example output: a consultant explains that a "communication problem" is sometimes an unresolved decision-rights problem. The clip offers a test question and names cases where the frame does not apply.
Limitation: do not turn one client story into a market claim. Get permission, anonymise responsibly, and avoid presenting public content as personalised legal, medical, financial, or other regulated advice.
Use case 4: researchers translating evidence responsibly
Good source material: a paper, preprint, dataset, research summary, methods note, conference talk, or public report.
The session should keep the claim, method, meaning, and uncertainty connected. Questions might include: what was the research question, what does the method allow you to claim, which result surprised you, what does the study not establish, what do experts disagree about, how have practitioners misused the finding, and where can the audience inspect the source?
Example output: a researcher explains why an observed association should not be described as causation, then gives a situated example of what a practitioner can cautiously test.
Limitation: REC does not perform peer review, verify a dataset, or replace subject-matter editing. A transcript and human face make a claim traceable, not automatically true.
The shared source-to-clip workflow
Across all four roles: bring a source and give the session something concrete. Define the audience and decide who needs the answer and why. Record the reasoning with questions that ask for evidence, example, decision, and limit.
Review the transcript, correct facts, and remove unsafe material. Select a grounded highlight with enough context for the answer to remain accurate. Choose the format, because some answers need a full article or documentation rather than a short clip. Publish with provenance and link the deeper source where appropriate.
Fit checklist
REC is likely a good fit if you know the subject from direct work, your source material contains real decisions or evidence, a guided question is easier than a blank-camera monologue, you want a transcript and traceable clip candidates, you are willing to review the output, and your goal is useful source material rather than synthetic presence.
It may be a poor fit if you need an AI avatar, fully scripted commercial, multi-person remote podcast studio, automatic social campaign, or guaranteed performance.
What REC actually contributes
REC researches the context the user supplies, prepares a guided solo on-camera interview, records the person's answers, produces a transcript, and helps surface grounded highlights that the user can turn into clips.
It does not create the founder's decision, operator's experience, consultant's diagnosis, or researcher's evidence. AI prepares; the person authors.
Choose the use case closest to your work. Bring one source object and one question your audience genuinely needs answered. That is enough to start a useful session.