About
Idavoll Software Engineering is a software company registered in Valença, Bahia. A senior engineering team: whoever scopes the work builds it.
Where the name comes from
From the field of Iðavöllr to systems that outlast us
In Norse mythology, Iðavöllr is the central plain where the gods gathered to plan, to build, and to lay the foundations of a new world. It is the ground of renewal - the place you return to in order to start something that lasts.
We took the name because it describes the part of the work we care about. Most software is written quickly and maintained badly. The interesting problem is the other one: building something that still runs, still makes sense, and can still be changed by someone else three years from now.
We are new
The company was registered in September 2026. No clients yet, no revenue yet and no case studies. We would rather you read that here than work it out from the CNPJ.
There will not be many case studies later either, and that is the commercial terms working as intended: code, infrastructure and accounts sit in the client’s organisation from the first commit, so nothing of theirs stays with us to write about. Anything that does appear here will have been published with their permission.
Why a senior team is enough
Building software has always taken a lot of manual labour. A project used to need many people simply to type repetitive code and wire systems together.
Today we use AI for that part. It does not understand your business and it does not decide the architecture, but it writes the mechanical half of engineering without complaining. The result is a team with no filler: you pay for whoever solves the problem, not for the hours of whoever types.
The obvious question is whether you are paying senior rates for something a computer generated. The answer is yes, because you are not paying for the typing, you are paying for the accountability. The machine writes the text, but an experienced person reads every generated line, decides whether it becomes a problem next month, and puts their own name on the contract to take the blame when it breaks.
Mission
We build systems that survive the real world, and the next developer.
Our work is to write what endures. Most code is rubbish within three years, and the interesting problem is the other one: a system your own team can still read and change long after our contract has ended. That takes less code, fewer dependencies and no cleverness.
Vision
We want every client to reach the point where they no longer need us - and the system keeps running with no contract in place.
Most of the money in Brazilian software is in dependency. The sustaining contract that never ends, because nobody on the client side understands the code they were handed. It is the most predictable revenue there is, and it is the revenue we turn down. The cost is immediate rather than hypothetical: we write the documentation, we train the client’s team, and we hand over a system they can maintain without us. What we give up is the most comfortable recurring revenue in the industry - which is exactly the one that is missed most at the start.
Most software studios grow by adding people and selling their hours. That model makes the average engineer on your project more junior every year, and it makes the studio a worse place to work. We grow by bringing in experienced engineers instead of padding the team with people still learning the basics.
In practice that means the people who scope your project are the people who build it. There is no account manager between you and the person writing the code, and no bench to keep busy.
What we will not trade
Each of these costs us something. A value that has never cost anything is not a value, it is a poster.
- 01
In Bahia
We work from Valença, in the interior of Bahia. The cost is the contracts that want dozens of people allocated by Monday, or an office in São Paulo - we turn those down instead of pretending to have either.
- 02
Dates we believe, even when they lose the deal
We work out how long the build actually takes and never shorten the estimate to win the work. The price of that is losing projects to whoever will promise the same system in half the time.
- 03
Repair before rewrite
When we take on software that hurts, we try to save what is there rather than start again. A full rewrite would bill far more, and we argue against it when the existing system can be brought back.
- 04
Accountability cannot be automated
The machine writes much of the text, but when the system goes down in the middle of the night the failure is ours. That costs our own sleep and our own money, fixing what we let through to production.
- 05
Built for whoever comes next
We write so that a different developer can change it in three years without us. That costs margin - we spend time deleting clever code that already works today, because it would be unreadable tomorrow.
What that means for you
We will tell you not to build it
If the thing you are asking for can be solved with software you already own, or should not be built at all, that is the first thing we will say - before there is an invoice attached to the answer.
Nothing is a black box
You get the repository, the infrastructure and the documentation as we go. Nothing is withheld to make leaving difficult.
We work in the open with you
Weekly written updates in plain language, including the weeks where something did not work.
Company details
- CNPJ
- 68.951.625/0001-72
- Legal name
- Idavoll Engenharia de Software LTDA
- Trade name
- Idavoll
- Primary activity
- 6201-5/01 — Custom software development
- Secondary activity
- 6204-0/00 — Information technology consulting
- Location
- Valença, Bahia, Brazil
- Founded
- September 2026