Preparing to pitch an accelerator, incubator, or early-stage investor
What evaluators decide during an early-stage pitch, and how to prepare the numbers, the deck, the team, and the answers before you walk in.
Accelerators, incubators, and early-stage investors make their decisions in much the same way. After a short pitch and hard questions, a small group of people, often with different backgrounds, decides whether they believe in the team enough to commit time or money.
This guide covers what those evaluators decide, how to prepare before the meeting, and how to handle the pitch itself. It draws on patterns observed across a large number of early-stage selection interviews, in sectors from software and hardware to semiconductors and life sciences.
What evaluators are deciding
Most evaluators score some version of four things: the team, the product, the market, and the traction. In practice they weigh those four in a particular order.
- The team comes first. A strong team committed to the company can advance with little traction, and evaluators openly call these bets on the jockey. Good revenue paired with doubts about the team, the moat, or the founders' openness to advice often fails to advance.
- Next comes a real insight. Evaluators look for something specific and hard to copy behind the pitch. A fluent description of a big market does not count.
- Traction is measured against time. A company a few months old needs named design partners or pilots under way. Past the one-year mark, evaluators expect money to be changing hands, and flat revenue over several months worries them at any level.
- Coachability is checked throughout. Programs and investors sell help as well as capital, so a founder who meets every challenge by restating the claim more firmly gets marked as difficult to advise.
Venture scale is a separate test. A profitable niche business can be judged viable and still fail to be investable if it cannot plausibly return a fund.
Before the pitch
Most of the outcome is set by preparation. Evaluators will check what you say against what you have written, against public records, and against arithmetic, often while you are still speaking.
Make every source agree
Read every written source side by side, from the application and deck to the website and each founder's LinkedIn profile. Revenue figures, founding dates, team titles, prior funding, and full-time status should match everywhere. A mismatch hurts your credibility far more than it hurts the figure in question, and credibility is much harder to win back.
Two details catch founders often. Every co-founder's profile should list the company, and anyone still employed elsewhere should be disclosed before an evaluator finds the other job.
Prepare the numbers slide
Do the arithmetic before an evaluator does it for you.
- Revenue in three states. Report contracted, signed, and collected revenue as separate figures, and expect to be asked for all three.
- Pilots with definitions. Say which pilots are paid and started, and which are still being discussed.
- Conversion and margins. If you report users, revenue, and price, the evaluators can calculate your paid conversion. Calculate it first and show it.
- Market size from the bottom up. Count customers and price, and drop the top-down share of a large market, which experienced evaluators discount on sight.
Name the competitors yourself
Put a competitor slide in the deck, with a specific difference against each named company. Evaluators search your category while you present, and a competitor they find on their own does more damage than one you raise.
Settle the hard facts
- IP. Know whether each patent belongs to the company, a founder, or a university, and its current status.
- Commitment. Know who works on the company full-time now, and the date each remaining founder will join if you are accepted. Programs that require relocation or a focus on a particular market will ask about both.
- Cap table and funding history. Have them clean, current, and ready to share.
- Terms. Read the program's or investor's standard terms and run the dilution against your cap table before the meeting. Raise any problem early.
Research the decision-makers
Find out who actually makes the decision. In many programs every evaluator scores, while the final call rests with a small group such as the fund staff and the lead for your sector. Read their backgrounds, and pay closest attention to their questions in the room.
Remove the logistics risk
Test every link in your application. Submit documents as PDFs. Have the deck ready to share in presenter mode, with a backup file, and make sure every founder can join on a working connection.
Building the pitch
Evaluators have heard hundreds of pitches, and the most common cause of a fast rejection is that nobody can say what the company makes. The pitch should answer that question before anything else.
- Open with what you make and who pays for it. Keep the problem brief. Evaluators have usually seen the problem many times, and a long problem section delays the part they came to hear.
- Explain the mechanism. Show how the product works, in specific terms. Analogies and restated benefits leave the question unanswered, and it will come back.
- Attach proof to each claim. Every benchmark, customer result, or verification you mention should be ready to open on screen.
- Give a structural reason you can't be copied. Name the constraint an incumbent cannot cheaply remove, such as data that cannot leave the customer, a validated toolchain, or a regulatory clearance. If the advantage is the team's speed and skill, make that case with evidence.
- Show the business model. Pricing, margins, and the buyer belong together on one slide.
- State the ask. Say what you will achieve with the money and by when, with milestones an evaluator can check later.
Write in your own voice, because experienced evaluators now recognize generated pitch language on sight. The usual tells are absolute claims ("no one has ever"), sentences that deny one framing to assert another, history lessons, aphoristic closers, and long essayistic problem sections. Once a pitch reads as machine-written, that judgment spreads to the rest of the company.
In the room
Who speaks
The CEO leads the pitch. When someone else presents without a stated reason, an evaluator asks why. Every co-founder should attend, because an absent co-founder or CTO draws questions about commitment.
At the start, say who will take which kind of question. Technical questions belong with the technical co-founder, and evaluators react well when the founder who knows the answer is the one giving it.
How to answer
- Answer the question asked. Asked what you own, founders often describe how hard the product was to build. Pause long enough to hear the actual question.
- Be candid about execution. Volunteering a failed experiment, a missing hire, or the reason a comparable company failed builds trust.
- Keep candor away from defensibility. Conceding that anyone could copy the product ends the conversation faster than a weak defense would.
- Never argue with the questioner. Interrupting, or repeating a claim more forcefully, gets noted, usually without anyone saying so.
- Admit what you don't know. A precise "we haven't measured that yet" is received better than a confident guess that fails the next question.
Questions to rehearse
These come up in most early-stage pitches, listed roughly by how often they are asked.
- How does it actually work? Expect a follow-up until the mechanism is clear.
- What stops someone bigger from building the same product? This question goes badly more often than any other.
- Where is the proof for that claim?
- Are those numbers real? Expect your figures to be divided by each other.
- What is the business model, and what are the margins?
- Who exactly pays for the product? Name the person, their title, and the budget that funds the purchase.
- Who else is solving the problem?
- Why won't a frontier AI model handle the job? AI companies should expect this one every time.
- Is everyone full-time, or will they be?
- Who owns the IP?
Investors and programs that commit capital add a few more. What will you achieve in six months? How will you spend the money? What hire is missing from the team?
What happens out of sight
Evaluators rarely sit silently while you speak. Many groups keep a running written discussion during the pitch and look things up in real time, which means:
- Your LinkedIn profiles are open, checked for current employers, start dates, and whether the company appears at all.
- Your application is open beside your live answers, and any gap between the two gets noticed.
- Your competitors are searched for, and links get shared within the group before you finish.
- Your numbers are run, usually by dividing one figure you stated by another.
- AI research tools are in use, asked what your company does and which questions to put to you.
Opinions also form early, often well before the questions end and sometimes during the pitch itself. The settled view usually rests on a single fact, such as an unclear product, a number that fails simple arithmetic, or a weak answer on defensibility.
One more dynamic shapes the outcome. A single credible objection can sink a company, while a single enthusiastic supporter usually earns only a second look. Work out which objection is most likely and answer it in the pitch before anyone raises it.
After the pitch
Send a short follow-up that answers any question you handled poorly, with the evidence you didn't have to hand. Keep it factual and brief.
Treat every piece of feedback as a test you will face again. When there is a second meeting, open it with what has changed since the first, which suggestion you acted on, and what resulted. Founders who return with the same pitch rarely advance, and founders who show visible progress over a short period often do. Have the diligence material ready to send the same day it is requested.
If you reapply after a rejection, lead with quantified change since the last application. Persistence alone counts for little, and the evaluators may remember the earlier pitch.
Checklist
Preparation
- Application, deck, website, and LinkedIn profiles agree on every fact
- Revenue split into contracted, signed, and collected
- Paid conversion, margins, and bottom-up market size calculated and on a slide
- Competitors named, each with a specific difference
- IP ownership and status confirmed
- Full-time and relocation plan stated, with dates
- Cap table and funding history clean and current
- Standard terms read and dilution modeled
- Decision-makers identified and researched
- All links tested, documents saved as PDF, backup deck ready
The pitch
- Opens with what the company makes and who pays
- Problem kept brief
- Mechanism explained in specific terms
- Proof ready for each claim
- Structural answer to "why can't someone bigger build this"
- Business model and ask with checkable milestones
- Written in the founders' own voice
In the room
- CEO leading, all co-founders present
- Question routing stated at the start
- One-sentence answers rehearsed for the ten questions above
Afterward
- Follow-up sent with any missing evidence
- Feedback logged, with what you will change
- Diligence material ready to send
