Tithi MondalBlog

Guide6 min readUpdated

App Prototype for Investors: What to Show and Skip

Planning an app prototype for investors? Learn what to show, how many screens to build, and what to leave out so your clickable demo stays clear.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

App Prototype for Investors: What to Show and Skip: cover illustration

Picture a founder from Kolkata who has a 20-minute meeting with investors on Google Meet. She has a pitch deck, but she also has an idea that is hard to explain in slides: a bill-splitting app for shared flats. She asks me, "Should I show a prototype? How much of it?"

My answer is yes, if the prototype is short and has a clear purpose. This guide explains what an app prototype for investors should contain, how many screens to make, and what to leave out. It does not give fundraising or financial advice. It covers the design side only.

What a prototype is, and why it helps in a pitch

A prototype is a clickable model of your app. It looks like the real product, and buttons move you from screen to screen. But no real code runs behind it. Designers often build prototypes in Figma.

A prototype helps in a pitch for one reason: people understand a product faster when they can see it than when they hear a description. A demo before development also shows that you have thought about the user, not only the idea.

A prototype is not proof that the business works. It does not show that users will pay, or that the product can be built at a given cost. It shows one thing: what you plan to make. Do not claim more than that.

If you want to know where a prototype sits among wireframes and mockups, read wireframe vs mockup vs prototype.

Decide what the demo must prove

Before any design, write one sentence: "After the demo, the investor should understand ___."

For the bill-splitting app, that sentence could be: "A flat of four people can add a shared expense and see who owes what in under 30 seconds."

Everything in the prototype must support that sentence. This is the same thinking used in MVP design. If a screen does not help the sentence, remove it from the demo.

How many screens to build

For a pitch demo, I suggest 8 to 15 screens. This is a guide, not a rule. The right number is the number of screens in one complete journey, plus a few more for context.

Here is a sample structure for the bill-splitting app.

OrderScreenPurpose in the demo
1Welcome and sign-in with phone numberShows the entry point
2Home with the flat's balanceShows the main value at once
3Add expenseThe core action
4Choose who shares itShows the clever part
5Expense added, balances updatedThe result
6Who owes whomThe payoff screen
7Settle up by UPIShows a real Indian payment habit
8Payment done, reminder sent on WhatsAppCloses the loop

That is 8 screens, and it tells a full story. An investor can follow it in 2 or 3 minutes.

Do not build 40 screens because you have time. A long prototype invites the viewer to wander, and wandering leads to questions about screens that are unfinished.

What to show

  • One main journey, start to result. The user begins with a need and ends with the need met.
  • The moment that makes you different. In our example, the "choose who shares it" screen. Give this screen extra care.
  • Real-looking content. Use believable names, amounts in rupees and Indian phone numbers. "Lorem ipsum" and "User 1" make the product feel unreal.
  • The right language. If your users read Bengali or Hindi, show one screen in that language. Read regional language app design for how this works.
  • A short problem frame. Open with one screen or sentence about the user's problem, before the product.

What to leave out

  • Settings, profile editing and notification preferences. Every app has them. They add nothing to the story.
  • Rare cases. Forgot password, empty states and error messages matter in the real product, but not in a pitch. Keep them in a separate folder in case someone asks.
  • Features that are not in your first version. If you show a loyalty program that you will build in year two, an investor may think you are planning too much.
  • Many visual variations. Pick one clean style. Dark mode, three colour themes and animation experiments distract.
  • Dead buttons. If a button in the prototype does nothing, the viewer will click it and feel the demo is broken. Either make it work or remove it.

One honest warning: do not show screens for things you do not plan to build, only to look bigger. Investors ask questions. You must be able to answer.

Build it so it does not break in the room

A prototype that fails during a call loses attention fast. These small habits help.

  1. Keep a recorded backup. Record a short screen video of the full journey. If the link fails, you play the video.
  2. Test on the device you will use. Open it on the laptop or phone you will share. Check sound, screen size and internet.
  3. Use a clear starting screen. Open the prototype at screen 1, not in the middle of a file.
  4. Practise the click path. Click through the demo ten times. You should not need to look for the next button.
  5. Prepare a one-page flow map. A single picture of all screens helps when someone asks, "What happens before this?"

A good prototype is also easy for developers to read later. If you plan to hire a developer, see the Figma developer handoff checklist.

Prototype and pitch deck work together

The prototype does not replace the deck. The deck explains the problem, the market and the plan. The prototype shows the product. A short pattern works well: 2 or 3 slides on the problem, then 2 to 3 minutes of demo, then back to slides for the rest.

A deck needs its own design care. My notes in pitch deck design guide cover that side.

How a designer builds this

My steps are the same as for any product, but compressed.

  1. Understand. I ask what the demo must prove and who will watch it.
  2. Map the flow. I draw the single journey and cut the rest.
  3. Wireframe. I sketch the 8 to 15 screens in plain form.
  4. Design the interface. I add colour, type and real-looking content.
  5. Prototype and hand off. I link the screens in Figma, test the click path and share the file.

A focused demo prototype takes less time than a full app design, because it covers less. Pricing depends on the number of screens and the polish you need. For the wider picture of cost, see how much UI/UX design costs in India.

If you have a pitch coming and need a clear clickable demo, you can read about my UI/UX design work or message me with your idea.

Frequently asked questions

Is a Figma prototype enough for an investor demo?

+

Yes, for most early-stage pitches. A clickable Figma prototype shows the product idea clearly. It does not prove that the product is built or that users will pay.

How long should a pitch demo be?

+

Aim for 2 to 3 minutes of clicking through one main journey. Keep extra screens in a backup file for questions.

Should I build a working app before meeting investors?

+

Not always. A prototype can be enough to explain the idea. Whether to build first is a business decision for you and your advisers.

Can I use real user data in the prototype?

+

Use made-up names and numbers instead. Real personal data should not appear in a demo that you share with others.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.