Management software, written to measure.

Web, mobile and desktop applications, online platforms, management suites, and also the takeover of existing code: migrating a PHP application to a modern stack, adding tests to a project that had none, bringing back into service a piece of software whose author can no longer be reached.

• Web and mobile applications (Android, iOS), programming interfaces, third-party integrations
• Multi-tenant platforms: per-customer data isolation, usage-based billing
• Management suites: accounting, invoicing, inventory, production
• E-commerce sites and marketplace connections
• Takeover and modernisation of existing code, adding test coverage
• Embedded applications, virtual and augmented reality

On a management project, business logic is written in isolated, tested services, never in the screens, which makes it possible to change the interface without redoing the calculations.

We maintain and extend applications written in WLangage under WinDev, WebDev and WinDev Mobile, and we migrate them to web technologies when the time is right: TypeScript, React, Next.js, a PostgreSQL database — bearing in mind that many of these applications have been running for ten or fifteen years and carry business rules nobody has documented anywhere but in the code, which makes the takeover more delicate than a mere port of the screens.

• Maintenance and extension of existing WinDev applications
• WebDev sites and portals, web services and programming interfaces
• WinDev Mobile applications for Android and iOS
• Migration from WLangage to TypeScript, React and Next.js
• Transfer of HFSQL databases to PostgreSQL or SQLite, with integrity checks
• Extraction and documentation of the business rules buried in the existing code
• Gradual coexistence: the old and the new run side by side for the duration of the switch

A migration is not done in one block: we start with a peripheral module, put it into service next to the WinDev application, then move forward module by module, the two systems sharing the same database during the transition; it takes longer than a complete rewrite announced for six months, and it avoids the production outage a failed single cut-over produces.

Native and cross-platform applications for phones and tablets, published on Google Play and the App Store, with the whole chain taken care of, including the developer accounts, the store listings and the app store review, which turns down a first submission more often than one would imagine.

• React Native applications, one code base for Android and iOS
• Native Kotlin and Swift applications when the hardware requires it
• Progressive web applications, installed without going through a store
• Offline mode and synchronisation on reconnection
• Barcode scanning, camera, geolocation, notifications
• Publication on Google Play and the App Store, updates and incident follow-up

Offline use is the point that decides the architecture: a field application that loses the network must keep recording, then reconcile without duplicates or losses, which is designed at the outset and not along the way.

We integrate language models into production applications, where the difficulty is not the demonstration: it lies in the traceability of the answers, the cost per request, the response time and the behaviour of the system when the model is wrong, knowing that an assistant answering without citing its source does not reach production at a customer subject to audit.

• Business agents and assistants connected to the information system
• Retrieval-augmented search over your documents (RAG), with source citation
• Structured extraction: invoices, payslips, contracts, receipts
• Classification, summarisation, translation, speech recognition
• Automation of repetitive tasks
• Compliance audit against the European AI Act

The models used (Claude, Gemini, OpenAI) are called from the server, so that no API key ever ends up in the visitor’s browser.

Database migration, warehouse construction, dashboards, of which the longest part is almost always the takeover of existing data: duplicates, dates in the wrong format, free-text fields to requalify.

• Takeover and cleansing of existing data
• Data warehouses and lakes, feed pipelines
• Dashboards and management indicators
• Relational, graph and vector databases

Deployment to production, monitoring, backup and restoration, bearing in mind that a recovery plan is something you test: until a restoration has been carried out for real, nobody knows how long it takes.

• Continuous deployment, staging and production environments
• Monitoring, logging, alerts
• Backups and proven restorations
• Application security audits

Audit of an existing system, project costing, drafting of a specification, arbitration between a bespoke development and off-the-shelf software, it being understood that a share of these engagements ends with the recommendation to buy rather than build.

• Technical audit and mapping of the existing system
• Specification and costing by work package
• Assistance in choosing a software package
• Outsourced technical leadership

Records of processing, impact assessments, retention periods, audit trail, all subjects that are handled during design: adding a reliable audit trail to an application already in service often amounts to rewriting its core.

• GDPR compliance: records of processing, impact assessments, retention periods
• Preparation for the European Artificial Intelligence Act
• Reliable audit trail and evidential archiving
• Electronic invoicing: Factur-X, EN 16931, Chorus Pro filing

An example of a concrete constraint: art. L102 B of the French tax procedures code requires six years of retention, art. L123-22 of the French commercial code requires ten for accounting records, so an automatic purge policy keeping the shorter period destroys records that are still required.

Sessions on your own use cases, code review with your developers, handover documentation, the goal being that your teams can make the application evolve without us.

• Workshops on your real use cases
• Code review and team coaching
• Operations and handover documentation