Your in-house recruiting agency.

From a role’s requirements to a screened shortlist[1] the same day, so you can do the human part, not the legwork.

[1]“Built ADF pipelines ingesting market data”Priya_Raman_CV.pdf, p. 1found in the file

Industry benchmarks

Where a recruiter’s hours go.

The legwork Scout takes on is where recruiting time goes, by the industry’s own numbers.

[01] Evidence

Every score shows why.

Scout reads each CV against the role’s rubric instead of matching keywords. It quotes the CV for every criterion it marks as met and drops any quote it can’t find in the file. Open a score to see the quotes behind it.

Priya_Raman_CV.pdfpage 1 of 2
Priya Raman
Senior Data Engineer · London
Experience
Northwind Capital — Senior Data Engineer, 2021 – present
  • Built ADF pipelines ingesting market data from fourteen vendors into one warehouse.
  • Owned the SQL Server warehouse end to end, from modelling to query tuning.
  • Moved two batch jobs onto Databricks as a pilot for the risk team.
Data Engineer, Halden Labs, 2018 – 2021
  • Wrote Python services for trade reconciliation and end-of-day reporting.
  • Ran the team’s on-call rota for the reporting stack.
Skills
Azure, SQL Server, T-SQL, Python, dbt, Power BI, Git
Education
BSc Computer Science, University of Manchester
Scoring against rubric v3
weight · result
  1. 1
    Azure Data Factory20must
    “Built ADF pipelines ingesting market data”
  2. 2
    SQL Server20must
    “Owned the SQL Server warehouse end to end”
  3. 3
    5+ years in data engineering15must
    “Data Engineer, Halden Labs, 2018 – 2021”
  4. 4
    Python10must
    “Wrote Python services for trade reconciliation”
  5. 5
    Databricks10
    “Moved two batch jobs onto Databricks”
  6. –
    Payments or capital markets10
    “Led payments integration for a European card scheme”
  7. –
    Terraform5
    No quote offered
The model’s claims would score89
After checking the quotes
··green
0amber 55green 75100

Quotes are checked

Met or partly met needs a quote from the CV. If Scout can’t find it there, the claim is dropped.

A 75 is always a 75

The AI checks each criterion against the CV. A fixed formula then turns those checks into the score, the same way on every role.

No verdicts from profiles

LinkedIn profiles are sorted into strong, some or thin. Only a scored CV can be marked red, and a dealbreaker needs a quote of at least six words.

[02] How it works

How a role moves through Scout.

Most roles go in this order, and finishing one step starts the next in the background.

01 / 06JD
  1. JD1/6

    Paste what the hiring manager sent.

    Text, a PDF or an email, in any language. Scout writes the JD in English and marks any gap the brief leaves for you to fill.

    • Notes from the intake call override the written brief
    • A finished JD is used unchanged
  2. Brand2/6

    JDs on your letterhead.

    Upload a JD you’ve already published. Scout copies its colours, footer and headings for every new one.

    • The preview on screen is the exported PDF
    • Diacritics print correctly, so București stays București
  3. Search3/6

    A rubric and searches for each role.

    Scout writes the screening rubric and the LinkedIn boolean searches in the background. You can edit both before anything is scored.

    • Dealbreakers are worded as the reason someone is ruled out
    • Each edit saves a new version of the rubric
  4. Sourcing4/6

    Sourcing in your own browser.

    The Scout collector, a Chrome extension, works through the searches in your LinkedIn session at about the pace a person would.

    • Pause or stop it at any point
    • It stops at a captcha, a sign-in page or a warning
  5. Candidates5/6

    Candidates screened as they arrive.

    Each profile is labelled strong, some or thin against the rubric, with a message drafted from your templates.

    • You send each message yourself from LinkedIn
    • Export the list to Excel or CSV
  6. CV scoring6/6

    CV scores with the evidence shown.

    Drag CVs from email, WhatsApp or LinkedIn onto the role. Each one is scored as above, quotes and all.

    • Green, amber or red against the rubric’s thresholds
    • Drop a CV straight onto the candidate it belongs to
[03] Teams

Use it alone or with your team.

