An investor is not testing your general knowledge and is not hunting for a reason to pass. They are working out how well you understand your own business and what your confidence actually rests on. "We don't know yet, and here is how we plan to find out" lands better than a number that falls apart on the second follow-up.
That gives you the frame for preparing: what is already backed by evidence, what is still an assumption, and what you can go and collect in the two weeks before the meeting. Some questions are closed with numbers, others with a hypothesis you name honestly. Both work. Generalities do not.
The questions group into eight blocks. The right column is what each block is actually finding out.
| Block of questions | What is really being checked |
|---|---|
| Problem and customer | A specific person with a specific job — or a composite sketch |
| Demand and traction | Whether you have crossed the line between interest and money |
| Economics | Whether you count money at the level of a single deal |
| Market | Where the market size number comes from and how much of it your team can reach |
| Competition and defensibility | Why a customer changes a habit and what keeps them a year later |
| Team | Who will carry the product to revenue and whether the line-up holds |
| The round | Whether the amount, the plan and the next metric are connected |
| Why now | Why this became possible only now |
Block 1. Problem and customer
Who exactly is your customer?
What the investor is checking. Whether you have a specific addressee — a job title, a company type, a size. Price and sales channel grow out of that. A broad definition usually means the segment has not been chosen yet.
- Does not convince yet: "Our customer is small and mid-sized business", or "anyone with a sales team".
- Works: "The head of a production site in companies of 50 to 300 people running shift schedules. They make the decision; the finance director signs off the budget."
- Prepare: one sentence describing the segment, plus three roles — who pays, who uses it, who can stop the deal.
How do they solve this today?
What the investor is checking. Whether you studied the customer's reality before you started building. A real job already has a solution: a spreadsheet, an agency, a dedicated employee, or a deliberate "we just put up with it".
- Does not convince yet: "There are no solutions on the market for this."
- Works: the current process step by step — who does what, how long it takes, and at which step it breaks.
- Prepare: the customer's process in three to five steps, written down from their words rather than derived from your hypothesis.
Why is the existing solution not good enough for them?
What the investor is checking. The strength of the job. There is a difference between "annoying but survivable" and "this costs us money every month". Nobody pays for the first one.
- Does not convince yet: "It's slow, expensive and inconvenient" — without a single detail.
- Works: a concrete consequence: what gets lost, how often, and how that ends for the person making the decision.
- Prepare: two or three real quotes from customer conversations, each with a date and a job title, plus one measurable marker of the problem — hours, repeat work, losses.
How much do they spend on this today?
What the investor is checking. Whether a budget exists. If the problem has no current cost, you have to create a new expense line, and that takes longer than taking over an existing one.
- Does not convince yet: "We're cheaper than the market" — with no statement of what exactly you replace.
- Works: the cost of the alternative, calculated: employee hours times their rate, plus subscriptions and agency work.
- Prepare: one line of arithmetic the other person can check in their head. Lines like that are the ones that most often fail to add up in a deck — more on that in our piece on pitch deck mistakes.
Block 2. Demand and traction
Who is already paying?
What the investor is checking. Whether you have crossed the line between interest and money. Interest is easy to collect; money changing hands is not — which is why a paying customer is what counts as proof.
- Does not convince yet: fifteen letters of interest presented as traction.
- Works: a split into three groups — who pays, who is testing for free, who has expressed interest. You name each group correctly yourself, before anyone asks a follow-up.
- Prepare: a list of paying customers with the date they first paid and company type, and separately the pilots and the terms they run on.
How much do they pay, and what for?
What the investor is checking. What the money is actually buying: a product that works on its own, or your manual work around it. The second one is normal at an early stage, but it is different economics and a different growth rate.
- Does not convince yet: a blended "average contract value" with no structure behind it — especially when it averages three deals that mean completely different things.
- Works: a breakdown of what the customer pays for: subscription, one-off implementation, support hours — with the share each part takes.
- Prepare: a table of "customer — what was paid for — how often", plus the share of one-off work in your revenue.
How many are still there after three months?
What the investor is checking. Retention is the calmest way to tell whether the product is needed or whether it was bought as a favour to someone you know. Small numbers are not a problem here; missing numbers are.
- Does not convince yet: "We haven't measured churn yet, but everyone is happy."
- Works: "Of the eight customers from the first quarter, six renewed. Two left: one changed the manager who sponsored us, the other did not have enough data for our report — that one we are fixing."
- Prepare: a cohort by start month, even if it has five rows, and the reasons for leaving in the customer's own words.
Where did the first customers come from, and can you repeat the channel?
What the investor is checking. Whether growth scales. The founder's personal network is an excellent start and a poor growth plan: it runs out somewhere around deal number ten.
- Does not convince yet: "Word of mouth" as the entire answer.
- Works: deals broken down by source, with a separate count of how many came through personal contacts and what you have already tried outside that circle.
- Prepare: the source of every deal, plus one channel tested without personal connections: what you spent, how many enquiries came in, how many actually paid.
Block 3. Economics
What does it cost to acquire a customer, and what do they bring in?
What the investor is checking. Less the numbers themselves than what you put inside them. Acquisition cost calculated from the ad budget alone is usually understated several times over: it leaves out the salesperson's work and the hours spent on onboarding.
- Does not convince yet: a neat pair of numbers with no explanation of where they came from.
- Works: "On a sample of twelve deals over six months: acquisition includes ads, the salesperson's pay and implementation hours; revenue is counted over the first twelve months, with no renewals, because we have not seen renewals yet."
- Prepare: the formula with its terms spelled out, the period it covers, and the list of assumptions. An honest sample beats a precise number pulled out of thin air.
How is your price built?
What the investor is checking. Whether the price comes from value to the customer or from glancing sideways at a competitor. "Competitor's price minus twenty per cent" means your position is defined by the competitor.
- Does not convince yet: "We set it below market so it's easier to get in."
- Works: a link to the customer's gain, and a billing unit that makes sense — per user, per site, per document, per result.
- Prepare: the customer's gain calculated, your price as a share of it, and the history of your pricing: when you raised it, who walked away, who stayed.
What happens to the economics at ten times the volume?
What the investor is checking. Where the manual labour is hidden in your process. With ten customers the founder still gets everything done personally; with a hundred they do not, and the costs nobody noticed become the main ones.
- Does not convince yet: "At scale the economics improve on their own."
- Works: a list: which costs grow in line with customer count (onboarding, support, training), which barely grow at all, and what you automate first.
- Prepare: the manual steps with an estimate in hours per customer — that same list is your cost-of-delivery plan for the year.
Block 4. Market
How did you size the market?
What the investor is checking. The direction of the calculation. A figure lifted from an industry report shows you can find reports. A bottom-up build shows you understand who you sell to and how many times.
- Does not convince yet: "The market is estimated at hundreds of billions" — followed straight away by the next slide.
- Works: a bottom-up build: the number of companies in the segment, times a realistic annual contract value, times the share of them you actually fit, with a source for every multiplier.
- Prepare: a table of multipliers, sources and dates. If there is no external data, say so plainly and justify the multiplier from your own funnel.
What share of the market can you realistically take in two years?
What the investor is checking. The link between ambition and what your team can physically process. "One per cent of the market" explains nothing, because there is no mechanism behind it.
- Does not convince yet: a percentage arrived at by dividing the revenue you want by the size of the market.
- Works: a bottom-up count: how many deals a salesperson closes per month, how many salespeople you hire and when, how many implementations the team can carry — and what revenue that adds up to.
- Prepare: a capacity-based calculation in two scenarios, base and cautious.
What has to happen for this market to grow?
What the investor is checking. Whether you see the external conditions, and whether the whole plan is balanced on one assumption — a regulatory change, for instance, whose timing you do not control.
- Does not convince yet: "The market grows thirty per cent a year", with no explanation of why it grows.
- Works: one or two concrete drivers (a new reporting requirement, a technology getting cheaper, a shift in customer habits) and a sign that the driver has already started working: for example, people now come to you asking for exactly this.
- Prepare: two drivers, one observable sign for each, and an answer for what you do if a driver does not fire.
Five questions — but about your deck specifically
A general list helps you prepare. The next useful thing is knowing what will be asked about your presentation: where the arithmetic stops adding up, which claim is not yet evidenced, which question comes first. The quick diagnostic, with no payment, comes back in a fixed structure: a starting score, strengths, risk areas and five questions.
Get a quick diagnostic Discuss a deep reviewBlock 5. Competition and defensibility
Why will a customer pick you over doing it by hand?
What the investor is checking. What you are actually competing with. For early products the main alternative is not another startup — it is a spreadsheet and an employee who is already on payroll.
- Does not convince yet: a comparison table where you have a tick in every row and nobody else has a single one.
- Works: a comparison against the manual method in measurable units, and an honest note about where the manual method is still more convenient.
- Prepare: a comparison on three parameters — time, cost, quality of the result — and one scenario in which the customer does not need you. Naming the limits of where you apply makes everything else more credible.
What stops a large player from copying this in a quarter?
What the investor is checking. Whether the advantage holds over time. "In theory it can be copied" is an acceptable answer if you know how much of a head start you have and what you intend to do with it.
- Does not convince yet: "Our technology is unique", with no detail at all, or "they're too slow".
- Works: real sources of advantage: data that only accumulates through working with customers; integrations that take months to approve; switching costs; industry knowledge from the inside; speed of iteration. Plus a plan for how the gap widens.
- Prepare: two or three factors with one piece of evidence each — evidence from what exists today, not from what is planned.
Block 6. Team
Why are you the people to build this?
What the investor is checking. The connection between your experience and this specific problem. Total years of experience say little; six years spent inside this exact industry say a lot.
- Does not convince yet: a retelling of the CV and the phrase "over ten years of industry experience".
- Works: two or three facts that explain your access to the customer and your understanding of the process from the inside: what you saw with your own eyes, why doors open for you.
- Prepare: one sentence per founder — what they did before, and what that gives the project now.
Who owns sales, and who owns the technology?
What the investor is checking. Whether both functions are covered and whether revenue has an owner. "We do everything together" usually means nobody is doing sales.
- Does not convince yet: "We're all generalists, we don't split responsibilities."
- Works: an explicit split of ownership and a calm admission of the gap, with a plan: "I do sales today; the first commercial hire is what this round is for."
- Prepare: a one-page responsibility map and a list of the gaps, stating how and when you close each.
What have you already done together?
What the investor is checking. Whether the team has been run in. A team that has not been through a single hard month together is a separate unknown, and it is better to remove it with facts.
- Does not convince yet: "We met at a conference six months ago" as the only fact about the team.
- Works: a concrete result you produced together, plus one difficult episode: what you disagreed about and how you settled it.
- Prepare: two or three shared facts and the status of your agreements: equity split, vesting terms, how much time each founder actually gives the company.
Block 7. The round
How much are you raising, and what for?
What the investor is checking. Whether the amount matches the plan of work and the stage you are at. The expense breakdown shows what you were thinking about when you named the number.
- Does not convince yet: "We need investment for growth and marketing."
- Works: "The amount covers eighteen months: half goes to engineering and two developers, a quarter to the commercial team, the rest to infrastructure and a buffer."
- Prepare: an allocation across four or five lines, a hiring plan by quarter, and the runway in months.
Which metric does this money get you to?
What the investor is checking. Whether you know what has to be shown at the next stage. Money does not buy time; it buys the move into a state where the next conversation becomes specific.
- Does not convince yet: "This is enough for eighteen months of work."
- Works: one headline metric with a number and a date, plus two supporting ones: "By the end of the period we are at this level of recurring revenue at this level of retention."
- Prepare: a one-sentence formulation and an intermediate checkpoint that shows whether you are on track.
What happens if the round does not close?
What the investor is checking. Sobriety and survivability. The question is almost never hostile: it shows whether the company stays alive without outside money.
- Does not convince yet: "Then we shut down", or "we're not considering that scenario."
- Works: a plan on your own money: what gets cut first, what revenue keeps the team together, what pace you can hold, and how many months you last that way.
- Prepare: your runway in months at current spend, a reduced scenario, and the point at which you take the decision to cut.
Block 8. Why now
What changed in the world that makes this possible only now?
What the investor is checking. Two questions at once: why nobody did this five years ago, and why it is not too late today. A good answer explains both.
- Does not convince yet: "Everyone is doing AI right now" — that describes a fashion, not a cause.
- Works: one or two concrete changes: a technology got cheap enough for the task to make economic sense; a new reporting requirement appeared; customers changed a habit.
- Prepare: the explanation of the change plus one fact from your own practice showing that the change has already reached your customers.
When you do not have an answer, the strongest move is to say so out loud: "We have not measured that yet. We will have the number after the next three implementations — I'll come back to you in a month." And then come back. A promise kept builds more trust than an elaborate answer given in the room.
How to rehearse
Knowing the answer and being able to say it are two different skills. Rehearsal is not about memorising; it is about not hunting for the wording at the moment the question lands.
- Take the five most uncomfortable questions. Not the ones that are pleasant to answer — the ones you want to steer away from. Usually that means retention, acquisition cost, and the no-round scenario.
- Answer out loud and record yourself. A formulation that is flawless in your head often falls apart by the second sentence. Listening back finds that in one pass.
- Set a timer for 60–90 seconds. People stop listening to answers longer than a minute and a half. If you cannot fit it, you have not yet chosen what matters most.
- Hold a three-sentence shape. The fact or the number. How it was obtained and on what sample. What you are doing next. Everything else only if asked.
- Build one page of numbers. Ten to twelve figures: revenue, paying customers, retention, acquisition cost, average contract value, runway in months, team size — and the date they are current as of. Repeat that same page in the deck appendix so no number ever sounds different in two places.
- Ask someone outside the team to run the questions back to back. Have them ask "why?" three times after each answer. The third "why" is what exposes what still needs collecting.
- Write the list of what is not yet evidenced. That is your two-week plan before the meeting, not a reason to postpone it. Some items will close with data; some will stay honest hypotheses.
What these questions look like against one specific presentation is visible in our pitch deck review example: on our demo deck for StockPulse, the deck states ARPA per year = 206,000 ₽ while 18,000 × 12 = 216,000 ₽, and all three pilots are free with the move to a paid plan agreed only verbally. Two numbers in one deck and unpaid pilots are exactly the material an investor's first two questions are made of. The recurring mismatches between slides are collected in our piece on pitch deck mistakes, and the order in which to assemble the story is in how to prepare a pitch deck for investors.
This material is informational, is not investment advice and does not promise any fundraising outcome. The wording of these questions differs between investors and between stages: treat this as a basis for preparation, not as a required script for the meeting.
Find out your five questions before the meeting
Send your presentation as PDF or PPTX to our Telegram bot and get a quick diagnostic with no payment: what already works in the deck, what still needs evidence, and the five questions that will be asked about this specific deck. No account required. A deep review with an extended fix map is ₽1,500.
No payment, no sign-up for the quick diagnostic. Startup pitch deck feedback here is produced by a language model following a fixed script, from what is inside your file only: it is a first-pass review, not due diligence.
Get a quick diagnostic Discuss a deep review