Almost every pitch deck has a dashboard on it. Sometimes it's a real metrics screen from the founder's analytics. Often it's a mockup - a projection, a target state, or a screenshot of what the product will look like once a feature ships. Investors are used to seeing both, and they expect them to be labeled accurately. This guide walks through how to build a dashboard mockup that holds up in an investor meeting, where the line is between honest founder LARP and the kind of misrepresentation that ends rounds, and how to label each flavor of dashboard so reviewers know what they're looking at.

What Investors Expect From a Dashboard Slide

Experienced investors read dashboard slides the way pilots read instruments. The first question isn't "is this number good?", it's "what does this number represent?" - a real audited metric, a directional projection, a hypothetical product state, or a benchmark. Every flavor is legitimate; what gets a deck killed is presenting one flavor as another.

A current-state dashboard says "this is the state of the business today". A projection says "this is what we expect by [date], assuming [conditions]". A product-UI mockup says "this is what the screen will look like when we ship this feature next quarter". A benchmark says "this is what category leaders typically look like at this stage". The visual can be the same in each case. The label is what changes, and investors do read the labels.

Three Flavors of Pitch Dashboard

Most founder dashboards fall into one of three buckets.

Current-state dashboards. Real metrics rendered cleanly. The data is yours, the source is auditable, and the label says "as of [date]". When you have real numbers to show, this is always the most credible option. If you use a mockup tool to clean up a real dashboard for the slide - removing customer PII, normalizing the time range, tightening the layout - that's housekeeping, not misrepresentation, as long as the numbers reflect what your actual dashboard says.

Projections. Forward-looking dashboards labeled as projected. A revenue chart that ends at $0 today and curves up to $200K MRR by month 18, with the model assumptions footnoted on the slide. Projections are not lies; they're forecasts, and serious investors evaluate them on the model behind them rather than the curve shape. Label them, footnote the assumptions, and move on.

Product UI mockups. Screenshots of a dashboard that doesn't exist yet, used to show what the product will look like at scale. Common on early-stage decks where the product is still being built. Label the slide as "product mockup" or "UI concept" and there's no confusion.

The same mockup tool produces all three flavors. The difference is what the label says, and that's the difference investors care about.

Step-by-Step: A Pitch-Ready Mockup

Step 1. Decide what the dashboard represents. Before you open the mockup tool, write the one-sentence answer to "what is this slide saying?" If it's current state, you should be using real numbers. If it's a projection, you'll need the model behind it on a follow-up slide. If it's product UI, you need to mark it as such. Don't start with the visual - start with the claim, and let the visual follow.

Step 2. Choose the platform template that matches the metric. If you're showing payment volume, use the Stripe template. If you're showing e-commerce revenue, use the Shopify template. If you're showing creator metrics, use the YouTube Studio template. If you're showing your own product, use the generic Creator template or design your own layout. Investors recognize the platforms, which is half the work of communication.

Step 3. Fill in numbers that match your narrative. The math has to hold. Gross volume should equal charges times average charge. Conversion rate should track sessions and orders. A mockup that shows internal contradictions is the easiest way to lose credibility in the Q&A. Use noisy numbers, not round ones - $9,847 reads as real, $10,000 reads as approximate. Match the scale to where your story says the business is; an over-the-top number on an early-stage slide reads as overreaching.

Step 4. Label clearly: current, projection, or product UI. A small label in the top corner of the slide, or just under the dashboard, that says what it is. "Current as of May 2026", "Projected Q4 2027", "Product mockup". This is invisible in the read-through and decisive in the diligence call. It's also the difference between a normal founder mockup and the thing that gets called out in the post-meeting debrief.

Labeling: Current, Projection, Product UI

Each flavor has a conventional label that investors recognize without slowing down.

For current-state: "As of [date]" or "Live metrics, [date]". If the data is auditable through a third party (Stripe, Shopify, Plaid-linked accounts), say so.

For projections: "Projection" or "Forecast" prominently on the slide, plus the model assumptions on a follow-up slide. Investors will ask about the assumptions; have the answer ready rather than letting them dig.

For product UI: "Product mockup", "UI concept", or "Coming Q3". Particularly important when the product looks polished enough to be confused with a real shipped feature.

For benchmarks: "Industry benchmark, source: [name]". Cite the source on the slide or in the appendix.

The pattern is the same in every case: name what you're showing, and let the visual do its work without ambiguity. The companion results dashboards for courses guide applies the same labeling discipline to a different audience.

What to Avoid So You Stay Fundable

Most of the failure modes around pitch-deck dashboards come from one root: a mockup that the slide implies is a real, audited metric. The fixes are short.

Don't show a projection without labeling it. An unlabeled curve climbing past competitors is read as a current claim, and the gap between that read and reality is exactly what kills rounds in diligence.

Don't show a product UI mockup as if the feature ships. "Here's our analytics dashboard" with no qualifier, when the analytics dashboard isn't built yet, is the kind of overstatement investors talk about with each other.

Don't insert customer logos, real testimonials, or specific named numbers into a mockup. The moment a mockup picks up a real entity's name, it stops being a mockup and starts being a misrepresentation of that entity.

Don't recycle the same mockup across different framings. A "product UI concept" on one slide and the same screenshot as "early traction" on another slide is the same image telling two different stories, which is the pattern that ends conversations.

A clearly labeled mockup is a perfectly normal part of a deck, and most founders use them. The work is in matching the visual to the label and treating the label as load-bearing. The same discipline carries across the rest of this cluster - from the pillar LARP guide to the spot-a-fake guide - and it's what separates a confident pitch from a flagged one.