Portals, internal systems and SaaS, built in stages.
We develop customer portals, internal systems and SaaS products. We start with a focused first version, with the value of each stage defined before work begins.
For SMEs and larger companies that need a system of their own
Your operations live in spreadsheets
Orders, appointments or stock in files that overwrite one another. With a system of your own, each piece of data is entered once and everyone sees the same version.
Your customers are asking for a portal
They want to see their orders, download invoices or raise complaints without phoning. A portal serves them at any hour and takes repetitive questions off your team.
You have an idea for a SaaS product
You want to validate a digital product and charge by subscription. We start with a small first version and grow it with usage data.
Your current system cannot be touched
Every change breaks something else. We replace it one part at a time, without halting your operations.
What every project includes.
01
Discovery and scope
We map the process, the users and the data. We define what goes into the first version, what is left for later and the number the system has to move, such as hours of data entry or errors, so we know whether it worked. If you prefer to explain it in conversation, we will arrange a short call.
02
Product design
Flows, screens and a clickable prototype you test before we write any code. Correcting things at this stage avoids reprogramming later.
03
Development in sprints
Short cycles according to the size of the project. In each one you see new features working and review them in staging before they reach production.
04
Connection with your systems
The components communicate through documented interfaces, so the system connects with your ERP, your CRM or an app. We define what data travels in each direction and how often.
05
Environments and releases
Local, development, staging and production, with automated deployments from GitHub. Every change reaches production by the same route.
06
Infrastructure
Containers and isolated virtual machines, with backups and monitoring, on Brova Cloud or on your own server. The system can be moved, copied and scaled without reinstalling anything.
07
Quality and testing
We use AI to write and review code faster and to generate automated tests. Every change is reviewed by a member of the team before it is released.
30 days of follow-up
For the 30 days after launch we monitor the system and fix whatever is needed. It is included in the project.
Each new stage is then agreed with its own scope and value.
We split the system into parts so that a change in one does not affect the others. This is known as MACH architecture: microservices, API-first, cloud-native and headless.
Each function, such as orders, invoicing or customers, is an independent component and, if one needs more capacity, it scales on its own. The components communicate through documented interfaces, which is how they connect with your ERP, your CRM or an app.
Everything runs in containers and can be moved, copied and scaled without reinstalling anything. The part the user sees is separate from the logic, so you can change the design without touching the system.
Building this way takes a little more work at the start and avoids rebuilding parts as the system grows. If what you need is small, we will tell you so in the proposal.
Systems that are already in production.
Each project tells the story of the problem, the decisions we made and what changed for the client.
A focused first version, so you can start using it quickly
Code and documentation that you own
Hosting on Brova Cloud, if you choose it
Launch and 30 days of follow-up
What people ask us most
MACH stands for microservices, API-first, cloud-native and headless. In practice, it means building the system from independent components that communicate with one another. It takes a little more work at the start and avoids rebuilding parts as the system grows.
At least a week. The final timeline depends on the scope, and in the proposal we define what goes into the first version and how long each stage takes.
With the analysis and the scope. On the first day we send you that first step: how we understood your process and what would go into the first version.
Yes. We will arrange a short call to understand your process. Request the call.
Yes. The code and the documentation are yours, and we hand them over to you.
Yes, after reviewing it. First we diagnose the code and the infrastructure and tell you what is worth keeping and what should be replaced.
Yes, to write and review code faster and to generate automated tests. Every change is reviewed by a member of the team before it is released.
Articles on custom software.
What we learn from every project, told through real examples.
Docker
Proxmox
GitHub
n8n
Payload CMS
Cloudflare
Power BI
Joaquín Martinez Herrera 2 min read
