Live samples · Real API output

Every tool. Real output.

Every artifact on this page was generated by the live API against realistic sample inputs (most use "Northwind Benefits" - a fictional dental insurer). Click any tool's header to run it yourself.

01

CX Mission Statement

Build your own →
For Acme Bench (B2B SaaS)
"At Acme Bench, our customers expect to get value on day one, not week three. We deliver that experience consistently through pre-built templates and opinionated defaults so our customers feel capable and in control from their first 15 minutes forward."
Brand promise

The statement leads with the core promise: value on day one, not week three. This is concrete, memorable, and avoids superlatives. It sets a realistic expectation that Acme Bench can measure and honor.

Customer value

The 'what's in it for them' is embedded in the contrast: replacing three days of setup with 15 minutes. The statement carries this through by emphasizing 'from their first 15 minutes forward' — a real, specific timeframe.

Consistent delivery

Pre-built templates and opinionated defaults are the engines of the promise. They're repeatable, scalable, and under Acme Bench's control. This grounds the statement in something the team can actually ship and maintain.

Customer feeling

Capable and in control anchor the emotional outcome. These are realistic, sustainable feelings that align with a fast-start experience. The statement reinforces this by tying it directly to the first-minutes experience.

02

Statement Critique

Critique your own →
Critiquing a corporate-speak statement · verdict
Rework required

"This is a textbook example of every mistake — zero customer specificity, all vanity phrases, no real promise."

Jeannie's rewrite

"At Globex, we help enterprise teams give their customers consistent, responsive support across every channel — so customers feel heard, and teams stay focused on what matters."

6 hard-fix issues flagged
Avoid vanity phrases: best-in-class, world-class, industry-leading, cutting-edge: "industry-leading provider of best-in-class omnichannel CX solutions, delivering world-class outcomes through cutting-edge AI"
Avoid corporate speak, jargon, acronyms: "omnichannel CX solutions"
Avoid 'deliver shareholder value': "maximize shareholder value"
03

Rollout Planner

Plan your rollout →
Announcement email subject

What we're here to do

