Over time, every service develops its knots: decisions that no longer fit together, fixes added one by one and workarounds that have quietly become part of the process. We trace the service from end to end, untangle the complex processes around it and reshape it into something pleasant to use and maintain.
2 min read
We take time to understand the problem deeply, make a well-argued plan, build it with modern tools, and hand over a service your team can confidently own.
Helen is a designer and web developer with a master’s degree in Applied Behavioural Sciences. At this stage, Helen’s role is to understand the problem in depth: the human factors, technical constraints, regulatory context and historical background. She turns this complexity into a clear strategic document that brings your team onto the same page: how the service works today, what people already love about it, what activities could be supported better, and where the redesign should focus to make the service easier to use.
Once the problem is clear enough, we move from analysis into design planning. We translate the strategic document into early service flows, page structures, interface ideas and content priorities, so the future service starts becoming concrete. We share these early designs with your team to test the emerging direction, surface missing constraints and check the logic with users where needed. The goal is to arrive at a design direction that is useful, realistic and ready for development.
Jaanus is a highly seasoned full-stack developer who typically works with React, Node.js, MongoDB, PostgreSQL and Redis, but is comfortable across the stack and can adapt to what the project requires. He plans the build and develops the service: breaking the work into clear steps, identifying technical risks early, making sensible simplifications where needed, and turning the agreed design into something real, usable and ready to launch.
Your team gets more than a finished product: they get a service they understand, can operate, and can take forward. Because we've been working with you throughout, you know not just what was made, but why it was made that way. After launch, we of course stay close to support first use, resolve issues, and make sure your team can confidently take ownership.
We are two Estonians who met at Pipedrive where we learned how strong product organisations build for scale, move under pressure, and keep quality high. Since then, we have spent more than a decade building complex digital services together.
Helen is a service designer who brings together user needs, business realities, communication, and technology. Her background spans film and media, over a decade in web development, product management, founding a company, user research, and an MA in Applied Behavioural Sciences. She turns that breadth into clear, validated service plans that are useful and feasible to build.
Service Design
User Research
Product Management
Web Development
Storytelling
Jaanus is a senior full-stack developer who turns clear service plans into fast, secure, and reliable digital services. He has built complex systems across aviation, university finance, sales, and travel, working from interfaces and APIs through databases and infrastructure. His strength is seeing how the whole system fits together and making sound architectural decisions that keep it maintainable and ready to grow.
System Architecture
Backend Engineering
Database Design
Security & Reliability
Performance Optimisation
Estonian Business School
Built a university website that could be managed as a system of collections.
Spordikoolituse - ja Teabe Sihtasutus
Conducted research to make national sports data easier to understand and use.
Eedu / Eedume OÜ
Founded an EdTech company with software that teaches students how to think through unfamiliar problems, not just solve familiar ones.
Every good service we have built has depended on someone opening the door and letting us look closely at how things really work. We're grateful to all the clients who have trusted us with the truth, stayed curious before the answer is obvious, and kept relentlessly working to make the change real.
We’ll find the thread and build the next working version.
