AMROAR Technologies

Candidate Pipeline Automation — Bridgepoint Talent | Amroar
Automation Make.com OpenAI Typeform Airtable Twilio SendGrid

200 applications. 4 hours of reading.
Now 25 minutes — for the ones that matter.

Bridgepoint Talent's recruiters were drowning in CVs. We built a screening engine that scores, routes, and responds — so humans only read the top 20%.

Client
Bridgepoint Talent
Industry
Recruitment & Staffing
Stack
Make · OpenAI · Airtable
Build Time
3 weeks
78%
Less time spent on manual CV screening per day
<3 hrs
First candidate response — was 5 to 7 days
More placements per recruiter per month
0
Qualified candidates missed or ghosted

A recruitment firm where the bottleneck
was the recruiters themselves.

Bridgepoint Talent is a specialist recruitment firm placing mid-to-senior professionals across finance, operations, and risk management in the US and UK. With 40 recruiters managing between 80 and 120 active roles at any given time, the volume of incoming applications had quietly become unmanageable.

Each role received between 80 and 250 applications. Recruiters were expected to screen them all, respond to relevant candidates, brief the client, coordinate interviews, and close placements — while simultaneously managing their pipeline. Most were spending the first two to three hours of every day just reading CVs, before they'd spoken to a single person.

The problem wasn't effort. The problem was that 80% of screening work was low-judgment pattern matching — does this person have the right experience, seniority level, and sector background for this role? That's exactly the kind of task that doesn't need a human. And by keeping humans on it, Bridgepoint was bottlenecking the parts that actually do.

They came to us with one ask: give recruiters their mornings back. What we built gave them a lot more than that.

Company Bridgepoint Talent
Industry Recruitment & Staffing
Team size 40 recruiters
Active roles 80–120 at any time
Applications/month ~4,000 across all roles
Automation type AI screening pipeline
Primary tool Make.com + OpenAI GPT-4o

Five reasons top candidates
were slipping through.

None of these were caused by bad recruiters. They were caused by a process designed for a volume it could no longer handle.

01
4 hours a day lost to CV reading
Each recruiter managed 8 to 12 active roles. Screening alone consumed most of the morning — before any calls, client updates, or pipeline work had started.
02
5 to 7 day response times
Candidates applied and waited almost a week for any response. The best candidates — who had multiple options — were accepting other offers before Bridgepoint replied.
03
No consistent scoring criteria
Different recruiters assessed the same CV differently. Seniority thresholds, sector experience, and deal-breaker criteria weren't applied consistently across the team.
04
Interview scheduling over email
Coordinating a three-way interview between a candidate, recruiter, and client contact took an average of 11 emails. One round of scheduling was eating 25 to 40 minutes per role.
05
Client briefings built from scratch
Every shortlist required a formatted briefing document — candidate summaries, suitability notes, availability, salary expectations. Built manually in Word for every role, every time.
06
Airtable used as a filing cabinet
Candidate records existed in Airtable but were updated manually and inconsistently. There was no pipeline view that anyone trusted enough to act on.

How the screening engine is wired.

Make.com handles the orchestration. Every tool in the stack has one job — and hands off cleanly to the next. No manual data movement between systems.

INPUT LAYER ORCHESTRATION ACTION LAYER HUMAN LAYER Typeform Application form + CV upload Structured per role template LinkedIn Apply Easy Apply integrations Parsed via webhook Email Inbox Direct applications to roles@ Parsed + routed automatically Make.com Scenario orchestration · Routing OpenAI scoring · Conditional logic Airtable Candidate record created Score + status logged SendGrid Rejection or interview email Personalised per score band Twilio SMS Fast-track availability check Score 80+ triggered only Calendly Interview booking link sent Recruiter calendar synced Slack Recruiter notified on shortlist Action required — top 20% Recruiter reviews shortlist in Airtable Conducts interview · Logs outcome Manages offer + placement

How every application gets
scored and routed.

OpenAI scores each application against a role-specific rubric. The score determines the response. No human decides who gets a reply — the criteria do.

