Mind map for client presentation

Write the one thing they must remember

The root of the map holds a single sentence: the thing you want the client to repeat to a colleague tomorrow. Not the project, not the service, not the timeline. One sentence, written as the client would say it, because a sentence they would not repeat is not a message yet.

Put two children under it. The first says why it matters to them, in their terms: the cost of the problem, the risk they carry, the number that changes. The second says what you want from them today. Every later branch can be checked against them.

Test the sentence before you build anything. Say it out loud in the time it takes to walk to a kitchen and back. If it takes longer than that, it is two sentences, and the room will only remember one of them. The complete Canvasola guide shows how to start a map and keep it tidy.

• The root is one sentence, in the client's words
• One child says why it matters to them, one says what you want today
• Every branch is checked against the root sentence
• The sentence is said out loud before any slide exists

Note: If you cannot write the sentence, you do not yet know what you are selling. That is a better problem to have the week before the meeting than during it.

One branch per slide

Each branch is a slide, and the branch label is the slide title. Under it add two children: the single point the slide makes, and the line that carries the room to the next one. Reading only the branch labels should tell the whole story.

Build the spine before the slides. If you make the actual slides first, you get twenty minutes of formatting that commits you to a structure you have not tested. On the map the structure costs a minute to change, and the slides can be built from the branch labels afterwards in whatever tool you present from.

Keep the branches you cut. Do not delete a slide you decided against. Move it to a branch called cut and why. That branch is how you answer the question later about why a certain topic was missing, and it keeps you from re-adding the same idea in the next pitch.

• One branch per slide, labeled with the slide title
• Children: the point, and the transition to the next slide
• The branch labels alone should tell the story
• Cut slides are moved, not deleted

Note: Eight branches is usually plenty for a client meeting. A structure that needs twenty slides is usually two ideas competing, and the second one deserves its own meeting.

Put the proof in the notes

The slides carry the argument and the notes carry the evidence. Open the rich note on a branch and use the bulleted list for the numbers, the sources and the caveats. When a client asks where a figure came from, the answer is one click away rather than a scroll through a document you cannot find under pressure.

Put the obvious objection in the note too, with your answer. Every experienced client has one question in mind about your proposal, usually about cost, timing or risk. Writing the objection down while you are calm means you can answer it in a sentence instead of defending the whole idea.

Keep the notes honest about the weak spots. A line saying the third-party data was unaudited does more for trust than a polished slide does, and it stops you being caught out by the one person who checked. Mark any figure that is an estimate as an estimate, every time.

• One bullet per figure, source and caveat
• The likely objection and the answer are written in the note
• Estimates are labeled as estimates
• Nothing in the notes depends on finding a separate document

Note: A note can hold far more than fits on a slide, up to 80,000 characters. That is exactly the point: the detail belongs here, and the slide only needs the one line.

Build the closing ask as the last branch

Make the last branch the ask, and never let a presentation end without one. Under it, three children: what you want them to decide or do, by when, and what the first step looks like if they say yes. A meeting that ends in general agreement is not a meeting that produced anything.

Put the cost of saying yes in the note, and the cost of doing nothing as well. Clients are not refusing the work; they are weighing it against the risk of changing something now. Naming both sides turns the decision into a comparison they can make.

Agree the shape of the ask with yourself before the meeting. If you need three decisions, you need three branches, because a single ask with three parts inside it will get a half answer. The board meeting guide covers how to state decisions so a minute-taker can record them.

• The last branch is the ask, always
• Children: the decision, the deadline, the first step
• The note covers the cost of yes and the cost of doing nothing
• Three decisions means three branches, not one branch with three parts

Note: If you are nervous about the ask, make it smaller rather than hiding it. A decision to run a two-week paid trial is easier to say yes to than a contract, and it still moves the project.

Rehearse with the presentation mode

