Fixed quote after a free call

Recruitment CRM automation that keeps your database alive

Most agency databases go stale because updating them competes with calls. We connect your recruitment CRM to email, calendar, job boards and phone, log activity against the right record, prompt candidates to refresh their details, flag likely duplicates for a person to merge and create next-step tasks on every open job. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why recruitment CRMs go stale

A recruitment CRM is only as useful as its last update. Candidates move jobs and change numbers, call notes sit in notebooks and inboxes, and the same person ends up on file three times under different emails. Recruiters stop trusting search results and re-source people the agency already knows.

On the client side it is the same story. Open job orders without a next action, contacts who left months ago and no reliable view of which clients send repeat roles. Directors make decisions from gut feel because the pipeline report is wrong.

What we build

What our recruitment CRM automation includes

Activity logged for you

Emails, meetings and call outcomes are attached to the right candidate, contact or job record, so notes stop living in personal inboxes.

Profile refresh prompts

Candidates who have not been in touch for a set period get a short message asking them to confirm availability, location and preferences, with the answers written back.

Duplicate detection

Likely duplicates matched by email, phone and name are queued for a consultant to merge, never merged blindly.

Next-step tasks on every job

Open job orders without a scheduled action get a task and a nudge, so roles do not quietly go cold.

Retention review list

Records due for review under your data retention policy are listed for compliance to keep, refresh or delete.

Desk and director reporting

A weekly summary of new jobs, submissions, interviews and placements by consultant and client.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Activity happens

    An email, meeting, call or application touches a candidate, contact or job.

  2. 02 Automated

    Record updated

    The workflow finds the matching record through the CRM API and logs the activity.

  3. 03 Automated

    Gaps flagged

    Stale profiles, duplicates and jobs without a next step are queued.

  4. 04 Consultant review

    Consultant tidies

    Consultants confirm merges, refresh key records and act on tasks.

  5. 05 Recruiter or director decides

    Commercial decisions

    Which clients and roles to prioritise stays with the recruiter or director.

How it behaves

How the self-updating CRM behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What candidates and clients see

  • An occasional short message asking candidates to confirm availability and preferences
  • Consultants who remember the last conversation
  • No duplicate outreach from two people at the same agency

What consultants see

  • Activity already logged against the right record
  • A tidy-up queue of duplicates and stale profiles
  • Tasks on jobs without a next step and a weekly desk report

What the automation does

  • Matches emails, meetings and applications to records
  • Writes notes and updates through the CRM API
  • Applies retention and opt-out rules before any message

Edge cases and fallbacks

Email matches two records
Logged to neither; queued for a consultant to choose.
Candidate asks to be forgotten
Refresh messages stop and the request goes to compliance to action.
Personal email in a consultant's inbox
Only addresses already on a CRM record are logged; everything else is ignored.
CRM API limit or outage
Updates are queued and retried, and an alert goes to the ops lead.

Architecture

A self-updating recruitment CRM at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Email and calendar Microsoft or Google Job boards Applications Calls Outcomes and notes n8n Match and log Recruitment CRM Bullhorn, JobAdder Tidy-up queue Duplicates, stale Consultant Merges and tasks Weekly report By desk
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Emails, meetings, applications and call outcomes are picked up as they happen.
  2. 2 n8n matches each one to a candidate, contact or job and logs it through the CRM API.
  3. 3 Stale profiles, likely duplicates and jobs without a next step land in a tidy-up queue for consultants.
  4. 4 A weekly report shows activity and placements by consultant and client.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Recruitment CRM automation & data hygiene project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    CRM setup, custom fields, how consultants log work today, data quality and reporting needs.

  2. 02

    Design

    2 to 3 days

    Matching rules, refresh message wording, retention rules, task logic and report layout.

  3. 03

    Build

    1 to 2 weeks

    API connections, activity logging, refresh prompts, duplicate queue and reporting.

  4. 04

    Shadow run

    About 1 week

    Logging runs into a sandbox or flagged fields while consultants check accuracy.

  5. 05

    Launch

    1 to 2 days

    Switch on for one desk, train consultants, then widen.

  6. 06

    Support

    Ongoing

    New fields, desks and reporting changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Bullhorn REST API and event subscriptions JobAdder API and webhooks Loxo Open API and webhooks Microsoft Graph or Google Workspace APIs Claude or OpenAI for note summaries

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    CRM fields, matching rules, retention and reporting.

    $200 – $400

  • Build

    Logging, refresh prompts, duplicate queue and tasks.

    $500 – $1,300

  • Integrations

    CRM API, email and calendar, job boards and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a sandbox run checked by consultants.

    $100 – $250

  • Launch and training

    Switch-on per desk and consultant walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM API access (some vendors limit it to higher plans), n8n and messaging are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM plan: Your CRM vendor's own plan; some vendors limit API access to higher tiers.
  • n8n: Self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Billed by the provider per use; short note summaries are usually a small monthly amount.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

EU and UK: storage limitation

Personal data must be kept no longer than necessary for its purpose, so candidate records need a retention rule and a review list.

Source: gdpr-info.eu

US: marketing texts need consent

Texts that promote roles or services to candidates are marketing under the TCPA rules and need prior express written consent.

Source: www.law.cornell.edu

UK: marketing by text and email

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a simple way to refuse each time.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Recruitment CRM automation & data hygiene questions, answered.

It takes the logging, chasing and tidying off consultants: activity attached to records, candidates asked to refresh their details, duplicates queued for merging and tasks created on jobs that have stalled. The CRM stays the system people work in.

Bullhorn has a documented REST API with entity event subscriptions, JobAdder has an API and webhooks for approved partners, Loxo offers a paid Open API with webhooks, Recruit CRM opens its API on Business plans and above, and Vincere issues API keys through support. We check your plan and access first.

Built-in automation works well inside the CRM. We use it where it fits and add what it does not cover, such as connecting phones, accounting, e-signature or custom reports across systems.

No. Likely duplicates are matched and queued, and a consultant confirms each merge, because a wrong merge mixes two people's personal data.

Yes. It lists records due for review under the retention policy you set, and compliance decides whether to refresh consent, keep or delete them.

Share of records updated in the last six months, duplicates found and merged, jobs with a scheduled next step and time from new job to first submission.

Free 20-minute call

Want this for your recruitment agency?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call