We build custom software for small and mid-sized companies across the European Union — and stay on to operate it.
Most companies sell you the build. The years that follow are where the software actually lives — so we stay for those too.
None of these situations is unusual, and none of them means anything has been done badly. They are what happens when a business grows faster than the software holding it together.
AH-01 Software written for one company's way of working, rather than a product it has to bend around.
AH-02 Engineering capacity and technical judgement for companies without an in-house team, or with one that is already at capacity.
We start with how the work is done today — the actual steps, the workarounds, the parts nobody has written down. The scope is agreed from that, not from a wishlist.
Structure, interfaces and data model are settled before code is written, and reviewed with the people who will use the result rather than only those who commissioned it.
Delivered in working increments you can open and judge, so the direction is corrected while correcting it is still cheap.
The system goes on being maintained, monitored and changed as the business changes. This is where most of a system's life happens, and it is part of the engagement, not a separate sale.
The interfaces your staff or customers work in every day.
The services underneath, and the interfaces other systems call.
How the business is represented, so reports agree with each other.
Making software that was never designed to cooperate do exactly that.
Where it runs, how it ships, and what happens when it does not.
The recurring work currently done by hand, done by the system instead.
Keeping a live system healthy once the build is finished.
Adopting software written by someone who is no longer available.
Three shapes. Which one fits is part of the first conversation, not something to settle before it.
| Model | Scope agreed up front | Capacity reserved monthly | Delivery owned end to end | Advisory without implementation |
|---|---|---|---|---|
| Fixed-scope project The outcome is known and can be written down. | Scope agreed up front yes | Capacity reserved monthly no | Delivery owned end to end yes | Advisory without implementation no |
| Dedicated team The work is continuous and the priorities move. | Scope agreed up front no | Capacity reserved monthly yes | Delivery owned end to end yes | Advisory without implementation yes |
| Consulting The decision matters more than the code. | Scope agreed up front no | Capacity reserved monthly no | Delivery owned end to end no | Advisory without implementation yes |
You describe the problem in your own words. No form, no qualification questionnaire, no sales sequence.
A call to understand the situation, the constraints and what has already been tried. The conversation is about the work itself, not a sales process.
What we understand the problem to be, what we would build, what we would not, and how we would price it. In writing, so it can be compared with other quotes.
You keep the written scope whether or not you work with us. If custom software is the wrong answer for you, that is what the document will say.
Who owns the source code, the infrastructure accounts and the documentation is written into the agreement before work begins, rather than discovered at the end of it.
If an existing product solves your problem for a fraction of the cost, we will tell you which one. A bad-fit project helps neither side.
Work does not start on a verbal understanding. What is included and what is not is agreed on paper before anyone writes code.
Every engagement has a stated point of contact, so a question about your system never has to start by explaining it again from the beginning.
Arroba Harmoniosa is an IT services company based in Lisbon, Portugal. We work with small and mid-sized companies across the European Union — under EU law, in EU jurisdiction, with the contractual and data-protection obligations that come with it.
There are no client logos on this page and no numbers we cannot stand behind. What we offer instead is a direct conversation with the people who would do the work.
Yes. We are established in Lisbon and work with small and mid-sized companies across the European Union. Engagements are handled remotely, under EU law.
It depends entirely on scope, and we would rather not publish a number that turns out to be wrong for you. Pricing is set out in the written scope after the first conversation, alongside the assumptions it rests on.
Yes — that is part of the IT consulting and outsourcing service. It starts with an assessment of the existing code and infrastructure, so that you get an honest view of what maintaining it involves before committing to anything.
It is maintained, monitored and changed as your business changes. Continuing to operate the system is part of the engagement rather than a separate contract sold afterwards.
No. Which of the three fits is something the first conversation is for. Some engagements also change shape over time, from a fixed-scope build into ongoing operation.
The company is directed by Aleksandrs Zukovs and is based in Lisbon. Who works on your project depends on what it needs, and that is agreed with you before anything starts.
Describe it in your own words — the process, the system, the thing that keeps breaking. You will get a straight answer about whether we are the right people for it, including when we are not.
Rua Ana de Castro Osório, no 5, NO-/CA, Lisboa, Portugal