Email body (Dana's voice)

Hi everyone, We just finalized something I want you to see. It's short. It's what we're here to do: *At Northwind Benefits, members expect clarity and speed when they need care. We deliver plain-language answers on first contact so members feel confident, respected, never confused.* This isn't a rebrand or a new initiative. It's a decision about what we already do — and what we stop doing. Starting this week, we're changing how we answer members. No more policy numbers without context. No more "per your plan document." No more transfers unless we've tried to answer first. If a member asks about a claim, we explain it in one or two sentences before we reference a section code. If they're confused, we restate it. If we don't know, we say that and we find out while they're still on the line. This will feel slower at first. It won't be. Transfers and call-backs take longer than clarity. I'm walking the floor this week. I want to hear what this brings up for you — what makes sense, what feels hard, what you need from leadership to make it real. More soon. Dana

Week-1 checklist (first 3 days)
  1. D1Monday: Send announcement email to all staff. Post Slack version in #general and pin it.
  2. D2Tuesday: Walk the member services floor. Ask three agents what they think the statement means for their calls today.
  3. D3Wednesday: Add the mission statement to the signature block of all member-facing email templates. Test with IT.
All-hands slide outline (10 slides, first 3)
  1. S1What we're here to do
  2. S2At Northwind Benefits, members expect clarity and speed when they need care. We deliver plain-language answers on first contact so members feel confident, respected, never confused.
  3. S3Why now
04

CX Success Blueprint

Draft your Blueprint →
Outcome

"Reduce new-customer churn in months 1-3 from 18% to 10% within 9 months, protecting $1.2M ARR by getting customers to first value in 48 hours instead of 3 weeks."

First domino to fall

Product ships MVP self-serve benchmark wizard by end of week 4 — customer uploads CSV, gets first report in 48 hours, no implementation manager required. This unblocks everything downstream.

Customer behaviors that drive the outcome (first 3)

Customer completes first benchmark analysis within 48 hours of contract signature

Customers who see their first competitive data point in week one renew at 2.3x the rate of those who wait three weeks

Customer invites 3+ team members to platform in first week

Multi-user accounts churn at 6% vs single-user at 24% — usage breadth predicts stickiness

Customer references Acme Bench data in internal meeting within 10 days

When customers use our data to make a decision in month one, they integrate us into workflow — churn drops to 4%

Org capabilities · 30-day moves (first 3)

Product ships self-serve benchmark wizard that produces first report in 48 hours with zero human handoff

Product

Ship MVP wizard: customer uploads CSV of their data, platform runs benchmark against anonymized peer set, delivers PDF report to customer email within 48 hours — no custom config, no implementation manager

Implementation team delivers kickoff calls in 20 minutes focused on workflow integration, not platform basics

Customer Success

Create 8-minute onboarding video that covers platform navigation and first benchmark interpretation, make it required step before kickoff call scheduling — managers reclaim 40 min per call for workflow design

Support monitors first-week activity and triggers proactive outreach when customer stalls before first value

Support

Build Slack alert that fires when new customer has account 72+ hours with no benchmark run — support reaches out via email with 'need help uploading data?' offer and links to wizard walkthrough

Purpose

This Charter defines how Acme Bench coordinates customer experience work across Customer Success, Product, Sales, and Support. It exists so customers get consistent, predictable outcomes from sign to renewal and beyond. It clarifies who owns what decisions, how conflicts resolve, and what cadence keeps us honest. The goal is to reduce onboarding time, start renewal conversations earlier, and close the loop on feature requests so customers see progress.

In scope
  • Onboarding process design and execution for all new customers
  • Renewal health tracking and proactive outreach 90+ days before renewal
  • Feature request intake, triage, and customer communication loop
  • Customer feedback synthesis shared with Product monthly
Out of scope
  • Product roadmap final prioritization — Product VP owns that call
  • Pricing and contract terms — CRO and Finance own that
  • Individual sales rep comp or territory design
  • Engineering sprint planning or resource allocation
Decision rights (first 3)

Changing the onboarding playbook or timeline

Decides: Director Customer Success

Prioritizing which feature requests get Product review this quarter

Decides: Product VP

Offering an at-risk customer a discount or custom term to save a renewal

Decides: CRO

06

CXI Compass v2

Take the assessment →
Overall CX maturity
63/100
Established

Northwind has cultural readiness and proof of traction; appoint a CX owner, map the journey, and measure 3 friction fixes to move from 63 to 75+ within a year.

Intentional Success
58/100

Northwind has tied CX work to business outcomes in pockets — the renewal script win proves that — but lacks executive accountability and a single owner. Low 20s NPS with no CX leader is the symptom. Insurance carriers live or die by retention and cross-sell; without one executive visibly accountable for those metrics, CX stays a department activity instead of a business priority.

Cultural Commitment
75/100

Your strongest pillar. Front-line and team leaders already believe customer focus matters; the script rewrite didn't happen by accident. The gap is connecting that commitment upward — your culture is ready to move faster, but it's waiting for executive clarity on what to prioritize.

Customer Collaboration
67/100

You're collecting feedback (NPS, script insights), but the closed loop is broken. You know renewal pain exists; you fixed the script. You haven't systematized how feedback enters the strategy, who acts on it, and what changes. That's the barrier between 67 and 80.

Experiential Innovation
50/100

No journey map and no systematic friction-finding is a hard floor in insurance. You're iterating tactically (script), not strategically. You cannot prioritize the 3 friction points you want to fix in 12 months without mapping and measuring. This is your highest-leverage gap.

07

Micromoment Mapper

Map a moment →
Zoom on: receiving a claim denial letter

"Member receives a physical denial letter days after a procedure, wades through legal language to find out they owe money, then searches for what to do next while wondering if they did something wrong."

Member opens letter assuming it's routine paperwork. Three paragraphs in they realize it's bad news. By the end they're anxious about money and confused about next steps, with no clear path forward except a phone number they know will take half an hour.

First 4 of 10 moments
t+0sneutral

Member pulls letter from mailbox, sees Northwind logo and official envelope

"Is this the explanation of benefits? Or something else?"

t+15sconfused

Member opens letter, reads first paragraph of dense legal language about plan provisions and statutory requirements

"Why does this sound like a legal notice? Did I do something wrong?"

t+45sanxious

Member skims three more paragraphs, finally finds sentence stating procedure is not covered

"Wait, what? I thought this was covered. How much do I owe?"

t+90sanxious

Member scans rest of letter looking for dollar amount owed, finds it buried in second page

"Okay, $2,400. Can I afford this? Do I have to pay it all now?"

Ruined-day moment · t+90s

This is when the member realizes they owe $2,400 they didn't budget for. The shock happens here, not when they read 'denied.' Financial surprise ruins the day faster than medical jargon.

08

Voice of Customer

Synthesize your feedback →

"Northwind's operational mechanics work when humans touch them (Jen), but automated touchpoints fail at the moments customers need clarity most."

Top 2 themes

Network changes invisible until bill arrives

medium

Root cause: Provider network updates are not triggering member notifications. Customer discovered change at point-of-service, which is too late to choose an in-network alternative.

Fix (Provider Relations + Member Communications):Trigger email/app push when a member's active provider drops network, with list of 3 nearby in-network alternatives within 48 hours of change.

Portal fails at critical lookup moments

low

Root cause: Portal error handling defaults to technical messages instead of guiding customers to a working path (call number, PDF download, retry time).

Fix (Digital Experience + IT):Replace 'Unable to load' with: 'We're having trouble loading this right now. Call 555-0100 (avg wait: 4 min) or try again in 15 minutes.'

Closed-loop response template

Thank you for the Q1 feedback. A few of you flagged the same pattern we're seeing: our systems don't warn you when something changes until it's too late. One of you paid $180 out-of-pocket because we didn't tell you your dentist left our network. That's on us. We're building notifications that trigger when your provider drops out, with in-network alternatives nearby. We're also rewriting denial letters so you understand the reason and next step in the first sentence, not buried in paragraph six. And we're making Jen's appeal walkthrough process the standard — she got it right. We'll update you in June on what shipped.

09

Executive Briefing

Prep your CEO meeting →
The one sentence the CFO will repeat
"Spend $480K to protect $2.4M in annual revenue by fixing the three things causing 14% renewal churn."

Renewal churn jumped from 11% to 14% over six months. Three specific failures drive it: members don't know their plan changed until they get a surprise bill, denial letters are incomprehensible, and we drop providers without warning. A focused 18-month program (2 FTE, $180K tooling, $480K total) targets those three breakpoints. Conservative estimate: reduce churn 3 points, protect $2.4M ARR. ROI at 5:1.

The ask

Approve $480K annual budget for 18 months: $300K for 2 FTE (senior CX operations analyst, technical writer with healthcare background) and $180K for notification tooling and letter-generation infrastructure.

If CFO pushes back (first objection)

"How do I know this isn't just another soft CX program that sounds good but doesn't move the number?"

Fair. Three things make this different: we can measure churn by cohort every 30 days, the three causes came from exit interviews with actual lost accounts, and we're running a 90-day pilot with 5,000 members before full rollout. If churn doesn't move in the pilot group, we stop.

10

CX ROI Calculator

Run the numbers →
Northwind · 85,000 members · 14% churn · Developing CX maturity

"A realistic two-year CX program targeting 3 points of churn reduction could protect $2.3M in annual revenue for Northwind—roughly 4% of your current base. With 85,000 policyholders and a 14% churn rate, retention improvements compound quickly. At your current maturity level, the impact grows as you move from reactive service fixes to proactive engagement across the policy lifecycle."

Recommended next steps
  • Map your current policyholder journey using the CXI Navigator framework to identify the three highest-friction moments between purchase and renewal.
  • Run a 90-day pilot targeting one segment (e.g., first-year policyholders or claims filers) with weekly feedback collection and response protocols—measure churn change in that cohort.
  • Read chapters 4-6 of Experience Is Everything to align your leadership team on the difference between reactive service recovery and proactive experience design.
Caveats
  • ·These figures assume you can operationalize feedback loops and act on policyholder signals within 30 days—many insurance carriers struggle with cross-functional coordination between claims, underwriting, and service.
  • ·NPS of 22 suggests silent detractors who haven't churned yet but won't refer—retention gains show up faster than referral lift in your first 18 months.
  • ·Support cost savings require deliberate channel strategy and self-service investment, not just headcount reduction—underfunding this creates new friction points.
11

Keynote Research Brief

Brief your next keynote →
Forrester CX Summit · Delta Dental · 45 min · VP+ audience

"Stop measuring how fast you fix problems. Start measuring how many problems members never face."

Opening hook

"Most of you measure member satisfaction by how fast your team answers a call. But your members aren't calling because they want to call you—they're calling because something broke. What if you stopped counting speed and started counting the calls that never happened?"

Lands immediately on the core pain: insurance is built on reactive efficiency metrics. Flips the script from 'better service' to 'fewer problems.' Concrete and non-fluffy. Sets up the proactive-vs-reactive contrast that's the entire talk.

Top 2 CX angles

Proactive CX vs. Reactive Customer Service

Show the gap in dental insurance: most communication is inbound (member calls after problem). Walk through a real scenario: claim denial notification sent via post (reactive), versus proactive outreach at point of eligibility change, with alternative coverage options (proactive). Frame it as 'fewer ruined days for customers'—a denied claim is a ruined dental day. The VP's job is reducing those days before they happen.

Micromoments & Micromapping (use sparingly, preview the idea)

Dental insurance has critical micromoments: when member receives a claim notice, when they're shopping for a new plan, when they're deciding whether to use their benefits, when they hit their annual max. Currently, Delta handles those moments reactively (reactive communication). Show one micromapped moment end-to-end and ask: 'What could we do 24 hours before this moment to make it less painful?' This introduces the idea that CX is not journey mapping at scale—it's identifying 3-5 micro-decisions where proactive intervention changes the outcome.

12

LinkedIn Post Drafter

Draft a post →
story-first
Hook: "A leader showed me their CX dashboard last week."
A leader showed me their CX dashboard last week. 47 metrics. Color-coded tiles. Real-time updates. I asked: "What decision did you make because of this today?" Silence. Most dashboards track everything and answer nothing. They show you what happened, not what to do next. Here's what actually works: Pick 3-5 metrics that connect to specific decisions. Not insights. Decisions. Example: If First Contact Resolution drops below 70%, you trigger a process review. If effort scores spike in one journey, you allocate resources there. The dashboard isn't the strategy. It's the signal. CX is a discipline, not a department. That means knowing which signals matter and what you'll do when they fire. Proactive beats pretty every time. What's one metric on your dashboard right now that actually changes how you work?
framework-first
Hook: "Your dashboard should answer one question: "What do I do Monday?""
Your dashboard should answer one question: "What do I do Monday?" Most don't. They show satisfaction scores, NPS trends, survey volumes. All backward-looking. None connected to action. Here's the reframe: Metrics exist to trigger decisions, not prove you measured something. If a number moves and nothing in your organization changes, delete that metric. What to track instead: • Leading indicators (effort scores in specific journeys) • Threshold triggers (when X drops below Y, we do Z) • Operational signals (time to resolve, repeat contacts) CX is a discipline, not a department. Discipline means knowing what matters and acting on it. I've seen teams cut dashboards from 40 metrics to 5 and make faster progress in 90 days than they did in two years. Fewer ruined days for customers starts with fewer wasted metrics for leaders. How many metrics on your dashboard right now actually change what you do?
Reader asked

What are the four reflection questions in the Connect Template?

Book GPT replied
The four reflection questions in the Connect Template are: 1. **What's our brand promise?** — What promise have we made to our customers? 2. **What's in it for the customer?** — What can customers achieve, feel, or do with our products and services? 3. **What experience can we consistently deliver?** — What can we realistically deliver every time, no exceptions? 4. **What do we want our customers to feel?** — What emotions do we want to evoke through our products, services, and people? These four questions map directly to the four blanks in the template. They force you to move beyond corporate speak and product features to focus on customer outcomes and emotions. As Jeannie puts it: 'These four questions capture the four key elements that must be included in your CX Mission Statement.'
Citations
Chapter 1: "What's our brand promise? What's in it for the customer? What can we consistently deliver? What do we want our customers to feel?"
Chapter 1: "These four questions capture the four key elements that must be included in your CX Mission Statement."
14

Ask Jeannie

Ask your own →
Reader asked

I just became the first CX leader at a 200-person healthcare company. First 90 days?

Ask Jeannie replied
Listen first. Don't propose anything in month one. Days 1-30: Sit in on support calls. Read a month of NPS open-text. Ride along with a sales AE and a CSM. Talk to 10 customers — current, churned, and won-but-unhappy. You need context before you can fix anything. Days 30-60: Find and fix one thing. Pick the most painful ruined-day moment you identified in month one. Ship a visible fix. Cite the customers who flagged it. Tell the whole company. This earns you the political capital to do the strategic work. Days 60-90: Draft the CX Mission Statement. Socialize the Success Blueprint draft. Identify the three customer behaviors you want to change and propose the measurement cadence. Leave the all-hands with a one-slide summary of what CX will look like in 12 months. Do not try to launch a transformation program in the first 90 days. You will not have the context or the trust.
Citations · grounded in Jeannie's KB
podcastJeannie's public teaching · common question
podcastJeannie's public teaching · common question
podcastJeannie's public teaching · common question
15

Change Agent Weekly

Get this week's note →

Hey there,

This week's question

What would still happen if you weren't there to push it?

That member-services script rewrite? That's proof the organization can solve for experience when the problem is clear and local. The board asking for ROI means they know CX exists — even if they don't yet know what it does. Your job this week isn't to react faster. It's to make one thing repeatable without you.

One tiny move this week

Pick the denial letter rewrite. Write a one-page brief: what's broken, what good looks like, why it matters to retention. Send it to product with a 15-minute meeting request. No deck. Just the brief and a question: 'What would you need to move this forward?'

Framework · Proactive vs Reactive CX

Reactive CX is you answering emails all Tuesday. Proactive CX is product rewriting the letter so fewer people need to email. That script rewrite was proactive — someone saw the pattern and fixed the root cause. The denial letter is the same opportunity. You're not asking product to care about CX. You're asking them to solve a problem they already own.

That 18% FCR lift is real impact. It happened because someone on the ground had clarity and permission. Your job is to create more of that — not to be in every room.

Every sample generated live.

No hand-authored fakes. Each tool produces this quality in 10–60 seconds against your own inputs. All 15 tools cost ~$0.03–0.08 per run.