Ashby and External Sourcing: Increasing Candidate Flow for Fast-Growing Companies

Ashby has built a strong following among fast-scaling, VC-backed companies, largely on the strength of its recruiting analytics and structured hiring workflows. Companies choose it to make better decisions about the candidates already in the pipeline — it doesn't independently generate more candidates to put into that pipeline.

Analytics are only as good as the data feeding them

Ashby's reporting can tell a team exactly where a pipeline is thin or where conversion is dropping — but knowing that doesn't fix it. For companies scaling headcount quickly across multiple functions, the fix usually has to come from outside the platform: more qualified candidates entering at the top.

Connecting an external sourcing layer

Ashby's API supports adding candidates to specific job postings with structured data and notes attached. A sourcing layer that pre-qualifies candidates externally through targeted social campaigns can deliver them directly into the relevant posting, ready for a recruiter to review.

What it means for a fast-scaling team

• Ashby's analytics get more useful once there's a healthy volume of qualified candidates to measure
• Recruiters spend less time cold-sourcing and more time on the structured evaluation Ashby is built for
• Hiring plans tied to aggressive growth targets are less likely to stall on thin pipelines
• Existing scorecards, stages, and reporting stay exactly as configured

When this is worth setting up

This shows up clearly on a growth-stage hiring plan when Ashby's own funnel analytics show healthy conversion rates but a thin top of funnel — the bottleneck is volume entering the pipeline, not how well the pipeline itself is run.

What SmartHire adds above Ashby

SmartHire sources and pre-screens candidates through targeted social campaigns, then delivers qualified matches into your Ashby postings via API. Your structured hiring process and analytics stay exactly as built — the only change is how much qualified volume they have to work with.

Checklist before connecting to Ashby

• Which jobs or regions in Ashby have the thinnest candidate flow today?
• Which fields should come with each candidate, such as contact details, screening answers and source?
• Who owns access, permissions and the integration user?
• How will duplicates be detected, and how long are records kept?
• Which numbers will you compare before and after: cost per qualified candidate, time to first candidate, recruiter hours?

A simple way to pilot it

Start with one role in one location, ideally roles where the team wants more qualified volume without adding manual sourcing. Run the sourcing layer for a few weeks alongside your normal process, and compare it with the same role's inbound results. If the numbers hold, extend to more roles. This is a pilot, so the results depend on the role and market, and you should treat any published benchmark as a guide only.

Candidate data is personal data. Check that consent, data-processing terms and storage locations meet your rules before you go live, and confirm what your plan and version of the system allow.

Does Ashby need to be replaced or changed?

No. The sourcing layer runs alongside it, and your team keeps working in Ashby exactly as before. It is a good fit for technology companies that want analytics-heavy recruiting.

How long does setup take?

It depends on which fields you connect and what your IT team needs to approve. Starting with a single role keeps the first setup short and makes problems easy to spot.

How do we know it is working?

Compare cost per qualified candidate, time to first qualified candidate and recruiter hours on screening against your existing baseline for the same type of role.