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

Personas

3,477 words

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

This document turns the Idea Brief's target-user paragraph into three people specific enough to write copy for, design an intake form around, and say no to. Where a detail isn't knowable yet (conversion rate, actual booking frequency), it's flagged as an assumption rather than presented as research — the same discipline the Market Research Report applies to its own numbers.

Executive summary

Primary Persona

Priya Raghavan, 34 — Co-founder & Head of Hardware, Fenwick Robotics (Somerville, MA).

Priya has a B.S. in Mechanical Engineering from Olin College (2014) and spent the five years after graduation as a New Product Introduction engineer at Flex, shepherding consumer-electronics designs from prototype through first mass-production run for other companies' products. In 2023 she left to co-found Fenwick Robotics with Marcus Webb, a former SaaS product manager who handles fundraising, go-to-market, and the board relationship. Fenwick builds a modular robotic arm-and-rail system that automates seeding and harvesting inside shipping-container vertical farms. The company raised $650,000 in a pre-seed round in early 2024 — a Boston-area hardware angel syndicate plus a friends-and-family tranche — and now runs seven people out of a shared shop space near Union Square.

Fenwick has a working, validated product: a 40-unit pilot fleet has been running for eight months across three commercial urban farms in the Northeast, with acceptable uptime and two signed letters of intent for a larger order. The problem in front of Priya right now is the gap between 40 units and the 2,000-unit first production run those letters of intent require, and it is exactly the gap the Idea Brief describes: her injection-molded housing supplier in Shenzhen is delivering a 62% first-pass yield against a promised 95%, and she cannot tell from the defect photos alone whether that's a mold design flaw, a process-control problem, or a material substitution the supplier made without telling her. A second contract manufacturer has quoted $38,000 for new tooling, and she has no benchmark for whether that number is fair or padded. Separately, her pilot customers' insurers are asking for UL certification on the 48V motor drive system before they'll approve unsupervised operation, and she doesn't know how to scope a test plan, let alone which of two competing lab quotes is reasonable. Her board is entirely software-background angels; none of them has run a manufacturing scale-up, and she has said as much to Marcus more than once.

"I can design a robot that works perfectly on my bench. I have no idea if the thing I designed can actually get built 2,000 times without falling apart — and everyone I ask either doesn't know or wants $400 an hour to find out, starting with a six-week onboarding call."

Priya is active in a roughly 800-member private Slack called Hard Tech Founders, reads r/hardware and Hacker News most mornings with coffee, follows a handful of manufacturing-consultant accounts on LinkedIn, and listens to the podcast "The Hardware Startup" on her commute. She attends Greentown Labs' monthly Hardware Happy Hour in Somerville when she can. Her current attempts to solve this specific problem: Googling "DFM checklist injection molding" and cross-referencing three contradictory blog posts; posting the yield-rate photos in the Slack group and getting either vague sympathy or a pitch from someone selling a $15,000-a-month retainer; asking her one technical board advisor, who told her flatly, "that's outside my lane, sorry"; and getting a quote from a boutique manufacturing consultancy that wanted a six-week engagement minimum for a decision she needs to make in the next ten days.

Based on your input

This reflects the founder's own description of the venture and its users.

Evidence-labelled section

Jobs-to-be-Done

Demand side. When I'm about to commit to a $38,000 tooling quote from a contract manufacturer I've never worked with before, I want an hour with someone who has actually negotiated CM tooling contracts at real production scale, so I can tell whether the price and terms are normal or a mistake I can't undo once the mold is cut.

Demand side. When my UL test lab flags a certification failure two weeks before a scheduled pilot deployment, I want same-week access to someone who has actually run EMC and safety compliance programs, so I can understand what's genuinely wrong and fix it without missing my launch window.

Supply side. When I've just retired after decades of full-time engineering work and have 10 to 15 spare hours a month, I want paid, intellectually engaging technical work that doesn't require me to build my own client pipeline or handle my own invoicing, so I can stay sharp and earn supplemental income without returning to a 40-hour week or starting a consultancy from scratch.

