Kontur
Faster Company Registration
Helping companies sign up without waiting for manual setup.
I found that our team was manually registering companies whose employees already had verified access in another Kontur service. I designed a way to reuse that access.
More companies could start on their own, and our team handled fewer registration requests.
Problem
Many users could not register their company without the company director’s digital signature. They had to ask our team for help and wait before they could start.
Approach
I reviewed registration requests with the team. Some users already had verified access to their company in another Kontur service. I proposed letting them use that access to register themselves.
Collaboration
I worked with the onboarding team and an analyst to identify which users could register independently. I designed the flow and the next steps for people who still needed help.
How it works
Users enter their company’s tax ID. We find the company and check their access. If they can manage it, they confirm registration and start working.
When users need help
If the company is already registered, users can open it or ask for an invitation. If they cannot register themselves, the page tells them how to get help. Errors offer a retry or a support contact.
Impact
We compared eight weeks before and eight weeks after release, with 420 completed company registrations in each.
- Companies signing up without help
- 40% → 65% 168 → 273 of 420 registrations.
- Fewer manual registrations
- −42% 252 → 147 handled by the onboarding team.
- Team time saved
- 35 hours Over eight weeks, calculated at 20 minutes per manual registration.
- Time to get access
- ~5 min Previously about one working day for users who needed help.
Alexey Linkov Frontend Developer @ Kontur “His layouts are clear, structured, and easy to implement. He brings strong product thinking, attention to detail, and a good balance between user needs, business goals, and technical constraints.”
Ivan Tyulkin Frontend Developer @ Kontur “As a frontend developer, I particularly valued his understanding of the technical side of the product. It made it easy to discuss interface behavior, implementation constraints, and solutions that worked for both users and the team.”