Product Owner
I turn user needs into a clear backlog: workflows, requirements, priorities and acceptance criteria. I check that the released feature solves the original problem.
- Paying clients · X-BOT
- 50+
- Modules · X-BOT
- ≈50
- Delivery time on one route · R/Engine
- −62.5%
What I can own
Clarify requirements
Turn user and paying-client requests into tasks with clear goals and boundaries.
Prioritize the backlog
Separate critical problems from additions and decide the order of implementation.
Design user workflows
Describe the user journey, interface states and behavior when errors or interruptions occur.
Define acceptance criteria
Specify what makes a feature ready and validate it against actual workflows.
Connect product components
Align data import, integrations, access rights and mobile, web and desktop transitions.
Develop after release
Use support requests and feedback to guide fixes and reusable features.
How this worked in practice
R/Engine · logistics and delivery
Defined the courier workflow: assignment import, stop order, GPS, delivery information and completion. Accepted changes on real routes and on iPhone/Android.
4 h+ without Route Engine → 1 h 30 min with the current version (−62.5%); a further −24% from July Beta to October Production (1:59 → 1:30). Used across five districts, tested on iPhone and Android.
X-BOT · community SaaS
Turned recurring paying-client requests into requirements and reusable modules; shipped updates and incorporated support feedback.
50+ paying clients, ≈50 modules and 12 months of commercial support.
Industrial CMS · B2B platform
Connected catalog, requests and publishing with employee workflows, access rights and acceptance criteria.
3 workflows: catalog, requests and publishing; 7 access roles.
Windows Inspection · .exe + Web App
Designed the .exe → Web App workflow: PC inspection, report delivery and review, access and licensing; personally accepted releases.
71 completed inspections from 30 March to 29 April 2026; 4 external PCs belonging to different users.