Client not named64 profiles proposed, 17 people on the team, 28 months of service.
Evidence from past work, not proof of the current product
This case applies to the engagement and period it describes. It does not prove outcomes of the microcourses, training, workshops, qualification or human evaluation that betaPlan offers today.
- Profiles proposed
- 64
- People who ever joined the team
- 17
- Peak team size in any one cycle
- 14
- Months of service
- 28
The engagement
Hiring in a market the client did not operate in.
The company had no legal entity and no recruitment channel in the country. We sourced and vetted candidates and proposed them by function, while the client ran its own interviews and decided. For everyone who signed, we took on 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.
The brief covered 6 functions. Programming and engineering was the largest, with 21 profiles proposed. The other 5 functions (data, regulatory affairs, business analysis with project management, and sales with support) account for 43 between them.
We proposed, the client decided. 46 of the 64 profiles have 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
6 functions
Decided by the client
18 still open
Signed on
On the team register
Started work
At least one active cycle
By function
Where the team was built.
Only the largest function is above our publication threshold on its own. The others are grouped, and a count of engaged people 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 had 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 working when this record closes, with fewer than 10 people; we do not publish the exact number. 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 country where you have no legal entity.
In this past engagement, we found and proposed the candidates; the client interviewed and decided; we administered the team for 28 months. It is not a promise that a similar team or offer exists today.