Custom software development, from scratch or from the system you already have

When your process no longer fits in a spreadsheet or an off-the-shelf tool. The signs tend to be the same: the team copies data from one place to another, nobody knows which file is the right one, and customers ask by message what a portal could show them on its own.

Off-the-shelf software makes your company work its way. Custom software does the opposite: it captures your process as it really is, with the stages, permissions and documents that make sense for you.

For an electrical engineering company, with 137 projects in the system, it brings together each project's progress by stage, the customer portal, issuing and signing technical documents, and the finance dashboard.

See the case study →

Yes, and we start with an audit. Before changing anything, we review five areas: security and access, the database, business rules and existing bugs, the server and migration risk, and the screens. The result is a written report that says what works, what is broken and what it costs to fix.

On an inherited Symfony system, we audited and migrated it with 3,067 work orders preserved and Pix payments reconciled automatically. Before the migration, a full copy of the environment was stored off the server.

An inherited system is not a reason to rewrite everything. Often the code is reasonable and the problems sit in a few places; the audit shows where.

Yes, by changing it step by step. Every change goes in with a database backup first, database changes that only add (nothing is deleted to make room) and a test in a staging environment before it goes live.

That is how both phases of the electrical projects system went: the second phase added user management, a new stage in the workflow, a simpler project form and the finance dashboard, with a database backup before every change, without rewriting what already worked and without a new stack.

See the case study →

For a new system: Next.js for the screens, Node.js with NestJS behind them and PostgreSQL for the database, running in Docker on a Linux server. These are open technologies with plenty of developers who know them, which keeps you from being locked into one vendor.

When the system already exists, we work in its technology, including PHP and Symfony. We integrate payments, email, WhatsApp through the official API and the spreadsheets your team already uses.

In our own product, an event operations system with live headcount, door check-in and parking, the rules about who sees what live in the database itself, not just on the screen.

See the case study →

Yours. The code lives in your company's repository, the server and the domain are in your name, and we get access by invite. If you ever want to continue with another team, you hand over access and the system keeps running.

We document what we build: how to install it, how to back it up and where each business rule lives. We never ask for your password over chat.

Manni, who is a copywriter. A system has words too: the button, the error notice, the confirmation email, the message your customer receives. When the system talks to your customers, in a portal, an email or a WhatsApp message, the copy goes through her.

Clear words on screen mean fewer people asking by message what the system should have told them.

1. 01You tell us in writing what you need, on WhatsApp or on the platform where you found us.
2. 02If a system already exists, we audit it before proposing any change.
3. 03We close the scope in writing, split into phases, with what is in, what is out, and the timeline and price of each.
4. 04You approve the screens before development starts.
5. 05Each phase is delivered to a test environment for you to check, and only then goes live, with a backup.

The price is fixed per phase and comes from the scope. We don't publish a rate card, because a dashboard for your team and a system with a customer portal and payments don't fit on the same line. Working in phases also lets you use the first part of the system before deciding on the next.

After launch, monthly maintenance covers updates, backups and small changes, agreed per system.