We connected people, skills, project work, and career goals. The answer: most of the talent is here. Now give it a clear path.
Customers now handle routine technology work themselves, so Meridian's growth depends on people who can diagnose harder business problems and deliver the solution.
That shift creates 60 growth-team positions in advisory, AI, automation and data work. These are not additional headcount on top of today's business. They are where the next phase of revenue is expected to come from, and they must be staffed from a company built to do different work.
The opportunity is to solve harder client problems. Build a focused team around that work.CEO takeaway
Nine in ten positions can be filled internally, which protects client delivery and keeps the cost of the shift far below open-market hiring.
The 54 internal positions use three routes, each with a different cost and timescale. Twenty-four people are ready to assign now. Eighteen develop inside their current teams over a quarter. Twelve transfer once a handover is agreed. Only six senior specialist positions need external hiring.
Most of the team can come from within. Develop 18 people, move 12, and hire only for the six remaining gaps.CEO takeaway
Thirty-six people already hold relevant experience elsewhere in Meridian, so the first wave of growth staffing needs no hiring approval and no waiting.
Twelve both want the move and can be released after a handover. The other 24 meet only one of those two conditions: interested but not releasable, or releasable but not interested. They are not in the plan.
The first 12 moves have both interest and a release route. Turn those conditions into dated handovers.CEO takeaway
Eighteen people can reach the standard inside their current teams, but only if one day a week is genuinely protected from client delivery.
That is 43.2 person-weeks over the quarter: 18 people, one day in five, twelve weeks. This capacity has to come out of work they do today. It cannot be added on top of a full workload.
Training will not work on top of a full workload. Protect time now and agree full-time release before day 90.CEO takeaway
Two different risks sit here: six senior positions no training can fill in time, and five critical roles with nobody trained to take over.
Hiring addresses the first risk. Senior advisory judgment and applied AI delivery take years of experience to build, and the growth plan needs them this year, so six specialists must come from the external market.
Hire missing experience and share critical knowledge. Growth should not depend on one person being available.CEO takeaway
Without protected learning time, agreed handovers and specialist hires, the growth team fills too slowly and existing client work continues to take priority.
A three-month delay moves roughly €1m of planned new-service revenue into a later period. That figure spreads €4m of annual revenue evenly across the year. It is a timing estimate, not a forecast, not profit, and not a lost sale.
| Today | Day 30 | Day 60 | Day 90 | |
|---|---|---|---|---|
| With the plan | 24 | 36 | 48 | 60 |
| Without the plan | 24 | 26 | 28 | 30 |
Waiting keeps capacity tied to yesterday’s work. Approve the launch or reset the delivery expectations.CEO takeaway
One owner, three milestones, and an explicit stop-or-scale decision at day 90, so the launch either earns its next budget or gets corrected early.
Everything starts with people and work already identified: 12 handovers, 18 protected learning slots, six searches, five cover tests. None of it depends on a reorganisation.
Confirm 12 handovers. Protect time for 18 learners. Open six searches.
Run four client pilots. Test cover for five critical roles.
Review results and readiness. Scale what works; fix what does not.
Approve one focused launch. Protect time, agree handovers, hire the missing experience, and review proof before scaling.CEO takeaway
Explore every finding, recommendation and source in the detailed report.
Selected highlights. The detailed view contains the complete report.
We connected people, skills, project work, and career goals. The answer: most of the talent is here. Now give it a clear path.
Customers now handle routine technology work themselves, so Meridian's growth depends on people who can diagnose harder business problems and deliver the solution.
That shift creates 60 growth-team positions in advisory, AI, automation and data work. These are not additional headcount on top of today's business. They are where the next phase of revenue is expected to come from, and they must be staffed from a company built to do different work.
Client demand is not the problem. The problem is supply: whether enough people can move into this work in time, and which work they stop doing to make that possible.
Read the breakdown below as a staffing requirement, not a hiring plan. The findings that follow set out how much of it Meridian can fill from its own people.
The opportunity is to solve harder client problems. Build a focused team around that work.CEO takeaway
Nine in ten positions can be filled internally, which protects client delivery and keeps the cost of the shift far below open-market hiring.
The 54 internal positions use three routes, each with a different cost and timescale. Twenty-four people are ready to assign now. Eighteen develop inside their current teams over a quarter. Twelve transfer once a handover is agreed. Only six senior specialist positions need external hiring.
The routes do not overlap. No one is counted twice, and a transfer who also needs coaching stays in the move count instead of appearing in both. That is why the total can be checked rather than taken on trust.
The internal route lowers salary cost but creates a different one. It requires management attention, protected learning time and handover capacity from the same teams that are delivering to clients today, and those are harder to free up at short notice than budget.
Most of the team can come from within. Develop 18 people, move 12, and hire only for the six remaining gaps.CEO takeaway
Thirty-six people already hold relevant experience elsewhere in Meridian, so the first wave of growth staffing needs no hiring approval and no waiting.
Twelve both want the move and can be released after a handover. The other 24 meet only one of those two conditions: interested but not releasable, or releasable but not interested. They are not in the plan.
The 24 interested and the 18 releasable are overlapping groups, not sequential stages. Adding them together would count the same people twice. Only the 12 who meet both conditions can be planned against, which is why the figure is 12 and not 36.
Plan against 12 today, and review the other 24 each quarter. Whether someone can be released changes with client workload far more often than whether they want the move.
36 people outside the ready and learning groups, with relevant project experience.
Interest and release counts can overlap. Do not add them.
The first 12 moves have both interest and a release route. Turn those conditions into dated handovers.CEO takeaway
Eighteen people can reach the standard inside their current teams, but only if one day a week is genuinely protected from client delivery.
That is 43.2 person-weeks over the quarter: 18 people, one day in five, twelve weeks. This capacity has to come out of work they do today. It cannot be added on top of a full workload.
This is the assumption most likely to break without anyone noticing. Learning time agreed in a planning meeting but not defended during a busy month goes back into client work. The shortfall then appears at day 90, when the 18 are not ready to take up their positions.
So the decision that matters is not the training plan itself. It is each team lead naming the routine work that stops, and the person who picks it up.
One protected day each week. Pair with an experienced lead.
Deliver one bounded client task with review.
Pass a practical check. Extend support where needed.
Training will not work on top of a full workload. Protect time now and agree full-time release before day 90.CEO takeaway
Two different risks sit here: six senior positions no training can fill in time, and five critical roles with nobody trained to take over.
Hiring addresses the first risk. Senior advisory judgment and applied AI delivery take years of experience to build, and the growth plan needs them this year, so six specialists must come from the external market.
Trained cover addresses the second risk. Eight roles are business-critical, three have a tested backup, and the remaining five would stop if that one person left. Those five people are already inside the 24 ready assignments, so cover is not extra headcount. It is a handover test someone has to schedule and run.
Neither action helps with the other risk. Hiring specialists does not reduce dependence on single individuals, and training backups does not add senior experience.
Work could stop while a replacement learns the client and the system. Pair a backup with each of the five uncovered roles and test the handover by day 60.
Hire missing experience and share critical knowledge. Growth should not depend on one person being available.CEO takeaway
Without protected learning time, agreed handovers and specialist hires, the growth team fills too slowly and existing client work continues to take priority.
A three-month delay moves roughly €1m of planned new-service revenue into a later period. That figure spreads €4m of annual revenue evenly across the year. It is a timing estimate, not a forecast, not profit, and not a lost sale.
The main risk is not that the plan fails. It is that the capability arrives after clients have met the same need elsewhere, either with a competitor or with their own teams. The work is then harder to win and worth less.
Delay also accumulates. Each month without protected learning time moves both the 18 learners and the 12 transfers back by a full month. That time cannot be recovered by working faster later, because the constraint is release and capacity, not effort.
| Today | Day 30 | Day 60 | Day 90 | |
|---|---|---|---|---|
| With the plan | 24 | 36 | 48 | 60 |
| Without the plan | 24 | 26 | 28 | 30 |
Waiting keeps capacity tied to yesterday’s work. Approve the launch or reset the delivery expectations.CEO takeaway
Every one of the 60 positions has exactly one staffing route, so the plan can be checked for double-counting before anything is committed.
Ready, develop, move and hire are separate counts within each service. A transfer who also needs coaching stays in the move count. Anything the four routes do not cover is shown as unfilled, rather than moved into another column to make the total look complete.
This is what makes the plan checkable. Staffing plans usually fail review because one capable person has been counted against three different needs. Here each person maps to a single planned position.
What the plan does not do is confirm the individuals. It reconciles the totals. Checking named people against all four service plans is the next piece of work, and it belongs to the service leads.
Future need: 18Time to capability: 90-day launch
Full-time roles; four separate groups.
Future need: 18Time to capability: 90-day launch
Full-time roles; four separate groups.
Future need: 12Time to capability: 90-day launch
Full-time roles; four separate groups.
Future need: 12Time to capability: 90-day launch
Full-time roles; four separate groups.
Defer lower-value internal projects and phase routine client work. Team leads must agree the tradeoff before moving people. The plan does not assume everyone can do two jobs.
The staffing plan is achievable only when current work has a new owner. Make the tradeoffs explicit.CEO takeaway
Every figure in this diagnosis traces back to a named input, a date, and a rule for what it does and does not prove.
This annex lists those inputs, how current they are, and the single review pass applied to them. 6,880 evidence points is a large amount of information, but volume is not the same as confidence.
Read this before quoting any figure outside this diagnosis. Several inputs are older than the planning date, and performance reviews are nine months older. A company-wide map also does not mean all 860 people were assessed for growth work.
Meridian is fictional, but the structure of this register is not. It is what a real diagnosis would have to produce before its numbers were used to move anyone.
Meridian is fictional. Its people, evidence records and expert review outcomes are invented for demonstration. The register below describes assumed inputs and does not refer to real employee files.Demo scenario
| Input | Records | Assumed date | What it tells us |
|---|---|---|---|
| Employee roster | 860 | September 2026 | Who is employed and in which department. |
| Role catalogue | 64 | September 2026 | Distinct job titles, not headcount or open positions. |
| Skill records | 3440 | August–September 2026 | Relevant skills, with manager confirmation where assumed. |
| Project examples | 1720 | Previous 12 months | What people have done on comparable work. |
| Performance reviews | 860 | December 2025 | Delivery quality; older signals need a current check. |
| Career conversations | 860 | September 2026 | Interest in the proposed work, not consent to a move. |
| Capacity reviews | 860 | September 2026 | Release conditions, handovers, and competing work. |
The funnel’s expert-validated step depicts this review in the fictional scenario. No actual expert sign-off took place.
Every figure here is sourced and dated. Confirm it against live records before it drives a real decision.CEO takeaway
Each count that drives a recommendation is recorded here with its evidence, the test applied, and the limit on what it can support.
Open any entry to check the figure behind it. The register states plainly what each number cannot prove, so that disagreement is about the evidence rather than about the recommendation.
The arithmetic reconciles: 24 ready, 18 developing, 12 moving and six hired make 60, and the overlapping candidate groups are reported as overlaps rather than added together. Consistent arithmetic is a minimum standard, not proof that the plan will work.
It does not establish readiness. Interest recorded in a conversation is not agreement to move. A skill record is not evidence of delivery. A nine-month-old review is not a current one. The open questions at the end of this annex are the ones to settle before any assignment is confirmed.
Covers the most people but proves the least. A recorded skill is a claim, not evidence of delivery.
The strongest input: work people have already delivered on comparable projects.
Interest confirmed within the last 12 months. This is the basis for every proposed move.
From December 2025, nine months before the planning date. Recheck before confirming any assignment.
Manager judgment on whether someone can be released. This changes with client workload.
Career conversations record willingness to consider a move. All 12 transfers still need a direct conversation, a manager-backed handover date, and a named owner for the work left behind.
36 candidates · 12 proposed transfersThe 43.2 person-weeks only exist if team leads remove an equivalent amount of routine work. Time protected on paper but not defended in practice returns to client delivery within weeks.
43.2 person-weeks of learning timeDelivery reviews date from December 2025. Where a manager rating conflicts with project evidence, keep the assignment conditional until a current check is done.
Annex A · input registerIt assumes searches close on time and learners progress as planned. Review the dependencies every two weeks and move the staffing date rather than leave a gap unreported.
Planned growth-team staffing over 90 daysChallenge these figures now, while they are still easy to change. Once assignments are announced, correcting a number costs far more.CEO takeaway
These three fictional profiles show what a proposed transfer actually requires: demonstrated experience, dated interest, a development need, and a release condition.
They are part of the 12 proposed transfers, not additional to them. None is an approved move. Each still needs a manager-backed handover date and a named person to take on the work being left behind.
The release condition is the part most plans leave unstated, and it is where transfers usually stall. Maya's client engagement has to pass to a named colleague. Luca's support rota needs a replacement. Amara has to document the most frequent support cases and train a colleague before she moves.
Identifying a suitable person is the straightforward part. Arranging the handover is the work. That is why these three show how the process runs, rather than forming a shortlist to approve.
Consultant → Client advisory · Consulting Services
Application engineer → AI solutions · Business Applications
Support specialist → Automation · Customer Success and Support
A good match becomes a workable move only when the person, the manager, and the receiving team agree the conditions.CEO takeaway
One owner, three milestones, and an explicit stop-or-scale decision at day 90, so the launch either earns its next budget or gets corrected early.
Everything starts with people and work already identified: 12 handovers, 18 protected learning slots, six searches, five cover tests. None of it depends on a reorganisation.
Day 90 is the decision point. Four client pilots, one per service, test whether the demand is real before the full revenue shift is funded. Releasing the 18 learners from their current teams is then confirmed on results rather than on expectation.
The measures shown here overlap and should not be added together. If the checks fail at day 90, extend supervision or move the staffing date and say so, rather than hold the original target and absorb the gap. The Helpwan modules below keep the evidence behind each check current, so the day-90 review is a decision on fact rather than a fresh study.
| Gap this diagnosis found | Helpwan module | What changes in practice | Measured at day 90 |
|---|---|---|---|
| The 60 positions and current capability sit in separate documents | Capability Map | One current view of what each position requires and who meets it today. | All 60 positions held in one place, updated as people move. |
| Performance evidence is nine months old and skill records are unconfirmed claims | Validation Hub | Managers confirm skills and delivery evidence against the positions that need them. | No confirmed assignment resting on evidence older than 90 days. |
| 24 of the 36 candidates are blocked by interest or release, and both change | Skill Match Finder / Mobility Map | Interest and release conditions are held per person and kept current. | The 24 reviewed each quarter without commissioning a new study. |
| Five business-critical roles have nobody trained to take over | Readiness & Succession Map | A named backup and a dated handover test for every critical role. | Five backups tested. No critical role left without cover. |
| The 90-day staffing plan is an estimate, and a three-month delay moves €1m | Capability Risk Analytics | Actual staffing is tracked against the plan, and slippage is flagged as it happens. | Slippage visible within two weeks instead of at day 90. |
Approve one focused launch. Protect time, agree handovers, hire the missing experience, and review proof before scaling.CEO takeaway
Start this week. The CEO names one owner. Team leads protect learning time and agree 12 handovers. Hiring starts for six specialists.