Replicable Success Model

You're right to hesitate—this is exactly the "situational vs. replicable" split. Start by running a post-mortem with the coordinator: list every revenue-generating action from last year, then tag each as (a) tied to her specific relationships, (b) driven by your materials, or (c) both. Be brutal. If a deal only happened because she knew the buyer's cousin, that's situational—do not package it. What survives the filter is your training curriculum, the onboarding sequence, and the pricing logic that worked across multiple clients.

Next, test for stickiness before you scale. Run the materials with a new hire in one pilot city, with zero coordinator involvement. Measure time-to-first-sale and error rates. That tells you what's actually transferable. For the two new cities, build the kit around the process, not the personality: a decision tree for community outreach, a checklist for partner vetting, and a feedback loop for local adaptation. Leave space for judgment—each city will need its own relationship-building, but your job is to make that repeatable, not identical. Package principles, not anecdotes.

You’re facing the classic trap: a win without a mechanism. The copywriter’s “timing felt right” is situational intuition, not a replicable principle. Your job is to separate the what from the when.

Run a structured post-mortem with four lenses:

1. Audience state — Was the list segmented by intent signals (e.g., recent site visits, open rates)? Pull the data. If yes, that’s a repeatable trigger.
2. Offer architecture — Did the email lead with a specific pain point or a social proof? Compare subject lines and CTAs against your baseline campaigns.
3. Sequence position — Did it go out after a webinar, a sales touch, or a pricing change? Map the timing to a preceding event, not a calendar date.
4. Copy mechanics — Count sentence length, question frequency, and personalization tokens. If you can’t measure it, you can’t replicate it.

Then write the playbook as conditional rules: “If prospect has visited pricing page twice in 7 days, send email variant B with subject line pattern X.” That converts her feel into a decision tree. Test the rule on the next launch, and treat the first iteration as a hypothesis, not gospel. That’s how you turn luck into a system.

Your instinct to worry is correct—but not for the reason you think. The risk isn't her relationships; it's that you'll copy the surface (skip demo, run audit) without extracting the principle. Her win worked because she shifted from "showing features" to "diagnosing workflow friction." That's replicable. The live audit was just one vehicle.

Do this: debrief her with a structured extraction. Ask, "What questions did you ask that made the client reveal pain they hadn't told you before? What did you look for in the audit that told you this deal was winnable? What did you not do that your standard process would have?" Capture those as judgment criteria, not as a script.

Then run a pilot with two reps on smaller deals—not the enterprise ones. Have them use the same diagnostic questions but their own delivery. Compare win rates and time-to-close against a control group. If it holds, codify it into a one-page "Discovery Diagnostic" checklist, train on it, and make it the default for deals above a certain size. That's replication: abstract the principle, re-implement in context, verify before scaling. Her relationships got her in the door; the process closed the deal.