Each account starts as a private workspace. If you start a team, roles created in it are shared with your colleagues, along with their sourcing sessions, candidates, CVs and scores.

See who is on which step

The role header shows which colleagues have it open and which step they’re on, so two people don’t work the same candidates.

An activity feed

See who imported candidates, who marked messages as sent and whose CVs arrived. The feed is built from the role’s own records, so it always matches them.

Shared and private templates

A template can belong to the team or to one person. The {{recruiter_name}} field fills in with the name of whoever creates the draft.

[04] Pricing

Pay for the work Scout does.

Scout is priced on usage: the roles it sets up, the profiles it screens and the CVs it scores.

What you pay for
unit · price
  • Role set up

    The JD, the rubric and the LinkedIn searches, written from one brief.

    Price not set yet
    per role
  • Profile screened

    A LinkedIn profile read against the rubric as it arrives.

    Price not set yet
    per profile
  • CV scored

    A CV scored against the rubric, each quote checked against the file.

    Price not set yet
    per CV
  • Match

    A CV matched against your open roles, or a JD against the people you already have.

    Price not set yet
    per match
Prices will be published here before anyone is billed.
One role, itemised
example
Senior Data Engineer
Meridian Financial · London
  • Role set up1 ×Price not set yet
  • Profile screened240 ×Price not set yet
  • CV scored18 ×Price not set yet
  • Match6 ×Price not set yet

Each line is a unit from the price list. The counts are an example, not an average.

Total for the role··
[05] Questions

Common questions.

Most are about your LinkedIn account and what happens to candidates’ data.

Does Scout scrape LinkedIn?

No. Scout’s servers don’t connect to LinkedIn at all. Sourcing runs in your own browser through the Scout collector extension, using your LinkedIn session, so the requests come from your computer.

Is my LinkedIn account at risk?

Yes, there is some risk. LinkedIn’s User Agreement prohibits software that collects profile data, and the collector runs on your account. Scout’s terms say so, and you accept them before your first run. To keep the risk down, runs open about 40 profiles an hour by default and stop at the first captcha, sign-in page or warning.

Will Scout message candidates for me?

No. Scout drafts a message for each candidate from your templates. You copy it, send it from LinkedIn and mark it as sent. The only thing a run can send is a connection request without a note, and only in sessions where you’ve allowed it.

What can the hiring manager’s brief look like?

Pasted text, a PDF or a Word file, in any language. Scout writes the JD in English and tells you if it translated anything. If the hiring manager has already signed off a JD, you can use it as it is.

Do I need the Chrome extension?

It’s the quickest way to source, but you can work without it. You can run the searches by hand and paste the results back, import a CSV, or drop in CVs.

Where are CVs stored?

In the EU. CV files, the text read from them and everything else on a role are stored in Frankfurt (Supabase, on AWS eu-central-1), and a file opens only for people who can see the role or talent pool it belongs to. Some of the work happens in the US: the app runs on Vercel, and to read and score a CV its text is sent to OpenAI’s API. OpenAI doesn’t train its models on API data and keeps requests for at most 30 days.

What about GDPR?

Your company is the controller of candidates’ data, and Scout processes it on your behalf. It only holds the people and CVs you add, and only you, or your team for team roles, can see them. Scout doesn’t decide anything about a candidate on its own. A person on your team makes every call, and each score shows the CV quotes it rests on, so you can explain how someone was assessed. You can delete a CV from the talent pool, a sourcing session with its candidates, or a closed role with everything on it, files included.

Does the EU AI Act apply to Scout?

Yes. The AI Act lists AI that filters applications or evaluates candidates as high-risk (Annex III), and the Digital Omnibus moved those obligations from August 2026 to 2 December 2027. Among other things, those rules ask for human oversight, transparency and record-keeping. In Scout, a person reviews every result and makes the decision, each score shows the evidence behind it and is worked out the same way on every role, and each score records the model and prompt version used. Companies using Scout have duties of their own as deployers, such as telling candidates that AI helps screen them.

Try it on a live role.

Paste in a brief you’re working on today. Scout writes the JD, the rubric and the searches from it.