Econt
Econt
Econt is Bulgaria's largest courier network. Its shipping system handles preparation, dispatch, tracking and delivery — used every day by company clients, private senders, office staff and couriers on the road.
Econt is Bulgaria's largest courier network. Its shipping system handles preparation, dispatch, tracking and delivery — used every day by company clients, private senders, office staff and couriers on the road.
Designed at Despark
Challenge
The system had been growing for years, one feature at a time, and the cost showed up where it hurt most: preparing a shipment took too long. Office queues moved slowly, couriers worked around the software, and business clients complained. Three groups depended on the same screens with entirely different pressures on them — and no one had mapped what the system was actually asking of each.
Strategy
I started by auditing every process and function in the existing system, then went to find out what using it is really like. I sat in Econt offices watching staff work through queues, interviewed couriers, and spent several days working as a courier's assistant — delivering and collecting parcels at real addresses. I ran interviews with business clients and watched them work in their own offices. That produced a map of where the system slowed people down and what each fix was worth, which became priority guides, wireframes, and a prototype that went through several rounds before it was given a new interface.
Outcome
I was responsible for UX and UI across the project — which meant deciding what the platform's structure should be, not just how it looked. The textbooаWhat I delivered was a system understood end to end: an audit of every process, a prioritised map of where time was being lost, wireframes and a tested prototype, and the interface for all of it. The map outlived the project — it's the part that keeps being useful after the redesign ships.k alignment, the reworked lesson-to-test flow, and the design system that carried the new brand into every screen were mine. Daily video lessons watched doubled in the year after launch, from 30,000 to over 60,000, with daily visits up from 20,000 to 30,000.
Challenge
The system had been growing for years, one feature at a time, and the cost showed up where it hurt most: preparing a shipment took too long. Office queues moved slowly, couriers worked around the software, and business clients complained. Three groups depended on the same screens with entirely different pressures on them — and no one had mapped what the system was actually asking of each.
Strategy
I started by auditing every process and function in the existing system, then went to find out what using it is really like. I sat in Econt offices watching staff work through queues, interviewed couriers, and spent several days working as a courier's assistant — delivering and collecting parcels at real addresses. I ran interviews with business clients and watched them work in their own offices. That produced a map of where the system slowed people down and what each fix was worth, which became priority guides, wireframes, and a prototype that went through several rounds before it was given a new interface.
Outcome
I was responsible for UX and UI across the project — which meant deciding what the platform's structure should be, not just how it looked. The textbooаWhat I delivered was a system understood end to end: an audit of every process, a prioritised map of where time was being lost, wireframes and a tested prototype, and the interface for all of it. The map outlived the project — it's the part that keeps being useful after the redesign ships.k alignment, the reworked lesson-to-test flow, and the design system that carried the new brand into every screen were mine. Daily video lessons watched doubled in the year after launch, from 30,000 to over 60,000, with daily visits up from 20,000 to 30,000.
© 2026 Design and code by Daniel Prashtilsky.