How we work
Your business already has a system. We start there
Sometimes it is software. Sometimes it is a spreadsheet, a manual handoff or knowledge held by one person. Before we suggest any change, we look at it through three questions:
- What should become possible? We begin with what the business, its customers or its team should be able to do differently - not with a feature.
- What happens today instead? We look for the real delay, risk, manual work or missed opportunity - and who carries it.
- What already works and should stay? We preserve useful products, processes and knowledge instead of replacing them with custom code.
You know the business. We bring the engineering judgment. We think it through together, and the final call is yours.
From questions to a decision
What we learn points to one of four next steps - often a combination:
- Use a proven product.
- Connect systems you already trust.
- Build what is specific to your business.
- Remove what no longer earns its place.
We lay out the options with their trade-offs and recommend one. We reach for building last, not first.
When we do build, we aim for software that makes the business less dependent on us, not more. If your team keeps needing a new product type, pricing rule or report, we build the ability for your team to add it themselves, without new development.
Working together, one step at a time
Every engagement starts with a focused assessment, usually 1–2 weeks at a fixed price, and continues in useful increments. Within each increment:
- You see it early. We deploy often to a test environment, so you can see the software taking shape and adjust its direction while that is still cheap.
- Your feedback shapes it. We refine the work based on what your team notices when using it - not only on what was specified at the start.
- Change stays safe and affordable. We automate tests, so the system can keep changing without breaking what already works.
At the end of each increment, we review the result together and decide whether to continue, adjust or stop. When the software keeps changing, we can stay on to look after it and develop it further.
What we ask of you
The work goes best when the people who know the business stay close to it.
- A decision-maker - someone on your side with the authority to set priorities and the time to stay involved.
- Access to the people who do the work - they often know where the real problem is.
- Timely answers - when the next step depends on you, a quick reply keeps the work moving.
- Honest feedback, including about us - early, while it is still easy to act on.
Some work is not ours to take
We do not work with companies whose business involves gambling, tobacco or weapons, or with companies built on exploitation, harmful addiction or serious environmental harm.
We also turn down companies that ask us to build dark patterns, manipulate people or hide material information - whatever their industry.
We delegate coding to AI agents. Never the thinking
AI agents write, test and change much of our code. That gives us more time to understand your business and to talk with the people who will use the software.
The questions, the trade-offs and the judgment about what should exist at all stay with people - with us and with you. Every change that reaches your system is reviewed by one of us, and we remain responsible for it.
What we build with
We build web applications with Ruby on Rails and PostgreSQL.
Ruby was designed for people, not machines - and after all these years, working with it still makes us happy. AI agents are remarkably good at it, and the code stays easy for us to read and review. The Ruby community is lively, friendly and full of good engineering and fresh ideas.
PostgreSQL has served us for many years without surprises, and each new release brings features we put to use.
We are comfortable with event-driven architectures, API design and distributed systems, and with connecting your system to the services around it - payment providers, supplier feeds, marketplaces. We also maintain several open-source Ruby gems. If your system is built with something else, we are still open to it. Whatever the stack, good software rests on the same principles and practices.
Have a decision in front of you?
Tell us what the business needs, where the software gets in the way, or what has become difficult to change.
You do not need a specification or a proposed solution. 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.