Filling out a contact form to get a product demo is so last decade. What you get is a couple of auto-generated emails and, if you’re lucky, someone reaches out — but only after days have passed.
What a drag, huh? Not for Chili Piper, who turned it into a profitable business. The recipe? Qualify the leads, connect them with the right salespeople, and schedule meetings within a click.
The next step for the company was to scale its secret sauce into a productivity suite for revenue teams.
I designed a few MVPs, all while creating and maintaining a design system for a team of designers, developers, and managers.
I started by introducing a free version and a set of new features to Chili Piper's beloved Concierge.
It replaces a call-to-action button with an interactive widget that shows different contact options based on who's visiting the website.
First impression counts. And it’s best when short and sweet. So the onboarding has just enough steps that it doesn’t feel like a chore.
When used to their full potential, lead qualification criteria can get tangled. To show what's happening behind the scenes, I designed a visual rule builder.
Don't repeat yourself
Never retype the same meeting details. With Chili Piper, you can save them as a template to automate your scheduling process without losing the personal touch.
While the goal is to instantly connect with the most valuable prospects, that's not always feasible. Nobody's picking the phone late at night or when in the middle of another pitch.
Meetings play a huge role in salespeople's daily routine. Yet, their calendar feels disconnected from their workflow. Let's change that.
Clock in, clock out
Write that down!
When the conversation is flowing, it's hard to capture all the relevant details. It shouldn't be with Meeting Notes, though.
Set an agenda for each meeting type and get your sales team on the same page. And if you wanna make sure you got everything right, send the meeting recap with just a click.
Ready for business trips
Chili Piper also helps salespeople at in-person conferences. It gives the managers a bird's-eye view of the team's schedule while they have access to the meeting details on-the-go.
To talk about the design system, let's go back to the point where none of the products were "done".
It's been a few weeks since we (I and two other designers) started working with Chili Piper. After producing a ton of diagrams and wireframes, we were excited to move on to the high fidelity phase.
But with that advancement, a new challenge arose: how to design the whole product suite in a consistent design language, with each of us focusing on separate parts?
We thought that a primitive library where everyone could dump the tokens and components they were using would be enough. It seemed intuitive, but got messy after a few days. (Surprise, I know.)
To embrace the chaos, we decided that it'll be best if just one of us was responsible for maintaining the design system. And that someone was me.
Shipping the MVPs was still my priority, and I was working on that full-time — except of Wednesdays. On Wednesdays, I was focused solely on the system.
I organized the list of ideas, improvements, and bugs into a kanban board in Notion, so that everyone could track my progress.
(I'm such a sucker for kanban boards.)
I also set up a Slack channel where I shared updates about the new changes to the system.
Inside the design team, we met every Friday to discuss what we liked and disliked about working with the system that week. And if we had enough time on our hands, we conducted peer-to-peer reviews of our source files.
The developers mirrored our components, tokens, and patterns in a Storybook library. That let them write front-end code in no time, and we could launch the suite into beta on schedule.
Even more benefits of the design system became clear once more stakeholders joined the process. In the old way, they had to wait for the designers to visualize their ideas.
Now, they could use the library to outline their concepts without reinventing the design language.
Shout-out to the people who also worked on this project.