HD
Henderson Drake onboarding

Phase One information request.

Confirm the information we already have, upload any missing source files, and answer only the outstanding questions required before the first Lead Engine build can begin. Final approval will be requested once all required information has been provided and verified.

1. What we already know from the SOP

Neil has already supplied these points, so please approve them or mark them as requiring corrections.

Campaign ownerChris Routledge
TargetSME and scale-up hiring managers
PropositionSpecialist EPM/BI recruitment knowledge
CadenceFive touches across roughly two weeks
Key proof pointUse a real relevant MPC profile in touchpoint 3
Pilot size10-20 prospects first
Reply rulePull replies out of sequence immediately
No response ruleMove to nurture and revisit after 90 days

2. Uploads and source files

Upload any existing exports, enriched samples, field maps, or notes that can help test the first Lead Engine proof.

How this is used Existing or previously enriched data is used internally to test matching, enrichment, deduplication, and field coverage. It does not change the visible Phase One deliverable.
Use CSV, Excel, PDF, Word, text, or JSON files. Uploads save to shared hosted storage.
No documents uploaded yet.

3. First target market

We know the SOP is aimed at SME/scale-up hiring managers. Confirm the exact slice for the first lead sample.

Pre-filled from Chris' email These company fields have already been supplied, so Henderson Drake only needs to approve them or mark the list as requiring corrections.
  • Recent blogs, white papers or company announcements.
  • New CEO, investments, new client wins or similar change signals.
  • Number of recent hires in the past 6 months.
  • Evidence that the company uses external recruitment agencies.
  • Employee retention.

4. Buying and hiring signals

Rank the signals that should be used to find and prioritise target companies. Use 1 for the strongest signal, or N/A if a signal should not be used.

5. Source and enrichment rules

Confirm how records can be found, enriched, and held for review before import.

6. JobAdder and import route

Confirm how the first batch should enter Henderson Drake's working system.

7. MPC profile inputs

The SOP needs a real relevant MPC profile for touchpoint 3. Confirm how Henderson Drake wants to provide and approve those profiles.

Pre-filled from Chris' email These candidate fields have already been supplied, so Henderson Drake only needs to approve them or mark the list as requiring corrections.
  • Communication level out of 10: ability to deliver technical and complex information to English-speaking stakeholders.
  • Number of end-to-end implementations in an EPM tool.
  • Industry sector experience, for example manufacturing, pharma or financial services.
  • Use case experience, including finance, FP&A, CapEx, OpEx, demand planning, supply planning, workforce/people planning, consolidation and account reconciliation.
  • Salary or compensation requirements.
  • Notice period.
  • Software certifications.
  • Number of months or years residing in current country.
  • Contractor or permanent employee.

8. Mailbox, logging and pilot rules

These are the minimum operational details needed before the SOP can become a controlled pilot workflow.

9. Review, routing and success measure

Agree who reviews the first output and how Henderson Drake will decide whether it is useful.

10. Wider programme workstreams

Select anything Henderson Drake wants prioritised immediately after the foundation stage, or pulled forward by agreement. These workstreams sit inside the wider Recruitment Market Engine programme rather than outside it.

11. Final approval and sign-off

Once the information above has been supplied, this confirms the first working section and keeps the build focused.

Phase One focus The first deliverable is a controlled lead sourcing and enrichment proof, with clean output prepared for JobAdder or an agreed import route.