Chris Arsenault

Category: The Musings

Long-form writing on technology, leadership, AI strategy, and execution inside complex organizations.

  • The Partnership Track Lesson

    Looking back: April 2026

    I spent time earlier in my career in consulting, and one of the things I watched most closely was the partnership track. The lesson of who made partner and who didn’t has stayed with me ever since — because what separated the two groups wasn’t what the firm told anyone they were measuring.

    The Formal vs. Actual Criteria

    Officially, partnership decisions were about revenue generation, client outcomes, thought leadership, and team development. Measurable things. Discussable things.

    Watching it happen in practice, the actual separator was something else: the breadth and depth of client relationships that the candidate had built across the firm’s senior client base. Revenue came and went. Client outcomes were often shared across teams in ways that made individual attribution fuzzy. Thought leadership was nice but rarely decisive.

    What mattered, really, was whether the senior clients at the firm picked up the phone for this person — and whether they recommended them to their peers.

    The candidates who made partner were the ones who had built real, bilateral relationships with senior clients over years. They didn’t just deliver projects well. They had invested in those clients as people — referred business to them, introduced them to people worth knowing, been available in ways that weren’t tied to current projects, and shown up for clients in moments when the firm didn’t specifically require it.

    The candidates who didn’t make partner were often equally strong technically. They delivered excellent projects. Their clients were satisfied. But they hadn’t built the durable relationship infrastructure — and so when the partnership decision was being made, the senior clients’ voices were either absent or measured.

    Why This Generalizes

    I took two lessons from watching this:

    First, the things that get formally measured are usually proxies for the things that actually matter. Revenue is a proxy for client value delivered. Project outcomes are a proxy for trust earned. Thought leadership is a proxy for professional authority. Partnership decisions eventually go to the people who have earned the underlying thing — not the ones who’ve optimized the proxy.

    This shaped how I think about metrics generally. If you optimize the proxy without building the underlying thing, the proxy eventually breaks down. If you build the underlying thing, the proxies take care of themselves.

    Second, career capital compounds through relationships — not through credentials. The consultants who made partner often had less impressive CVs than some who didn’t. What they had was a network of senior clients who would recommend them, hire them, and advocate for them. That network was the real asset. The credentials were the visible surface.

    I’ve watched this play out in every industry since. The operators who build durable careers do it through relationships that compound. The operators who build credential-heavy careers often hit ceilings when the credentials alone aren’t enough.

    The Pattern in Non-Consulting Contexts

    Looking back, the consulting partnership track was an unusually legible laboratory for this pattern because the stakes were so visible — the decision was binary, the timing was known, and the outcomes were watched. But the same dynamic operates everywhere in professional services, enterprise sales, and executive progression generally.

    • In enterprise sales, the reps who get promoted to director and VP are almost always the ones with the deepest client relationships — not necessarily the ones with the biggest quota attainment in any single year.
    • In founder paths, the CEOs who build durable companies are almost always the ones who’ve built wide networks of peer relationships they can draw on — not necessarily the ones with the best product on day one.
    • In board service, the directors who get invited to the most boards are the ones who’ve treated prior boards well — being responsive, adding value outside the meetings, supporting other directors in difficult moments.

    The pattern is always the same: durable career capital is relational. The credentials, titles, and deal records are the visible output. The relationships are the underlying engine.

    If you’re earlier in your career and you’re optimizing for credentials — thinking the next job, the next title, the next deal is what matters — look at the people 15 years ahead of you who have the kind of career you’d want. Almost all of them built their position on relationships that span decades.

    That’s the asset. Build it deliberately. It pays for a long time.

  • The HL7 Problem — A Pattern That Repeats

    Looking back: April 2026

    Early in my career selling into medical technology, I lost a deal I thought I’d won. Not a deal slipped — a deal lost, definitively. The lesson has shaped how I think about enterprise selling ever since.

    The deal was with a regional hospital system. The clinical champion was enthusiastic. The department head had quietly approved. The CMO had met with me twice and was leaning in. Everything looked right. Legal had the redlines. I was forecasting it to close that quarter.

    Then IT got involved.

    What Happened

    The hospital ran an electronic medical records system I’d assumed would interoperate cleanly with our device. It didn’t. Specifically, the HL7 messaging format my clinical data needed to export into was implemented slightly differently in their EMR than in the two reference hospitals I’d cited. The integration wasn’t impossible — it was non-trivial, required their IT team’s involvement, and would add two to three months to the implementation timeline.

    None of this had come up in discovery. Not because I hadn’t asked — because I’d asked the wrong people. I’d asked the clinical champion about integration and she’d answered based on her general understanding, which was “our IT team handles that kind of thing.” That answer was technically true and functionally useless.

    The deal didn’t die. It slipped two quarters while the integration questions got worked through. But the damage was done: my CMO champion got frustrated with the timeline, my clinical champion started getting pressure from her department to explore alternatives, and by the time we got to a workable integration plan, a competitor had re-entered the conversation with a solution that had already been proven in that EMR environment.

    We got the deal back, eventually. But it closed six months late at a 20% discount I wouldn’t have had to give if I’d identified the HL7 issue in discovery.

    What I Learned

    Three things, which I now teach anyone I mentor in enterprise selling:

    1. Every enterprise deal has a silent second stakeholder.
    It’s never the champion. It’s not the economic buyer. It’s the person whose job is to say “hold on” at some technical, legal, or operational layer. In medtech, it was IT. In telecom, it’s facilities or network ops. In construction, it’s the bonding company. In consulting, it’s procurement. The pattern is universal.

    2. The silent stakeholder must be surfaced in discovery, not at close.
    The cost of finding them early is 15 minutes of conversation with your champion, asking “when this goes to [X], what’s the first question they’ll have?” The cost of finding them late is a slipped quarter, a discount, and sometimes a lost deal.

    3. Your champion’s answers about the silent stakeholder are almost always wrong.
    Not because your champion is wrong about their own job. Because they’re answering based on how they’d want the process to go, not how it actually goes. “Our IT team will handle that” is directional truth. It is not actionable intelligence. You have to get to the IT team yourself — not through the champion’s interpretation of what IT will need.

    Why This Pattern Matters So Much

    Looking back, the HL7 problem was probably the single most expensive lesson of my medtech career. But the principle it taught — silent stakeholders exist in every enterprise deal, they must be surfaced early, and your champion can’t fully characterize them — is something I now apply in every deal review, in every deal I’m in directly, and in every coaching conversation I have with someone earlier in their career.

    I’ve watched sellers in construction learn this lesson with bonding companies. In consulting, with procurement. In telecom, with network operations. The industry changes; the pattern doesn’t.

    The irony is that the fix is cheap. A seller who asks two or three specific questions in discovery about the silent stakeholders will catch most of these issues before they compound. But most sellers don’t ask, because the questions feel awkward, and because the champion is giving them warm signals that make the deal feel safe.

    Warm signals from the champion are not the same as visibility into the full buying process. I learned that once. I don’t forget it.

    If you’re selling enterprise anything and you haven’t identified your silent stakeholders in discovery, you don’t have a deal yet. You have a relationship that might become a deal, pending surprise.

    Don’t be surprised. Ask early. Ask specifically. Get past the champion’s version of the process to the actual one.

    That’s the HL7 lesson. It cost me a quarter. It’s saved me many more.

  • Why Medtech Champions Move Departments and How That Shapes Everything

    Looking back: April 2026

    One of the most durable lessons I took from selling into medical technology was this: your clinical champion will change roles before your deal closes. Not sometimes. Usually.

    This is true in every industry — champions get promoted, move sites, leave. But medtech has a particularly high rate of internal rotation. Clinicians shift sub-specialties. Hospital systems reorganize. Academic physicians move between institutions. The cadence is faster than in most B2B contexts, which made medtech a reliable teacher about multi-threading.

    The Pattern

    A typical medtech enterprise cycle runs 6 to 18 months. A clinical champion’s seat in a specific role at a specific institution is often 18 to 36 months. Do the math on overlap and you realize: in a non-trivial percentage of deals, the person who championed you at month one is in a different role by the time your deal is operational.

    I saw this go sideways on specific deals. A surgical champion who was thrilled in the discovery phase got recruited to a different hospital system at month five. His replacement had a different preferred vendor. The deal didn’t die — it just stopped moving, and nobody could tell me why for three months.

    Another deal — an internal medicine champion got pulled into an administrative role mid-cycle. She wasn’t moving institutions. She was just moving offices, and the new role didn’t include authority over clinical purchasing. The deal required a new champion, whom we had never met.

    What I Learned About Building Deals

    The first obvious lesson: multi-thread everything. In medtech, this meant cultivating at least three clinical relationships on a given deal, plus administrative, plus materials management. No single-threaded deal survived contact with institutional reality.

    The less obvious lesson, the one that took me longer: build relationships with people who will outlast any specific role. The senior clinicians who remained in an institution for decades were worth more than a junior champion in the current buying center. A dean, a department chair, a longtime nursing director — their presence was stable across reorganizations.

    I started building relationships at those levels even when they weren’t directly involved in my deals. Two years later, I’d find that one of them had become the sponsor I needed on a deal I hadn’t even started yet.

    Why This Applies Everywhere

    Medtech taught me the pattern, but I’ve since watched it play out in every industry:

    • In telecom, CIOs rotate between business units every 3 to 4 years. The relationships with their VPs — who often stay longer — outlast them.
    • In construction, project managers change but the owner’s representative often stays for years. Build that relationship and you have durable access.
    • In consulting, the engagement manager on any specific project will rotate. The senior partner sponsoring the client relationship rarely does.

    The common pattern: in any enterprise selling motion, there are transient relationships and durable ones. The transient ones drive individual deals. The durable ones drive careers.

    The operators I’ve watched build the strongest enterprise selling records were the ones who invested in durable relationships even when they didn’t need them for the current deal. The ones who invested only in transient relationships had bursty results — strong when the specific person was in place, invisible when they moved.

    The Principle I Now Apply

    In every account I work, I try to answer one question explicitly: who, at this account, will still be there in five years?

    The answer is sometimes the obvious senior executive. Often it’s someone adjacent to the buying center — a longtime operations director, an influential technical lead, a specialist who’s built a career at the institution. These people are often not the deal decision-maker in the current cycle. They are the decision-makers across decades.

    Medtech made this legible because the rotation was so frequent that the lesson arrived early. Every industry has the same pattern. It just compresses or expands the timeline on which the lesson becomes obvious.

    Looking back, the reason I still emphasize multi-threading so heavily — in content, in coaching, in deal reviews — is that medtech taught me, early, how expensive single-threading is in an industry where people move. The insight generalized. The urgency came from the compressed laboratory of clinical sales.

    If you’re selling into any industry with high role rotation — and most B2B industries qualify — the multi-threading lesson is the same lesson medtech teaches. Learn it early or pay for it later.

  • What Clinical Sales Taught Me About Trust

    Looking back: April 2026

    I’ve been thinking lately about what medical technology sales taught me earlier in my career. Almost every framework I use today for understanding trust-based selling traces back, in some form, to patterns I first saw playing out in hospitals and physician offices.

    Medtech is a compressed laboratory for trust economics. What takes years to show up in other industries shows up in quarters in medtech, because the stakes are clinical — the buyer’s decisions have patient consequences, and that raises the trust threshold for every interaction.

    Three patterns shaped how I think about selling generally.

    Clinicians Talk to Each Other More Than They Talk to Reps

    In most B2B industries, the buyer’s information flow includes the vendor heavily. Case studies, webinars, sales conversations, demos — these shape how the buyer understands their options.

    In medtech, the information flow runs primarily through other clinicians. A physician evaluating a new device talks to three or four peers before they’ll seriously consider it. Those peer conversations happen in hallways at conferences, in text threads between specialists, in informal networks that predate any sales cycle.

    What this meant practically: your reputation among clinicians was almost entirely shaped by conversations you weren’t in. The rep in the room during a sales call was far less influential than the three physicians at a different hospital who had mentioned you (or hadn’t) in passing.

    Looking back, this was my first real lesson in reputation as infrastructure. You can’t engineer it directly. You can only behave, over years, in ways that make the conversations about you land well. Everything else is downstream.

    The Reference Check Is Informal and Constant

    The formal reference conversations in medtech — scripted, polished, compliance-aware — are the least important ones. The real references happen sideways: a department head asks a friend at another institution “hey, have you used them?” The friend gives a 30-second answer. That answer decides more than any prepared reference call will.

    This shaped how I think about customer success in every industry since. The goal of customer success isn’t to produce good references. It’s to produce a customer who, when asked casually, gives a 30-second answer that advances your deal — without knowing they’re being asked for anything.

    Most sellers optimize for the formal reference. They should be optimizing for the informal one.

    Small Reputation Mistakes Compound Rapidly

    In consumer markets, a bad experience is a marginal data point — the company is big, the customer is one of many, the reputation absorbs the hit. In medtech, the physician community is small enough that one bad experience propagates quickly.

    I watched reps lose entire territory coverage over a single bad interaction with a senior clinician. Not because the clinician complained publicly — because they mentioned it, once, to a colleague, who mentioned it to another, and within six months the rep was persona non grata across five hospitals they’d never visited.

    This is the trust-decay pattern you read about in theory. In medtech I watched it operate in real time. It made me permanently cautious about small interactions that seem low-stakes in the moment. The senior clinician whose call I didn’t return was not, in any individual moment, a big deal. Cumulatively, those misses were career-altering for some reps.

    The thing medtech taught me that I carry into every industry since: trust-based selling isn’t a style preference. It’s the load-bearing infrastructure of any long-term revenue relationship. Every industry has its own compression rate on how fast the infrastructure shows up — medtech’s is faster than most.

    The operators I watched win in medtech weren’t the best pitchers. They were the most consistent depositors. They returned calls. They kept promises. They didn’t play games with reference lists. Over years, their reputations compounded, and their pipeline started showing up before they’d done anything to generate it.

    That’s the whole game, in every industry I’ve sold in since. Medtech just taught me to see it earlier.

    The people who think of trust as a “soft” variable have usually never sold into an environment where trust failure meant being shut out of an entire professional community within months. Medtech operates at that compression. So do a lot of other industries, eventually. Start treating trust as load-bearing infrastructure before your industry forces you to.

  • Case Studies That Aren’t Case Studies

    Most case studies are bad. Not badly written — badly conceived. They’re structured to showcase the vendor, not to illustrate a situation the reader recognizes and can learn from. The result is a document that the customer signed off on but that nobody will actually read carefully, because it doesn’t tell the reader anything useful.

    Real case studies — the ones that actually convert readers into pipeline — are structured fundamentally differently.

    What Most Case Studies Do Wrong

    The typical case study template:

    • Challenge: Customer had a problem
    • Solution: We solved it
    • Results: Here are some numbers

    This structure serves the vendor but not the reader. The challenge is usually described in generic terms that could apply to anyone. The solution is a product description dressed up as a story. The results are numbers that have been sanitized until they’re unfalsifiable.

    The reader can tell. They skim it, nod politely, and don’t internalize any of it. It doesn’t change how they think about their own situation because the case study didn’t make their situation specific enough to relate to.

    What Great Case Studies Do

    Great case studies are structured around the reader’s recognition, not the vendor’s positioning:

    1. They start with a situation the reader recognizes.
    Not “our customer had a challenge with operational efficiency.” Something like “the logistics team had cut headcount 20% the previous year, and the VP of Operations was being asked to absorb the same work with fewer people, while still meeting on-time delivery targets. The specific failure mode they were seeing was…”

    The reader either has that situation or knows someone who does. The specificity is what allows recognition. Generic descriptions force the reader to translate, and most readers don’t bother.

    2. They describe what the customer actually tried first.
    Most case studies jump from “problem” to “our solution.” Real narratives include the false starts. “They first tried hiring a consultant to redesign the workflow. That produced a recommendation but not an implementation. They then tried an internal tiger team. That got bogged down in competing priorities. By the time they engaged us, they had already lost six months to approaches that didn’t work.”

    This detail does two things: it makes the story credible, and it tells the reader which alternative paths have been tried. If the reader is currently considering one of those paths, the case study has saved them time — which makes them trust the vendor more.

    3. They describe the specific mechanism, not just the outcome.
    Not “we solved it using our platform.” Specifically: “what worked was X. The reason it worked is Y. The critical step that a lot of teams miss is Z.”

    This turns the case study from marketing collateral into something useful. The reader learns something they can apply whether they buy from the vendor or not. That generosity is what makes the case study convert — the reader trusts the vendor more because the vendor was honest about the mechanism, not just the outcome.

    4. They include what didn’t work or what was hard.
    Every real project has friction. Great case studies describe it. “The implementation was harder than expected in month three, because [specific reason]. We adjusted by [specific thing], and that’s what got it unstuck.”

    The acknowledgment of difficulty makes the story credible. Case studies that describe projects as smooth are read as fiction — because they are.

    How to Produce Them

    Great case studies require great interviews. Thirty-minute generic phone calls with the customer produce bland quotes. Deep interviews — 90 minutes to two hours, structured around specific questions, with the customer pre-briefed — produce the specificity that makes case studies work.

    The questions that matter:

    • Before you engaged with us, what had you already tried?
    • What specifically was the failure mode you were seeing?
    • What did the first 30 days of working with us actually look like?
    • Where was the friction? What was harder than expected?
    • If a peer asked you what made this work, what would you tell them?
    • What would you do differently if you did it again?

    Those six questions produce a case study that reads like journalism, not marketing. They’re also uncomfortable to ask, because they invite honest answers.

    The Diagnostic

    Pull your three most recent case studies. Ask:

    • Would the reader recognize themselves in the opening?
    • Does the case study describe the mechanism, or just the outcome?
    • Does it acknowledge friction?
    • Would a reader learn something even if they didn’t buy?

    If the answer is no to any of those, the case study is functioning as decoration rather than as a conversion tool.

    Case studies that actually drive pipeline are less about the vendor and more about the reader. The vendor that does this earns credibility. The vendor that doesn’t produces beautiful, useless documents.

    Most case studies are the latter. Which is why most case studies don’t convert. Which is why most marketing teams have given up on case studies as a meaningful channel — because they’re using the wrong structure.

    Change the structure and the channel starts working again.

  • Marketing Attribution Is a Lie You Tell Yourself

    Every marketing organization has an attribution model. Most of them are fiction, and the more confident the marketing team is about their attribution math, the more fictional it probably is. This is not a cynical take — it’s just the honest accounting.

    The reason matters. If you don’t know what’s actually driving pipeline, you don’t know what to keep doing, what to stop doing, and what to invest in. Attribution that pretends precision it doesn’t have leads to worse decisions than no attribution at all.

    Why Attribution Models Lie

    1. First-touch and last-touch are both wrong.
    Every attribution model is some variation on “which touchpoint caused the pipeline.” First-touch attributes to the top of the funnel — the ad, the content, the event that the customer first saw. Last-touch attributes to the bottom — the demo signup, the pricing page visit, the meeting booked. Both are accurate for about 5% of buyers and misleading for the other 95%.

    The reality is that enterprise buyers typically interact with 15 to 30 touchpoints over a 6 to 18 month journey before they buy. Attributing the pipeline to any single touch is arithmetically convenient and substantively wrong.

    2. Multi-touch attribution models are tunable fiction.
    “U-shaped,” “W-shaped,” “time-decay,” “position-based.” These models assign weights across touchpoints. The weights are chosen by the marketing team. Different weights produce different conclusions. The model isn’t discovering truth — it’s reflecting whatever assumptions got baked into the weights.

    3. The touchpoints that matter most are invisible.
    Word of mouth. Private conversations. A customer mentioning your product in a Slack community the marketing team doesn’t see. These are often the dominant drivers of pipeline, and they leave no data. The attribution model compensates by over-crediting the visible touchpoints — producing a model that systematically over-weights what’s measurable.

    What Marketing Should Actually Do

    1. Measure what’s unambiguously attributable.
    Direct response: someone clicked on an ad and signed up for a demo. That’s attributable. Count that. Optimize that. Don’t pretend the attribution extends further than it actually does.

    2. For everything else, run experiments.
    Turn off a channel for a quarter. See what happens. If pipeline drops, the channel was contributing. If it doesn’t, the channel was vanity. This is crude but more honest than model attribution.

    3. Ask the customer.
    In customer onboarding, ask: “How did you first hear about us? What made you evaluate us? Who else did you consider?” This is qualitative data, but it’s qualitative data from the only source that actually knows — the customer. It’s worth more than any attribution model.

    The Danger of Attribution Theater

    The deeper risk of bad attribution is that it’s self-reinforcing. Marketing gets credit for what the model says they did. The team doubles down on those channels. The channels that were actually driving pipeline but weren’t captured by the model get underfunded. Over time, marketing optimizes itself into a corner.

    I’ve watched this happen in multiple organizations: the attribution model shows content marketing is high-ROI, so the team doubles content investment. Pipeline drops. The model still says content is the dominant driver, because the model can’t see the shift in word-of-mouth that was actually the wind behind the growth. The team can’t figure out what’s broken because their own measurement is lying to them.

    The fix is to be less confident about what your marketing is doing. Treat attribution as directionally useful, not precisely true. Validate with experiments and customer conversations. And resist the executive pressure to present attribution as if it were accounting.

    What to Tell the Board

    When a board or executive team asks “which channel is driving the pipeline,” the honest answer is usually “we can attribute roughly X% with high confidence. For the remaining Y%, we have hypotheses we’re testing, but we don’t have certainty.”

    This sounds weak. It’s actually the only honest version. CMOs who present confident attribution numbers are either using flawed models or hiding what they don’t know. The ones who present with appropriate uncertainty build more trust over time, not less.

    Marketing attribution is useful as a working hypothesis, not as a source of truth. Treat it that way, and you’ll make better decisions. Treat it as precise, and you’ll eventually invest in the wrong things for long enough that the growth trajectory suffers.

    The measurement is valuable. The certainty is the lie.

  • Handling the ‘Send Me a Proposal’ Trap

    “Send me a proposal.” Those four words kill more deals than any competitor ever will. They sound like progress — the customer is asking for something specific, something formal, something that looks like a buying step. Often they’re the opposite: they’re the polite exit ramp.

    Knowing the difference is a craft.

    What “Send Me a Proposal” Often Means

    Before you race back to the office to draft a document, consider what the phrase often actually signals:

    “I need to look busy.”
    The customer is evaluating three vendors to satisfy an internal process. You’re one of them. A proposal from you becomes file material, not a decision input. The customer has already decided — probably for internal build, or for the vendor they worked with before.

    “I want to end this meeting politely.”
    The conversation wasn’t going anywhere useful. Asking for a proposal is a soft way to give you something to do without committing to next steps.

    “I need to justify this upward.”
    The customer likes what you’re offering but can’t justify it without documentation. The proposal is real, but the request came before the conversation fully surfaced the objections you’d need to handle in the document.

    “I want to compare pricing.”
    The customer is using your proposal to pressure an incumbent vendor or to benchmark another option. You’re the stalking horse.

    All four of these are more common than “I want to evaluate your offering seriously and move to close.” Treating every proposal request as the last one is how sellers end up writing twelve proposals to get one close.

    The Qualifying Move

    Before accepting the request at face value, run a qualifying sequence:

    1. “What specifically would you want to see in the proposal?”
    If the customer says “standard stuff — pricing, timeline, scope,” you’re in a commoditized bake-off. If they say “specifically how you’d address X and how the implementation would go for Y team,” you have a real proposal request.

    2. “Who else will be reviewing this document?”
    If the customer names specific stakeholders (“my CFO, our ops lead, and procurement”), the proposal is real. If they say “just me” or “I’ll pass it around,” the proposal is probably not going to a real committee.

    3. “What’s the decision timeline after you review it?”
    A real proposal has a decision attached. “We’ll make a decision by [specific date]” is a good sign. “We’ll take some time to think about it” is a warning. “I’m not sure” often means the request was tactical rather than strategic.

    The Counter-Move

    When the qualifying sequence suggests the proposal request is a soft deflection, the right move is often not to write the proposal. Instead:

    “Happy to put something together. Before I do, it would help me make the proposal more useful if we could do a 20-minute working session with [specific stakeholder] to walk through how it would actually fit their situation. Without that, the proposal ends up generic — and I don’t think a generic proposal serves either of us. Can we schedule that for next week?”

    This move does three things: it qualifies the seriousness of the request, it engineers another stakeholder conversation, and it repositions you from “vendor sending paper” to “thoughtful partner who’s trying to help.” Customers who are serious will find the time. Customers who weren’t serious will reveal themselves.

    When to Send the Proposal Anyway

    Sometimes the proposal is the right move even when the signals are mixed:

    • Strategic account where being in the consideration set is worth the cost
    • Customer with a history of slow but real buying cycles
    • Situation where your proposal itself can reframe the conversation

    In those cases, write the proposal — but write it as a strategic document, not a commodity quote. Include discovery findings, the problem framing, a recommendation, a proposed structure, a pricing approach. Make it something the customer couldn’t get from a competitor, because it reflects specifically what was surfaced in your conversation.

    The Cost of Getting This Wrong

    Every generic proposal written for a soft-signal request is lost time. A typical enterprise proposal is 10 to 20 hours of work — legal, pricing, SE, rep time. If 70% of proposals go to deals that were never real, the cost compounds fast.

    The seller who writes 30 proposals per year and closes six of them has the same result as the seller who writes 10 proposals per year and closes six — except the first seller spent 400 hours on paper that went nowhere.

    The proposal is a tool, not an automatic response. Use it when it’s going to move a real deal forward. Qualify before writing. Sometimes the best response to “send me a proposal” is a working session that produces a real deal, instead of paper that produces silence.

    “Send me a proposal” is the phrase sellers want to hear and should investigate before trusting. Most of the time, what sounds like the last step is actually the last-but-polite exit.

  • The Art of the Follow-Up

    Most deals die in silence. Not in rejection — in silence. The customer stops responding, the rep stops reaching out, and the deal slides quietly off the forecast. This is the most common deal-death pattern in enterprise sales, and it’s also the most preventable.

    The prevention is the follow-up. But most follow-ups are wrong.

    The Typical Follow-Up

    The typical follow-up sequence looks like this:

    • Week 1: “Just following up on our conversation.”
    • Week 2: “Circling back to see if you’ve had a chance to review.”
    • Week 3: “Did you get a chance to look at the proposal?”
    • Week 4: “Bumping this to the top of your inbox.”

    None of these are follow-ups. They’re nudges. They add zero value, ask for an answer, and signal to the customer that you have nothing else to offer.

    The customer interprets the pattern accurately: “This seller wants something from me and has nothing useful to give me. Each of their emails is a request for attention. I’ll respond when I have a reason — but the pattern of asking makes me respond less, not more.”

    What a Real Follow-Up Does

    A real follow-up delivers value, then asks. Sometimes it doesn’t ask at all.

    Week 1 real follow-up:
    “One thing that came up in our conversation that I wanted to think about more — you mentioned [specific challenge]. I looked at a couple of analogous situations from our work and wanted to share what we’ve seen. [Specific observation or insight]. Happy to discuss further if useful — no rush.”

    Week 2 real follow-up:
    “Saw the announcement from [their competitor or industry development]. That probably has implications for [specific thing they discussed]. Wanted to flag it. [Brief observation].”

    Week 3 real follow-up:
    “[Useful article or resource that’s relevant to their work]. Not directly related to our conversation but thought it might be interesting given what you’re focused on.”

    Week 4 real follow-up:
    “It’s been a few weeks since we connected. I know things shift — happy to re-start the conversation whenever it makes sense. No pressure. Here’s something I’ve been thinking about that touches on what we discussed: [short insight].”

    Every touch delivers something. Every touch signals “I’m useful to stay connected with, not a distraction.” The customer responds because responding is valuable to them, not because they’re pressured.

    Three Rules

    1. Every follow-up should be able to stand on its own.
    If the customer read only this one email and nothing else, would it be worth their time? If no, don’t send it. The “hey just checking in” email fails this test universally.

    2. The cadence should be geometric, not arithmetic.
    Not “every week for eight weeks.” Try: 3 days, 7 days, 14 days, 30 days, 60 days. The intervals lengthen. The customer doesn’t feel hunted. The touches are rare enough that each one is noticed.

    3. After the fourth value-add follow-up, consider the long-game sequence.
    If the customer hasn’t responded after four substantive touches, the situation has changed — or never was what you thought. Drop the frequency. Move to quarterly check-ins that maintain presence without feeling like pursuit. Many deals I’ve seen close on the eighth or ninth touch, but rarely on the fourth or fifth.

    The Psychology

    Customers stop responding for specific reasons: competing priorities, internal politics, a champion who’s lost steam, a budget that moved, a stakeholder who blocked. None of these reasons are visible to you. All of them are navigable.

    The follow-up that breaks through the silence is rarely the pressure follow-up. It’s the follow-up that makes the customer remember that you’re the thoughtful seller they liked, and that reopens a door they’d let drift closed.

    The Diagnostic

    Pull the last ten follow-up emails you sent to deals that went cold. Ask yourself: if the customer read only this email, would they have responded? Or does the email require them to have remembered the earlier context, felt social pressure, and given you a charity reply?

    If your follow-ups require all three to convert, that’s why your follow-ups don’t convert.

    The art of the follow-up is the art of staying present without being pushy. Of continuing to add value when nobody has asked for it. Of being the person the customer thinks of when they’re ready — not the person they’re avoiding in their inbox.

    Most follow-ups are the latter. The ones that convert are the former.

    That’s the craft.

  • The First Meeting Close

    The last five minutes of a first meeting decide whether you get a second meeting. Most sellers fumble this transition — they run out of time, they get polite-ended, or they take the customer’s vague “we’ll be in touch” as a good sign. It’s usually not.

    Handled well, the last five minutes of the first meeting are the difference between a 30% second-meeting conversion and a 70% one.

    What Most Sellers Do

    The typical ending to a first meeting is some version of:

    “Well, this has been great. I’ll send you some more information and we can take it from there.”

    This is polite, non-committal, and completely non-productive. The customer has no specific reason to act on it. The ball is in your court, which means the next move is your outreach against their attention. You’ve given them the meeting and asked for nothing in return.

    What Top Sellers Do

    The best first-meeting endings have three specific components:

    1. A summary of what you heard.
    Not “I think we can help you.” Specifically: “Based on our conversation, it sounds like the three things most on your mind right now are X, Y, and Z. The one you spent the most time on was X, and the reason that matters most is [specific consequence].” This shows you were listening, confirms alignment, and gives the customer the chance to correct any misreading.

    2. A concrete next step, tied to a specific benefit.
    Not “let’s schedule a follow-up.” “There are two things I think would be useful for our next conversation. First, I’d like to bring our solutions engineer in to walk through how [specific thing] would work in your environment. Second, I’d like to introduce you to [specific customer] who solved [similar problem]. Can we get 45 minutes on the calendar for the week of [date]?”

    3. The calendar invitation on the spot.
    Not “I’ll send you an invite.” You open your calendar, they open theirs, you pick a time, it gets booked. The hand-to-calendar-to-booking transition takes 90 seconds and dramatically increases the probability the next meeting actually happens.

    The Qualifying Close

    For deals where you need to qualify further, the last-five-minutes move is slightly different:

    “Based on what we discussed, I think there’s potentially a real fit here — but I want to be respectful of both our time. Can I suggest a specific way to test that? If we agree to take this to the next stage, the next step would be [specific action]. Would it make sense to schedule that for two weeks out, or does that feel premature?”

    This does three things: it explicitly qualifies, it asks for commitment, and it lets the customer push back if they’re not ready. A customer who says “yes, two weeks works” has just self-qualified. A customer who says “let’s hold off” has given you an honest signal about where they really are.

    The Hard Part

    The hard part of the first-meeting close is that it requires the seller to ask directly for the next step. Many sellers avoid this because it feels pushy. It isn’t. Customers expect it. They often prefer it — because it relieves them of having to figure out the next step themselves.

    What feels pushy is not asking. What feels pushy is “let me send you more information” followed by four unanswered emails over three weeks. The direct ask is actually the less-pushy option. It just feels harder in the moment.

    The Practice

    Before your next first meeting, write down your closing sequence:

    • The summary (three bullets on what you heard)
    • The next step (specific, mutually valuable)
    • The calendar ask (with two or three specific date/time options)

    Say it out loud before the meeting. If it feels stilted, rework it. The seller who walks in with the closing sequence pre-written will execute better than the one who improvises, every time.

    First meetings are harder to get than second meetings, but easier to get wrong. The close — the last five minutes — is what determines whether the first meeting produces the second.

    Treat those five minutes with the same preparation you treat the opening five. Most sellers don’t. Which is why most first meetings convert poorly.

    Yours don’t have to.

  • The Conference Playbook

    Most people attend conferences wrong. They travel, take notes, collect badges, and come home with nothing concrete. The people who actually produce revenue from conferences are running a deliberate pre-during-post playbook — and they treat conferences as one of the most efficient opportunity sources in their book, not a passive networking event.

    Here’s what the playbook actually looks like.

    Pre-Conference

    The work that determines ROI is the work you do before you get on the plane.

    Build your target list, by name.
    Before the conference, you should have 10 to 20 specific people you want to meet. Not “people in procurement at mid-market companies” — Maria Chen at Company X, who’s the VP of Operations, and who just announced an expansion into your geography. The list is specific or it isn’t a list.

    Reach out before the event.
    A week or two before, send a specific note to each person on your list: “I see you’re attending [conference]. I’d love 20 minutes while we’re both there — I’m interested in what you’re doing around [specific topic]. Would Tuesday lunch or the Wednesday reception work?” The conversion rate on pre-conference outreach is multiples higher than cold outreach any other time.

    Review the agenda strategically, not topically.
    Don’t pick sessions based on “interesting topics.” Pick sessions based on who’s going to be in the room. A session by a mediocre speaker on a topic you’re not interested in, attended by eight of your target accounts, is a better use of your time than the keynote.

    Book your calendar in advance.
    The best conference time slots are breakfast, the first coffee break, lunch, the afternoon break, and the first hour of the reception. If those slots aren’t already booked with named meetings before you get on the plane, you’ll end up making small talk with whoever’s nearest you.

    During

    Skip most of the sessions.
    This is counterintuitive. Sessions are the visible structure of the conference. But sessions are available on video afterward. The people are not. Every minute in a session is a minute not spent in the hallway.

    Work the hallways, the lobby, and the coffee stations.
    These are where the actual conference happens. Target accounts drift between sessions, check emails at the coffee station, and chat informally in the lobby. Being visible in these spaces for two hours produces more encounters than sitting through four sessions.

    Have a clear opening line and a short story.
    When you meet someone, you have about thirty seconds before they decide whether to continue the conversation. Have a specific opener ready: “I’ve been thinking about [specific thing they care about]” beats “So what brings you here?”

    End every meeting with a specific next step.
    Not “we should stay in touch.” “I’ll send you the framework we discussed on Monday, and if you want to dig into it further, let’s set up 30 minutes the week of [date].” Specificity compounds through the follow-up.

    Post

    This is where most people lose the ROI entirely.

    Send a personal, specific follow-up within 48 hours.
    Not a generic “great to meet you.” Reference the specific topic you discussed, deliver the thing you promised, suggest a concrete next step. Send it from the airport, the hotel, or within 48 hours — longer than that and the memory fades.

    Calendar your ongoing follow-ups.
    Most relationships from a conference need three or four post-event touches over the subsequent three months to convert. Build those into your calendar before the post-conference inbox pile-up pulls your attention away.

    Track what worked.
    After every conference, spend 30 minutes reviewing: which meetings produced pipeline, which contacts felt most valuable, which sessions were surprisingly high-leverage, which were wastes. Conferences get better with iteration. The seller who runs the same playbook for three years straight improves conference ROI by multiples.

    Conferences are not free networking. They’re expensive investments with variable returns, and the return depends almost entirely on preparation, execution, and follow-through.

    Treat the conference as a three-week engagement — one week of prep, one week on site, one week of follow-up — and the math works. Treat it as three days of travel and passive engagement, and it doesn’t.

    Most people treat it as the latter. Which is why conferences feel like they don’t produce much. For most attendees, they don’t.

    The ones running the playbook are the ones producing the pipeline. The badges look the same. The outcomes don’t.