2025
Cumulus Dealer
Cumulus Dealer — a component-driven quoting and policy platform for ERGO Hestia's car-dealer network, scaling the same design system across Sales, Service, and Administration modules of a complex motor-insurance product.
Product Design
Design System
Know More
Cumulus Dealer scales ERGO Hestia's design system across a complex, multi-step motor-insurance sales tool.
From Scattered Dealer Tools to One Componentized Platform: Scaling the Design System into Cumulus Dealer
Cumulus Dealer is the tool car-dealership staff use to search vehicles, calculate motor-insurance premiums, apply discounts and add-ons, issue policies, and manage renewals — all in one dark-themed, data-dense interface. Rather than designing this end-to-end flow as a one-off product, I built it directly on the shared component system already governing ERGO Hestia's platforms: the same three-pillar structure — Obsługa (Service), Sprzedaż (Sales), and Administracja (Administration) — the same colour tokens, and the same form and data patterns. A dedicated in-product style-guide screen shipped alongside the tool, giving the delivery team and partner agencies a live, always-current reference for every component in use.
Problem
Motor-insurance quoting for car dealers is a long, data-heavy journey: looking up a vehicle, running a multi-step premium calculation, layering discounts and optional add-ons, generating documents, and later handling renewals — often for the same client and vehicle multiple times. Built without a shared system, a flow like this tends to accumulate one-off modals, inconsistent tables, and mismatched buttons and tags, which slows down both design QA and frontend implementation, and makes the tool harder for dealership staff to learn. The challenge was to keep a genuinely complex, multi-step process feeling coherent from the first vehicle search to the final signed policy.
Dealer-network staff needed a single tool to search vehicles, calculate premiums, apply discounts and add-ons, issue policies, and manage renewals — without every screen reinventing its own UI.
Solution
Instead of styling Cumulus Dealer as a standalone product, I mapped every screen back to the existing component library and extended it only where the motor-insurance flow genuinely needed something new — such as package-comparison price cards and vehicle-lookup modals. The in-product style-guide screen catalogued these building blocks — package cards, button variants, colour tokens, selects, and data-table headers — directly inside the product, so anyone extending the tool later had a single, current reference rather than a static document that could drift out of sync.
Obsługa (Service) → policy search, applications, documents, offers, and reports — the day-to-day case-handling screens.
Sprzedaż (Sales) → policy issuance and vehicle-document scanning, built around the same step-based calculation pattern.
Administracja (Administration) → tariff management, code-dictionary edits, user administration, SSO, and banner management for back-office staff.
Shared components → price/package cards, button and tag variants, colour tokens, form fields, and sortable data grids reused across all three modules.
Applied the shared design system's tokens and components — price cards, tags, buttons, forms, and data grids — to every step of the quoting flow, backed by a live in-product style guide.
Profit
Reusing one design system across Sales, Service, and Administration kept a complex, multi-step insurance product coherent, faster to extend, and easier to maintain.
Efficiency → reusing existing price cards, buttons, tags, and tables cut design and implementation time for new steps in the quoting flow.
Consistency → shared colour tokens and typography kept dozens of screens — from vehicle search to renewals — visually and behaviourally predictable.
Scalability → the same system flexed from a simple dealer quote to complex back-office configuration without breaking its visual language.
Adoption → the in-product style guide gave the delivery team and partner agencies a live reference, lowering onboarding time for new contributors.
3
Shared modules
Service, Sales, and Administration — all built from the same component system rather than three separate interfaces.
30
+
Screens & flows
Vehicle search, multi-step calculation, discounts and add-ons, policy management, and renewals — all assembled from reusable components.
Launch
Here are the core flows built entirely on the shared component system, spanning the dealer's day-to-day quoting work.
Vehicle & policy search
Look up vehicles via Eurotax data and search, filter, and manage existing policies from one grid.
Multi-step premium calculation
A guided, step-based flow for configuring coverage, reused directly from the platform's step-pattern components.
Discounts & add-ons
Modal-based configuration for pricing adjustments and optional coverage, built on shared modal and form patterns.
Policy issuance & renewals
Document generation and renewal handling, sharing the same table and form components as the search and calculation flows.
Sales path
Desktop
Full insurance sales path
Protoype
Team & Tools
Team composition and design tools utilized for this project.
Collaborated across three project teams, managing designers and working closely with developers, supported by a well-configured toolkit.
My team
I worked as UI/UX Designer on the dealer-network workstream, alongside a Product Owner, Business Analyst, and Frontend/Backend Developers delivering Cumulus Dealer for ERGO Hestia. I was responsible for mapping the product's motor-insurance flows onto the existing design system, extending it only where the domain required new patterns, and maintaining the in-product style guide as the team's day-to-day reference during implementation.
Tools I used
Sketch – screen design and component reuse from the shared library.
InVision – clickable prototypes for stakeholder and dealer-network review.
Zeplin – specs and assets for frontend implementation.
Jira – backlog and cross-team issue tracking.
Confluence – flow documentation and style-guide upkeep.
2025
Cumulus Dealer
Cumulus Dealer — a component-driven quoting and policy platform for ERGO Hestia's car-dealer network, scaling the same design system across Sales, Service, and Administration modules of a complex motor-insurance product.
Product Design
Design System
Know More
Cumulus Dealer scales ERGO Hestia's design system across a complex, multi-step motor-insurance sales tool.
From Scattered Dealer Tools to One Componentized Platform: Scaling the Design System into Cumulus Dealer
Cumulus Dealer is the tool car-dealership staff use to search vehicles, calculate motor-insurance premiums, apply discounts and add-ons, issue policies, and manage renewals — all in one dark-themed, data-dense interface. Rather than designing this end-to-end flow as a one-off product, I built it directly on the shared component system already governing ERGO Hestia's platforms: the same three-pillar structure — Obsługa (Service), Sprzedaż (Sales), and Administracja (Administration) — the same colour tokens, and the same form and data patterns. A dedicated in-product style-guide screen shipped alongside the tool, giving the delivery team and partner agencies a live, always-current reference for every component in use.
Problem
Motor-insurance quoting for car dealers is a long, data-heavy journey: looking up a vehicle, running a multi-step premium calculation, layering discounts and optional add-ons, generating documents, and later handling renewals — often for the same client and vehicle multiple times. Built without a shared system, a flow like this tends to accumulate one-off modals, inconsistent tables, and mismatched buttons and tags, which slows down both design QA and frontend implementation, and makes the tool harder for dealership staff to learn. The challenge was to keep a genuinely complex, multi-step process feeling coherent from the first vehicle search to the final signed policy.
Dealer-network staff needed a single tool to search vehicles, calculate premiums, apply discounts and add-ons, issue policies, and manage renewals — without every screen reinventing its own UI.
Solution
Instead of styling Cumulus Dealer as a standalone product, I mapped every screen back to the existing component library and extended it only where the motor-insurance flow genuinely needed something new — such as package-comparison price cards and vehicle-lookup modals. The in-product style-guide screen catalogued these building blocks — package cards, button variants, colour tokens, selects, and data-table headers — directly inside the product, so anyone extending the tool later had a single, current reference rather than a static document that could drift out of sync.
Obsługa (Service) → policy search, applications, documents, offers, and reports — the day-to-day case-handling screens.
Sprzedaż (Sales) → policy issuance and vehicle-document scanning, built around the same step-based calculation pattern.
Administracja (Administration) → tariff management, code-dictionary edits, user administration, SSO, and banner management for back-office staff.
Shared components → price/package cards, button and tag variants, colour tokens, form fields, and sortable data grids reused across all three modules.
Applied the shared design system's tokens and components — price cards, tags, buttons, forms, and data grids — to every step of the quoting flow, backed by a live in-product style guide.
Profit
Reusing one design system across Sales, Service, and Administration kept a complex, multi-step insurance product coherent, faster to extend, and easier to maintain.
Efficiency → reusing existing price cards, buttons, tags, and tables cut design and implementation time for new steps in the quoting flow.
Consistency → shared colour tokens and typography kept dozens of screens — from vehicle search to renewals — visually and behaviourally predictable.
Scalability → the same system flexed from a simple dealer quote to complex back-office configuration without breaking its visual language.
Adoption → the in-product style guide gave the delivery team and partner agencies a live reference, lowering onboarding time for new contributors.
3
Shared modules
Service, Sales, and Administration — all built from the same component system rather than three separate interfaces.
30
+
Screens & flows
Vehicle search, multi-step calculation, discounts and add-ons, policy management, and renewals — all assembled from reusable components.
Launch
Here are the core flows built entirely on the shared component system, spanning the dealer's day-to-day quoting work.
Vehicle & policy search
Look up vehicles via Eurotax data and search, filter, and manage existing policies from one grid.
Multi-step premium calculation
A guided, step-based flow for configuring coverage, reused directly from the platform's step-pattern components.
Discounts & add-ons
Modal-based configuration for pricing adjustments and optional coverage, built on shared modal and form patterns.
Policy issuance & renewals
Document generation and renewal handling, sharing the same table and form components as the search and calculation flows.
Sales path
Desktop
Full insurance sales path
Protoype
Team & Tools
Team composition and design tools utilized for this project.
Collaborated across three project teams, managing designers and working closely with developers, supported by a well-configured toolkit.
My team
I worked as UI/UX Designer on the dealer-network workstream, alongside a Product Owner, Business Analyst, and Frontend/Backend Developers delivering Cumulus Dealer for ERGO Hestia. I was responsible for mapping the product's motor-insurance flows onto the existing design system, extending it only where the domain required new patterns, and maintaining the in-product style guide as the team's day-to-day reference during implementation.
Tools I used
Sketch – screen design and component reuse from the shared library.
InVision – clickable prototypes for stakeholder and dealer-network review.
Zeplin – specs and assets for frontend implementation.
Jira – backlog and cross-team issue tracking.
Confluence – flow documentation and style-guide upkeep.
2025
Cumulus Dealer
Cumulus Dealer — a component-driven quoting and policy platform for ERGO Hestia's car-dealer network, scaling the same design system across Sales, Service, and Administration modules of a complex motor-insurance product.
Product Design
Design System
Know More
Cumulus Dealer scales ERGO Hestia's design system across a complex, multi-step motor-insurance sales tool.
From Scattered Dealer Tools to One Componentized Platform: Scaling the Design System into Cumulus Dealer
Cumulus Dealer is the tool car-dealership staff use to search vehicles, calculate motor-insurance premiums, apply discounts and add-ons, issue policies, and manage renewals — all in one dark-themed, data-dense interface. Rather than designing this end-to-end flow as a one-off product, I built it directly on the shared component system already governing ERGO Hestia's platforms: the same three-pillar structure — Obsługa (Service), Sprzedaż (Sales), and Administracja (Administration) — the same colour tokens, and the same form and data patterns. A dedicated in-product style-guide screen shipped alongside the tool, giving the delivery team and partner agencies a live, always-current reference for every component in use.
Problem
Motor-insurance quoting for car dealers is a long, data-heavy journey: looking up a vehicle, running a multi-step premium calculation, layering discounts and optional add-ons, generating documents, and later handling renewals — often for the same client and vehicle multiple times. Built without a shared system, a flow like this tends to accumulate one-off modals, inconsistent tables, and mismatched buttons and tags, which slows down both design QA and frontend implementation, and makes the tool harder for dealership staff to learn. The challenge was to keep a genuinely complex, multi-step process feeling coherent from the first vehicle search to the final signed policy.
Dealer-network staff needed a single tool to search vehicles, calculate premiums, apply discounts and add-ons, issue policies, and manage renewals — without every screen reinventing its own UI.
Solution
Instead of styling Cumulus Dealer as a standalone product, I mapped every screen back to the existing component library and extended it only where the motor-insurance flow genuinely needed something new — such as package-comparison price cards and vehicle-lookup modals. The in-product style-guide screen catalogued these building blocks — package cards, button variants, colour tokens, selects, and data-table headers — directly inside the product, so anyone extending the tool later had a single, current reference rather than a static document that could drift out of sync.
Obsługa (Service) → policy search, applications, documents, offers, and reports — the day-to-day case-handling screens.
Sprzedaż (Sales) → policy issuance and vehicle-document scanning, built around the same step-based calculation pattern.
Administracja (Administration) → tariff management, code-dictionary edits, user administration, SSO, and banner management for back-office staff.
Shared components → price/package cards, button and tag variants, colour tokens, form fields, and sortable data grids reused across all three modules.
Applied the shared design system's tokens and components — price cards, tags, buttons, forms, and data grids — to every step of the quoting flow, backed by a live in-product style guide.
Profit
Reusing one design system across Sales, Service, and Administration kept a complex, multi-step insurance product coherent, faster to extend, and easier to maintain.
Efficiency → reusing existing price cards, buttons, tags, and tables cut design and implementation time for new steps in the quoting flow.
Consistency → shared colour tokens and typography kept dozens of screens — from vehicle search to renewals — visually and behaviourally predictable.
Scalability → the same system flexed from a simple dealer quote to complex back-office configuration without breaking its visual language.
Adoption → the in-product style guide gave the delivery team and partner agencies a live reference, lowering onboarding time for new contributors.
3
Shared modules
Service, Sales, and Administration — all built from the same component system rather than three separate interfaces.
30
+
Screens & flows
Vehicle search, multi-step calculation, discounts and add-ons, policy management, and renewals — all assembled from reusable components.
Launch
Here are the core flows built entirely on the shared component system, spanning the dealer's day-to-day quoting work.
Vehicle & policy search
Look up vehicles via Eurotax data and search, filter, and manage existing policies from one grid.
Multi-step premium calculation
A guided, step-based flow for configuring coverage, reused directly from the platform's step-pattern components.
Discounts & add-ons
Modal-based configuration for pricing adjustments and optional coverage, built on shared modal and form patterns.
Policy issuance & renewals
Document generation and renewal handling, sharing the same table and form components as the search and calculation flows.
Sales path
Desktop
Full insurance sales path
Protoype
Team & Tools
Team composition and design tools utilized for this project.
Collaborated across three project teams, managing designers and working closely with developers, supported by a well-configured toolkit.
My team
I worked as UI/UX Designer on the dealer-network workstream, alongside a Product Owner, Business Analyst, and Frontend/Backend Developers delivering Cumulus Dealer for ERGO Hestia. I was responsible for mapping the product's motor-insurance flows onto the existing design system, extending it only where the domain required new patterns, and maintaining the in-product style guide as the team's day-to-day reference during implementation.
Tools I used
Sketch – screen design and component reuse from the shared library.
InVision – clickable prototypes for stakeholder and dealer-network review.
Zeplin – specs and assets for frontend implementation.
Jira – backlog and cross-team issue tracking.
Confluence – flow documentation and style-guide upkeep.