Principal designer,
7 + years of experience

Projects

CV

Linkedin

Email

Telegram

Instagram

Daria Moroz

Principal designer,
7 + years of experience

Projects

CV

Linkedin

Email

Telegram

Instagram

Daria Moroz

Daria Moroz

tendee

Tendee

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.

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

Role

Sole product

Designer

Scope

Product architecture

UX/UI

Role-based workflows

Design system

Documentation

Implementation review

Team

Founder

PM

Frontend & Backend

Presentology

context

context

Tendee was originally built for the company’s own employees and internal processes. The company later decided to transform it into a SaaS product that could be sold to other organisations.

Tendee was originally built for the company’s own employees and internal processes. The company later decided to transform it into a SaaS product that could be sold to other organisations.

The existing version worked, but was not ready for this transition. Confusing navigation, inconsistent workflows, and interaction issues made the product difficult to learn and scale.

The existing version worked, but was not ready for this transition. Confusing nav, inconsistent workflows, and interaction issues made the product difficult to learn and scale.

This required more than a visual redesign. We needed to rebuild the system almost from scratch while preserving essential business logic and accommodating the constraints of the existing backend.

This required more than a visual redesign. We needed to rebuild the system almost from scratch while preserving essential business logic and accommodating the constraints of the existing backend.

System
complexity

System
complexity

Tendee brings the entire tender lifecycle into one platform

Pricing

->

Tender

->

Approval

->

Submission

Contract

->

Payment

->

Delivery

->

Logistics

Pricing

Tender

Approval

Submission

Contract

Payment

Delivery

Logistics

The system supports five roles

Administrator

Manager

Approver

Finance Spec

Logistics Spec

They work with shared objects but have access to different sections and actions depending on their permissions.

The connected objects have their own statuses, actions, and approval rules.

my
approach

my approach

The project had no dedicated analyst, complete technical specification, or predefined product architecture. Requirements emerged gradually and changed throughout the process.

The project had no dedicated analyst, complete technical specification, or predefined product architecture. Requirements emerged gradually and changed throughout the process.

I began with a complete audit of the existing system, reviewing every page, entity, and user flow to identify interaction and logic issues.

I began with a complete audit of the existing system, reviewing every page, entity, and user flow to identify interaction and logic issues.

I started the redesign with the initial price justification workflow — a relatively contained but representative process that allowed us to establish the product’s core principles. I then moved to the tender as the central and most complex entity and extended the resulting patterns across the remaining modules.

I started the redesign with the initial price justification workflow — a relatively contained but representative process that allowed us to establish the product’s core principles. I then moved to the tender as the central and most complex entity and extended the resulting patterns across the remaining modules.

01

Separating viewing
from editing

Decision

I separated object pages into two distinct states:

  • a structured read-only view;

  • a dedicated edit mode activated through an explicit action.

In view mode, information is presented as grouped parameters. Input fields only appear when the user chooses to edit the object.

Problem

Previously, every object opened directly in edit mode. Users had to review large amounts of information inside filled form fields, while critical data could be changed accidentally.

Before

After
(better to check the desktop version)

System-wide effect

Complex records became easier to review, while changing data became a deliberate action. This solution became a shared pattern across Tendee’s core entities.

02

Creating a consistent status-transition model

Decision

I created a consistent action hierarchy:

  • progression is always positioned on the right;

  • returning to a previous stage is on the left;

  • negative actions are highlighted with colour;

  • primary actions retain consistent positions;

  • inactive elements no longer imitate interactive behaviour.

Before

After
(better to check the desktop version)

Problem

The location of actions changed depending on an object’s status. The button for progressing to the next stage could appear in different places, while some elements looked interactive without performing any action. Users had to relearn the interface at every stage of the workflow.

System-wide effect

Transitions became consistent and predictable across tenders, approvals, and related objects.

03

Rebuilding navigation
for scale

Decision

I consolidated navigation into a single sidebar with expandable groups. Available sections and actions adapt to each user’s role.

After
(better to check the desktop version)

Problem

The existing navigation was split between top and side panels. Selecting a section in the top navigation completely changed the contents of the sidebar.

This model obscured the overall product structure, consumed workspace, and could not scale effectively across multiple modules and user roles.

System-wide effect

The product structure became easier to understand and could expand without introducing additional navigation levels. Removing the top panel also created more space for data-heavy tables.

selected projects

From the past few years

Cytonic AI

Web 3

AI constructor

VIEW NOW

Arcanum

DEX

Token dashboard

VIEW NOW

Presentologi

AI constructor

Presentation tool

VIEW NOW

null.face

Business

Digital agency

VIEW NOW

Coinstars

Dex

Web 3

VIEW NOW

Apollo

Fintech

AI

VIEW NOW

FitChoice

Mobile app

Trainer AI

VIEW NOW

Dental clinic

Business website

VIEW NOW

Cytonic airdrop

Web 3

Airdrop app

VIEW NOW

Case 01

Separating viewing
from editing

Problem

Previously, every object opened directly in edit mode. Users had to review large amounts of information inside filled form fields, while critical data could be changed accidentally.

Decision

I separated object pages into two distinct states:

  • a structured read-only view;

  • a dedicated edit mode activated through an explicit action.

