- Role
- Product design
- Platform
- Web, responsive
- Year
- 2026

Case study 01
Krool
A place for conversations, and the work that follows.
I explored how a sales inbox and a CRM could work as one product.
- Role
- Product design
- Platform
- Web, responsive
- Year
- 2026

Case study 01
Krool
A place for conversations, and the work that follows.
I explored how a sales inbox and a CRM could work as one product.
02Listen The question
What happens after a message comes in?
Krool began with a question: how could incoming conversations sit closer to the work they create?
A message might lead to a reply, a follow-up, or a change in a lead’s progress. I wanted to explore those moments as parts of the same product.
AssumptionAn early assumption, not yet tested with sales teams.
02 Listen The question
What happens after a message comes in?
Krool began with a question: how could incoming conversations sit closer to the work they create?
A message might lead to a reply, a follow-up, or a change in a lead’s progress. I wanted to explore those moments as parts of the same product.
An early assumption, not yet tested with sales teams.
03Brainstorm Shaping the idea
Giving each part a place.
The three moments became three screens: Inbox for replies, Dashboard for follow-ups, and Pipeline for lead progress. Each one started as a sketch.


The day’s activity
01 / 03
Dashboard, 1 of 3
03 Brainstorm
Giving each part a place.
The three moments became three screens: Inbox for replies, Dashboard for follow-ups, and Pipeline for lead progress. Each one started as a sketch.
01Dashboard


The day’s activity
01 / 03
04Decide
Keeping the context close.
One design decision, written as a record: the question behind it, what I chose, what it cost, and what is still left to test.
Decision record
Inbox
- Question
- How could a lead’s details stay close to the reply?
- Decision
- I brought the conversation list, the open conversation, and contact details into one view.
- Trade-off
- It also put more information on one screen.
- To test
- Whether the screen stays easy to read.

04 Decide
Keeping the context close.
One design decision, written as a record: the question behind it, what I chose, what it cost, and what is still left to test.
Decision record
Inbox
- Question
- How could a lead’s details stay close to the reply?
- Decision
- I brought the conversation list, the open conversation, and contact details into one view.
- Trade-off
- It also put more information on one screen.
- To test
- Whether the screen stays easy to read.

The product, in view
5.1 Dashboard

5.1 Dashboard
A view of the day.
One overview of the work ahead: conversations, response time, follow-ups, and tasks.
Syamil
5.2 Inbox

5.2 Inbox
Room for the conversation.
The message list, the open conversation, and contact details sit together in one view.
Syamil
5.3 Pipeline

5.3 Pipeline
A place for each lead.
A board organises leads across stages, from a new contact to a closed deal.
Syamil
5.4 Analytics

5.4 Analytics
Where the leads come from.
Conversion by stage, volume per channel, and revenue by source, read together.
Syamil
5.5 Calendar

5.5 Calendar
The follow-ups, on a calendar.
Follow-ups and tasks sit on a monthly view, with weekly and daily views one tap away.
Syamil
5.6 Ask Krool

5.6 Ask Krool
A list, from a sentence.
A request typed to the assistant returns matching leads, with their channel and stage.
Syamil
Dashboard01 / 06
5.1 Dashboard

5.2 Inbox

5.3 Pipeline

5.4 Analytics

5.5 Calendar

5.6 Ask Krool

Dashboard, 01 / 06
06Looking back
The screens were only part of it.
Working on Krool meant deciding what belonged together, not only how each page should look.
If I continued
I would spend more time with the people who do this work, and let their routines test the structure I designed.
06 Looking back
The screens were only part of it.
Working on Krool meant deciding what belonged together, not only how each page should look.
If I continued
I would spend more time with the people who do this work, and let their routines test the structure I designed.
07A starting point for yours
Could this be a starting point for your product?
Krool is an exploration. If parts of it feel close to what you’re building, I’d be happy to hear your idea.
We can talk about what fits, what needs to change, and how it could work for your team and customers.
A first conversation about your idea, your needs, and where we could begin.
07 A starting point for yours
Could this be a starting point for your product?
Krool is an exploration. If parts of it feel close to what you’re building, I’d be happy to hear your idea.
We can talk about what fits, what needs to change, and how it could work for your team and customers.
A first conversation about your idea, your needs, and where we could begin.













