WORKING STRATEGY · ASSUMPTION-LED
What it takes to finish FY27 at 800 employees
The hiring target must absorb attrition as well as growth. This model converts that requirement into monthly starts, funnel activity, recruiter capacity and business interview load.
Opening FY27 headcount
Plan of record: 400 at 31 December 2026. Lower scenarios hedge delivery risk; each 25-person shortfall adds about 23 FY27 gross starts.
01 · DELIVERY MATHEMATICS
The 800 target is a gross-starts problem
At the plan-of-record opening case, approximately 110 departures raise the requirement from 400 net additions to about 510 starts in the balanced seasonal profile. The lower scenarios show the FY27 cost if Verda exits 2026 below 400.
Recruiters required13staffed capacity at 85% utilisation
Peak delivery capacity14recruiter-equivalents in November; bridge if needed
Target TA team27transparent working capability model
Interview load floor6.3hours / month across 80 trained interviewers
472–550 gross starts and 12–14 recruiters in the 400 opening case.
If productivity is 3.0 / 3.0 / 5.0 starts per recruiter per month.
Per active interviewer / month with 50 active specialists and 1.5× process overhead.
Applied to Engineering, offers rise from about 665 to 694; treat 80% as a target.
Observed baseline · interview-reported
Verda has already demonstrated meaningful hiring velocity
Headcount reportedly grew from approximately 60 to 260 in ten months. Reaching 400 in the remaining 3.5 months would require about 40 net additions per month before replacements—roughly twice the recent net run-rate. These are calibration points, not substitutes for ATS and HRIS validation.
20net additions / month
21–23estimated gross starts / month
1.9×FY27 average vs recent gross run-rate
2.2×FY27 peak vs recent gross run-rate
Public-profile signal · reconstructed 12 Sep 2026
Recent visible leaver activity is below the planning case
Seven employee leavers were identified through mid-September. Against estimated average 2026 headcount of 160, the raw annualised signal is 6.2%; adjusting only for LinkedIn’s current-workforce coverage suggests approximately 8%. This is an indicative floor—not audited attrition—and must be replaced with HRIS data.
7employee leavers identified YTD
6.2%raw annualised signal
≈8%coverage-adjusted indication
18.4%conservative planning case retained
Model impact: at 10% attrition, the 400-opening case falls from 510 to approximately 460 gross starts, 11 recruiters and a 25-person TA team. At the recommended 12% planning floor, it requires approximately 472 starts, 12 recruiters and 26 total TA employees.
Start-distribution profile
Balanced seasonal
Flattest profile: moderate spring build and an August dip; Q4 remains the largest quarter at 27%, without a sharp late-year surge.
Monthly plan
Gross starts required
Illustrative planning profiles—not a forecast of Verda’s observed seasonality.
Q111623% of gross starts
Q213326% of gross starts
Q312224% of gross starts
Q413827% of gross starts
Starts lag workload. Offer activity for Q4 starts runs through Q3; overall interview and offer demand is spread across Q1–Q3.
Decision rule: the final curve should come from approved role-level start dates, site-delivery milestones and quarterly budgets. Seasonality and TA capacity should constrain that plan, not substitute for it. Earlier hiring slightly increases annual replacement demand because more employees are exposed to attrition.
Engineering
Plan continuously; bring forward foundational and dependency roles before the teams they unlock.
Data centre
Work backwards from design, construction, commissioning and ready-for-service stage gates.
GTM & other
Front-load revenue roles where ramp-to-productivity supports it; phase corporate roles to business need.
02 · OPERATING MODEL
Scale output without scaling friction
The model assumes focused hiring cohorts, evidence-rich assessment and a maximum of four candidate interviews for most roles.
Engineering
230starts · recurring role cohorts with role-specific scorecards
Data centre
204starts · working aggregate to validate across operations and construction / delivery
Other functions
77starts · conventional role-specific hiring unless volume recurs
Working TA composition
Every seat has a named purpose
Final spans and sequencing follow the first-30-day audit, including candidate-experience and onboarding ownership and whether one Talent Intelligence & Marketing partner is sufficient.
1 VP Talent1 Head of TA13 recruiters4 sourcers3 coordinators2 TA Ops & Analytics1 Talent Systems & Automation1 Executive Talent Partner1 Talent Intelligence & Marketing
Top-of-funnel activity28,059
→
Recruiter screens5,727
→
First interviews2,743
→
Final candidates1,457
→
Offers665
→
Starts510
Top-of-funnel activity is a scale indicator combining inbound applications and outbound sourcing activity—not a forecast of applications alone. Funnel assumptions must be recalibrated by role cohort.
High-signal interviews
Structured evidence against role outcomes, with fewer low-value stages and explicit decision ownership.
Selection process
A stretch against Ashby’s 17.9-day technical median; protected capacity, same-day feedback and automation make it attainable.
Approved offer delivery
Automated approvals, document generation and signature routing remove avoidable offer delay.
These are enterprise commitments, not TA-only promises: they require same-week interview slots, same-day feedback, pre-approved compensation bands, Legal-approved templates and a defined executive approval SLA.
03 · AI-NATIVE TALENT ENGINE
Build a system that compounds
AI and automation should remove coordination, surface decision-quality evidence and create one planning truth—without automating human judgement or candidate relationships. The ambition is an architecture that can support the next five to ten years, not only the FY27 surge.
Connected source of truth
Connect the ATS, HRIS, Finance workforce plan and compensation data through governed APIs. Keep the architecture system-agnostic until the current stack is audited.
Outcome: one role-level demand modelAutomate the administrative path
Scheduling, candidate communications, interview prompts, feedback nudges, approvals, document generation, signature routing and status updates.
Outcome: less manual work and frictionGive recruiters an information edge
Talent and location mapping, skills inference, candidate rediscovery, sourcing prioritisation, funnel anomaly detection and capacity forecasting.
Outcome: faster, better-targeted pipelinesMake progress visible in real time
An automated dashboard for Talent, hiring leaders, Finance and Ruben: plan versus actual, forecast starts, capacity, ageing, conversion, offer SLAs, cost and quality.
Outcome: one version of the truthProposed system architecture
One governed data spine, four systems of record
Keep specialist systems authoritative in their domains while a shared role ID and governed integration layer make planning, workflow and reporting coherent.
Business demand
Approved roles · site milestones · hiring-manager priorities · required-in-seat dates
ATS + CRM
Requisitions, candidates, stages, interviews, offers and source.
HRIS
People, organisation, starts, exits, tenure and internal movement.
Finance planning
Approved headcount, budget, forecast, cost centre and scenario.
Compensation
Level, location band, equity, exceptions and offer guardrails.
Shared data contract
Canonical role ID + talent data layer
Owner · function · level · location · budget · priority · target start · project milestone
- Role-based access
- Data quality rules
- Audit history
- Retention controls
Workflow orchestration
Scheduling, nudges, approvals, documents and signatures.
Planning dashboard
Plan versus actual, forecast starts, cost, capacity and risk.
Talent intelligence
Market maps, skills, supply, competition and pipeline health.
Candidate Intelligence
Transparent candidate guidance and consent-led talent discovery.
Design rule: integrate rather than duplicate. The ATS should not become the workforce plan, Finance should not become the recruiting workflow, and the dashboard should calculate from governed source data rather than manual updates.
Candidate experience productLee-built prototype → Verda implementation
Candidate Intelligence
A prototype AI tool Lee has built that could be implemented on Verda’s careers site. A candidate uploads a CV and selects a role; the tool provides structured feedback against published requirements and, where there is credible fit, lets the candidate opt in to share details with the hiring team.
Why build it
Help strong candidates surface in high-volume applicant pools, give applicants useful and transparent guidance, and provide recruiters with structured—not autonomous—decision support.
Required guardrails
No automated rejection · explicit consent · AI disclosure · explainable criteria · accessible human route · adverse-impact monitoring · auditable outcomes · Legal approval before build.
Discover
Market maps · talent signals · rediscovery
Engage
Prioritisation · personalisation · nurture
Select
Scheduling · evidence capture · nudges
Close
Approvals · documents · signatures
Learn
Forecasts · quality · bottleneck alerts
Human accountability by design
AI prepares, recommends and monitors; accountable people decide. Every use case needs GDPR review, role-based access, audit trails, bias and validity testing, candidate disclosure and clear vendor data-retention rules. Under the EU AI Act, transparency duties already apply and recruitment tools that materially influence CV sorting, ranking or fit assessment may fall within Annex III high-risk employment rules from 2 December 2027. Legal must confirm classification, Verda’s provider/deployer role and obligations before procurement, pilot or build.
API-firstInteroperableData ownershipFast to implementLow recruiter effortCandidate-centredSecure by designMeasurable ROI
04 · FIVE-TO-TEN-YEAR TALENT ARCHITECTURE
Build for FY27. Design for every cycle after it.
The FY27 team must deliver the surge without hard-wiring Verda to one hiring volume, one organisation shape or one generation of tools.
Design principle
Build an operating system that remains valuable whether Verda hires 100, 500 or 1,000 people a year.
Permanent core, elastic edge
Keep strategic capability and critical relationships in-house; use pre-qualified contract recruiters, specialist search and agencies as controlled surge capacity with clear activation thresholds.
Capabilities, not temporary silos
Build durable strengths in delivery, sourcing, operations, systems, executive talent, intelligence and marketing. Add adaptable domain specialisation, career paths, training and leadership succession.
Rolling 18–24-month demand
Connect required-in-seat dates, project dependencies, location, level, cost and recruiter capacity. Reforecast with Finance, HR and business leaders rather than resetting once a year.
Make reward a hiring system
Partner on market data, location and level bands, equity, exceptions and offer-loss analysis. Pre-approved guardrails enable the 24-hour offer SLA without weakening financial control.
Create a proprietary demand edge
Combine a shared skills taxonomy, internal and external supply, competitor movement and cost signals with a segmented employer proposition, technical proof, employee advocates and campaign conversion.
Codify what should repeat
Own smaller role-specific cohorts, reusable assessments and a site-launch playbook spanning market mapping, entity/EOR and supplier options, relocation, mobilisation and handoff—measuring interviewer effort per hire.
Design every candidate journey
Set measurable experience standards from first contact to onboarding handoff. Give VP+ candidates a discreet, personalised “business-class” journey with a named concierge and disciplined close.
Learn from employee outcomes
Connect source and assessment evidence to probation, ramp, performance and retention. Improve the process using outcomes—not activity volume or hiring-manager instinct alone.
Build, buy and retire deliberately
Use architecture standards, portability, security, AI evaluation, bias monitoring, vendor-risk reviews and measurable ROI. Prevent the long-term stack becoming a collection of disconnected tools.
05 · ROADMAP
Control first. Scale second.
The first 90 days create one source of truth, clarify accountability and pilot the operating model before peak FY27 delivery.
Align
Agree the workforce assumptions, CEO/CFO decision cadence and escalation route.
Output: one shared hiring forecastDiagnose and control
Audit the team, funnels, systems, integrations, data quality, suppliers, experience and interviewer load. Start a weekly hiring control room.
Output: verified baseline and constraintsDesign
Set recruiter allocation, sourcing coverage, assessment architecture, target tooling architecture and vendor shortlist, automation backlog and offer workflow.
Output: operating model and dashboard MVPPilot
Run smaller engineering and data-centre cohorts; pilot scheduling, evidence capture and offer automation; measure quality and interviewer hours.
Output: evidence before scaleScale
Ramp TA capacity, deepen pipelines in London, Helsinki and Spain, and connect ATS, HRIS, Finance and compensation data.
Output: capacity and infrastructure ahead of peakOptimise and sustain
Reduce low-signal activity, expand recruiter copilots, embed quality measures and manage a rolling automated gross-start forecast.
Output: speed, quality and forecast discipline06 · TALENT-LOCATION INTELLIGENCE
Prioritise Verda’s existing hiring markets
The market map broadens sourcing intelligence. It does not recommend moving hiring or opening new hubs.
London
Existing base for leadership, engineering, programme delivery and scarce specialists.
Helsinki
Global HQ for engineering, Nordic specialists and roles requiring leadership proximity.
Spain
Existing approved market for engineering, MEP, project delivery and selected operations cohorts. Madrid is the current market-map benchmark.
Current concentration appears heavily Finnish
LinkedIn associates 150 of 202 visible Verda members with Finland and 144 with the Helsinki area—approximately 74% and 71% respectively. This is a directional public-profile signal, not payroll data. It suggests that scaling London and Spain would represent a meaningful workforce-mix shift and should be planned explicitly.
How the wider research should be used
Frankfurt, Dublin, Amsterdam and Paris can supply scarce specialist candidates into approved Verda locations. Warsaw, Milan, Lisbon, Bucharest and Stockholm remain research references for cross-border sourcing, relocation and future contingency planning.
07 · CEO DECISIONS
What Talent needs from Ruben and the leadership team
Approve the workforce plan and curve
Function, level, location, priority, target start month, quarterly budget and site milestone—not only an 800-person headline.
Clarify Talent leadership remits
Define the responsibilities of the VP Talent, Head of TA, Head of People and hiring leaders.
Fund capacity and infrastructure early
Approve the phased TA build, bridge capacity, critical integrations and automation ahead of the selected curve’s peak workload.
Protect interview and decision time
Hold leaders to interview availability, same-day feedback and agreed approval SLAs.
Confirm approved hiring guardrails
Keep London, Helsinki and Spain as priorities while defining cross-border sourcing and relocation rules.
Define quality and responsible AI
Pair speed and volume with probation, retention, ramp and hiring-manager outcomes; approve the decision rights and controls for AI use.
DATA REQUIRED TO REPLACE ASSUMPTIONS
Eleven priority-one inputs
The strategy can begin now. These inputs determine whether the capacity and timing are accurate.
- Approved role-level workforce plan
- 31 December 2026 headcount forecast
- Twenty-four months of employee movements
- Recruiting funnel by role family
- Monthly TA roster, composition, agency support and planned vacancies
- Recruiter productivity and workload
- Interview activity and feedback time
- Offer outcomes and approval time
- Hiring-manager interview capacity
- ATS, HRIS, Finance and compensation data access
- Quarterly budgets and site-delivery milestones