How Do I Explain Complex Technology to Investors?
Updated: 3 days ago
Start with the problem and the outcome, not the mechanism. Explain your technology at the level of what it makes possible, why it works, and why it is hard to copy, and save the technical depth for diligence. Put it in one sentence before you put it in twenty slides, show it rather than describe it wherever you can, and test the explanation on someone outside your field before you test it on an investor.
Most founders of technical companies explain their technology the way they would explain it to a peer: mechanism first, with the commercial implications left for the listener to work out. Investors rarely do that work. They are not usually assessing whether the science is elegant. They are assessing whether a team can turn it into a large company, and the explanation has to answer that question first.
What investors actually need to understand
An investor does not need to understand your technology the way your engineers do. They need to understand enough to answer a specific set of questions.
The question | What they need from you | What they do not need yet |
What problem does this solve? | A clear, specific problem with a real cost | The history of the field |
How big is it? | Who has the problem and what it is worth to solve | Every possible application |
Why does this work? | The core insight, in plain language | The full method |
Why is it hard to copy? | What protects it: IP, data, know-how, time | Every patent claim |
Why now? | What has changed that makes this possible or urgent | Your full research timeline |
Why this team? | Why you are the people to build it | Every publication |
How does it make money? | The business model and the route to revenue | A detailed pricing model |
What could go wrong? | The main risks and how you will reduce them | A list of every uncertainty |
The middle column is the explanation. The right-hand column belongs in the appendix or the data room, where the investors who want it can find it.
There are usually two investors in the room
In many funds, the decision involves two kinds of reader.
The generalist partner who will champion the deal internally. They need the story: the problem, the outcome, the market and the team. They will have to retell it to colleagues who were not in the meeting.
The technical reviewer, an associate, advisor or expert brought in for diligence. They need the evidence: data, methods, benchmarks and honest limits.
Your materials have to work for both, and they have to work in that order. Lead with what the generalist needs, and make the depth available for the technical reviewer without forcing everyone through it. A deck that only satisfies the technical reviewer never reaches them, because the partner did not get far enough to call them.
The most important test is that the explanation survives being retold. Most investment decisions are made in a partner meeting you will not attend. Whatever your champion can repeat accurately is what the decision is based on.
Techniques that work
Start with one sentence
Before building a deck, write one sentence that says what the company does, for whom, and what changes as a result. Then cut it until it works without any technical term a generalist would not know.
If you cannot write that sentence, the deck will not fix it. Every slide will be compensating for the missing sentence.
Climb the "so what" ladder
Technical founders often start at the bottom rung and stop there. Walk up it instead:
Mechanism. What the technology does at a technical level. Capability. What that makes possible that was not possible before. Outcome. What changes for the customer as a result. Market. Who will pay for that outcome, and how much.
Investors mostly need the top three rungs. The mechanism is there to make the others believable, not to lead.
Compare with how things are done today
Absolute numbers mean little to an investor outside your field. Relative ones mean a great deal. "Ten times faster than the current method", "a fifth of the cost", "the first approach that works at room temperature". A comparison with the incumbent tells an investor both what you do and why it matters, in a single line.
Use analogy carefully
A good analogy can make an unfamiliar idea feel familiar quickly. A bad one can make a serious technology sound trivial, or imply something that is not true. Use analogy to make the idea graspable, then move quickly to the real explanation, and never let the analogy carry a claim the technology cannot support.
Show it
Seeing a technology work is more persuasive than any description of it. A short film of the product in use, a demonstration, or 3D animation showing what cannot be filmed can communicate in thirty seconds what a slide struggles to do in five minutes. A short film also travels: it can be forwarded to a partner who missed the meeting and explain the company without you. More on why in the benefits of film production for UK startups, and on the techniques in how to make a product film for something that's hard to see.
Name the risks yourself
Every deep tech investment carries technical risk, and investors know it. Naming the main risks yourself, along with the milestones that will reduce them, signals that the team understands its own technology and is not hoping the question does not come up. It also lets you frame the risks rather than having them framed for you.
Make milestones do the explaining
Investors fund progress through uncertainty. A clear sequence of technical and commercial milestones, each reducing a specific risk, explains the technology's maturity better than a general description of where it is. "Prototype validated in the lab, pilot with two customers next, certification after that" tells an investor exactly where the company stands.
Where the technology goes in a deck
The technology usually needs less space at the front of a deck than founders expect, and more space at the back.
A typical order that works for technical companies:
1. The problem. Specific, costly, real. 2. The insight. The idea that makes a better solution possible. 3. What it does. The outcome, shown rather than described where possible. 4. Proof. Data, results, pilots, customers, partners. 5. Why now. 6. The market. 7. Why it is hard to copy. 8. The team. 9. The business model. 10. Milestones and the raise.
The deeper technical explanation then goes in an appendix and the data room, for the investors and reviewers who want it.
The insight slide is often the most important one in a deep tech deck, and the most often missing. It is the one sentence that explains why your approach works when others have not.
The deck itself is part of the explanation
How the materials look is not separate from how well they explain. A clear structure, well-designed diagrams, readable charts and a consistent visual identity make a complex idea easier to follow, and they signal that the team pays attention to detail. A crowded, inconsistent deck makes the technology look less mature than it is.
This is the halo at work: the impression formed before the content is read colours how the content is judged. It is covered in more detail in the halo effect in branding.
Test it before an investor does
The outsider test. Explain the company to a smart person with no background in your field. If they cannot explain it back to you, the investor will not either.
The retelling test. Ask that person to explain it to someone else a few days later. Listen to what survives. That is roughly what an investor will say in their partner meeting.
The jargon test. Go through the deck and mark every term a generalist would not know. Remove it, define it, or move it to the appendix.
The one-minute test. If you had sixty seconds in a lift with the partner you most want to back you, what would you say? That is the opening of the deck.
Common mistakes
Leading with the mechanism. The most common mistake, and the one that loses generalist partners on the second slide.
Treating the deck as a technical paper. A deck is an argument for an investment, not a record of the research.
Too much detail, too early. Depth belongs in the appendix and data room, not the opening slides.
No clear insight. The deck explains what the technology is but never says why it works when others have not.
Hiding the risks. Investors will find them. It is better that they hear them from you.
Overclaiming. A single claim that does not survive technical diligence can end an otherwise strong process.
Designing for the founder rather than the reader. What feels complete to someone who built the technology is often impenetrable to someone meeting it for the first time.
Frequently asked questions
How do you explain complex technology simply?
Start with the problem and what changes when it is solved, then explain the core insight in plain language, compare the result with how things are done today, and show it working wherever possible. Keep the full technical detail for those who ask for it. The aim is clarity, not oversimplification: arrange the true explanation so it can be understood, rather than removing the parts that make it true.
How much technical detail should a pitch deck include?
Enough to make the main claims believable, and no more in the main deck. Most of the technical depth should sit in an appendix and the data room, where technical reviewers can examine it during diligence. The main deck should focus on the problem, the insight, the proof, the market, defensibility, the team and the milestones.
What is the most important slide in a deep tech pitch deck?
Often the insight slide: the single idea that explains why your approach works when previous approaches have not. It connects the problem to the solution and is the slide most likely to make a generalist investor believe the technology, yet it is frequently missing.
Should I use a video in an investor pitch?
Often, yes. A short film or animation can show a technology working, or show what cannot be filmed, far more clearly than slides. It also travels well, because it can be shared with partners who were not in the meeting. Keep it short, focused on the outcome, and honest about what is real footage and what is animation.
How do I explain my technology to a non-technical investor?
Lead with the outcome and the customer, use comparisons with current methods rather than absolute technical figures, use analogy carefully to make the idea familiar, and then show proof. Test the explanation on someone outside your field and refine it until they can explain it back accurately.
How do I handle technical due diligence?
Prepare for it from the start by keeping the technical evidence organised in a data room: methods, data, benchmarks, IP, test results and the team's background. Be clear about limits and risks. Diligence goes more smoothly when the main deck's claims are precise enough that the detailed evidence simply confirms them.
Working with VMV.STUDIO
VMV.STUDIO helps deep tech, aerospace, advanced manufacturing and energy companies explain what they do, to investors and everyone else. That includes the narrative, investor decks, diagrams and data visualisation, and the films, 3D and motion that show a technology working, all made in the same team.
If your technology is easier to build than to explain, get in touch.
Comments