Watch the 45-minute recording and download the org-design template.
Key takeaways
- The ideal first-year platform team is 5–7 people
- Split between infra, MLOps, and enablement — not all engineers
- The team lead title matters: "AI Platform Lead" outperforms "AI Manager" in talent attraction
- Embed one platform engineer in each pilot business unit rather than centralising all execution
- Quarterly rechartering prevents the CoE from becoming a bottleneck instead of an enabler
Why platform team design fails
Most mid-market AI programmes under-staff the platform function and over-staff the use-case development function. The logic seems sound: "We need people building the actual AI features." The outcome is predictable: every use-case team reinvents the same evaluation harness, the same prompt versioning approach, and the same deployment pipeline. Six months in, there are six divergent approaches, none of them production-grade.
The platform team's job is to make the next use-case deploy in half the time of the previous one. That compounds. A team that halves deployment time every three projects will outproduce a team of individual contributors within one year.
The five roles you need in year one
1. AI Platform Lead — owns the technical roadmap, vendor relationships, and CoE governance. Should have production ML engineering experience, not just data science. The anti-pattern is hiring a research scientist into this role.
2. MLOps / DevEx Engineer (×2) — owns the model registry, CI/CD for AI pipelines, evaluation harness, and cost dashboards. These two roles are the force-multiplier for every use-case team. If you can only hire two platform engineers in year one, hire these.
3. AI Infrastructure Specialist — owns the compute layer (managed inference endpoints, vector database sizing, caching strategy) and the data pipeline into the AI layer. At mid-market scale this role often also covers cloud architecture.
4. AI Enablement Lead — owns training, documentation, internal community of practice, and change management. This role is consistently under-hired and over-demanded. When business units feel unsupported, adoption stalls regardless of how good the technology is.
5. Applied AI Engineer (embedded, rotational) — six-month rotations into business units to co-build first use cases, then return to the platform team with domain knowledge. This is the fastest way to build the institutional knowledge that makes the second and third projects faster than the first.
Hiring sequence
Hire in this order:
- AI Platform Lead (week 1 — this person helps hire everyone else)
- MLOps Engineers (weeks 4–8 — needed before any pilot reaches scale)
- AI Infrastructure Specialist (weeks 6–10 — needed for foundation work)
- Enablement Lead (weeks 8–12 — needed before first business unit expansion)
- Applied AI Engineers (months 4–6 — hired after the pilot process is defined)
The most expensive mistake is hiring Applied AI Engineers before the platform is stable. They will spend 80% of their time on infrastructure and 20% on the use cases they were hired for.
Compensation benchmarks (APAC mid-market, 2026)
| Role | HK/SG annual | CN annual | JP annual |
|---|---|---|---|
| AI Platform Lead | HKD 1.4–1.8M / SGD 180–230K | CNY 900K–1.2M | JPY 18–24M |
| MLOps Engineer | HKD 900K–1.2M / SGD 120–160K | CNY 600–900K | JPY 12–18M |
| AI Infrastructure Specialist | HKD 800K–1.1M / SGD 110–150K | CNY 550–800K | JPY 11–16M |
| Enablement Lead | HKD 700K–950K / SGD 95–130K | CNY 450–700K | JPY 9–14M |
These ranges reflect the Q1 2026 market. AI talent compensation has increased 18–22% year-over-year since 2024, and the trend is likely to continue through 2027.
The quarterly recharter ritual
Every 90 days the platform team should answer three questions formally:
- What did we ship, and what was the measured business impact?
- Which use-case teams are blocked by platform limitations versus own-team capability gaps?
- What is the one capability investment that would most accelerate the next quarter?
Teams that skip this ritual drift toward infra-for-its-own-sake. Teams that do it rigorously maintain tight alignment between platform investment and business outcome.
Download the org-design template
The template linked in the recording includes: role description cards for all five positions, a 90-day onboarding plan for the AI Platform Lead, a competency matrix for AI hiring interviews, and a quarterly recharter agenda. AIMenta clients can access the editable version through the client portal.
Where this applies
How AIMenta turns these ideas into engagements — explore the relevant service lines, industries, and markets.
Beyond this insight
Cross-reference our practice depth.
If this article matches your stage of thinking, the underlying capabilities ship across all six pillars, ten verticals, and nine Asian markets.