How to Write a Fundraising FAQ for Your Team
When a startup starts raising money, the founders know what is going on and everyone else guesses. Guesses turn into rumors, and rumors turn into worried one-on-ones. A short, honest fundraising FAQ for your team fixes that. It answers the questions people are already asking, sets clear rules on confidentiality and gives everyone the same information at the same time.
Key takeaways
- A fundraising FAQ gives your whole team the same clear answers about why you are raising, what changes and what stays the same.
- Collect real questions first, then answer them in plain language. Say "we don't know yet" when that is the truth.
- Cover the sensitive topics directly: runway, equity and dilution, hiring plans and confidentiality.
- Keep it in one place, update it at each stage of the raise and pair it with a live Q&A.
Fundraising is stressful for founders, but it can be just as unsettling for the people who work with you. They see closed-door calls, a CEO who is suddenly never at stand-up and a calendar full of meetings with names they do not recognize. Some will wonder whether the company is in trouble. Others will wonder what happens to their stock options. Most will not ask out loud.
A written FAQ will not replace good conversations, but it gives those conversations a solid starting point. A quick note: this article covers internal communication, not legal, tax or securities advice. Equity and tax topics can be complex, so have your lawyer or accountant review anything technical before you share it.
Why your team needs a fundraising FAQ
A good FAQ does three jobs at once. It reduces anxiety, it protects the company and it saves founder time.
- It reduces anxiety. When people understand why the company is raising and roughly what the timeline is, they stop filling the gaps with worst-case stories.
- It protects the company. A clear section on confidentiality explains what can and cannot be shared outside the company, which matters during a raise.
- It saves founder time. Instead of answering the same question ten times in ten one-on-ones, you answer it once, carefully, and point people to the document.
- It treats people fairly. Everyone gets the same information, not just the people who sit closest to the founders.
It also forces you to think. If you struggle to write a simple answer to "Why are we raising now?", that is useful feedback before you explain it to investors.
Collect the real questions first
The most common mistake with internal FAQs is writing the questions you wish people would ask. Start with the ones they are actually asking.
- Ask your managers. Team leads usually know what their people are worried about. Ask each one for the top three questions they have heard.
- Open an anonymous form. A simple anonymous form built in a tool such as Google Forms, Microsoft Forms or Tally lets people ask awkward questions without putting their name on them.
- Review past all-hands notes. Look for questions about money, growth or the future that came up in earlier meetings.
- Add the obvious ones. Some questions come up in almost every startup raise. You will find a list in the next section.
- Group and trim. Combine similar questions and aim for 10 to 20 in total. A shorter FAQ that people actually read beats a long one nobody finishes.
Pro tip
Keep the exact wording people use. If someone asks "Are we running out of money?", do not soften it to "What is our financial position?" Answering the blunt version shows you heard the real concern.
The questions almost every team asks
Every company is different, but these topics come up again and again. Plan an answer for each one, even if the answer is short.
Why are we raising, and why now?
Explain the purpose in one or two sentences: to hire for a specific plan, to expand into a new market or to build a product line. Tie it to progress the team already knows about. A raise framed as fuel for growth is easier to hear than a vague "we need more money."
Is the company in trouble?
Answer this one directly, even if nobody wrote it down. Share as much as you comfortably can about runway in general terms, such as "we have enough cash to operate well into next year." If the situation is tighter than that, it is still better to be honest about the plan than to let people find out later.
What happens to my stock options?
This is often the biggest worry. Explain in simple terms that new investment usually means new shares are issued, so everyone's percentage ownership, including the founders', typically goes down. The aim is for the company to be worth more, so a smaller slice of a larger company can still be worth more. Avoid promising any specific outcome.
You can also mention that in the US, option exercise prices are usually set at fair market value based on a 409A valuation, and a new round may lead to an updated valuation for future grants. In the UK, many startups use EMI options, the main tax-advantaged scheme for small companies. Keep this part general, and suggest people speak to a tax adviser about their own situation.
Will we hire? Will anyone be let go?
Share the hiring plan at the level of detail you can stand behind. If the plan depends on how much you raise, say so. If there are no plans for layoffs, say that clearly. If you cannot rule anything out, say that you will share decisions with the team first.
What can I tell people outside the company?
Be specific. Most companies ask staff not to discuss the raise, investor names, valuation or terms with anyone outside the company, including on social media, until there is a public announcement. Explain why: a leak can upset negotiations or create confusion with customers.
What should I do if an investor contacts me?
Investors sometimes talk to team members during their review. Tell people whether this might happen, who will arrange it and what to do if someone reaches out directly. Usually the answer is: be polite, do not share confidential details and let a founder know.
Common mistake
Writing a cheerful FAQ that avoids every hard topic. People notice what is missing, and silence on runway, layoffs or dilution reads as bad news. One honest paragraph on a difficult subject earns more trust than ten upbeat ones.
How to write answers people trust
Good FAQ answers are short, specific and honest about uncertainty. Use these principles as you draft.
- Lead with the answer. Put "yes", "no" or "we don't know yet" in the first sentence, then explain.
- Use plain language. Avoid investor jargon. If you must use a term like "dilution" or "priced round", explain it in one line.
- Be honest about unknowns. "We don't know yet, and we will update this by the end of the month" is a complete and respectable answer.
- Avoid promises you cannot keep. Do not guarantee a close date, a valuation or a specific outcome for anyone's equity.
- Keep it human. Write in the same voice you use at team meetings. A legal-sounding FAQ makes people more nervous, not less.
Using AI to help draft
An AI assistant such as ChatGPT, Claude, Gemini or Microsoft Copilot can help you turn rough notes into clear, friendly answers, or rewrite a technical paragraph in plainer words. Do not paste confidential terms, investor names or financial details into a tool unless your company's policy allows it, and check current privacy settings first. Always review the final wording yourself.
A fundraising FAQ template you can copy
Use this table to plan your FAQ before you write it up in your company wiki or a shared document. The rows below are examples you can adapt.
| Question | Short answer (example) | Who answers | Can share outside? | Update when |
|---|---|---|---|---|
| Why are we raising now? | To fund the product and sales hires in next year's plan, building on this year's customer growth. | CEO | No, until announced | If the plan changes |
| What happens to my options? | Your options stay the same, but your percentage will likely go down as new shares are issued. We will hold a session on how equity works. | CEO with finance lead | No | After the round closes |
| Will we hire? | Yes, we plan to hire if the round closes as planned. Details will follow once it does. | Head of people | No | At close |
Add a "last updated" date at the top of the final document so people know they are reading the current version.
Hypothetical example
Imagine Tom, the CEO of a 15-person startup, preparing to raise a seed extension. His managers report that people are quietly asking whether the company is in trouble and what happens to their options. Tom collects 14 questions through an anonymous form, writes short answers, has his lawyer check the equity section and shares the FAQ at the next all-hands with 20 minutes for live questions. He updates it twice: once when the lead investor is confirmed and once at close. Afterward, two team members tell him it was the first time they understood how their options work. (The people and details are made up for illustration.)
Sharing and updating the FAQ
How you share the FAQ matters as much as what it says. A document dropped into a chat channel on a Friday evening will create more worry than it solves.
Launch it with a conversation
Introduce the FAQ at an all-hands or team meeting. Walk through the main points, then open the floor for questions. Let people know where the document lives and how to ask follow-up questions, including anonymously.
Update it at each stage
Plan to revisit the FAQ at a few natural points: when you start the raise, when you have a lead investor, when the round closes and when it is announced publicly. Mark new or changed answers so people do not have to reread the whole thing.
Store it where people already look
Put it in your existing knowledge base, whether that is Notion, Confluence, Slite or Guru, or a shared folder your team actually uses. Limit access to employees, and remind people that it is internal.
Your fundraising FAQ checklist
- Ask managers for the top questions their teams are asking
- Open an anonymous form for awkward questions
- Draft answers on purpose, runway, equity, hiring and confidentiality
- Lead each answer with a clear yes, no or "we don't know yet"
- Have your lawyer or accountant check equity and tax wording
- Launch the FAQ at a team meeting with live Q&A
- Add a "last updated" date and store it in your wiki
- Update it when you get a lead, at close and at announcement
Frequently asked questions
When should I share a fundraising FAQ with my team?
Ideally around the time you start meeting investors seriously, before rumors take hold. Some founders wait until a lead investor is confirmed. Either way, share it before people hear about the raise from someone outside the company.
Should I share the valuation with the team?
Many founders do not share valuation details until the round closes, and some never share them widely. If you choose not to, say so in the FAQ and explain why, rather than leaving the question unanswered.
What if the raise fails?
Include a short answer about the plan if things take longer than expected, such as extending runway or adjusting hiring. If the raise does fail, update the FAQ quickly and talk to the team in person.
Do small teams of five or six people need a written FAQ?
A shorter version still helps. Even in a tiny team, a written page makes sure everyone hears the same thing and gives people something to reread later.
Related reading
The bottom line
A fundraising FAQ is one of the simplest ways to keep your team steady while you raise. Start with the questions people are really asking, answer them plainly and honestly, cover equity and confidentiality carefully, and update the document as the raise moves forward.
Set aside an hour this week to gather questions from your managers. By the time your next investor meeting comes around, your team will feel informed instead of left out.
