Service · Custom software
Custom software development: platforms, portals and APIs
We design and build the core software of mid-sized companies: platforms, customer and distributor portals, APIs and internal apps, with the same engineering that runs systems handling hundreds of thousands of requests a day, from a senior team in Colombia on US-overlapping hours.
Proof · Engineering proven at hundreds of thousands of requests a day
When your operation no longer fits in spreadsheets or per-seat licenses
There are two typical symptoms. First: critical processes in spreadsheets that five people edit at once without knowing which version is right. Second: off-the-shelf software that charges per user, doesn't adapt to how you work, and forces you to keep a layer of manual work around it.
The risk of custom software isn't the code: it's ending up with a system only its author understands. That's why every project ships with automated tests, repeatable deployments and documentation, with the code owned by your company. And if what you need already exists off the shelf, we tell you before building it.
What we build
- 01
Platforms and APIs
The core system of your operation and the APIs that let customers, partners or other systems connect, designed for the volume you'll have, not just today's.
- 02
Back office, quoting tools and dashboards
Management systems, quoting tools, approval flows and live dashboards, built around your process, not the other way around.
- 03
Customer, distributor and supplier portals
Portals where customers or distributors place orders, check their account and download documents, connected to your ERP with per-user permissions.
- 04
Apps for the field, the warehouse and service points
Mobile and kiosk apps for your team in the field, in the warehouse or at the point of sale, connected to the systems you already use.
- 05
Maintenance and new phases
We stay on after delivery: updates, security patches and the next phases when the operation calls for them.
Every project ships with the repository in your company's name, automated tests, automated deployment, technical and user documentation, and infrastructure in your own accounts.
Risks we control
- Depending on a single person
- Repository, documentation and access in your company's name: any competent team can take over.
- Scope that grows unchecked
- Phases with acceptance criteria; anything new is estimated separately and you decide if it goes in.
- Not holding up under load
- Load tests before going to production and monitoring from day one.
- Breaking what already works
- API integration with your current systems and automated tests on every change.
What we build it with
For new builds we usually use TypeScript (NestJS and Next.js), Python (FastAPI), PostgreSQL and Redis, with Docker and continuous deployment on AWS or the client's own servers. We maintain what you already run in PHP, .NET, Java, Python, Node, Go or Ruby.
How we build custom software
01
Understand the process
In the technical review
We measure the layer of work around the current tool (hours, people, errors) and write the process on one page. If it doesn't fit on a page, there's nothing to build yet.
02
Scope and budget
Fixed proposal
We define the smallest piece that has to be built, what integrates with what you already have and what it costs to maintain. You get a fixed proposal with scope, cost and timeline.
03
Build and deliver
Weekly sprints
Weekly deliveries you can test in a real environment. You see progress working, not a status report.
Is it right for your company?
It's for you if…
- You run critical processes in spreadsheets or on a system nobody dares to touch.
- You pay per-seat licenses for software that doesn't fit your operation.
- Your edge lies in how you do something, and no off-the-shelf tool allows it.
It may not be for you if…
- You want a template website or a standard online store: we don't build template sites.
- The process is still being invented: it's better to start with a cheaper configuration or automation, and build once the rules settle.
Frequently asked questions
How do you decide whether to build or buy?
With four questions: whether it's what makes you win, how long you've been fighting the tool, whether the process is stable, and who will maintain it next year. If the answer is to buy, we say so even if we lose the project.
Is it cheaper than paying for SaaS licenses?
It depends on the number of users, how much you have to bend your operation to the tool, and who will maintain the software. We run the numbers with you: licenses and the manual work around them against the cost of building and maintaining. If the SaaS is cheaper, we tell you.
What if the scope changes mid-project?
New work is estimated separately and you decide whether it goes in now, in the next phase or not at all. The agreed scope, cost and dates don't change without your written approval.
Which languages and technologies do you work with?
Yes. We maintain what you already run in PHP, .NET, Java, Python, Node, Go, Ruby or Delphi. For anything new we choose technology your team can maintain and that has long-term support.
Who maintains the system after delivery?
We put a number on maintenance before starting, not after. The answer to «who» has to be a name, not «we'll see»: it can be your team, us, or both.
Go deeper
Tell us what you want to build
In 30 minutes we look at whether to build, buy or configure it, and tell you even when the answer isn't to build.