STEP 01 Application Received STEP 02 Extract CV Fields STEP 03 OpenAI Scores 0–100 Role rubric applied STEP 04 Score Router SCORE < 60 Rejection email Personalised via SendGrid SCORE 60–79 Warm hold email Pool for future roles SCORE 80+ SMS + Interview Twilio + Calendly fired ALL PATHS Log to Airtable STEP 06 Recruiter Acts on 80+ ⏱ Steps 01–05 complete in under 90 seconds per application. Recruiters notified only when a score of 80+ is reached.
0 – 59
Automated rejection
Personalised rejection email sent via SendGrid. Candidate thanked, told they haven't been progressed, encouraged to apply for future roles. No recruiter time used.
60 – 79
Warm hold pool
Candidate receives a holding email. Record tagged in Airtable as "pipeline candidate" — searchable for future roles without re-advertising. Recruiter can manually promote at any time.
80 – 100
Fast-tracked immediately
Twilio SMS fires within 90 seconds of application. Calendly interview link included. Recruiter pinged in Slack. This is the only group that requires a recruiter to take action.

Three phases. One continuous pipeline.

Built and tested in three weeks. The testing phase deliberately included edge cases — part-time roles, career changers, internal referrals — to make sure the scoring held up under real conditions.

01

Application intake + AI scoring engine

Every application source — Typeform, LinkedIn Easy Apply, and direct email — was routed into a single Make.com scenario. The first module parses the incoming data and extracts the CV. That gets passed to OpenAI GPT-4o with a role-specific prompt that scores the candidate across five dimensions: relevant experience, seniority match, sector background, tenure pattern, and any flagged deal-breakers defined by the client brief.

The rubric is set once per role when the job is opened — recruiters fill in a structured brief in Airtable that Make.com reads to build the scoring prompt. Different roles weight different dimensions. A risk analyst role weights sector experience heavily. A generalist ops hire weights adaptability. The same infrastructure handles both.

Make.com OpenAI GPT-4o Typeform Airtable (rubric source)
02

Score-based routing + automated outreach

Once the score comes back, the Make.com router fires one of three paths. Candidates below 60 receive a personalised rejection via SendGrid — not a generic bounce, but a message that references the role they applied for and their approximate experience level. Candidates between 60 and 79 go into a warm hold pool in Airtable with a holding email. Candidates scoring 80 or above are fast-tracked.

For fast-tracked candidates, Twilio sends an SMS within 90 seconds of their application — something along the lines of confirming receipt and asking for availability for a brief call. If they respond, a Calendly link fires. The recruiter gets a Slack notification with the candidate's Airtable card linked. By the time the recruiter looks at it, the interview is often already booked.

Make.com Router SendGrid Twilio SMS Calendly Slack
03

Interview logging + automated client briefing

After the recruiter conducts an interview, they update a simple Airtable form — suitability rating, key notes, candidate's stated salary expectation and availability. That triggers the final Make.com flow: a structured client briefing document is generated automatically, pulling from the candidate's Airtable record and the recruiter's post-interview notes, formatted into Bridgepoint's house style, and emailed to the client contact.

What used to be 45 minutes of formatting in Word is now a 90-second automated output. The recruiter's job is the interview and the notes. Everything else is automated.

Airtable Make.com Document Generation SendGrid

What changed after go-live.

Measured across the first 90 days in production, compared to the same period in the prior year.

78%
Reduction in daily screening time per recruiter
The average recruiter went from 3.5 to 4 hours of CV reading per day to around 25 minutes reviewing pre-scored shortlists. That time went back into calls, client relationships, and closing — the work that actually drives revenue.
<3 hrs
First candidate response — was 5 to 7 days
Top-scored candidates now hear from Bridgepoint within 90 seconds of applying. Not a form confirmation — an actual personalised outreach with an interview booking link. Bridgepoint is almost always first to contact the candidates they want.
More placements per recruiter per month
With the screening bottleneck gone, recruiters could handle more active roles simultaneously. Combined with faster candidate response times, placement volume per recruiter tripled within the first quarter after launch.
0
Qualified candidates missed or ghosted
Previously, candidates scoring what would have been an 80+ were regularly overlooked — buried under volume, or simply not reached in time. Now every application above threshold gets the same response within the same window, with no exceptions.

Seven tools. One pipeline.

⚙️
Make.com
Scenario orchestration, routing, scheduling
🤖
OpenAI GPT-4o
CV scoring against role-specific rubric
📋
Typeform
Structured application intake per role
🗃️
Airtable
Candidate records, pipeline, rubric source
💬
Twilio SMS
Instant outreach for top-scored candidates
📧
SendGrid
Rejection, hold, and briefing emails
📅
Calendly
Interview scheduling, recruiter sync

What's your team doing
that a machine should be?

Tell us the process. We'll tell you whether it can be automated, what it would take, and what it should cost — in 30 minutes, before you commit to anything.

Shivam or Sonam on the call. Not a junior consultant.