The bridge nobody built: Why the next sales hire was already on the support team

Reps on that customer support team were closing something that looked exactly like sales, inside tickets that were officially about something else, and nobody had told them to. I found this sitting with the VP of Customer Experience, going through activity data for a review that had nothing to do with sales. A subscription question that ended in an upsell. A complaint that ended in a renewal instead of a cancellation. Nobody had trained that behavior into the team. It had built itself, because the reps were good enough at the actual job to notice the opening and take it.

That is not a story about a few exceptional reps. It is a story about how most growing companies draw their org chart: as a set of sealed boxes, filled one at a time, each one hired against a job description written as if the skills inside it stop at the edge of the box. Support handles tickets. Sales handles pipeline. The two departments sit on different floors and get measured on completely different numbers, even when the same person is quietly doing both jobs at once.

What the incentives were actually paying for

The first problem was not talent. It was incentive design. Support was compensated on ticket volume and resolution time, metrics that have nothing to do with revenue. The reps generating that upsell had no formal reason to keep doing it beyond the satisfaction of doing it well, and no way to signal to the business that it was happening at all. So we built an incentive model that paid support reps for the sales they were already generating inside their existing job. The volume of that behavior changed almost immediately, because people do more of what gets measured and paid, even when the skill was sitting there unrewarded the whole time.

Mapping the bridge

The incentive model fixed the immediate leak. It did not answer the bigger question, which was what to do with a rep who was good enough at this to actually become a salesperson, not just get paid a little more for acting like one inside a ticket. That meant sitting down with the VP of Sales and doing something most companies never bother to do: mapping what each job actually required, not the job titles, and finding where they overlapped. Objection handling. Reading what a customer needs instead of what they are asking for. Knowing when to push and when to let a decision breathe. None of that showed up in either job description. All of it showed up in the daily work, in people nobody was tracking for it.

The interview versus the ticket log

Growing a sales team is, by default, an external hiring problem. Post the role, screen resumes, run the interviews, hope the person who interviews well is also the person who can sell under real pressure. That process is expensive, and it is also a guess, because nothing in an hour of interviews proves what six months of transcripts already had. The reps quietly selling inside their tickets had already been evaluated, for months, under real conditions, by real customers who had no idea they were part of an evaluation. We simply had not built anything that noticed.

What the pilot solved before I left

I left that organization before the pilot had time to compound into a number worth quoting, and I am not going to manufacture one just to make the story tidier. The number was never the actual point. What the pilot solved was structural: new hires in support finally had a real answer to what happens after this job, instead of the usual answer, which is nothing, a lateral move, or leaving for a company that offered one. The sales team got a way to grow that did not depend entirely on the recruiting market, which is the only lever most companies pull when a department needs to get bigger. A business that cannot answer what happens after this job, for the role it is about to post, has a gap worth examining, whether or not a pilot somewhere else ever produced a metric to prove it.

That pilot was not the first time I built something like this, and it has not been the last. People carry aspirations whether or not a job description accounts for them, and I have come to think that noticing those aspirations and building a real path toward them is not an HR initiative. It is a basic part of managing people well. Most managers wait for someone to ask for a promotion and then decide whether the timing is convenient. Fewer go looking for the aspiration before the person has found the words to ask for it.

The org chart most companies draw is a floor plan. What they actually need is a map of where their people can already go, drawn from what those people are doing right now, whether or not the job title has caught up to it yet.