Custom Systems
Most of the businesses that hire us have already been through a SaaS that almost fit. Airtable until it ran out of road, a CRM that asked for three clicks per action, a no-code tool that charged per user. They end up doing the real work in a side spreadsheet and using the SaaS only so the reports look formal. When this happens the answer is not another subscription, it is a system built for how your operation runs.
What we build
Systems built from scratch in Node.js and Next.js 15, over PostgreSQL, deployed on Coolify over Hetzner or on the infrastructure you prefer. Client portals, internal tools for your team, unique workflows that do not exist in any SaaS, dashboards connected to your operation, integrations against the tools you already use. The code is yours from the first line.
The fitness coach case is the long example. We built the WhatsApp agent on Twilio, the lead database in PostgreSQL, the Next.js dashboard with the live agent view and the historical view, the connectors against Meta Leads Centre, and the authentication. All in three weeks. No templates, no wrappers, no dependency on an external platform that tomorrow changes its pricing. The full case study is published.
How we work
Discovery on a call with Javier. Map of the operation: which tasks each person does, which data travels between the tools, what breaks today and why. From there we shape the system plan, split into pieces you can see move one at a time. The first piece is live in week one, the second in week two, and so on.
Every Friday a demo. You open the system, use it in front of us, tell us what grates, and the next week we come back with the changes. Prices are fixed from the start: we lock the scope in the discovery call and we do not touch it mid-project unless you ask. The first three months of support are included.
screenshot
Part of the fitness coach custom system: the historical view over PostgreSQL, with the 1105 leads from before the agent categorized by campaign and region. Three weeks of build, code owned 100% by the client.
FAQ
Which stack do you use by default and why?
Node.js for the backend, Next.js 15 for frontend and API routes, PostgreSQL for data, Coolify over Hetzner for deployment. We pick this stack because we know it deeply, it is cheap to run, and it lets you move to any other host without rewriting. If your case asks for something different, we talk it through.
What happens to the code when the project ends?
It is yours. Repo in your GitHub organization, deployment docs, infrastructure credentials in your name. If tomorrow you decide another team should take over the project, you hand them the repo and it runs. We keep no keys.
What if in six months we need to add something?
The first three months of support cover small changes and fixes. After that you can hire us by the hour for what you need, or hand the code to another team. Because the system is written in modular pieces, adding a new piece does not force a rewrite of the rest.