Anastasia AmosovaGet in touch

Saint Petersburg · open to product teams

Product Designer · Oct ’25 — present

Resurs-Plus

for industrial safety

B2B/B2CMarketplaceIndustrial

Resurs-Plus is a professional marketplace where companies post jobs and specialists find suitable projects and respond to them.

I designed the structure of the platform, the flows for each role, the order and specialist cards, and the systems for responses and pricing plans.

Resurs-Plus

Information architecture

(Product architecture)

First I broke the product down into roles and flows →

Before drawing any interfaces I put together a product map: I separated the client and the contractor flows and described the main points of interaction — registration, personal accounts, posting a job, responding, choosing a contractor, chat, completing the work, reviews and payment.

That let me design not a set of separate pages, but a connected system in which the actions of one role continue the flow of the other.

Role model

(Role model)

One product — different user jobs

The flows differ, but the order, the response, the profile, the chat and the rating have to stay shared entities of the platform.

Client

Needs to state the task quickly, collect responses, compare specialists and choose a contractor.

Client

Specialist

Needs to find suitable projects, understand the terms quickly and send a competitive response.

Specialist

Key interfaces

(Key interfaces)
Order card

Order card

Terms, deadlines, specialisation and requirements are gathered in one place, so a specialist can quickly tell whether the job suits them.

Response

Response

The specialist sets a price, a deadline and a comment, and sends the response straight from the order flow.

Choosing a contractor

Choosing a contractor

When choosing, the client sees the specialist's profile, specialisation, rating, reviews and proposed terms.

Trust and communication

(Trust & communication)

The deal doesn't end when a contractor is chosen

Once a specialist is selected, a working flow opens up between the two sides: chat, exchange of messages and files, delivery of the job and then evaluation of the result. Ratings and reviews become part of the profile and help the next clients make their decision.

Chat

Chat

Communication after a contractor is chosen

Order history

Order history

Specialisation, experience and work history

Reviews and rating

Reviews and rating

Reputation is built from completed orders

Result

(Result)

For me Resurs-Plus is a project not about separate pages, but about the connections between users, entities and product states. It was the product map that helped me understand those connections first and only then move on to interfaces.

Role architecture

The different jobs of client and contractor live inside one system

Role architecture

Connected marketplace flow

Order, response, selection, chat and rating work as consecutive steps of a single journey

Connected marketplace flow

A base for scaling

New tools can be added around the core mechanic without rebuilding the product from scratch

A base for scaling

I'm drawn to complex B2B and SaaS systems: lots of data, several roles, connected flows and constraints.

What I enjoy most is the moment when a clear product structure starts to emerge from a pile of requirements.

I'm comfortable with iteration and rework, and I prefer to justify a decision by the user's task rather than by “it looks nicer this way”.