hilda business opens soon. Demos are already available.

Book a demo

Custom development

A need no module covers? We build the missing one, inside the same software, on the same data, with the same permissions.

The eight modules cover what repeats from one company to the next: invoicing, selling, tracking projects, holding stock. They do not cover what makes your trade yours.

When what you need exists nowhere, the usual answer is a spreadsheet on the side, or a second piece of software that never talks to the first. We offer a third: writing the module that is missing , inside hilda business.

What "inside the software" means

A custom module is not an application parked next door. It lives where the others live, and it inherits everything from them:

  • the same data — your customers, your products, your documents. Nothing to copy, nothing to synchronise, nothing that drifts apart one day;
  • the same permissions — your users, your roles, your organisation. No second password, no second list of people to keep up to date;
  • the same interface — your teams do not switch tools, they find one more entry in the menu;
  • the same billing — one more line on the subscription, not a parallel contract.

This is also what separates a module from an integration. An integration links two pieces of software and inherits both release calendars. A module has only one: ours.

Three shapes, depending on what is missing

A whole module. Your trade has a notion nobody else has — site tracking, a round book, a regulatory register. It deserves its own screens and its own rules.

An extension of an existing module. The need is close to what exists without being identical: one more field, a particular calculation, a document to produce in an imposed format. It is often the cheapest answer, and the one we look for first.

A bridge to a third-party tool. You keep software you do not want to give up, and we make the information flow between the two in the right direction.

How it goes

  1. We look at the real work. Half a day, on site or by video, with the people who will perform the task every day. Not a specification written in advance.
  2. We quote a written scope. What is included, what is not, and what will wait for a second stage. A firm quote, not a range.
  3. We deliver in usable slices. The first slice is already good for something. We correct alongside you rather than disappear for three months.
  4. It becomes a module like the others. Maintained, updated, backed up, and covered by the same support.

What we turn down

We do not take on development we could not maintain three years from now. A module with a single author and no successor is a debt you would carry, not us.

We also refuse to rewrite an existing module identically for one customer. When a need is a good one, it is almost always good for others: it then belongs in the standard module, and you no longer pay for its upkeep alone.

What it costs

On request , always, and never before seeing the real work. An estimate given over the phone is a wrong estimate — in one direction or the other, and both cost you.

Two markers all the same. Extending an existing module is usually counted in days; a whole module, in weeks. And digital investment remains 120% deductible until 31 December 2027, development included.

Let us talk about what is missing

Half an hour is enough to know whether it is a module, an extension, or already possible without writing a line.

hilda business

Your business copilot, one module at a time.