Company / Segment
Exact Sales
Pré-sales Machine
Product Type
Web App
B2B, SaaS
My Role
Sr. Ux Designer
Deliverables
Prototype (Axure)Exact-Sales is a fast-growing start-up with few competitors. It has developed and maintains a software called Spotter. The software makes the qualification of leads through algorithms (artificial intelligence). Spotter then features a sales funnel that helps the pre-seller decide which contacts he should work with/prioritize.
In 2017, the company was losing customers to competitors who offered similar products but with an extra tool: They are sending scheduled emails. In addition, investors noticing this market movement made us a requirement as a condition for a new investment round. We need to find a way for our product to send emails by triggers.
If we failed, our company would fall behind competitors who already had this capability, or worse, we could lose the investment. The pressure was enormous, so I felt both excited and anxious. My challenge was to design a tool for creating and sending emails, to be delivered to developers within two months
As a Senior UX designer, I worked for two developer teams, conducting research and designing interfaces.
Strategy and Research
With a short time to research in-depth, I decided to do it online to analyze competitors and prepare myself for running interviews. Soon after, I interviewed five clients/partners and the company's board of directors.
The interviews were more like conversations, but I aimed to answer the following questions:
We figured out that the tool was limited to compare just three suppliers, and essential information for decision-making was challenging to find.
Contrary to what I imagined, specialized tools for email campaigns are expensive and unfeasible for small and medium-sized companies - our target. In general, our customers need a simple tool, which alleviates the workload and frees up the pre-salesperson for other activities considered more critical.
After gathering a lot of information, it was time to shape the project scope.
Why are these tools expensive? What's the minimum required to create a satisfying email campaign? These were essential and decisive questions in our project. From these questions, we decided to make an MVP with limited emails, however, at no extra cost to the customer. Of course, if the tool had good acceptance, we would lift the limit and charge an additional amount in new versions.
As a design decision, I defined the product would have the minimum necessary for an email campaign: Contact List + Template and a campaign creation mechanism that combined the mentioned items with the Time variable (schedule).
"When I have a lot of contacts that are not 'ready' yet,
I want to 'nourish' them with useful information via email,
So I can get in touch as soon as the spotter points out a good score."
_Dashboard
_New Campaign
Design and Solution
With enough information in hand, the conceptual basis and the team's agreement, I started to design the interface.
Below we can see the visual style guide created by a third-party service. The design team created components giving rise to the design system. The Design System was created by the team, in weekly meetings
It is very important to make this very clear. At the same time, other projects were taking place and being conducted by other designers. Each project contributed new elements, components and behaviours to the design library we built TOGETHER. Therefore, the pieces shown here served for several projects and were made by me but discussed with the team and often improved by colleagues. And that's how things go when you have a good team.
I put it here for you to take a look
I created those interaction on figma in order to develop my skills on prototyping.
_Search
_Tab Nav
_Tooltip
_Stepper
We built high-fidelity prototypes on Axure with good interaction levels. This way, we could use it in costumers meetings presentations. Plus, we could not wait for the entire development cycle to show customers how it would work.
Importantly, I faced resistance from colleagues when presenting a simple proposal. They expected something more complete like the competitors. But if there's something I've learned over time, it's that new products should start simple and give the user a chance to learn and follow the evolution of the product in its complexity.
The directors supported, and the project continued with the promise of evolutions. But, first, we would launch a Beta test.
Learnings
We learned that it is necessary to do a lean process and fast tests in the "beta" version in certain situations to bring insights. However, it is a risk that must be well analyzed and not used as a standard procedure.