Rehearse on the map, not on the slides. Press P to enter presentation mode: the first slide shows the root label with your one sentence, and then each first-level branch takes one slide showing the branch label with its immediate children. That is the spine of the argument, which is what you need to say out loud.

Stand up and speak it. One slide should take under ninety seconds, and if it does not, it is two slides. When you reach the ask, say it in the same words you wrote on the branch, without softening it, and then stop talking. The silence after an ask is working for you, not against you.

Rehearse with the real material nearby. Keep the deck outline in a second workspace tab and use split view to show both side by side with a draggable divider, so you can check the map against the slides you will open. The split view guide covers the setup.

• Presentation mode shows the root sentence, then one slide per branch
• Ninety seconds per slide is the ceiling
• The ask is said in the words written on the branch
• Split view puts the deck outline next to the map

Note: Presentation mode walks the map in a fixed order: the root, then one slide per branch. Arrow keys or space move between slides, Escape exits, and on-screen Prev and Next buttons are there when you prefer the mouse.

Send the map as the follow-up

The map becomes the record of what was agreed. Export it as PNG for a quick image to attach to the follow-up email, or as vector SVG if they want to drop the structure into their own deck. The export guide covers the formats and their trade-offs.

Update the map after the meeting, not before sending it. Add a branch for what was agreed, note what was deferred and why, and keep the branches that were rejected with their reasons. Within a week that map is more useful than the deck, because it answers the next question before it is asked.

Version history keeps 20 snapshots, so a structure you were happy with is recoverable. If you cut a branch in the wrong place during a late edit, you can step back to the version from before the meeting and rebuild from there rather than reconstructing it from memory.

• PNG for an email attachment, SVG for their own deck
• What was agreed and deferred is added to the map after the meeting
• Rejected branches keep their reasons
• Version history holds 20 snapshots to fall back on

Note: A map is not a contract and it is not a shared document. It is a summary you send as a file, so write what was agreed in plain language and let the client correct you if you have got it wrong.

A checklist you can reuse

• The root holds one sentence the client would repeat
• Two children explain why it matters and what you want today
• One branch per slide, with the branch labels telling the story
• Cut slides are moved aside with a reason, not deleted
• Every figure, caveat and objection is in the notes
• The last branch is the ask, with a deadline and a first step
• Presentation mode has been used for a full timed rehearsal
• The follow-up export is sent with what was agreed written down

Common mistakes to avoid

• Building slides before the structure. Formatted slides commit you to an untested argument, and changing your mind later costs hours. Prove the spine on the map first, where it costs minutes.
• Branches that are titles only. A map of slide titles has no argument in it, only a schedule. Add the point and the transition under each branch so the labels alone tell the story.
• The proof kept outside the map. Numbers that live in another document are numbers you cannot find while being asked about them. Put the source and the caveat in the note.
• No ask at the end. A presentation that ends in general agreement leaves the client with nothing to do. Make the ask a branch and say it in the words you wrote.
• Sending the deck and nothing else. The map carries the reasoning that the slides dropped. Send the export with what was agreed written down, and let the client correct it.

Frequently asked questions

How many slides should a client presentation have?

Eight branches is a comfortable number for a working client meeting, with the caveat that slides can be as dense as the room allows. If the structure needs twenty, it is usually two ideas competing, and the second one deserves a separate conversation.

Can I present directly from the mind map?

You can walk the structure in presentation mode: the root sentence, then one slide per branch with its immediate children. The order is fixed by the map, so it works best as a rehearsal tool or as a summary at the end of a live deck rather than as the deck itself.

What format should I send the map in?

PNG for an email attachment, since it needs no software to open, and SVG when they want to place the structure in their own deck, since it stays sharp at any size. Both come from the export action in the toolbar.

Does everyone on the team need their own copy?

There is no shared editing in Canvasola, so everyone works from a file or an export. Send the PNG or SVG to the people who need to review the structure, and keep the map itself as the place where you make changes.

This guide is part of the mind map use cases collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.