A photo of me, Alan
A photo of me, Alan
A photo of me, Alan

SalesLynk

Sales CRM SaaS Platform

SaaS

Cyber Security

CRM

The Problem:

Sales teams often struggle to find accurate and relevant information about potential prospects, companies, and markets efficiently. The process of researching and gathering insights can be time-consuming, leading to missed opportunities and decreased productivity. Existing tools and platforms lack intuitive user interfaces, making it challenging for sales professionals to quickly access the data they need to effectively engage with prospects and close deals. This results in frustration and hampers the overall effectiveness of the sales team.

The Solution:

Saleslynk is a web based platform designed to streamline the prospect research process and empower sales teams with actionable insights to drive conversions. With it's modern and minimal interface, as well as the segmented search functionality, the platform offers a much more user friendly, efficient experience than other options currently available to sales teams.

The Process:

1.

Discovery Workshop

In the discovery workshop with the client we focused on the problem they were trying to solve, who the intended users are, similar solutions that currently exist and the pain points that have been identified in them.

2.

User Interviews and Surveys

I interviewed a number of users who matched the demographic of the intended user group to find out more information about the issues they were having with their current ways of working. I identified two key areas that I felt would be important to focus on, issues with the search functionality/knowing what to search for, and old, dated interfaces that were cluttered and confusing.

3.

User Stories

From the information gathered in the interviews and surveys, I created a number of user stories which would provide a breakdown of the steps that the users would take to perform certain tasks in order to achieve an end goal. These user stories focused on searching for an individual, searching for a company, and searching for an industry. I also included stories for accessing search history, and admin stories for accessing user metrics.

4.

System Flow Diagrams

From the user stories I was able to map out a high level system flow diagram for standard users (sales team members) and admin users (sales managers).

5.

Use Cases and Acceptance Criteria

From the system flow diagrams I was able to drill down to a much more granular level and create individual use cases with acceptance criteria which would outline how the user would perform key tasks within the platform. Some examples are; account creation/login, selecting a search segment, searching and form validation, saving a search, viewing insight categories, accessing admin portal, and adding credits.

6.

Wireframes

I created a number of sets of wireframes which varied based on the permissions of the user. When creating the wireframes I referred to the use cases and acceptance criteria. I carried out additional research for the segmented search functionality and opted for a tabbed search section (which was also influenced by the way in which the search function would request information from a number of APIs as well as the internal database). I presented the wireframes in an interactive Adobe XD prototype.

7.

UI Designs and Prototype

Once the wireframes had been signed off I created the UI for the product. In-line with the SalesLynk branding (and as requested by the client) I created a dark themed interface with brightly coloured icons and components. I created an interactive prototype in Adobe XD which was used to present SalesLynk to potential investors, as well as being used in various usability testing exercises.

8.

Component Library and Design System

While creating the UI designs I was also compiling a component library which included buttons, form fields, form validation, text styles, colours, progress charts, toggles, and checkboxes etc. I later developed a high-level design system in Zeroheight with rules and guidance for each of the components, as well as a library of assets such as icons. The component library would reduce the developers reliance on a designer in later phases of the product.

Gallery

A photo of me, Alan

Website designed and developed by Alan in Framer