Concrete projects, measurable results

Teams were already planning their jobs in shared calendars, yet nobody had the overall picture — neither the geographic spread nor the real workload per technician. Rather than imposing yet another data-entry tool, the application aggregates the existing calendars, geocodes free-text job addresses and plots them on a map alongside workload indicators. No double entry: the calendar remains the source of truth, the tool merely reveals it.

Sizing gas networks relied on a spreadsheet mastered by a handful of engineers: the pressure-loss calculation was sound, but impossible to pass on and unusable in the field. We moved that calculation engine into a standalone web component, embedded both in a dedicated application and in the client's existing dashboard — one implementation of the maths, two entry points, no chance of the two drifting apart. It works offline and pulls its reference data from a central server.

Advisors ran their audits on paper, then re-entered everything back at the office, losing accuracy at every copy. The tool covers two distinct audit frameworks, one of them a climate-resilience assessment, and generates the PDF report handed to the farmer. The real difficulty was logistical: a desktop client deployed across dozens of advisors, usable without reliable connectivity on the farm, with an automatic version check at launch and authentication tied to the organisation's directory. Multi-season tracking lets the same farm be compared year on year.

Born from an internal need: tracking time spent without forcing on the team a tool they would end up working around. The challenge in timesheet software is not technical but behavioural — hence entry cut back to the bare minimum and automatic reminders. Architecturally, a configurable rules engine absorbs each organisation's specifics: service types, validation thresholds, approval chains. A connector layer then syncs the data into the HR tools already in place, rather than claiming to replace them.

Reselling second-hand clothing at scale means qualifying thousands of items one by one — that is where the bottleneck sits, not in the selling. We industrialised the whole chain: online drop-off, a photo-capture app, a detection model that automatically locates and classifies the garment in the picture, label printing and stock management. Business reference data — brands, sizes, price grids — stays in the teams' own spreadsheets and syncs into the API: the technology bends to the business, not the other way round.

Purchase orders and invoices arrived through every channel — email, attached PDFs, XML feeds — then moved through informal approvals. The platform imports Peppol documents, extracts their lines from the UBL format, normalises them and routes them through a multi-role approval workflow: buyer, accountant, management. Once approved, invoices flow on to Sage BOB together with their suppliers, accounting codes and analytical sections — accounting re-keys nothing. The API contract is versioned and shared between front end and back end, so both evolve together without silent regressions.

Umpires are assessed from the stands, often in venues where the network is unusable. The application is therefore offline-first: the structured form, the score calculation and the PDF report generation all run entirely in the browser, and the file is saved straight to the assessor's device. An interrupted assessment — flat battery, closed tab — is restored exactly as it was. Multilingual, installable like a native app, and with no back end for the federation to maintain.

Konekto took over this craft printing house in Ottignies, running since 1953, which had no online presence worthy of its trade. The site presents its four crafts — announcements and invitations, graphic design, offset and digital printing, finishing — each with its own quote request, and gathers the B2B offer into enterprise packs. The technical choice is deliberately minimal: static pages, no CMS and no framework, and audience measurement through a Matomo we host ourselves rather than Google Analytics. A site a small business can keep alive on its own, and that will not need rebuilding in three years.

Elgacert is the mandatory route for certifying gas and electrical installations: a regulated platform whose SOAP interface is strict and unforgiving. We isolated that complexity inside a dedicated module — a client generated from the official WSDL, signed and secured exchanges, data normalisation, rejection handling — which exposes a simple interface to the rest of the system. Teams file their certification requests, track their status and consult the full history there, without ever talking directly to the platform or re-keying anything.

Answering a tender means reading hundreds of pages without missing a single requirement, then producing a structured response and a compliance matrix. We modelled that work as four specialised agents — requirements analysis, architecture, UX, writing — chained across seven tasks that produce the response and its appendices: a requirement-by-requirement inventory, screen sketches, a compliance matrix. The system is parameterised by the company's context (stack, methodology, working language) and reviewed by a human at every step. It is our own tool, proven on our own bids before being offered.

Checking an electrical inspection report means reading scanned PDFs line by line to cross-check two documents. The module chains Google Cloud Vision OCR over each file with a language-model analysis, and returns a structured JSON verdict rather than prose someone has to interpret again. The engineering point lies elsewhere: the prompt is stored in the database and split into three blocks, only one of which is editable from the back office. The business tunes the checking criteria without a redeployment, and without ever being able to break the guardrails that frame the request.

Submitting a bid for a European public contract demands hard guarantees: bidder identity, timestamped submission, integrity and confidentiality of the sealed bids until the official opening. The platform frames the entire cycle — assembling the file, secure submission, then comparative analysis by evaluators against structured criteria. The bulk of the work is not the interface: it is the traceability and non-repudiation rules imposed by regulation, which have to hold at Union scale.

The kilometre charge generates offences in volume, and each one opens a case that may run all the way to appeal. The system covers that full cycle: receiving the reports, notifying the offender, processing appeals and tracking payments, with dedicated interfaces for regional officers. The dominant constraint is not functional but combinatorial — volume crossed with statutory deadlines: every step is timestamped and every decision must remain justifiable years later.