This case study follows how a Series A fintech matched its VP of Sales role to a candidate who had already scaled three startups through the same stage transition, by screening on career triggers instead of titles. A title-based search surfaced impressive logos who had only ever run mature sales machines. A trajectory screen surfaced the person who had personally built a repeatable motion from founder-led selling, three times over, and that is who got the offer. Below is the whole path from brief to shortlist, and how the interview confirmed the match.
The clearest way to explain trajectory fit is to walk a single hire from brief to offer. So this is a case study, but an honest one. It is a composite, built to teach the method rather than to report on one named account. It reads like a specific search because that is the point: you can see where a title-based screen goes wrong, and where a trajectory screen finds the person a keyword string would have buried.
This case study is an illustrative, anonymized composite. The Series A fintech, the VP of Sales role, and the candidate are invented to make the trajectory matching method concrete. It is not a specific Numi customer, and the outcomes are illustrative, not verified results. No real company or person is named or described.
The brief
The company is a Series A fintech. Founder-led sales had carried them further than most: the founders had closed the first several dozen customers themselves on conviction, relationships, and a genuinely good product. That motion had now hit its ceiling. The founders were the pipeline, the demo, the negotiation, and the close, and there were only so many hours in their week. The board wanted a VP of Sales to build a motion that did not depend on the founders being in every room.
The instinct, and the first draft of the spec, was predictable: "VP of Sales, B2B SaaS, 8 plus years, enterprise experience, strong logos." That spec would have worked fine if the job were to run an established sales organization. It was not. The actual job was a transition: take a company from founder-led selling to a repeatable, teachable, hireable motion. So we rewrote the brief as a problem instead of a title. The hardest thing this person had to do in year one was to build a first real pipeline, hire and ramp the first non-founder reps, and turn the founders' instinct into a process a new rep could run without them.
The triggers we derived
Once the brief is a problem, the screen writes itself. We asked a simple question: what would show up in a career history if this person had already solved this exact problem? That question turns a fuzzy spec into concrete, checkable markers. We landed on three.
- A Seed to Series A stage transition, personally driven. Not present in the building while it happened, but personally responsible for the sales motion that got the company through it.
- A first-repeatable-revenue build. Evidence that they had set up a first pipeline, hired the first reps, and written the first playbook, rather than inheriting all three.
- A from-scratch motion, not an inherited machine. The company should have been small and messy when they joined, and more organized when they left, with the candidate holding the pen on that change.
This is exactly the sourcing discipline in our guide on how to find candidates who scaled Seed to Series A, and the brief-to-shortlist path follows the matching framework we use on every role. The triggers are the bridge between what the business needs and what you can actually search a profile for.
Why the title search surfaced the wrong shortlist
To make the contrast visible, we ran two screens in parallel. The first was the conventional one: title, seniority, keywords, logos. It produced a clean, senior, impressive list. Nearly all of it was wrong for this role.
The title search rewarded people who had held the VP of Sales title at large, recognizable companies. But a VP of Sales title at a company that is already a machine tells you the person was good at running a system someone else had built. That is a real skill. It is not this job. Several of the strongest candidates on the title list had never once built a pipeline from nothing, never made the first sales hire, never had to sell before there was a category or a case study to point to. On paper they outranked everyone. In this seat, most of them would have stalled the moment they discovered there was no machine to run, only a blank page.
The title search also actively pushed the right people down. A candidate whose best work happened when a company was tiny carries small, unfamiliar logos from that period. A Boolean string sorts those below the household names, which is the exact inverse of what this brief needed.
The trajectory screen and the shortlist
The second screen ignored titles and logos and read for the three triggers. It read the dates, the company stage at the time of joining, and the sequence of moves, which is where the signal actually lives. That screen surfaced a very different shortlist, and at the top of it sat a candidate the title search had ranked near the bottom.
This person had driven the Seed-to-Series-A and first-repeatable-revenue transition not once but three times, at three different startups. Each time they had joined when the company was small and founder-dependent, built the first repeatable motion, and left it as something a team could run. The titles varied, the logos were mostly obscure, and the total years of experience were unremarkable next to the enterprise veterans on the other list. But the trajectory was an almost exact rhyme with the problem in the brief. They had solved this specific problem three times over.
How the interview confirmed what they owned
A trigger screen tells you a candidate was present for the transition. It cannot, on its own, tell you what they personally did versus what the founders or a strong peer did around them. That distinction is the whole ballgame in a trajectory hire, and it only comes out in the interview.
So the interview was built to test ownership, not to admire the story. Instead of "tell me about scaling the team," the questions were specific: which was the first process you wrote, who did you hire first and why, what broke in the second quarter, what decision did you get wrong. The answers matter because a person who truly owned the motion answers in first person and specifics, while a passenger drifts to "we" and generalities.
Because trajectory fit is judged on exactly these details, the interviews were recorded, transcribed, and structured so the hiring team could review the evidence together rather than trust three separate memories from three days earlier. When the candidate said "I built the first pipeline," the team could go back to the transcript and read what they described building, and note the two moments where the candidate volunteered that a co-founder, not they, had led. That candor read as a strength, and it was checkable because it was captured. This is what an interview intelligence tool is for: turning a persuasive conversation into reviewable evidence. Numi does that on European infrastructure, and it does not score or rank the candidate for you.
What the case is meant to show
The lesson is not that logos are bad or that titles never matter. It is that a startup hiring for a transition should match on the transition, and a title search structurally cannot do that. The right candidate here would have been filtered out by every conventional screen and surfaced by a trajectory one, and the interview is what turned "looks like a fit" into "owned the exact thing we need." If you are running a search like this, start by rewriting your brief as a problem, derive the triggers, and treat the interview as evidence you keep rather than a memory you lose. If you are also comparing tooling, our interview intelligence hub covers the recruiting-specific options, including how Numi compares to Metaview on EU data residency.