Unyte Africa — Insurance, made operable

The brief

Unyte's policy operators were the bottleneck. The dashboards they used were slow, fragile, and missed the workflow they actually performed — which meant the company couldn't onboard new partners as fast as the market wanted.

The mandate: rebuild the operator surfaces, harden the platform, and make the testing story real enough that we could ship without flinching.

Approach

• A layered testing strategy. Unit tests with React Testing Library for primitives, integration tests for flows, and Cypress end-to-end for the critical paths (policy creation, claims, payments). The first month was almost entirely test infrastructure.
• Operator-first dashboards. I shadowed the policy team for a week, then redesigned the primary dashboards around their actual workflows — bulk actions, keyboard shortcuts, inline editing.
• Security as a habit. Vulnerability scans, structured input validation, and activity tracking became part of the deploy pipeline rather than an audit afterthought.

Outcome

• −60% production defects within the first quarter of the new testing story.
• Operator throughput rose as the redesigned dashboards eliminated the click-heavy flows that had bottlenecked the team.
• Cleaner security posture with regular vulnerability scans and an activity log that the ops team actually used.