Area 12 · Development and web

Bespoke software

Writing your own software is worth it in two situations: when your operating habits match nothing available on the market, or when bending a ready-made product costs more than building one. The rest of the time a careful configuration comes cheaper, and we will say so plainly. When the arithmetic falls the other way, we take the project end to end: discovery, wireframes, development in iterations, go-live, then the releases that follow. Everything happens remotely, over video calls and secure access.

6
services in this area
100%
of projects delivered remotely
EUR 95
per hour excl. VAT, billed by time
Mon-Fri 8:00-18:00
working hours, CET

How we invoice

The right contract follows from what you already know about the need. Agreeing a fixed price for a scope nobody has yet put on paper nearly always ends in an argument over what it covered.

Watch out: every addition is renegotiated Fixed price per stage Once the scope is on paper, approved and unlikely to shift
Watch out: somebody has to hold the line Time and materials, EUR 95/hour excl. VAT As the detail takes shape across the iterations
Watch out: a team with no priorities Dedicated team, custom quote When your roadmap stretches across several months
Minimal commitment Discovery alone You know where it hurts and have nothing to hand a supplier

Your contract states who owns the code. We propose assigning the economic rights to your company; how far that assignment reaches, and whether a different supplier may take the software further, deserve a reading by your lawyer before signing. The repository, the documentation and the installation procedure all come to you, so a handover stays possible, to your own people or to somebody else entirely. Open libraries stand apart: each keeps its own licence, and their inventory travels with the code.

How a project unfolds

The rhythm is steady: a demonstration every fortnight, on an environment your teams open themselves. Any gap between what you expected and what comes out shows up after a fortnight, not at the moment of signing the final acceptance.

01

First conversation

A short video call to understand the need and check that it really calls for development. Sometimes we point you towards an existing product instead: that costs us nothing and saves you an unnecessary spend.

02

Discovery and wireframes

Interviews with the people doing the work, the requirement written down, a diagram of the exchanges, clickable screens. This stage is billed in its own right and its output is yours, whatever happens next.

03

Iterations

A fortnight, a demonstration, an approval. The order of the work can be rearranged from one iteration to the next without renegotiating the contract as a whole, provided the overall volume stays where it was agreed.

04

Production and aftercare

The switch to production, user training over video calls and close attention through the first weeks. Past that point, if you wish, we continue under a maintenance agreement.

Questions and answers

Frequently it will, and saying so early costs us nothing. Where your activity fits inside Odoo, a well-configured accounting package or a properly thought-out CRM, configuration comes cheaper than fresh code. Bespoke earns its place where your method of working is itself the advantage, or where reshaping a packaged product ends up dearer than building. Discovery exists to set those two numbers side by side.

A figure announced before anyone has looked at the process is not an estimate, it is a wager. So we begin with discovery, billed separately, at the end of which you hold the written requirement, the schedule and the cost breakdown. What follows runs either as a fixed price per stage or on time and materials at EUR 95 per hour excl. VAT when priorities move along the way. A dedicated team over several months is quoted from the profiles involved.

Yes, once the code has been audited. We examine the architecture, the tests, the dependencies and the documentation, then write down what can carry on living and what is better rewritten. Two precautions beforehand: let your lawyer establish which rights belong to your company, and recover access to the repositories, servers and provider accounts, which go missing far more often than the source itself.

You leave with everything. The repository is handed over at each approved stage rather than only at the end, together with the deployment scripts, the architecture notes and the inventory of third-party components. Accounts with hosts and providers are opened in your company name from the outset, so that no access depends on us. An outside team should be able to pick the work up without calling us.

We work with local authorities and public bodies, remotely as we do with companies. Application documents and the submission of bids follow the public procurement code and go through the buyer profile named in the notice. On the technical side we account for the usual expectations: RGAA accessibility for online services, reversibility and open formats, hosting in Europe, and invoices filed through Chorus Pro.

Describe the problem in your own words

No specification is needed. Tell us which part of the work devours the most time and what ought to change. We will propose a way of working together and how long discovery would take.

When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.