Skip to content

fictional idea · Sample content

See a real IdeaClarify report.

A complete fictional example. Unedited and downloadable.

  • Named sources
  • Assumptions labelled
  • Risks stated
  • Reports connected

Product Requirements

5,948 words

A short excerpt. The complete report is one click away.

This PRD translates MentorLoop's Strategy and Personas work into a build-ready v1 specification for a two-person team — one technical co-founder and one part-time contract designer — shipping inside four months with no engineering co-founder. Every requirement below is scoped against that constraint first: if a feature cannot be justified against the core loop (a founder finds a vetted mentor, books an hour, pays, and the mentor gets paid), it is named explicitly in Scope as deferred, not silently dropped.

Executive summary

Overview & Goals

MentorLoop is a two-sided marketplace web application connecting early-stage hardware and deep-tech founders (pre-seed through Series A, concentrated in Boston, the Bay Area, Munich, and Stuttgart) with retired and semi-retired engineers and manufacturing/operations leaders who hold deep domain expertise in design for manufacturability (DFM), supply-chain qualification, EMC/safety certification (UL, CE, FCC), and contract-manufacturer tooling negotiation. Founders search or browse mentor profiles by expertise domain, book a paid hourly session with a specific named mentor, and pay through the platform; mentors set their own rate and availability and receive payout after each completed session, net of MentorLoop's 20% platform fee. v1 is web-only, launching first in the US and Germany, and exists to prove one thing: that a structured, vetted, paid booking marketplace for this specific expertise gap can generate real, repeat, two-sided transaction volume — not just sign-ups on either side.

This v1 must achieve three goals, each directly load-bearing for the go/no-go decision on building the Structured Track package and expanding beyond two markets:

  1. Prove the core transaction loop end to end. A founder must be able to discover a relevant mentor, book them, pay for the session, and (post-session) leave a review, with zero manual intervention from the MentorLoop team for a booking that goes smoothly. Manual intervention should only ever be required for the exception paths (vetting, disputes), not the happy path.
  2. Prove mentor supply-side activation, not just sign-up. It is not enough for retired engineers to create a profile; v1 must show that a meaningful share of approved mentors actually set live availability and accept at least one real booking within their first 60 days on the platform — the single biggest unproven assumption from the Idea Brief's own Key Assumptions section.
  3. Prove the platform can operate its own exception paths at this team's actual capacity. With one technical founder and no dedicated ops hire, mentor vetting and dispute handling must be operable by a single person in well under an hour per case, or the model does not survive past the first few dozen bookings.

Everything in this document is designed to make those three goals measurable within 90 days of launch, not to build every feature the long-term vision implies (see the Structured Track and other deferred items below).

Reasoned analysis

This synthesis is model-generated analysis, not an independently verified fact.

Evidence-labelled section

Success Metrics

Measured across the first 90 days after public launch in the US and Germany:

  • Mentor supply onboarded: at least 25 mentors fully approved and with live, bookable availability (not merely an approved-but-inactive application) by day 90, drawn roughly evenly across the four target metro areas (Boston, Bay Area, Munich, Stuttgart).
  • Mentor activation rate: at least 60% of approved mentors accept and complete at least one real booking within their first 60 days on the platform — the direct test of the Idea Brief's own unproven assumption that retired engineers will actually convert into active, repeat mentors, not just sign up.
  • Bookings completed: at least 120 completed (paid and session-held) sessions in the first 90 days.
  • Gross booking volume (GMV): at least $24,000 in total session payments processed, based on a blended average session price of roughly $200 (within the stated $150-250/hour mentor rate range) across 120 completed bookings.
  • Platform take-rate revenue: at least $4,800 in platform fee revenue (20% of the GMV target above) — a modest but real, non-zero proof that the transaction mechanism itself works end to end, independent of the Structured Track's larger, deferred revenue line.
  • Repeat-booking rate: at least 20% of founders who complete one booking make a second booking (with any mentor) within the 90-day window — the clearest signal that the product delivers ongoing value rather than a single, one-off transaction.
  • Dispute rate: fewer than 8% of completed bookings result in a filed dispute, and of those, a median resolution time under 3 business days — evidence the vetting process (US-11) is doing its job and the manual dispute process (US-12) is operable at this team's actual capacity.
  • Review coverage: at least 70% of completed bookings receive a founder-submitted review, since review density is what makes the marketplace trustworthy to the next prospective founder.
Reasoned analysis

This synthesis is model-generated analysis, not an independently verified fact.

Risk

Needs real-world validation

Needs validation

Several claims here rest on assumptions rather than evidence and should be checked against primary research — customer interviews, live pricing tests, and supply-side outreach — before they are treated as settled.

Next action

What to do next

Reasoned analysis

Carry the confirmed points forward into the next spine phase as input, and treat the open questions above as the first things to test.

Same question, two answers

The same question, answered by a generic chatbot and by IdeaClarify — side by side.

See the comparison

Get this for your idea