Supply side. When I agree to mentor a founder I've never worked with before, I want clear, enforced boundaries on scope, liability, and IP exposure before the first call happens, so I can share real expertise without risking my own financial or professional standing over advice given in a single paid hour.

Shared, both sides. When I'm deciding whether to trust a stranger on the other side of a marketplace I've never used before — a mentor evaluating whether a stranger's advice is real expertise, a founder evaluating whether a stranger's payment and follow-through are genuine — I want verifiable, specific proof before committing time or money, so neither of us wastes a paid hour discovering the fit was wrong only after the call has already started.

Based on your input

This reflects the founder's own description of the venture and its users.

Risk

Objections & Trust Barriers

"Why would I pay $150 to $250 an hour when SCORE and MicroMentor are free?" This is Priya's most immediate objection, and it deserves a direct answer rather than a dismissal: SCORE and MicroMentor are free because they're generalist and volunteer-run, and a generalist mentor genuinely cannot help with a tooling negotiation or a UL test plan — the cost of "free" here isn't zero, it's a wrong answer or no answer at a moment that costs real money. Positioning and onboarding copy need to make the ROI math explicit and concrete (a $200 hour that prevents a $38,000 tooling mistake or a missed launch window), not just assert that the mentors are better.

"How do I know this mentor won't just try to get hired by my startup, or ask for equity, instead of giving me an hour of advice?" A real concern on both sides — Priya doesn't want a sales pitch disguised as mentorship, and Klaus doesn't want to be seen as angling for a job he's already retired from. This needs explicit platform terms (no direct equity or employment solicitation through a booked session) stated up front in both the founder's and the mentor's onboarding, not left as an implicit norm.

"What if the mentor sees my confidential design or roadmap and there's no NDA in place?" This is a real, currently-unresolved gap flagged in the Idea Brief's own Open Questions, and it should stay flagged rather than glossed over here: MentorLoop needs an NDA-by-default mechanism attached to every booking before its first paid session, not after the first founder asks about it. Positioning can't promise confidentiality the product doesn't yet structurally guarantee.

"How do I know this mentor's background is real, not embellished?" Priya's Clarity.fm experience — generic "20+ years in industry" listings with no way to verify anything — is exactly the failure mode MentorLoop's mentor profiles need to visibly not repeat: named company, named years, named technical domain, ideally with some form of reference or credential check behind the listing rather than pure self-reporting. The credibility mechanism is the product here as much as the marketplace mechanism is.

"Am I violating a non-compete or IP-assignment clause from my old employer by mentoring for pay?" Klaus's specific hesitation, and likely a common one among retirees from large industrial employers with standard-form IP-assignment language. This is a real legal question MentorLoop cannot fully answer generically for every mentor's former employer and every jurisdiction — the honest response is plain-language guidance plus a recommendation to check with a former employer's HR department before onboarding, not a blanket "don't worry about it" that could expose a mentor later.

"What if my advice turns out to be wrong, and the founder blames me for a real financial loss?" Klaus's liability concern, and a legitimate one: advice given in a single paid hour on a complex, multi-variable manufacturing decision is inherently uncertain. This needs explicit "advice, not a warranty" language in the platform's terms of service and every session, and realistically some form of liability insurance or indemnification structure before volume scales — this is unresolved product and legal work, not something copy alone can paper over.

"If a session goes badly — wrong expertise, poor communication, unprepared mentor — what actually happens?" Also flagged, honestly, as unresolved in the Idea Brief: there is no committed refund, re-match, or visible rating system yet. Until there is, expectation-setting before booking (clear scope descriptions, a short pre-call intake question) is the only mitigation available, and the absence of a real recourse mechanism should be treated as a launch-blocking product gap, not a marketing problem to write around.

Needs validation

These points rest on assumptions and need primary research before the plan relies on them.

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