Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Investor Faq

ASecurity

Use when a founder needs their objections answered in writing — "investor FAQ", "objection handling for the raise", "the hard questions", "what will investors push back on", "we keep getting the same three questions", or after a memo exists and needs pressure-testing. Also use to pressure-test a plan before writing anything: an objection with no good answer is a business problem, not a writing problem. Investor-side; for sales objections use objection-handling.

5 stars
0 votes
0 copies
0 views
Added 10/4/2026
ai-agentsrustgotestingapi

Works with

api

Security Analysis

A100/100

Scanned 10/4/2026

$npx -y skills add The-Utopia-Studio/skills --skill investor-faq --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Investor Faq?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Investor Faq
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/the-utopia-studio-investor-faq/badge)](https://www.skillsdirectory.com/skills/the-utopia-studio-investor-faq)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: investor-faq
description: Use when a founder needs their objections answered in writing — "investor FAQ", "objection handling for the raise", "the hard questions", "what will investors push back on", "we keep getting the same three questions", or after a memo exists and needs pressure-testing. Also use to pressure-test a plan before writing anything: an objection with no good answer is a business problem, not a writing problem. Investor-side; for sales objections use objection-handling.
---

# Investor FAQ

## Why this document wins deals

Every objection to your deal will be raised. The only question is whether it is raised in a room you are in, or in a partner meeting you are not, by someone reconstructing your answer from memory.

The FAQ puts your answer in writing, in your framing, in the reading room. It also does something no other document does: writing it honestly tells you which parts of your business do not yet have an answer.

Investors read a real FAQ as confidence. A soft one — "Why is your team the best? Because we are passionate" — is worse than none, because it proves you either cannot see the objections or won't engage them.

## How to build it

**1. Harvest, don't invent.** Pull questions from what has actually been asked: every investor call, every "quick question" email, the questions your own team asks when you present internally, and the ones a competitor's investor would ask. 25–35 questions for a seed round, 15–20 for pre-seed.

**2. Group into five or six themes.** The standard set:

- *The market* — is this real, is it big, why now
- *The thing itself* — does it work, is it defensible, why you
- *The numbers* — are the figures real, is the margin credible, is it capital-hungry
- *The competition* — what stops a better-funded player
- *Execution* — the biggest risk, the team, the dependencies
- *The deal* — price, structure, dilution, return, exit

**3. Sort hardest-first inside each theme.** The instinct is to open with the easy one. Do the opposite: a reader who sees the hardest question answered first in a section reads the rest with trust. A reader who has to hunt for it assumes it is missing on purpose.

**4. Write the questions in the investor's words, including the sharp edge.** "Colocation is a low-margin commodity business. Why is this venture-scale?" — not "Tell us about your margins." A softened question announces that the answer is softened too.

**5. Answer in 80–150 words.** One-line answers look evasive; 400-word answers look defensive. If an answer needs more, it belongs in the memorandum and the FAQ should point to it.

## The answer pattern

Four moves, in order, in every answer:

1. **Concede the true part.** One clause. "It is, for the base layer."
2. **Reframe to the thing that is actually true.** "The base layer is the entry point, not the business."
3. **Evidence.** A number, a contract, a third-party report. Non-negotiable — an answer with no evidence is an opinion.
4. **What would change your mind, or what is still open.** One sentence, where it applies.

The concession is the move founders skip and the one that does the work. An answer that disputes the premise reads as a fight; an answer that grants the premise and then dismantles the conclusion reads as command of the facts.

## Judgment

**Keep the question you cannot answer well.** If the honest answer is "this is a real risk, here is the bound on it, here is what we watch" — that is a good FAQ entry. Investors are not looking for a business with no risks; they are checking whether you can see yours. The only thing to cut is a question that is genuinely not about your deal.

**Two or three answers should be uncomfortable to publish.** If nothing in the document costs you anything to admit, you have written marketing and a professional reader will notice within two entries.

**End with an open invitation.** A final entry — "anything we have not covered: email X" — and mean it. It converts the FAQ from a defensive wall into an opening.

**Never contradict the memorandum.** The FAQ is where numbers drift most, because answers get written fast under pressure. Every figure goes through the fact ledger.

## What good looks like

- The three objections you dread most are all in there, near the top of their section.
- Every answer contains at least one verifiable fact, not just reasoning.
- No answer uses "we believe" as its only support.
- Someone who has never met you could answer a live investor question from this document, in your voice.
- Questions read as a sceptic wrote them.
- An honest "we don't know yet, here is the bound" appears at least once.

## Gotchas

- **Marketing voice creeps in around question 12.** Energy drops and the answers get vaguer. Write the hardest ten first, when you are fresh, and re-read the back half specifically for softening.
- **The FAQ becomes the dumping ground.** When a question needs 500 words and a table, it is a memorandum section. Move it and cross-reference.
- **Stale answers after a pivot or a re-price.** The FAQ is the last document anyone updates and it contains the most specific claims. Check it first after any change.
- **Anticipating questions nobody asks.** If it has never been asked in ten calls, it is padding — and it signals what you are anxious about.
- **Legal exposure in forward-looking answers.** Return and exit answers need the same care as the memo's: state assumptions, avoid anything that reads as a promise of a return.
- **Answering a question that isn't the real one.** "Isn't this capital-intensive?" is usually "will I be diluted to nothing?". Answer the question behind it, with the dilution maths.

## Worked example

Weak:

> **Q: Isn't this market very competitive?**
> A: While there are other players, we believe our technology and team give us a strong advantage, and we are moving fast.

Strong:

> **Q: What stops a better-funded operator from copying this in eighteen months?**
>
> Nothing stops them starting — and two probably will. What is hard to copy is the sequence. The site permit took 14 months and there are four comparable sites in the region; we hold one of them on a 20-year lease. The grid connection agreement is capacity-allocated and the next allocation window is 2029. Both signed customers have 5-year terms with switching costs we can quantify at roughly 7 months of their own engineering time.
>
> So a competitor with more money arrives in 2029 into a market where the cheap power and the anchor demand are already contracted. That is a real business for them, and a worse one than ours.
>
> *Where this gets harder:* if the regulator opens a second allocation window early, the timing advantage compresses to about two years. We would still hold the lease and the contracts, but we would be competing on price sooner than the plan assumes.

Attribution

The-Utopia-StudioThe-Utopia-Studio
View sourceSee grades on GitHubMore from The-Utopia-Studio →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →