Skip to content
Lebtaglebtag

Custom software development

Not every problem fits an off-the-shelf product. When the process is the company's edge, bending the business to the available software costs more, over time, than building what the business actually needs.

We build web, mobile, desktop applications and Chrome extensions — and often a combination of them, because part of the problem only gets solved on the user's own machine.

When it makes sense

  • The process is the edge

    Your operation does something no market system covers, and adapting the business to the tool means losing the advantage.

  • An integration nobody offers

    Systems that need to talk and don't, with your own rules in between.

  • Something has to run on the user's machine

    Digital certificates, local file access, fiscal printers, credential vaults. The web can't reach.

  • An MVP to validate before investing heavily

    A small, real version, live, to find out whether the idea holds.

How we do it

  1. 01

    We start with the critical path

    The first delivery is the part that proves or kills the idea, not the login screen. It lets you see it working early and change course while that's still cheap.

  2. 02

    We pick mature stacks on purpose

    Next.js, PostgreSQL, n8n, C#/Avalonia when it's desktop. Technology without surprises is what makes shipping in weeks possible — and what any team can maintain afterwards.

  3. 03

    We ship to production early

    A real environment, monitoring and automated deploys from the first week. Software that only runs on the developer's machine isn't a delivery.

  4. 04

    We hand over the keys

    Repository, infrastructure and credentials are yours. Documentation and handoff are part of the scope, not an extra.

What you get

  • An application in production, with automated deploys
  • Repository, infrastructure and credentials in your name
  • Technical and operating documentation
  • Monitoring and a clear support path
  • Handoff to your team or to another vendor

Where we've applied it

FiscalRural is our own product from zero to launch: a Next.js app on Vercel, an n8n and PostgreSQL backend, a Chrome extension that carries data into the tax authority's software with no retyping, and a land-value database covering 2,700+ municipalities. Hubfiscal adds to that a C#/Avalonia desktop app with a local credential vault and auto-update.

Questions about custom development

Do you build mobile apps?

Yes. We assess case by case whether the best path is a native app, a hybrid one or an installable web app, because the answer changes with what the app needs to access on the device. Many cases that arrive asking for an app are well served by an installable web app, which ships faster and doesn't depend on store approval.

After delivery, who maintains it?

You decide. Since the code and infrastructure are yours, either your team or another vendor can take over. We also stay on for maintenance when it makes sense for both sides — but that's your choice, not a contractual lock.

Can we start small?

That's what we recommend. A lean first version, live, with the critical path working, teaches more in two weeks than three months of documents. Our own products started that way.

Other services