The MedTech founder story playbook.

Who runs the interview

The interviewer must be someone outside the founder's daily orbit. Not the co-founder. Not the head of marketing. Not the agency partner the founder has been working with for two years. Familiarity is the enemy here — the people who already know the answers don't push for the better version.

The right interviewer is someone the founder respects but doesn't have a reflexive shorthand with. An outside agency, a peer founder from a different category, a strategist on a short engagement. Their job is to ask questions the founder hasn't been asked before, in a way that requires real answers.

Setup

This can happen in person or over Zoom — same outcome either way. No film crew, no studio, no budget. Most founders over-estimate what's required. Down-and-dirty is fine.

Quiet room. Phones away. If it's a video call, do what you reasonably can to look and sound good on camera — decent lighting, a clean background, a half-decent mic on both ends. None of it has to be perfect; it just has to not get in the way.

Block ninety minutes. Sixty is the floor — anything shorter and you don't get past the rehearsed material.

Record the conversation. Most video tools do this automatically; in person, a phone on the table works. The whole playbook depends on the audio being clean enough to mine afterward.

What the founder should do to prepare

Nothing. Truly nothing. No rehearsing, no scripting their answers, no rereading their own pitch deck the night before. The whole point is to surface what they say when they aren't performing. Founders who prep over-deliver the polished version and the playbook gets less raw material to work with.

Tell them: clear your calendar, get a good night's sleep, show up willing to talk.

What the interviewer should do to prepare

Read everything public. The website, the deck if you've been given one, any podcast appearances, the founder's LinkedIn, any clinical papers. Build a mental map of what the founder says when they're being official.

Then write down three to five hypotheses about what's missing from the official story. Where does the deck get vague? What's the problem framed in the abstract that probably has a concrete origin? Those hypotheses are what you'll quietly steer toward in the interview.

Below are the four question arcs we run, in order. Ask them as conversation, not as a checklist. The questions are written to be said out loud — adapt the phrasing to how you actually talk.

Rules for the interviewer

Don't fill silence. Founders fill silence with their best material. The five seconds after a founder answers are more valuable than the answer itself.

If they drift into spec talk, gently steer back. "That's helpful — and before you got there, what was the moment that made you certain?" works almost every time.

The most valuable thing you'll say is "say more about that." Use it constantly. Especially on the answers that seemed throwaway.

Don't take notes during. Eye contact and listening matter more than capture. The recording is doing that job. Take notes only after the founder leaves the room — first impressions while they're still fresh.

What to extract

Pull 8 to 12 verbatim quotes. Don't paraphrase them. Don't clean up the grammar. Don't smooth the cadence. The roughness is a feature.

You're looking for lines that do specific work:

• One or two lines that name the moment the founder saw the problem
• One or two lines that show conviction — what they walked away from, what they almost gave up on
• Three to four lines that describe the problem in different audiences' language
• One or two lines that frame differentiation in plain words a buyer could repeat
• One line, if you're lucky, that captures the whole company in a sentence

That last one is rare and never written down on purpose. Watch for it.

The four canonical assets

• The 30-second founder story. One paragraph. Origin moment, problem witnessed, decision to build. This is the cold-phase opener — the version a rep tells at the start of a discovery call.
• The problem statement, in three versions. Same problem, three audiences: clinician, administrator, patient. Each version is one short paragraph in that audience's actual language.
• The differentiation paragraph. One paragraph that a buyer could repeat to their boss without notes. Not a feature list. Not a comparison table. A claim about why this team, why this approach, why now.
• The proof framing. One or two sentences that introduce your clinical data, testimonials, or outcomes. The framing matters as much as the data itself — it tells the buyer what the data is for.

The founder review

Once you have drafts, run them past the founder. Not for approval — for one specific check: does this sound like you? Not "is this accurate" (the founder will say yes to almost any accurate thing). Not "is this polished" (founders over-polish). Just: would you say this, out loud, to a buyer?

