Contract software ERP · CRM · management system integrations Testing and maintenance

Custom software development for your processes.

Does your process live across Excel, email, PDFs and an ERP that talks to nobody? We build the software that connects them. Integrated with the systems you already use, tested with your users, maintained over time.

Let's talk about your project See a real case

Peer-reviewed research published by Elsevier

1.5 days

instead of 50 person-days
T&B Associati

800

pages of PDF orders
imported · Podartis

400+

candidates imported
Arethusa

Who it's for

Do you recognise any of these situations?

The same data is entered two or three times, in different systems, by different people.
An Excel sheet has become a critical system and only one person knows how to use it.
Orders, documents or requests arrive as PDFs or by email and someone copies them by hand.
Your ERP doesn't do what you need and replacing it would cost too much.
Your current software no longer has a supplier to maintain it.
You have a process to digitise and no product on the market really covers it.

How we work

Four steps, each with a result you can verify.

Process and requirements analysis

We map processes, users, data and integrations. We deliver scope, priorities, risks, acceptance criteria and a written proposal.

First paid phase

Phased development

Short, verifiable releases. Each phase ends with a feature your users can try, not with a progress percentage.

Verifiable releases

Testing and release

Tests, security checks and acceptance testing against the criteria agreed at the start. Technical and user documentation delivered together with the software.

Documented checks

04 · Ongoing management

After release, the software has to be maintained. The fee describes activities and responsibilities: updates, fixes, security patches, monitoring and backups where agreed, and support with agreed response times.

What you receive

What we deliver, in black and white.

Scope document with processes, integrations, priorities and acceptance criteria.
Working software in an agreed production environment: your servers or a European cloud.
Tested integrations with your ERP or management system, CRM, email and document archives.
Results of the checks: what was tested, how and with what outcome.
Technical and user documentation.
A clear agreement on code and licences, written before we start.

Published case · T&B Associati

From Excel to the ERP: 50 person-days in 1.5 days.

An entire project lived in Excel sheets and had to be moved into the management software. Doing it by hand would have taken about 50 person-days. We built an automatic migration that intelligently filled in thousands of cells: 52,000 hours entered, 23,000 cells filled, 1.5 days of work, 180% ROI.

We applied the same approach for Podartis (800 pages of PDF orders imported automatically into the ERP, with anomalies flagged to an operator) and for Arethusa (over 400 candidates imported from shared mailboxes into the HR platform).

Time and cost

What makes time and cost vary.

We don't publish a single price list because two "similar" projects can differ by an order of magnitude. These are the factors that weigh most, and that we clarify in the initial analysis:

Number of processes and users involved.
Integrations: how many, and how well documented the systems to connect are.
Quality of the starting data: clean, scattered, duplicated.
Security and regulatory requirements that apply to your case.

Tell us about the process you want to fix.

The first call is free and without obligation. We tell you straight away whether custom software makes sense, or whether something that already exists is enough for you.

Let's talk about your project

Frequently asked questions

Before we start, people usually ask us:

Do we have to rewrite all of our existing software?

Almost never. If software already exists, we assess it and tell you in writing what to keep, what to improve and what to replace, with our reasons. Often the best solution is new software that works alongside the existing one.

Do you integrate with our ERP or management system?

It is the most frequent part of our work. First we check how the system exposes its data (API, database, exchange files) and what the contract with its vendor allows, then we design the integration and test it with real data.

Who owns the code?

We put it in the contract before we start: which developments are yours, which reusable HTX components we license to you, and how you export data and code if you ever change supplier.

How much does it cost and how long does it take?

It depends on the number of processes, integrations and users, and on the quality of the starting data. The first call is free. Process and requirements analysis is the first paid phase and ends with a written scope, plan and estimate: you decide whether to continue knowing what you are buying.

What does maintenance include?

The activities written into the contract: updates, fixes, security patches, monitoring and backups where agreed, and support with agreed response times. No vague promises of unlimited assistance.

Already have a prototype or software that needs securing?

See from prototype to production and software security.