Should You Create a Startup Advisory Board?

Create an advisory board when you can name the decision it will improve, the expertise you are missing, and the work each advisor will actually do. Do not create one because a list of impressive names makes the company look more established.

An advisor can help with a narrow customer introduction, a difficult technical choice, or a domain-specific mistake you are likely to make. A group that only meets occasionally and offers general encouragement is probably a network, not an advisory board. Start with one useful relationship and earn the right to formalize it.

Key takeaways

• Begin with a problem the company cannot solve quickly with its current team.
• Test the working relationship before discussing a long-term title or equity.
• Give each advisor a defined contribution, cadence, and end date.
• Keep advisors advisory: they do not replace founders, employees, or a board of directors.
• Put confidentiality, intellectual property, compensation, and termination terms in writing.

What gap would an advisor close?

Write the gap as a decision, not a résumé requirement. “We need a famous operator” is vague. “We need someone who has sold hospital software to help us test whether our buyer, procurement path, and pilot promise are credible” is testable.

An advisor is most useful when the missing context is specific and expensive to learn from scratch. That might be a regulated industry, a technical architecture, an unusual sales channel, or a customer group the founders cannot reach. The U.S. Small Business Administration’s resource-partner guidance describes ongoing mentoring and individualized advising as ways small businesses get help with planning, strategy, operations, and other concrete problems. That is a better model than collecting occasional opinions from a large group.

Before contacting anyone, write down:

• the decision you need to make;
• what you already know and where the evidence is weak;
• the advisor’s specific experience that matches the gap; and
• what would be different after four or six conversations.

If you cannot answer the last question, you may need customer research, a contractor, or a peer conversation instead. An advisor should not become a substitute for doing the work that only the founder can do.

Test the relationship before creating the board

Titles create expectations before you know whether two people work well together. Start with a small request: review one customer call, challenge one product assumption, introduce you to one relevant buyer, or walk through one technical decision. Give the person enough context to offer useful feedback, then see whether they ask sharp questions and follow through.

The Founder Institute’s FAST guidance recommends working with a potential advisor for at least one month and spending at least eight hours together before discussing its formal agreement. You do not have to follow those numbers as a universal rule, but the principle is sound: observe the relationship before you price it.

Look for evidence in both directions. The advisor should bring relevant judgment, access, or pattern recognition. You should be able to prepare a focused question, act on the advice, and report what happened. If every meeting turns into broad brainstorming, the problem may be your question or the relationship itself.

Give the role a small, clear shape

Most early companies do not need a large board. One or two advisors with different, specific strengths can be more useful than a panel that gives everyone permission to comment on everything.

For each person, define:

1. The problem or decisions they will advise on.
2. The type of help they may provide, such as review, introductions, or customer context.
3. The meeting rhythm and the preparation expected from both sides.
4. The first milestone that will show whether the relationship is useful.
5. The date when you will review, renew, or end the arrangement.

Keep decision rights with the founders. An advisory board can recommend a pricing change, question a roadmap, or help prepare for a customer conversation. It does not approve budgets, hire executives, issue equity, or bind the company to a contract. Those are governance or management responsibilities, not a way to make advice sound more official.

If an advisor wants to do a defined project, treat that as consulting work with a scope, deliverable, and payment. If they want to join the company and own an ongoing function, you may be discussing a hire. Calling every helpful person an advisor makes the relationship harder to manage.

Do not trade equity for a vague promise

Early advisors are often compensated with equity, but equity should follow a defined contribution and vest over time. Do not give a permanent grant for a one-time introduction or a few encouraging calls.

The FAST framework varies its suggested equity by company stage and level of engagement, and includes vesting rather than treating an advisor’s promise as fully earned on day one. Those figures are a framework, not a market price. The value depends on the person’s actual contribution, the company’s stage, the work involved, and the opportunity cost of the equity.

Before offering anything, compare three options:

• a short paid project for a defined deliverable;
• a limited advisory trial with no equity while both sides evaluate the fit; or
• a written advisor agreement with modest, time-based vesting and a clear end condition.

Do not improvise the legal and tax terms. Cooley GO explains that an advisor agreement generally addresses confidentiality and assignment of intellectual property created through the relationship. Its guidance on advisor option grants also notes that termination and exercise windows can matter when options are part of compensation. Have qualified counsel review the agreement and the company’s equity plan before you issue anything.

Protect the company and the advisor

The advisor needs to know what information is confidential, what they may share, and what happens if they advise a competitor. The company needs to know who owns work product, whether an introduction creates an obligation, and how either side can end the relationship.

Keep access narrow. An advisor who is helping with enterprise sales does not automatically need production credentials, customer data, or the entire product roadmap. Share the material required for the question at hand, and remove access when the relationship ends.

Be especially careful with university employees, researchers, and people who sit on other companies’ boards. Their employer or existing agreements may affect confidential information, intellectual property, or conflicts of interest. Ask them to disclose restrictions before you share sensitive material, and get professional advice when the arrangement touches institutional resources or research.

A simple decision test

You are probably ready to formalize an advisor relationship when you can answer yes to most of these questions:

Question	Ready signal	Wait signal
What gap does the advisor close?	One specific decision or access problem	General desire for “more guidance”
Why this person?	Relevant experience and useful access	Mostly reputation or social proof
What will they do?	Defined contributions and cadence	Occasional opinions with no owner
How will you test value?	A milestone and review date	Success means “they seem helpful”
What are you offering?	Proportional payment or vesting	Permanent equity for a vague promise
Who decides?	Founders retain operating authority	Advisor is expected to run the company

If the wait signals dominate, keep the relationship informal and keep learning. You can always formalize a useful advisor later. It is much harder to undo an oversized equity grant, a confusing title, or access that was never documented.

FAQ

Is an advisory board the same as a board of directors?

No. An advisory board gives non-binding advice. A board of directors has formal governance authority and legal responsibilities under the company’s structure. Use the correct title and ask counsel about the rules that apply to your company.

How many advisors should a startup have?

As few as can cover the specific gaps you have. Start with one advisor, test the relationship, and add another only when the person brings a different capability. A larger group is not automatically more useful.

Should I give an advisor equity?

Maybe, but only for a defined and continuing contribution that is documented and vests over time. A paid project or trial may be more appropriate when the need is narrow or temporary. Ask counsel about the tax and corporate requirements before issuing equity.

What if an advisor stops responding?

Use the review date and termination terms you agreed to. Stop future compensation when the agreement allows, remove access, document what vested, and update public references. A clean ending is part of a well-designed relationship.

Wrap up

Write the one decision you want help with, test the relationship through a small request, and set a review date before you discuss a board or equity. If the advisor makes the company more capable of making that decision, formalize the smallest arrangement that matches the work. If not, thank them and keep looking for the missing evidence yourself.

If you want peers to pressure-test the role before you offer it, bring the decision and proposed scope to the buildpurdue cohort.