Hassan Iskandar · CIO · InsurTech · Mid-market · 140 employees
Wira's biggest AI-coding readiness gaps are evidence gaps: the supplied deal record documents a 140-person InsurTech engineering org and a CIO-led negotiation, but no editor/agent stack, no AI workflow practices, and no adoption or velocity baseline. The Etiqa partnership signed 5 days ago is a positive commercial signal, yet it does not prove Day 1 tooling readiness or Day 2 workflow applicability. The highest-leverage 90-day move is a two-cohort pilot (≤35 engineers each) that starts with a tooling/secrets inventory and shared Cursor/Claude Code rules, then instruments cycle time and escaped-bug counts before running a gated PR-review and agent-guardrail workflow on Day 2.
The deal record lists a 140-person engineering org but no Claude Code, Cursor, Copilot, MCP, IDE-rule, or secrets-handling detail; that absence means Day 1 must start with tooling discovery rather than assuming labs can run.
The supplied context contains no PR-review, testing, prompt-hygiene, or agent-guardrail practice, so Day 2 applicability is unproven for a 140-person org; the score sits at risk until a workflow baseline exists.
The contact is the CIO and the deal is in Negotiation at 80% probability with a recent Etiqa partnership, a positive leadership signal; no supplied note describes workflow-change tolerance or agent blast-radius policy, so it lands watch.
No cycle time, PRs/dev/week, time-to-merge, or deploy-frequency baseline appears in the deal record; with 140 engineers, the workshop cannot establish its throughput gap without pre-work instrumentation.
No daily/weekly AI usage, licence utilization, or sub-team distribution is supplied; the only headcount signal is 140 employees, so adoption cannot be assumed and the score is critical.
No defect rate, escaped-bug count, time-to-feature, or dev-satisfaction data is supplied; client health 72 and the Etiqa partnership are commercial signals, not output-quality evidence, so the score is at risk.