The people behind the work
A small team of product engineers who think beyond the next release
Since 2007, we have built, evolved and looked after software that businesses depend on. The people who ask the questions also shape the solution, build and test it, and stay accountable for what follows.
Each of us works across product thinking, software development and client conversations. We each bring a different strength, and shared context means any of us can pick up where another left off.
Our team
Denitsa Belogusheva
Co-founder · Engineering lead · 19 years in software · LinkedIn
Denitsa keeps the whole system in view: the business need, the technical consequences, the people doing the work, and the software that will live with the decision.
She has led work from the first client conversation to long-term care, and still writes and reviews code. When requirements are complex, she works directly with clients and partners.
She looks past whether software works to whether the people using it understand it - and whether it makes their work easier. She shares that care with the team through mentoring, feedback and reusable review workflows.
Sava Lachezarov
Co-founder · Systems design · 25 years in software · LinkedIn
Sava thinks in systems.
Having worked across product development, architecture, infrastructure and developer tooling, he looks at how the parts connect, where a change in one place will be felt in another, and which solution addresses the cause rather than the symptom.
He notices the friction others have learned to live with - a step repeated by hand, a detail people have to remember - and proposes the tool that takes it away, easing both the work and the mental load.
His background in journalism and facilitation shapes the way he asks questions, explains technical choices and navigates difficult conversations.
Gabriela Velinova
Product engineer · Delivery and team practices · 11 years in software · LinkedIn
Gabriela brings order to complex work. She plans it, keeps the people involved coordinated and makes sure decisions are written down.
When an idea is still taking shape, she asks the questions that turn it into clear business rules, then builds those rules into working software. For a long-running e-commerce business, she designed and built the promotion-code system and delivered a supplier integration that opened an entirely new channel for the business.
She presents clearly to clients, to the team and at conferences. Through trainings and mentoring, she helps developers grow and the whole team get better at the work.
Shared roots. Room to grow
We are graduates of the Faculty of Mathematics and Informatics at Sofia University. That shared foundation still shapes how we reason about systems, learn together and challenge one another’s decisions.
We keep learning across product engineering, leadership and facilitation. Beyond client work, we have run internships since 2010, mentored developers through initiatives including Rails Girls, published open-source Ruby gems and supported the local Ruby community.
We are a remote company and value focused work. We still make a point of meeting in person, with each other and with clients, because long partnerships need human connection too.
Small by design
We are three product engineers, and we intend to stay small. We work with only a few clients at a time, so the people you talk to are the people who do the work. If we cannot give your work the attention it needs, we say so up front - not halfway through.
Before an engagement begins, you know who will lead it, who else will contribute, and how much of our time is reserved for you.
A small team works only when your software does not depend on any one of us. So we build continuity into the way the work is understood, recorded and owned:
- Decisions with reasons. We record not only what was decided, but why, so future changes can respect the original trade-offs or revisit them deliberately.
- Knowledge that outlasts any one of us. Automated tests capture how the system should behave; technical and user documentation explain the rest.
- Yours from day one. The code, repositories, documentation and access needed to run the system are yours, not ours.
- A continuity plan, agreed up front. We agree who would take over, and how they would get up to speed, if one of us becomes unavailable - or if the team itself changes.
We want you to stay because the partnership works - not because your software cannot leave with us.
Talk to the people who would do the work
Tell us what your business needs, where the software gets in the way, or what has become difficult to change.
A few lines are enough; you do not need a specification. The first conversation is free, and if we are not the right fit, we say so.
Or write to hi@tutuf.com in English or Bulgarian.