Here is everything this site stores, and why. You can change your mind any time with the cookie button in the corner.

No advertising and no tracking across other sites.

Menu

SK

From Pipeliner to Coevera

In June 2026 Pipeliner CRM relaunched as Coevera. I led the new colour theme inside the application: one system for the whole CRM that feels like Coevera, yet still like the CRM its customers know.

A Coevera reports dashboard after the rebrand, with the Power Panel open

It starts with a conversation

Before I design anything, we talk. Like a doctor, I ask about the symptoms until I find the cause: what in the process is not working, for whom, and since when. When we find the root of the problem together, we create value for everyone involved before the work even begins.

The brief

It started with a request: match the colours across the whole Pipeliner CRM and create one unified colour theme for the new Coevera.

The shift could not be too strong. Customers should still feel at home in their CRM, while the application and the administration finally look like one product.

What I did

  1. Presented a completely redesigned front end. I led the presentation of the new look before a single ticket existed.

  2. Built a Figma system with variables for every state, so each colour has one source and every hover, focus or disabled state follows it.

  3. Unified the application and the administration under one theme.

  4. Built it on my own branch. Our front-end developers saw the changes running in the application itself, not in a static handoff file.

  5. Reviewed it in over 200 tickets. Once the developers took the branch and matched it to their environment, I checked every screen against the system.

How it came together

Variables first, so a colour changes in one place. Then my branch, where the theme ran in the real application. The developers took it over, matched it to their environment, and the review tickets closed the gaps. Because the system was robust, the whole shift took about three months.

The added value

The rebrand never stopped the release cycle. New features kept shipping while the theme moved in underneath them.

The Product Owner and the CRM's biggest customers previewed the new look right in the pre-production app, with real data and real workflows, instead of clicking through a static prototype.

Across the whole CRM

The same variables and components, from the account detail to reports. Swipe or use the arrows.

Components, matched

Every widget was rebuilt from the new variables, so it carries the brand without being redrawn screen by screen. The quote process widget is one of them.

The quote process widget in the Coevera design: steps, progress and the tasks for the current step

The mobile app

The CRM mobile apps for iOS and Android, and their store listings, moved to the new brand as well.

App Store image: the Coevera pipeline on an iPhone
App Store image: Coevera CRM mobile app, opportunities and Voyager AI
Google Play image: the Coevera Android app showing the sales pipeline

The result

Coevera launched with one colour theme across every screen of the application and the administration, after about three months and more than 200 review tickets, without pausing a single release.

What it taught me

A rebrand is a design system project. When the variables are right and people can see them in the real product early, a new name reaches every screen without stopping the work around it.

Next case study

The missing piece of the sales cycle

Read it