Mechanics

The Pitch

Pitching yourself is not the same in every context. A VC coffee chat, a job interview, a cofounder conversation, and an advisory ask each have a different structure, a different stakes level, and a different failure mode. Using the same script in all four is a reliable way to underperform in three of them.

The VC / Investor Coffee Chat

Relationship-building, not transactional

Goal: Leave having demonstrated you're worth a second conversation — and having learned something specific about their thesis.

Opening (2 min)

One crisp sentence on who you are and why you asked for this specific person. Not a resume recitation — a reason for the conversation.

The ask (1 min)

Name what you want to learn. 'I'm building a thesis on [domain] and wanted to understand how you think about [specific question].' This makes you useful, not needy.

Deep listening (15 min)

Ask one good question and shut up. Let them talk. The best intelligence you'll get is in what they say unprompted.

Your perspective (5 min)

When asked, offer your actual view on the domain — not a safe non-answer. A wrong but thoughtful take is more memorable than a diplomatic nothing.

The close (2 min)

Ask one specific follow-up: 'Is there one person in [domain] who shaped how you think about this that I should talk to?' Then use the name when you outreach.

Common failure mode

Treating it as a job ask. No VC hires on a first coffee chat. The job of this meeting is to earn a second meeting.

The Job Interview

High — they are evaluating whether they trust you with real work

Goal: Demonstrate capability + judgment + culture fit with specific evidence.

Tell me about yourself (3 min)

Backwards resume: start from where you're going (target role), then explain how your background makes that logical. End with why this company specifically.

Behavioral questions (STAR format)

Situation, Task, Action, Result. Keep the situation/task brief (30 sec). Emphasize what YOU specifically did, not the team. End with a quantified result.

Technical / domain questions

In deep tech interviews, you will be asked to demonstrate actual knowledge. Don't bluff. Saying 'I don't know, but here's how I'd approach it' beats a confident wrong answer.

Your questions (5–8 min)

Ask about the specific work you'd own, what success looks like in 90 days, and what the team dynamics are. Avoid questions whose answers are on the website.

Common failure mode

General answers. 'We achieved great results as a team' tells the interviewer nothing about you. Every answer needs a specific action you personally took.

The Cofounder Conversation

Existential — this is a multi-year personal and professional commitment

Goal: Establish whether you share a thesis, complement each other's skills, and can disagree productively.

The thesis alignment check

Before anything else: do you agree on the problem? The customer? The why now? If you don't, everything downstream breaks. Spend half the conversation here.

The skill map

What do you each bring? Where do you overlap (redundancy) and where do you complement (coverage)? Be honest about weaknesses — this conversation is the last time they're cheap to surface.

The stress test

Have a genuine disagreement. It doesn't need to be hostile. Pick something you actually disagree on about the problem or approach and argue it. Watch how they handle it.

The logistics

Equity, vesting, decision rights (who has final say when you can't agree?), commitment level. Awkward. Do it before you build anything.

Common failure mode

Chemistry substituting for compatibility. You can like someone and be a terrible cofounder pair. Validate the thesis and the skill map independently of whether you enjoy their company.

The Advisory Ask

Low stakes, but most people get it wrong

Goal: Get specific help from a specific person on a specific problem. Not a general mentorship relationship.

Be specific about what you need

Not 'I'd love your mentorship' — 'I'm making a decision about [X] and I think your experience at [Y] is directly relevant. Would you be willing to give me 30 minutes?'

Do the work first

Come with your thinking already done. Show them you've considered the problem seriously. Advisors give their best help to people who've already done 80% of the work.

Make it easy to say yes

30 minutes on Zoom. Specific question. You drive the agenda. No preparation required on their part.

Close the loop

Tell them what you decided and how their input influenced it. This is how advisors become recurring resources — most people never report back.

Common failure mode

Asking for ongoing mentorship from a busy person you barely know. That's a big ask. Start with a single specific request. Let the relationship develop from there.

The 90-Second Version — For Every Context

Every context above has an opening 90 seconds. Most of the pitch is won or lost there. Write it down. Say it out loud until it sounds like a person talking, not a resume being recited.

Who I am

[Technical domain or functional background] — what you've actually built or done, not what your job title was.

What I'm doing now

The MBA, the context, the direction. One sentence.

What I'm targeting

Specific enough to exclude 80% of roles. 'Something in tech' is noise. 'Operator role at a deep tech scale-up targeting US enterprise' is signal.

Why you specifically

If you're talking to this person in particular, say why. 'I've followed your work on [X]' or 'I was introduced by [Y] because...' Don't skip this.