Case study · Client not named
64 profiles proposed, 17 people on the team, 28 months of delivery.
The company had no entity and no hiring pipeline in the country. We sourced and vetted candidates, proposed them by function, and the client ran its own interviews and decided. For everyone who signed we carried the onboarding and the day to day administration. The first fortnightly cycle closed on 4 April 2024 and the last one in this record on 31 July 2026, 58 cycles later.
Historical evidence, not current-product proof
This case applies to the named engagement and period. It does not prove outcomes from betaPlan current microcourses, training, workshops, qualification or human-evaluation work.
64
Profiles proposed
17
People who ever joined the team
14
Peak team size, any one period
28
Months of delivery
The engagement
Hiring in a market the client did not operate in.
The brief covered 6 functions. Programming and engineering was the largest, with 21 profiles proposed. The other 5 functions, across data, regulatory, business analysis with project management, and sales with support, account for 43 between them.
We proposed, the client decided. 46 of the 64 profiles carry a decision on file and 18 were still open when the record closes. Of those decided, 17 joined the team and 29 did not. No candidate is named here and no scoring sheet is published, because the record for this client is a folder of CVs filed by function and status and a team register, not an assessment file.
The pipeline
From 64 proposed profiles to a team that stayed.
Every step is a count of records, not of interviews. The client ran its own interviews and kept its own notes.
Proposed
64 (100%)
6 functions
Decided by the client
46 (72%)
18 still open
Signed on
19 (30%)
On the team register
Started work
17 (27%)
At least one active cycle
By function
Where the team was built.
Only the largest function clears our disclosure floor on its own. The rest are grouped, and an engaged count under 10 is withheld rather than rounded.
| Function | Proposed | Engaged |
|---|---|---|
| Programming and engineering | 21 | 13 |
| Five other functions | 43 | withheld |
The outcome
The team held for two years.
The team register runs from 4 April 2024 to 31 July 2026, 58 fortnightly cycles. The team reached 10 people in the seventh week and peaked at 14 in August 2024. 33 of the 58 cycles carried 10 or more people. Of the 17 who started, 12 passed 6 months and 11 passed 12 months, with a median engagement of 19 months.
The team was still running when this record closes, at a size below 10, which we withhold. What the record shows is a team that was built in a market the client did not know, that stayed, and that was still working two years later.
A team in a market where you have no entity.
In this historical engagement, we sourced and proposed; the client interviewed and decided; we administered the resulting team for 28 months. It is not a promise that an equivalent current team or supply exists.