What custom software is (and what it is not)
Custom software is software whose requirements come from the process of a specific company, not from an entire market. It can be an internal system, a client portal, an app or a SaaS platform: what defines the concept is where the rules come from, not the size of the project.
It is also not a synonym for a large, expensive or long project. A good custom project starts with a small slice — the process that costs the most today —, goes into use and grows based on what real use shows. Building everything at once, before using it, is the most common and most costly mistake.
Custom, off-the-shelf or low-code: how to decide
There is no single answer, and the best option for your company may be not to build anything. This is the criterion we use in the first conversation:
- Off-the-shelf software is the right fit when your process is the same as the market's (accounting, email, payroll). If a ready-made product solves the problem, our recommendation is not to build.
- Low-code and no-code work well to validate an idea or automate a simple, internal flow. They tend to hit limits as rules, permissions, data volume or integrations grow — and migrating later has a cost.
- Custom software pays off when the process is part of your differentiation, when there are rules and integrations that off-the-shelf software only covers with workarounds, when you need to own the product and the code, or when per-user license costs grow faster than the business.
How we run a custom project
We start with discovery: understanding the process, who uses it, what goes wrong today and what "working" means. From that come the initial slice, an architecture sized for the current stage and an estimate. Only then does development begin, in two-week sprints, with a demo at the end of each cycle, mandatory code review, automated tests and continuous deployment to a staging environment.
You follow stages, deliverables and approvals through the client portal, and the code, technical documentation and decision records stay available to you and your team.
What drives cost and timeline
We do not publish a price list, because the value depends on factors that only discovery clarifies. To get a rough order of magnitude before talking, use the free preliminary estimate. The factors that weigh the most:
- Number of user profiles and complexity of permissions
- Number and quality of integrations: a well-documented API costs far less than a legacy system without an API
- Volume of data to migrate and the condition it is in
- Regulatory and privacy requirements (Brazil's LGPD data protection law, tax rules, auditing)
- Level of interface polish and platforms served (web, iOS, Android)