Walk your team through real customer journeys. Highlight where deals stall, where customers struggle, and where expansion opportunities hide, all on a shared map.

The Knowledge Gap

Your product team has spent weeks researching users, mapping journeys, and identifying where people struggle. Meanwhile your sales team is learning the product from a slide deck that was last updated three quarters ago. Customer success is troubleshooting issues they have never seen mapped to the broader user flow.

As a result, sales reps talk about features instead of problems, and CS teams react to tickets instead of anticipating friction. Both groups are missing the context that product already has: how customers move through your product, where they get stuck, and what makes them successful.

What You Need

Cartographer with an AI assistant, such as Claude, ChatGPT, or similar, connected through the MCP server.
Knowledge of your customer journey, from first contact through onboarding, adoption, and renewal. Even a rough outline works as a starting point.
Real examples of where deals stall, where customers churn, and where expansion happens. Support tickets, win/loss notes, and CS call summaries are all good inputs.

The Workflow

You will build a story map that follows the customer lifecycle, then add the pain points, objections, and opportunities that your sales and CS teams need to understand. The map does not go stale, because it is the same map product keeps updating as they build.

Map the Customer Journey

Start with journeys that follow the customer lifecycle rather than your product’s feature set. Think “Evaluate & Buy”, “Onboard”, “First Value”, “Expand Usage”, and “Renew”. Under each journey, create steps for the specific things a customer does at that stage.

Ask your AI assistant to help scaffold this. Describe your product and customer lifecycle, and it will create the journey and step structure using journeys_create and steps_create. You can refine from there: rename steps, reorder journeys, and adjust until the map reflects reality.

Mark Pain Points and Opportunities

Walk through each step and add cards for the problems customers face and the opportunities they represent:

risk cards for common objections, known friction points, and reasons deals stall. “Security review takes 3 weeks”, “Users resist changing existing workflow”, “Admin setup is too complex for mid-market.”
objective cards for expansion opportunities and success milestones. “Cross-sell analytics add-on after adoption”, “Executive sponsor unlocks department-wide rollout.”
question cards for discovery questions reps should ask. “Who else is involved in the evaluation?”, “What does success look like in 90 days?”
learn cards for insights from real customers. “Enterprise buyers care more about audit logs than SSO”, “Onboarding completion correlates with 6-month retention.”

Feed your AI assistant win/loss reports, CS call notes, or support ticket summaries. It extracts the relevant insights and creates typed cards placed at the right stage of the journey.

Add Personas for Buyer Roles

Create personas for the different stakeholders involved in a deal: the end user, the champion, the economic buyer, and the blocker. Tag cards with the persona who cares most about that concern.

A risk card about “needs IT security review” gets tagged with the IT Buyer persona. An objective card about “faster report generation” gets tagged with the End User. When a rep is preparing for a call with a specific stakeholder, they filter the map by that persona and see what matters to that person at each stage.

Build the Talk Track

Ask your AI assistant to read the map and generate talk tracks for each persona and journey stage. It pulls from the card descriptions, comments, and risk/question cards to build messaging that addresses customer concerns rather than generic value propositions.

When product adds a new learn card from a customer interview, or resolves a risk card by shipping a feature, you can regenerate the talk track to reflect the change.

Create saved views filtered by persona, and share them as read-only links. The “Champion Playbook” view shows only cards tagged with the Champion persona. The “Onboarding Guide” view collapses pre-sale journeys and focuses on the post-sale experience.

Reps bookmark their relevant views and check them before calls. CS managers pull up the map during team meetings to walk through the journey stage by stage. Everyone works from the same map that product maintains.

Running a Training Session

The map itself is the training deck. Walk through it left to right, journey by journey:

Set the stage. Start with the “Evaluate & Buy” journey. Show the steps a prospect goes through and the risk cards at each step. These are the objections reps will hear.
Introduce the personas. Filter by each buyer persona and show how their concerns differ: the end user cares about daily workflow, the economic buyer cares about ROI timelines, and the IT buyer cares about compliance.
Walk the critical path. Highlight the steps with the most risk and question cards. These are where deals stall or customers churn. Discuss each one, share what has worked in the past, and connect it to product features that address the concern.
Show the opportunities. Filter for objective cards to show expansion triggers. These are the signals that a customer is ready to grow, and the conversations CS and sales should be having.

Keeping It Current

The biggest problem with training material is that it goes stale. A story map avoids this because it is already where your product team works. When product ships a feature that removes a friction point, the corresponding risk card gets resolved. When a new customer interview turns up a new objection, it becomes a card on the map.

Set a cadence, monthly or quarterly, to review the map with sales and CS. Walk through what changed since the last session: new risks, resolved pain points, and updated learnings.

Tips

Use customer tags for real deals. Tag cards with real customers when a pain point or opportunity comes from a specific account. This helps reps personalize conversations and gives CS managers account-level context.
Separate “before” and “after” the sale. Sales cares most about the pre-sale journey. CS cares most about post-sale. Create views for each so nobody has to wade through irrelevant stages.
Add discovery questions as question cards. Place the questions reps should ask at each stage on the map. New reps get a built-in script for every conversation.
Capture competitive intel. When reps hear about competitors during deals, add learn cards with the context. Over time the map builds a competitive landscape that product and sales both benefit from.
Do not over-polish. This is not a slide deck. Rough cards with real quotes and honest assessments are more useful than polished marketing language.

Sales & Customer Success Training Material