Skip to main content
Back to Blog case study

How Growing Tech Companies Cut Their Time to Fill

Sofia Castellanos 7 min read
How Growing Tech Companies Cut Their Time to Fill

Time to fill is the metric most talent teams watch most closely, and for good reason. A role open for ninety days is not just a recruiting problem: it is an engineering sprint that did not ship, a sales territory that sat uncovered, a team that ran at reduced capacity through a quarter of work.

The teams that have cut their time to fill most meaningfully in our early-access cohort did not do it by adding sourcing tools or posting to more job boards. They did it by changing where the first message in a recruiting conversation comes from.

The bottleneck was not volume, it was conversion

Most growing tech companies have already optimized the volume side of sourcing. They are posting to LinkedIn, running Boolean searches, using one or two sourcing tools, maybe working with a recruiter or two on key roles. The pipe is full of names. The problem is that almost none of them respond.

Industry benchmarks for cold InMail reply rates typically land between 15 and 25 percent for well-crafted, targeted messages. For most teams, the actual rate is lower. A recruiter sending forty messages to find two phone screens is spending most of their week generating noise. The math of it means that cutting time to fill through volume sourcing requires either more volume (more time, more cost) or better targeting (hard to do at scale with anonymous outreach).

Warm introductions solve the conversion problem at its root. A candidate who receives a message forwarded by someone they actually know and respect is not comparing your outreach to forty other InMails in their inbox. They are evaluating a personal request from a trusted contact. The decision calculus is completely different.

What the shift looked like for three teams in our cohort

One team, a 70-person SaaS company in growth mode that was hiring primarily for engineering roles, had been running a standard sourcing playbook: two sourcers running searches, heavy InMail spend, 6-8 week average time to fill for senior engineers. After connecting employee networks through Drafted and starting to route introductions through warm paths, their first-quarter result was that 40 percent of their engineering hires came through a Drafted-surfaced introduction. Their average time to fill for roles where a warm path existed dropped by roughly two weeks compared to the prior period.

The mechanism was not complicated. They had several senior engineers with deep networks in the Boston technical community, particularly in distributed systems and backend infrastructure. Drafted identified which of their open roles mapped best to those employees' connection graphs and triggered targeted introduction requests. The candidates were already in their employees' networks. The only thing that changed was making those connections visible and actionable for the recruiting team.

A second team, an early-stage fintech company staffing up a go-to-market function, faced a different challenge: finding candidates with both technical product fluency and enterprise sales experience. That combination is genuinely rare, and cold sourcing for it produced a lot of irrelevant candidates who had one skill but not the other. After running Drafted's network analysis, they found that two of their existing employees had overlapping connections to exactly the profile they were looking for, people who had done presales or solutions engineering before moving into quota-carrying roles. The first warm introduction through that path led to a hire in five weeks, against a prior benchmark of eleven weeks for comparable roles.

The third example comes from a product team at a mid-size developer tools company that needed to hire two principal engineers within a quarter for a replatforming project. Pipeline had been empty for six weeks despite heavy sourcing. Drafted's scan identified six warm paths to candidates who matched the technical requirements, all through first-degree connections of existing team members. Three candidates agreed to take a first call within two weeks of the introductions. One hire closed in the quarter.

The time savings are mostly in the early funnel

When we look at where warm introductions compress the timeline, it is almost entirely in the first two stages: awareness (do they know about the role?) and consideration (do they want to learn more?). Cold sourcing treats both stages as unknowns. You write to someone who may or may not be open to moving, may or may not be interested in your company specifically, and may or may not read your message at all.

With a warm introduction, you already have partial information before the first message goes out. The connector knows the candidate and can make a quick judgment about whether this person is likely to be open. They can embed that context in the introduction: "I know you've been thinking about moving," or "this is the kind of infrastructure problem you like." That pre-qualification at the connector layer compresses weeks out of the front of the funnel.

The stages after first contact (technical screens, interviews, reference checks, offer) do not change much with warm introductions. You still need to do the work. But fewer cycles are wasted on candidates who were never going to be interested, and fewer cycles are lost to candidates going dark after an initial response.

What this does not fix

We want to be honest about the limits. Warm introductions work best when your team's collective network includes people who are realistic candidates for your open roles. For highly specialized roles in niche technical areas, or for roles that require geographic presence in a market where you have no employee network coverage, warm paths may not exist at all.

The approach also depends on employee participation. Introductions require employees to be willing to forward a message to a contact. Most are, when the ask is specific, low-effort, and clearly benefits the company. But if employees are disengaged or if the request process is burdensome, the conversion from "warm path identified" to "introduction sent" breaks down. Drafted tries to minimize that friction with one-click draft generation, but the fundamental social dynamic is still a real factor.

And finally, warm introductions do not guarantee the candidate is qualified. They guarantee the candidate will read the message. The recruiting team still needs to do real screening. The time savings come from spending more of that screening time on people who are likely to be interested, not from removing the screening itself.

The metric shift worth watching

Teams that run this well stop tracking sourcing volume as a primary indicator and start tracking warm path conversion rate: of the introductions made through their team's network, what fraction resulted in a first call, and of those, what fraction advanced? That number, when it is healthy, tells you that your network coverage is real and your introduction process is working. Volume sourcing metrics tell you how hard your team is working. Warm path conversion tells you whether that work is landing.

Try Drafted

Start hiring through warm introductions

See your first warm path in under 48 hours. No credit card required.