SaaS / Fintech · E&M Technologies client work · Under NDA
Bancassurance Platform
At E&M Technologies, I worked as Frontend Lead on a multi-tenant platform for a financial services provider selling insurance through several bank partnerships.
The problem
The provider was selling through banks that compete with each other. Each one needed its own branding, products and compliance rules, with certainty that its customers would never be visible to a rival.
The obvious route was a separate copy of the system for each bank. That multiplies the maintenance bill, and the copies eventually drift apart.
The value mapped
One codebase, with partner boundaries enforced in the architecture rather than remembered by whoever writes the next query. That makes onboarding a new bank a configuration exercise instead of a separate release, while keeping the record of decisions available when finance or compliance needs it.
| What was built | How it pays for itself |
|---|---|
| Multi-tenant RBAC with tenant-scoped JWTs | A new partner is configured rather than forked |
| Maker-checker approvals across seven entity types | Decisions have a defined review process before money or policies move |
| Action-level audit logging | Who did what, to which record, can be established without reconstructing events from application logs |
What this proves
I can translate a complex partner organisation into a permission model, lead frontend architecture around those requirements and build interfaces that reflect how the business actually operates.
Code under NDA; architecture described, not shown.
The next big build took the same discipline somewhere very different: enterprise-grade reliability demanded by an organisation with neither an enterprise budget nor an ops team.

