Tendee
From an internal tool to a scalable B2B SaaS platform
From an internal tool to a scalable B2B SaaS platform
Tendee helps companies manage the entire tender lifecycle — from initial price justification and bid submission to approvals, contracts, payments, deliveries, and logistics.
As the sole product designer, I completely redesigned the company’s internal tool to prepare it for the commercial market.
Role
Sole Product Designer
Scope
Product architecture, UX/UI, role-based workflows, design system, documentation, implementation review
Team
Founder, PM, Frontend & Backend, Presentologi
Project type
Airdrop app
Web 3
Roles
Project manager
Head of design
Deliverables
UX testing
App architecture
Brand identity
UI design
Pitch decks
selected projects
From the past few years
01
Eliminating response delay after on-chain transactions
Define
The problem was lack of trust due to delayed feedback. The goal was to ensure stability despite blockchain limits.
The problem was lack of trust due to delayed feedback. The goal was to ensure stability despite blockchain limits.
Discover
UX testing showed that users were confused by blockchain delays, leading to repeated clicks and many support tickets
UX testing showed that users were confused by blockchain delays, leading to repeated clicks and many support tickets
Develop
I chose a frontend optimization: balances updated instantly after actions, while errors were explained if transactions actually failed
I chose a frontend optimization: balances updated instantly after actions, while errors were explained if transactions actually failed
Deliver
UX became smoother and more predictable, even within Web3 limitations
UX became smoother and more predictable, even within Web3 limitations
Support-related issues dropped by
~90%
Scenario completion improved by up to
85%
02
Improving scenario completion through
A/B testing of tooltips
Define
Key elements were unclear, causing failed scenarios. The goal was to boost completion and cut support
Discover
UX testing showed most users failed flows due to unclear mechanics and lack of familiar cues
Develop
I suggested tooltips and ran an A/B test, comparing flows with and without them
Deliver
All users with tooltips completed tasks, while the control group failed. The team agreed
to implement tooltips
Support-related issues dropped by
~70%
Scenario completion improved from 25%
90%
context
Case 02
Improving scenario completion through
A/B testing of tooltips
Discover
UX testing showed most users failed flows due to unclear mechanics and lack
of familiar cues
UX testing showed most users failed flows due to unclear mechanics and lack of familiar cues
Define
Key elements were unclear, causing failed scenarios. The goal was to boost completion and cut support
Develop
I suggested tooltips and ran an A/B test, comparing flows with and without them
Deliver
All users with tooltips completed tasks, while the control group failed. The team agreed to implement tooltips
All users with tooltips completed tasks, while the control group failed. The team agreed
to implement tooltips
Support-related issues dropped by
~70%
Scenario completion improved from 25%
90%
03
Shaping raw ideas
into interface logic
Define
No shared product logic caused misalignment. The goal was to build
a clear structure and documentation
Discover
The product had no clear definition,
and the team shared conflicting ideas
without a single vision
Develop
I ran sessions to define scenarios, created user flows, and introduced a Figma Helper system for statuses and notes
Deliver
The team gained a single reference point, made faster decisions, and navigated files independently
Rework due to misalignment reduced
Decisions speed improved from 2 to
0,5 days
Case 03
Shaping raw ideas
into interface logic
Discover
The product had no clear definition, and the team shared conflicting ideas without
a single vision
The product had no clear definition,
and the team shared conflicting ideas
without a single vision
Define
No shared product logic caused misalignment. The goal was to build a clear structure and documentation
No shared product logic caused misalignment. The goal was to build
a clear structure and documentation
Develop
I ran sessions to define scenarios, created user flows, and introduced a Figma Helper system for statuses and notes
Deliver
The team gained a single reference point, made faster decisions, and navigated files independently
Rework due to misalignment reduced
Decisions speed improved from 2 to
0,5 days
04
Building a visual
system from scratch
Define
No unified visual system existed. The goal was to create a cohesive identity scalable across all materials
Discover
The project started with no brand, style,
or UI, while teams worked in parallel, risking inconsistency
Develop
I ran a competitive audit, designed
a concept with typography, UI patterns, and style, then built a design system and brand guide
Deliver
The result was a unified visual language across all touchpoints, faster workflows,
and stronger brand positioning
Rework on inconsistencies reduced
Brand recognition increased
Case 04
Building a visual
system from scratch
Discover
The project started with no brand, style,
or UI, while teams worked in parallel, risking inconsistency
Define
No unified visual system existed. The goal was to create a cohesive identity scalable across all materials
Develop
I ran a competitive audit, designed
a concept with typography, UI patterns, and style, then built a design system and brand guide
Deliver
The result was a unified visual language across all touchpoints, faster workflows, and stronger brand positioning
The result was a unified visual language across all touchpoints, faster workflows,
and stronger brand positioning
Rework on inconsistencies reduced
Brand recognition increased
Questions
you might have
What’s your preferred work setup?
Do you have Web3 experience?
What leadership experience do you have?
Share a product design initiative you led and its impact
Have you worked with design systems?
How do you approach research?
Why do you prefer startups or early-stage products?
Anything else we should know?
Questions you might have
What’s your preferred work setup?
Do you have Web3 experience?
What leadership experience do you have?
Share a product design initiative you led and its impact
Have you worked with design systems?
How do you approach research?
Why do you prefer startups or early-stage products?
Anything else we should know?
Questions
you might have
What’s your preferred work setup?
Do you have Web3 experience?
What leadership experience do you have?
Share a product design initiative you led and its impact
Have you worked with design systems?
How do you approach research?
Why do you prefer startups or early-stage products?
Anything else we should know?