The recommendation to build nothing.
A market product covers it, or the problem is one of process rather than software. It happens, and we say so.
Systems
When the process is the company’s edge, bending it to fit a generic system means giving up the very thing that makes it competitive. We build the system around the operation — not the other way round.
When it makes sense
Let us be blunt: if there is a market product that solves your case well, buying it is cheaper, faster and less risky. We sell ready-made systems ourselves, and that is frequently what we recommend.
Bespoke development is justified when at least one of these is true:
If none of this applies, we say so in the first meeting.
It starts with a conversation
No project starts with a proposal. It starts with a meeting.
Its purpose is not to sell: it is to understand the operation and size the problem. We want to know how the work happens today, where it jams, who does what, which decisions depend on which information, and what has already been tried.
One of three things comes out of that conversation:
A market product covers it, or the problem is one of process rather than software. It happens, and we say so.
Often 20% of what was imagined solves 80% of the pain. Better to deliver that in two months than the rest in two years.
Scope, phases, technologies, timelines and investment, with clarity about what is in and what was left for later.
Only after that stage do we talk about a proposal. It is the conversation that avoids the worst possible outcome in bespoke development: competently building the wrong solution.
The architecture
This is the technical decision with the biggest impact on your system’s long-term cost — and the one that shows up least in a commercial proposal.
We build every solution with independent layers: business rules on one side, data access on another, interfaces on a third. They communicate through defined contracts, not direct coupling.
The layers are independent: each can change without dragging the others along.
Interfaces
Contracts
Persistence
Data
The technology in each layer is chosen per project, to match the client’s environment. What never changes is the separation between them.
If today you need a web system and in a year an app for the field team, the app consumes the same backend. No business rule is rewritten, no logic duplicated, and you never end up in the classic situation where web and mobile compute the same figure in slightly different ways.
The data-access layer isolates the database from everything else. Migrating from SQL Server to PostgreSQL, or the reverse, is localised work.
A third-party ERP, a marketplace or a partner system consumes the same API your front-end does. There is no “integration hack” because there is no need to invent a parallel path.
A business rule isolated from interface and database can be tested automatically. A rule scattered inside a screen cannot.
The technologies
We do not commit to a single stack out of dogma. Each layer has options, and the choice is made per project, considering the client’s existing technology, the team that will live with the system, and the nature of the operation.
The choice is usually less technical than it looks: what the company already has, and who will administer the database day to day, weigh more.
Both solve the same problems with equivalent quality. The decision weighs what the company already runs and who will maintain it in future.
An ORM (Object-Relational Mapper) is the layer that translates between the world of objects, where the code lives, and the world of tables, where the data lives. Without one, every query becomes hand-written SQL and every result becomes repetitive conversion code.
The front-end choice does not lock in the others. That is the practical advantage of layered separation: starting with web and adding mobile later is natural evolution, not a restart.
Who builds it
Bespoke projects are settled by the repertoire of whoever builds them. Our team combines deliberately different profiles.
Most serious defects in business systems are not programming errors — they come from the programmer not understanding accounting.
How we run it
No cost, no commitment. Understanding the operation, the problem and the context.
Scope, phases, technologies and investment. What goes in now and what waits.
Screens and flows before code. Changing your mind is far cheaper at this stage — and this is where the client discovers what they actually wanted.
Partial, working deliveries at short intervals. You watch the system grow and correct course along the way, instead of receiving everything at the end and finding out it was not what you meant.
Testing with the real team, real data and real volume. Not with the manager who approved the project, but with whoever will open that screen fifty times a day.
Data migration, training and support through the critical adoption phase.
A bespoke system does not end — it follows the company. Legislation changes, the operation grows, new needs appear.
Frequently asked questions
It depends entirely on scope, and any figure given before understanding the operation would be invention. What we can say is that we work in phases: the first delivery is sized to create value on its own, not to be a useless fragment until the project ends.
A first working version usually takes two to six months, depending on complexity. Larger projects are split into phases with intermediate deliveries.
That is settled in the contract, transparently, before starting. Our preference is that the client has certainty about the system’s continuity — including in the event of no longer working with us.
Yes. We work remotely and serve clients in Brazil and Paraguay.
A common scenario. We assess what exists and recommend the path: evolve it, rewrite it in parts, or integrate. Rewriting everything is rarely the right answer.
Yes, and it is a speciality of the house — including closed or undocumented systems. See our Integrations page.
A contract covering both corrective and evolutionary maintenance. A system in production needs continuous attention: legislation changes, volume grows, needs emerge.
The first conversation costs nothing and commits you to nothing. If we conclude that the best solution for you is not us, we say so — and point you where it makes sense to go.