If the answer is no, the canon hasn't kept the founder's voice. Go back to the transcript and rebuild.

The grid below is the map. Each column is a cycle stage. Each row is a touchpoint that uses one or more of the canonical assets you built in Phase 04.

What this grid is actually for

Two things. First, it's a check on your existing materials. Take your current deck, your current cold emails, your current website — and ask which canonical asset each piece is leading with. If the answer is "none of them," you've found a gap.

Second, it's a brief for what to build. Anything in the grid that you don't currently have is your next sprint. Sequence it by where you lose the most deals.

Why this isn't optional in MedTech

Most categories can sell on words. MedTech can't. Your buyer is being asked to evaluate something with a complex mechanism, a regulatory pathway, and clinical implications — across multiple meetings, often in front of multiple stakeholders, in rooms where nobody has time to read carefully.

The companies that win are the ones whose story is visualized clearly enough to be re-told. If a buyer can't picture your device, your differentiation, and the problem you solve, they can't carry your story into the next meeting you're not in.

Design isn't decoration here. It's the vehicle that carries the canon through the org chart.

The minimum viable asset stack

Once the canon is locked, the asset stack to build is more consistent than most founders expect:

This isn't comprehensive. It's the minimum. The full stack — interactive sales tools, segment-specific decks, KOL highlight reels, social cuts — comes after these are in place.

Designing TO the canon

The discipline that separates designed-canon work from generic-MedTech work is one thing: the design serves the canon, not the other way around. The most common failure mode is design that's beautiful but disconnected from the language you sweated to extract. Brand identity should be applied to the canon's voice, not the other way around.

The check is simple. If you read the canon, then look at the designed deck, the connection between them should be obvious. Not buried, not subtle — obvious. If the canon says "you only see it from inside the OR," the deck should look and feel like a thing that came from inside the OR.

When to bring in outside help

The earlier phases are mostly process. The design phase is mostly craft. The cost of doing it badly is also where it's highest — a thin deck, a generic-looking animation, or a sales sheet that could belong to any device company will erode every dollar you spent on the canon.

This is the part of the work Vuelab does. We don't run the playbook for you. We build the designed asset stack once the canon is locked, in the founder's voice, across every piece a buyer will touch.

The distribution problem

Most companies build a canon, dump it in a Dropbox folder, and pray. Six months later, half the team is working from an older version of the deck, the cold email templates haven't been updated, and the founder's podcast bio still has the original language from before the canon refresh.

The reason this happens is that a doc isn't a distribution system. It's a holding area. The canon doesn't compound until every piece of sales material — deck, sheet, animation, web page, rep talk track — is pulled from the same controlled source, with version control, and pushed out the moment anything changes.

Where the canon lives

The canon needs a single controlled source of truth, not a doc-of-the-moment. For Vuelab clients, that source of truth lives in Nuvue — the platform we use to host, version, and distribute every canonical asset across the entire sales motion. The canon is the content. Nuvue is how it travels.

Nuvue is built specifically for this problem. The four canonical assets, the deck, the animation, the sales sheets, the rep talk tracks — all of it lives in one place, gets pushed to every channel automatically, and updates the moment the canon is refreshed.

Why distribution decides whether the canon works

A canon nobody can find is a canon that doesn't compound. The whole point of investing in the work is that every rep, marketer, and exec can grab the right asset for the touchpoint they're about to walk into — a cold email, a discovery call, an RFP, a conference booth — without DM-ing someone for the latest version.

That only happens if the canon lives on a platform built for distribution: organized by sales-cycle stage, searchable by audience, and versioned so when something is updated once, it's updated everywhere. A doc-of-the-moment can't do that. Neither can a Dropbox folder. Nuvue can — it's why we built it.

And it has to work on a phone

The most important moments in a sales cycle don't happen at a desk. They happen in a hallway between sessions at a conference, in a parking lot before a hospital visit, on the sideline of a kid's soccer game when a buyer texts back. If your distribution platform isn't mobile-responsive, half the value is gone.

+ Expand all