How we work

Whether it's a new application, modernisation, or reinforcing your team — we bring structure and delivery. Transparent, in short cycles, with you in control.

• Direct communication — you always talk directly to the developers building your system.
• First results within weeks — after the first sprint, you'll see working software, not a concept paper.
• Flexible priorities — requirements change. Our cycles are short enough to react to new insights.
• Your code belongs to you — open-source technologies, full source code, no vendor lock-in.
• Quality built in — you decide how much to invest in QA. We advise where it's best spent.
• Beyond the launch — operations, maintenance, and further development from one team. With or without an SLA — that's your call too.

This process is the common denominator for every Tegonal project. Depending on the situation, we adjust scope, pace, and focus — whether it's a startup with an MVP or an established company with a complex system landscape.

What happens in the first week

In the first week, we have two or three conversations — not to tick off requirements, but to understand your business. What's driving the project? What dependencies exist? Where's the biggest risk?

In parallel, we look at existing systems if there are any. By the end of the week, we deliver an initial assessment: what's realistic, what isn't, and whether we're the right team for it. Sometimes the most honest answer is a recommendation to someone else.

When things don't go to plan

No project runs exactly to plan — and we don't pretend otherwise. Requirements change, technical surprises come up, priorities shift.

That's why we work in short cycles. If an assumption turns out to be wrong after two weeks, we've invested two weeks — not six months. We raise problems as soon as we see them, not at the next status meeting. And if an estimate was off, we say so openly and adjust the plan together.

Different starting points

Not every project starts from zero. Where you are determines how we begin.

You have an idea but no code. We help sharpen the concept, build an initial prototype, and validate it with real users — before you invest in full development.

Your existing system needs modernising. We analyse the current architecture, identify the biggest bottlenecks, and modernise step by step — without putting ongoing operations at risk.

You need more capacity temporarily. Our developers integrate into your team, work with your tools and processes, and hand over cleanly when the engagement ends.

Who's behind the process

At Tegonal, there's no separation between the people who sell and the people who build. The person discussing requirements with you also writes the code.

Our developers are co-owners of the cooperative. That's not a detail in the company structure — it means the person building your system has a personal stake in making it work long-term. Not just until sign-off.

What we don't do

We don't do fixed-price projects without a preliminary phase. Anyone who gives you a fixed price after a one-hour conversation has either padded too much or understood too little.

We don't take on projects we believe won't work as planned. If your timeline is unrealistic or the chosen approach is bound to fail, we'll say so — even if it means not getting the contract.

And we don't promise technologies we don't master. Our stack is deliberately focused, because deep knowledge delivers better results than broad promises.