Designing an InsurTech & FinTech SaaS platform
- Location: Hong Kong
- Year: 2020-2023
Under NDA — Limited Preview
This case study is part of work completed under a Non-Disclosure Agreement (NDA). Due to confidentiality, only general context and challenges are shared here.
If you’d like to learn more about the project or discuss the design approach in detail, feel free to reach out.
Context
- Company: Coherent.global
- Position:
- Dec 2020 to Apr 2021: Senior UX-UI Designer
- May 2020 to Oct 2023: Product Design Lead
- August 2023 to Oct 2023: Design System Lead
I joined Coherent in September 2020 and began working on their flagship product, Spark, in December of the same year. Within five months, I transitioned to the role of Lead Product Designer, overseeing a team of two other designers.
Spark, the company’s hero product
Spark is Coherent’s flagship SaaS product—a cloud-based logic engine that transforms complex Excel models into ready-to-use APIs. It empowers businesses to unlock the value of their spreadsheet-based IP with no-code automation, testing tools, version control, and audit trails, all within a secure, cloud-native environment.
For a more in-depth overview of the product, you can watch this video and this additional walkthrough.
Challenges
Highly technical product with steep domain requirements
Spark required deep understanding of the insurance industry, particularly how actuaries work with complex Excel models. In addition to insurance workflows, designing effectively meant grasping spreadsheet logic, Excel-specific behavior, and API architecture.
No direct access to end users for research
The Sales team tightly controlled client relationships, limiting the Design team’s ability to engage with users. This made it difficult to validate assumptions or gather first-hand feedback during early stages of the design process.
Design assets not structured for scale
The existing design files lacked structure and were hard to understand/navigate for anyone outside the design team. They weren’t set up with reusable components. Even small updates could become time-consuming, as changes had to be manually applied across multiple screens and Figma pages.