In view mode, information is presented as grouped parameters. Input fields only appear when the user chooses to edit the object.

System-wide effect

Complex records became easier to review, while changing data became a deliberate action. This solution became a shared pattern across Tendee’s core entities.

Creating a consistent status-transition
model

Problem

The location of actions changed depending on an object’s status. The button for progressing to the next stage could appear in different places, while some elements looked interactive without performing any action. Users had to relearn the interface at every stage of the workflow.

Decision

I created a consistent action hierarchy:

  • progression is always positioned on the right;

  • returning to a previous stage is on the left;

  • negative actions are highlighted with colour;

  • primary actions retain consistent positions;

  • inactive elements no longer imitate interactive behaviour.

System-wide effect

Transitions became consistent and predictable across tenders, approvals, and related objects.

Before

After

Before

After

Case 02

Creating a consistent status-transition
model

Separating
viewing
from editing

Problem

The location of actions changed depending on an object’s status. The button for progressing to the next stage could appear in different places, while some elements looked interactive without performing any action. Users had to relearn the interface at every stage of the workflow.

Previously, every object opened directly in edit mode. Users had to review large amounts of information inside filled form fields, while critical data could be changed accidentally.

Decision

I created a consistent action hierarchy:

  • progression is always positioned on the right;

  • returning to a previous stage is on the left;

  • negative actions are highlighted with colour;

  • primary actions retain consistent positions;

  • inactive elements no longer imitate interactive behaviour.

I separated object pages into two distinct states:

  • a structured read-only view;

  • a dedicated edit mode activated through an explicit action.

In view mode, information is presented as grouped parameters. Input fields only appear when the user chooses to edit the object.

System-wide effect

Transitions became consistent and predictable across tenders, approvals, and related objects.

Complex records became easier to review, while changing data became a deliberate action. This solution became a shared pattern across Tendee’s core entities.

Before

After

Case 03

Rebuilding navigation
for scale

Rebuilding
navigation
for scale

Problem

The existing navigation was split between top and side panels. Selecting a section in the top navigation completely changed the contents of the sidebar.

This model obscured the overall product structure, consumed workspace, and could not scale effectively across multiple modules and user roles.

Decision

I consolidated navigation into a single sidebar with expandable groups. Available sections and actions adapt to each user’s role.

System-wide effect

The product structure became easier to understand and could expand without introducing additional navigation levels. Removing the top panel also created more space for data-heavy tables.

handoff
& UI KIT

handoff & UI KIT

I created a design system covering inputs, forms, tables, buttons, statuses, and complex object states.

I created a design system covering inputs, forms, tables, buttons, statuses, and complex object states.

For documentation, I used my own Figma Helper System: numbering use cases and screens while placing conditions, transitions, and developer notes directly alongside the designs.

For documentation, I used my own Figma Helper System: numbering use cases and screens while placing conditions, transitions, and developer notes directly alongside the designs.

Solutions were reviewed with the founder, Project Manager, and developers. After implementation, I tested each module on staging and provided the team with the required corrections.

Solutions were reviewed with the founder, Project Manager, and developers. After implementation, I tested each module on staging and provided the team with the required corrections.

outcome

outcome

Tendee was fully redesigned and handed over for development. The team implemented all planned modules, along with several additional ones.

Tendee was fully redesigned and handed over for development. The team implemented all planned modules, along with several additional ones.

A fragmented internal tool became a coherent commercial platform with five user roles, connected lifecycles, and consistent interaction patterns.

A fragmented internal tool became a coherent commercial platform with five user roles, connected lifecycles, and consistent interaction patterns.

Product metrics are not yet available, so I do not attribute unverified quantitative impact to these decisions. The confirmed outcome is an implemented product architecture, resolved UX issues, and a solid foundation for commercial launch.

Product metrics are not yet available, so I do not attribute unverified quantitative impact to these decisions. The confirmed outcome is an implemented product architecture, resolved UX issues, and a solid foundation for commercial launch.

Questions

you might have

Where do I make the biggest impact?

What do I take ownership of?

How do I make decisions when data is limited?

How do I work with teams and help designers grow?

How do I help a product scale without losing quality?

How do I connect design decisions to product outcomes?

How do I use AI, 3D, and motion?

What working arrangements am I open to?

Questions you might have

Where do I make the biggest impact?

What do I take ownership of?

How do I make decisions when data is limited?

How do I work with teams and help designers grow?

How do I help a product scale without losing quality?

How do I connect design decisions to product outcomes?

How do I use AI, 3D, and motion?

What working arrangements am I open to?

Telegram

Email

CV

get in touch

@2025

Email: frostybirdyworks@gmail.com

Telegram: @FrostyBirdy

get in touch

@2025

Email: frostybirdyworks@gmail.com

Telegram: @FrostyBirdy

get in touch

Questions

you might have

Where do I make the biggest impact?

What do I take ownership of?

How do I make decisions when data is limited?

How do I work with teams and help designers grow?

How do I help a product scale without losing quality?

How do I connect design decisions to product outcomes?

How do I use AI, 3D, and motion?

What working arrangements am I open to?

Create a free website with Framer, the website builder loved by startups, designers and agencies.