Convex
Website Migration

About

A redesign of the flagship website for Convex, a recently acquired ServiceTitan company.

During Convex’s website migration, I was in charge of maintaining the design system, directing developer hand-offs, and leading the front-end review process. Throughout the project, I collaborated with a design lead, developers, CMS admins, and QA analysts.

Timeline

August 2024 - February 2025

Tools

Figma / Jira

Overview

About

Convex is a leading sales and marketing platform that serves digital-first businesses within commercial services, committed to empowering team growth and acceleration. The company’s flagship website highlights the software’s features, showcases outcomes across industries, and connects relevant users to the product. For the migration, we redesigned and redeveloped all components and pages to give Convex a complete refresh. Some of these updated pages are featured below:

Convex screens

Project Scope

As the main goal of the Convex redesign and redevelopment, our team aimed to improve the overall website experience and increase leads. As designers, we played an instrumental role in our team’s success. To support the mission, some of our main design objectives were to…

Offer an experience that is intuitive and easy to navigate

Increase visual appeal and alignment with other brands

Simplify the process of getting in touch and booking a demo

Alignment

While we wanted the new website to have a strong identity, we also aimed to ensure that it would align with the flagship websites of ServiceTitan’s other brands — Aspire, FieldRoutes, and ServiceTitan. As the other websites had been tested by CRO and refined to successfully drive leads, we felt this approach would offer a strong starting point.

ServiceTitan brands – Convex, ServiceTitan, Aspire, and FieldRoutes

Process

Component Library

I supported the Design Lead with creating a comprehensive library of components, ensuring they were intuitive for designers and developers. He began by laying out a foundation of desktop components and page templates. I then added mobile versions of each component, created additions such as the header and footer, and reorganized the Figma file.

Layout with multiple components

Content Migration

We then established how we would translate current components into new layouts, which included bringing over existing copy and assets to complete polished mock-ups of the website’s pages. For a few select instances, such as the homepage and industry pages, we collaborated with agencies, stakeholders, and our in-house copywriter to refresh the structure and content.

Before and after screens

Interaction States

Another integral aspect of the design process was considering how the user would interact with the website’s components. I created multiple variants for foundational elements including buttons, input fields, and selection drop-downs. I also designed and laid out various states for the header navigation.

Navigation

Front-End Reviews

Referencing our newly created design system, the developers brought the website to life by translating our visual work to code. During this stage, I led front-end reviews to ensure the published components were accurate to the Figma file, noting factors such as typography, spacing, responsiveness, and interactivity. I also responded to dev inquiries, documented any design issues, and collaborated with other team members to polish the website.

Jira tickets

Key Learnings

Leadership

Before the Convex website migration, I hadn’t had the opportunity to lead a project of this scale. While collaborating with other team members, there were various instances in which I needed to make immediate calls on design decisions involving approaches, interactions, and visual improvements. I learned more about the website migration process, developed and shared trust with team members, and contributed to large-scale impact. As a Junior, it initially took a moment to solidify my role as the main point of contact. Eventually, my teammates trusted me to make decisions without involving the Design Lead. That felt like a big win!

Slack message that reads '@Hailey for taking the initiative in leading the design process for the final push, whose careful eye, devoted attention to detail, and clear communication uplifted the website in countless ways, and for probably having the most decisive impact of any non-developer on the successful launch of the website.'

Adaptability

The entire process was neither linear nor straightforward, and it allowed for significant learning opportunities along the way. At times, there were discrepancies between the initial Figma designs and how they turned out in development, but we still made it work! I constantly had to challenge what I knew, ask tons of questions, and seek support from my teammates. It all helped me better understand their roles, what should be prioritized, and their collaboration preferences – which all shaped my perspective as a designer.

Return to Homepage