Secure workspace

Access required

Enter the Henderson Drake access code to view the current phase map.

HD
Henderson Drake phase map

Recruitment Market Engine phase map.

This is the current customer-facing delivery map for the Henderson Drake system. The work is one connected machine, delivered in controlled phases so the data, scoring, outreach, call intelligence, and consultant workflow are built in the right order.

Important delivery principle

Later phases are not separate surprise products. They are the delivery order for the agreed machine. The foundation must create clean records and clear matching rules first, then outreach, RingCentral transcription intelligence, scoring, ranking, and consultant workflow can build on that foundation.

Customer-facing phase map

Each phase has a clear working output. Some workstreams can overlap once access and approvals are available, but the dependencies below keep the build controlled.

Phase 1 Foundation

Lead sourcing and enrichment foundation

Build the first controlled engine for finding, enriching, scoring, deduplicating, and preparing high-quality target records for review and JobAdder/import readiness.

  • Agree the first specialist market, geography, and target company profile.
  • Use approved buying and hiring signals to source and enrich target companies and contacts.
  • Prepare clean output with source evidence, confidence, and duplicate handling.
  • Prove the first sample before live writeback or wider rollout.
Phase 2 Activation

Outreach cadence, reply capture, and lead bank

Turn approved records into controlled outreach activity, with replies and warm opportunities held in one place for consultant action.

  • Confirm approved email/SMS routes, send windows, suppression rules, and campaign ownership.
  • Build the first cadence around the agreed value proposition and MPC proof point.
  • Capture replies, remove people from sequence when needed, and route warm leads into the lead bank.
  • Give the team a clear view of what needs action and who owns it.
Phase 3 Call intelligence

RingCentral transcripts, notes, and scoring gaps

Use existing RingCentral call recordings and transcripts to fill the blanks that scoring cannot reliably get from public data or static records alone.

  • Connect available RingCentral transcript data into the review workflow.
  • Match calls to the right person or company using phone number, contact record, and JobAdder matching rules.
  • Extract useful notes, summaries, salary/compensation signals, notice period, availability, and other agreed criteria.
  • Push the notes, summary, or field suggestions into the agreed destination for review or update.
Phase 4 Ranking

Scoring, ranking, and consultant workflow

Bring source data, outreach activity, JobAdder context, and call intelligence together so Henderson Drake can prioritise the right records and actions.

  • Combine buying signals, enrichment data, call notes, and agreed criteria into a practical ranking model.
  • Show which records are ready, which need review, and which should be held back.
  • Support team allocation, ownership, and action status.
  • Keep the review route visible so scoring can be tuned from real feedback.
Phase 5 Scale

Refresh, optimisation, and wider database improvement

Scale the machine once the first routes are proven, with regular refreshes, quality checks, and wider record improvement.

  • Expand into further markets, roles, geographies, or specialist segments.
  • Refresh target lists and update scoring based on new signals and real outcomes.
  • Improve existing JobAdder data where matching, field coverage, or evidence is weak.
  • Report on quality, gaps, and next improvements.

Dependencies and order

The build can move quickly, but the system needs the right inputs before each later stage can work properly.

What must come first

  • Approved first market, company profile, source policy, and required output fields.
  • JobAdder/import route, duplicate rules, owner rules, and review process.
  • Agreed candidate/MPC field list and rules for what can be used in outreach.
  • Clear success measure for the first reviewed sample.

What can be pulled forward

  • RingCentral can start earlier once transcript access, matching rules, and destination fields are confirmed.
  • Outreach can start once the first sample is approved and suppression rules are agreed.
  • Lead-bank workflow can start once reply ownership and team allocation rules are confirmed.
  • Live writeback should wait until the first output is reviewed and signed off.

Included in the current programme

This map treats the following as part of the connected Recruitment Market Engine programme, subject to the sequencing and approvals above.

  • Lead sourcing, enrichment, deduplication, confidence scoring, and JobAdder/import-ready output.
  • Outreach cadence, reply handling, suppression rules, and lead-bank workflow.
  • RingCentral transcription intelligence for notes, summaries, scoring gaps, and criteria updates.
  • Ranking, consultant allocation, review queues, and quality feedback.
  • Refresh, optimisation, and wider database improvement once the first routes are proven.