Overview
Introduced Low Code / No Code (LCNC) capabilities into an insurance SaaS platform by integrating the Form.io Angular library. Insurance application forms are massive, with hundreds of fields and complex business logic. By shifting from hard-coded UI to JSON-configured dynamic forms, implementation time dropped from 5 weeks to 1 week per client, making the system truly scalable.
The Problem
During client implementations on the BPA insurance platform, even a single field change required a full development cycle: UI changes, API modifications, QA testing, and deployment. This took approximately 5 weeks per change cycle. Insurance application forms are extensive by nature, capturing detailed information with complex business logic. The process was not scalable for future growth.
My Role
As Product Manager, I identified the bottleneck and drove the LCNC transformation:
- Identified implementation process bottlenecks affecting client delivery
- Researched third-party solutions: form builders, design system standards
- Selected Form.io Angular library for dynamic form building
- Defined the approach: UI field details as JSON, passed as API parameters
- Coordinated with tech team to modify the system architecture
- Validated the LCNC approach with real client implementations
Stakeholders
Internal
- Tech Team (Angular + API)
- Design Team
- Business / Client Delivery
- QA Team
External
- Form.io (library provider)
- Insurance Clients (US)
The LCNC Shift
Key Capabilities Delivered
Dynamic Form Builder
Form.io Angular library renders complex insurance forms dynamically from JSON configuration
JSON-Driven Configuration
UI field details defined in JSON and passed as API parameters, eliminating separate UI and backend changes
Configuration at Product Setup
New forms and field changes configured during product setup, no deployment cycle required
Scalable for Any Insurance Line
New clients and insurance lines onboarded through configuration, not custom development
Results
Key Learnings
- LCNC is a scalability strategy, not just a convenience: Without this shift, every new insurance client would have repeated the same 5-week cycle. LCNC turned a linear process into a configurable one.
- JSON as the interface between business and tech: Defining UI fields as JSON parameters within the API eliminated the need for separate UI and backend changes, collapsing two workstreams into one.
- Identify the bottleneck before optimizing: The real problem was not slow development but the coupling between UI, API, and QA. Decoupling through configuration solved all three.