pitch-lensing
Structure and review an investor pitch deck with the "lensing" method from pitch designer Chris Laughlin. Use when outlining a fundraising deck, rewriting the opening slides, reviewing a deck before it goes to investors, planning when to start a raise, or preparing pitch delivery. Replaces the generic Problem / Solution template with a four-slide context opener built around how each investor partner already sees the world.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- pitch-lensing
- description
- Structure and review an investor pitch deck with the "lensing" method from pitch designer Chris Laughlin. Use when outlining a fundraising deck, rewriting the opening slides, reviewing a deck before it goes to investors, planning when to start a raise, or preparing pitch delivery. Replaces the generic Problem / Solution template with a four-slide context opener built around how each investor partner already sees the world.
02 资源文件 2
- 参考文档DERIVATION.json1.7 KB
- 许可证LICENSE10.5 KB
03 SKILL.md 正文
Pitch lensing
Method source: Chris Laughlin's talk at an Emerson Collective founder event (June 2024), on opening a pitch, timing a raise, and a set of fast rules. This skill restates his framework as a working procedure. Credit him when you cite it.
The core idea
Every investor sees your company through their own lens: their thesis, their portfolio, and the pitch they heard five minutes before yours. You cannot remove that lens. You can give them a corrective one. Lensing is the context you set before you reveal what the company does, so the reveal lands the way you intend.
There are two lenses. Yours shows the internal metrics that run the company. The investor's shows what they need to believe. Build the deck for the second.
Step 1: Map the lens, per partner
Before writing slides, for each target partner (not firm; partners at one firm disagree):
- What have they invested in, and what did they say publicly about why?
- What do they believe about this market? Find podcasts, posts, blog essays.
- What would make them pattern-match you to a past loss or a competitor?
- Back-channel: ask founders they backed what they push on in meetings.
Output a short lens note per partner: belief, likely objection, the frame that corrects it. If you have no data, say so and keep the generic opener.
Step 2: Build the four-slide opener
Never compress this into one slide. It is worth the slide count.
| # | Slide job | What it must make the investor feel |
|---|---|---|
| 1 | The shift. Something happened or is happening right now, at a 30,000 ft altitude everyone can agree with. Say how big a deal it is. | "Yes, that is true and it matters." |
| 2 | The gap. That shift opens an opportunity nobody is capturing, or nobody is executing on the right way. | "Huh, nobody is doing that properly." |
| 3 | The pull. If someone gets it right, it is huge, because the market is demanding it: growth, desperate buyers, customers who would pull it from your hands. | "There is a prize here." |
| 4 | The reveal. You got it right. Here is the product and how it works. | "These people found it." |
Calibrate altitude. Too low and slide 1 is your feature ("our novel material cuts CO2 by 30%"). Too high and it is a platitude about the planet. Aim for the backdrop a skeptical partner would nod at without argument.
Time is not evenly spread. Some slides get two seconds, some get two minutes. That is correct.
Step 3: Time the raise so the news does the work
- Raise when you can, not when you have to. A board saying "it is time" is not the signal.
- Line up hires, customer traction and launches so metrics are at their highest and rising while you are in market. Pull go-lives forward, move renewals, sequence announcements.
- Know your own news cycle (PR, data drops) and play it during the process.
- Run a tight process. No half-open conversations months early, no mass-sending the investor update as a pre-pitch.
- Expect to raise at the busiest, least convenient moment. That is the cost of good timing.
Step 4: Delivery
A sloppy pitch delivered with conviction beats a perfect one delivered flat. Before each rehearsal, get into the founder posture: the world has a backwards problem, it is upsetting nobody fixed it, what you are building is not incremental, and you will build it with or without this investor. You are selling equity; act like it.
Step 5: Apply the fast rules
Run every deck through this checklist and flag each violation with the slide number.
Structure
- Do not open with mission, vision, values.
- No slide titled "Problem", and never follow it with one titled "Solution". Use the four-slide opener.
- Start with an executive summary when the numbers are strong; do not bury the lead.
- Build ~25 slides, plan to get through ~10. The rest are backup.
- Do not end on a "Thank you" slide. End on the ask or the prize.
Charts and numbers
- A chart should go up. If monthly does not, try quarterly. If that does not, find a better metric.
- Do not stretch a chart across the whole slide; compress it a little, not absurdly.
- Cumulative charts always look good and every investor knows it. Avoid them as the headline.
- If the model cannot reach about $100M revenue within 10 years, rethink the plan.
- Ask for a range and open at the low end; once you go up, the only lower number is zero.
Positioning
- The best moat is pain and suffering: work nobody wants to do.
- Mention AI where it is real, but do not reduce the product to a chatbot.
- Be more creative with the story than feels comfortable. Most pitches are dull.
Process
- You do not need to send the deck in advance. If you send something, send a teaser, not the whole deck.
- Warm up with tier 2 and tier 3 investors before tier 1 to work out the kinks.
- While raising, fundraising is 100% of the job. Optimize for the shortest raise.
- Assume the next round is harder than the last.
- Asking for pitch feedback produces feedback, not all of it good. Ask less, and only people with the right lens.
Outputs
Outlining a new deck: return (a) lens notes per partner if targets are known, (b) the four-slide opener as headline + one-line proof for each, (c) the remaining ~6 main slides and the backup list, (d) a raise-timing note listing which milestones should land during the process.
Reviewing an existing deck: return a table slide | issue | rule | fix, then a rewritten four-slide opener. Lead with the single highest-impact change.
Keep headlines as full-sentence claims, not labels ("Agents now install skills by the thousand", not "Market").
04 同仓库更多 Skills
zero-downtime-cloud-move
Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.
zayats-ceo-branding
Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.
yc-app-roast
YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
yc-app-review
YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
x-growth-playbook
X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.
workplan
Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.