The Disappearing Act
The deal closes on Thursday. Contracts signed. Your customer is excited. Your AE is celebrating. You send the handoff email to the onboarding team with implementation details and a note: "Great customer. Let's make sure they have a good experience."
By Tuesday, the customer has a question about how the product handles a specific edge case.
They email support.
Support tells them it's a "sales engineering question."
The customer re-emails sales, asking for you.
You're already on to the next deal. You forward the email to support with a note: "Can you handle this?"
Support responds: "This is actually a product design question. Sales engineering should answer it."
The customer's email sits in limbo for 36 hours.
By Wednesday morning, they're no longer excited.
They're annoyed.
Temptation
The trap is handoff responsibility.
During the sales process, it's clear: you're the customer's technical advocate. You answer questions. You explain how the product works. You build confidence.
The deal closes. Your job is done.
Now there's a support team. An onboarding team. A customer success team.
Surely one of them is responsible for answering this question?
The temptation is to assume that the structure is the answer.
That handoff automatically creates clarity.
It doesn't.
The Trap
Here's what the customer experiences:
During sales: "I have a technical question. I can reach the SE immediately. They know my business. They explain things I understand."
After the deal: "I have a technical question. I email support. They don't know my business. They don't know what we discussed. They give me a generic answer. Or they bounce me somewhere else."
Trust doesn't evaporate because the product is bad.
It evaporates because the customer went from feeling like they had an advocate to feeling like they got shuttled into a queue.
This is where technical trust actually breaks.
Not during the demo.
Not during the call.
In the moment after the deal when the customer realizes they're no longer a prospect.
They're a ticket.
The Asymmetry
You built trust by being present and responsive. You erode it by becoming invisible and unresponsive.
The Bold Fix
Technical trust doesn't end when the contract is signed.
It accelerates or collapses based on what happens in the first week.
This means the handoff isn't a completion event.
It's a transition event.
And it requires explicit communication:
- Who is the customer's first contact for technical questions?
- How long should they expect to wait for an answer?
- What happens if the question falls between two teams?
- When should they loop in the SE (you) versus relying on support?
You need to answer these before the first post-sales question arrives.
Not in documentation.
In conversation.
During onboarding.
Explicitly.
The Anatomy
There are three moments where trust collapses in the support handoff:
1. The Unclear Boundary Customer has a question. Support doesn't know if it's a support question or a sales engineering question. Instead of asking the customer or escalating immediately, they bounce it back. Customer waits. Trust erodes.
Fix: Before handoff, clarify with your team: "Here are the types of questions I want to know about immediately. Here's what support should handle. Let's talk through what lives in the gray area."
2. The Missing Context Support receives a ticket. Customer is asking about something you discussed extensively during sales. But support doesn't have that context. So they answer generically or incorrectly. Customer thinks, "Didn't support even read the notes?"
Fix: Document the technical context during sales. Not just deal info. Technical decisions, architecture choices, and specific use cases this customer cares about. Make it available to support immediately.
3. The Disappeared Expert Customer needs clarification from the person who sold them the solution. But that person (you) is already on to the next deal. You're not in the Slack channel. You're not part of the onboarding calls. When customer asks for you, they get routed through three different teams before anyone finds you.
Fix: Stay connected to the first 30 days. Not as the primary contact, but as an available escalation. Make sure support knows when to pull you in. Show up when they do.
The Counterintuitive Inversion
The customers most likely to renew are often the ones who had problems during onboarding — and had them solved quickly by someone who understood their business.
Not the customers who never had problems.
Because trust isn't built by smooth sailing.
It's built by turbulence handled well.
The disappearing act destroys that opportunity.
Three Bold Contexts
Context 1: The Vanished SE Deal closes. SE disappears. Customer has a technical question. Support bounces it. Customer waits 48 hours. Gets a generic answer. Feels abandoned. Starts looking for alternatives.
Context 2: The Lingering SE Deal closes. SE stays connected for 30 days. Customer has technical questions. SE or support answers immediately. SE is looped in on actual problems. Customer thinks, "They actually care about our success."
Context 3: The Unclear SE Deal closes. SE "stays connected" but customer doesn't know how to reach them or when to involve them. Customer tries to escalate. Process is murky. Confusion replaces confidence.
The goal is Context 2. Visible, responsive, boundaried presence.
Pattern to Remember
The Disappearing Act: Trust built during sales collapses during the support handoff not because the product fails, but because the customer goes from having an advocate to being a ticket. The handoff creates an invisible boundary where nobody is clearly responsible. Questions get bounced. Customers feel abandoned. Technical trust erodes in week one.
The fix: The handoff isn't a completion event. It's a transition event. Stay visibly connected to the first 30 days. Make your role explicit. Make sure support knows when to escalate to you. Solve early problems together. This is where trust either accelerates or collapses.
Technical Trust Demo Sprint
The product is technically strong.
The conversation keeps going sideways.
In one sprint: a buyer-specific demo and evaluation package.
Discovery interview · Two edited videos · Architecture visual · Evaluation guide
|
| |
|
Hit reply and tell me: Have you ever felt like you disappeared after closing a deal? What did that moment feel like from the customer's perspective?
(Anonymized, always.)
