THE CUSTOMER NARRATIVE SYSTEM:

    How 18 interviews become a GTM system your team runs without you

    When your customer is asked to explain a decision, their mind edits.

    The long story becomes the short one.

    that whole mess took a year. don't get into it
    "Yeah, once we saw the need it was straightforward."

    The parts they deem irrelevant are cut.

    their rep took 3 days to reply. but whatever
    "Yeah I'd say it was pretty smooth."

    Messiness is skipped for professionalism.

    Mark chewed me out in that first meeting
    "Internal debate? Yeah a bit, nothing major."

    And vulnerability rarely makes it through.

    I'd never bought something like this before
    "We were confident in our process."

    In the end, most of what drove their decision never arrives at all.

    Which means your teams aren't operating from what your customers experienced.

    They're operating from what your customers chose to say about it, when asked.

    The research never found the one thing your customers use to buy

    Cost, risk, and internal politics all play a role. But here's what your customer's buying decision is based on:

    A story.

    • "If I purchase this, what am I signing my team up for?"
    • "Is this going to move the number I need to move?"
    • "Succeed or fail, how smart or stupid am I gonna look?"

    That story they're constructing as they move through your funnel is what closes (or loses) the deal. What matters is whether you and your teams work with it, or against it.

    The problem is, traditional research strips away the connective story tissue, leaving your teams with isolated data that requires heavy interpretation to use, if it can be used at all.

    The process in four steps

    1
    Weeks 1–5

    Interviews

    45-minute story interviews with 18 of your customers

    Together with you and your team, we'll identify the right customers to interview based on your goals. Once introductions are made, I handle the rest.

    The important thing to know is that the methodology is built on one idea:

    When people tell stories, they filter less.

    The interview is carefully structured into a narrative format, so candid answers emerge naturally.

    By encouraging customers to dredge up the entire context rather than serve a curated answer, you discover the parts that were always missing.

    So your teams get a more honest picture of what your customers experienced.

    2
    Week 6

    Extraction

    Deep (and human) transcript analysis across 17 evidence categories

    Every passage where a customer reveals something real gets pulled and tagged. 17 categories, including:

    • Threshold crossings (the moment certainty tipped)
    • Competitive evaluations (who almost won, and why they lost)
    • Advocacy stories (the version your customers retell to their peers)

    Then the broader context around each deal:

    • The antagonists that almost killed the deal internally
    • The supporting characters that made it happen
    • The politics the whole thing sat in

    Every finding is held against a specific test:

    Does it reveal...

    • Psychology
    • Action
    • Emotion

    ...that relates to your business goals, or is it biographical filler that just sounds like evidence?

    Anything that doesn't pass the test is cut.

    3
    Week 7

    Synthesis

    11 frameworks. One for each question your teams are already trying to answer

    The extracted evidence is fed into 11 framework systems. Each one is built to answer a different GTM question.

    • One framework shows you where your marketing diverges from what customers experienced.
    • Another reveals the low-hanging fruit to improve conversions.
    • Another maps the customer's internal journey stage by stage: what they felt, thought, and did at each point from before the problem all the way to advocacy.

    Pull any finding and you can trace it back through the framework, through the pattern, to the exact words a customer used.

    See for yourself

    What the customer said

    "We want better analytics"

    What the team built

    Product plans and builds a brand new system for deeper analytics.

    What was really happening

    Their CEO keeps asking "are we getting value from this?" in exec meetings and they have no easy proof to show. This request is driven by anxiety about looking like they wasted budget, not a lack of features.

    What the team needed to build

    Product builds a "CEO Dashboard" that spotlights the biggest, most persuasive wins from the existing data.

    That's the difference between knowing what customers say they care about and knowing what's driving their decisions.

    4
    Week 8

    Delivery

    The most important part of the process for you and your teams. Here's what happens:

    1. I walk you and your key stakeholders through the complete Customer Narrative System
    2. I explain what I found, why it matters, and what the data suggests you do first
    3. You get the interactive software with full access to all frameworks
    4. I run each of your teams through an onboarding call
    5. Then you own it

    Your team references it for their GTM decisions. When debates happen about what customers want, they go to the source.

    If there are adoption issues, I'm available for 2 more training calls as part of every engagement.

    Once you're sure the system works, you can schedule a refresh of the insights anytime you want. Every 6 months, every year - whatever cadence makes sense for your business.

    Meet the person who runs every engagement and see what it costs