Services

Custom software development

Designing applications adapted to a specific process rather than adopting a generic tool.

• Applications dedicated to a specific business process
• Dashboards and admin interfaces
• Internal portals for a team
• Desktop utilities for recurring tasks
• File-processing tools (sorting, conversion, checks)
• Internal data management applications
• Proofs of concept
• Minimum viable products (MVP)

Examples: order-tracking tool, stock management interface, field data-entry application.

Who it's for: small companies, freelancers and teams who haven't found a tool that matches how they actually work.

Expected result: a tool matching the existing process, documented and able to evolve.

Limits: custom development requires time for scoping; it is not suited to very generic needs already covered by existing software.

Automation

Removing or reducing manual repetitive tasks.

• Importing and exporting data between systems
• Automatic document generation
• Scheduled tasks (regular processing)
• Automatic reports
• Synchronisation between several systems
• Notifications (email or another channel agreed with the client)
• Processing CSV, Excel, JSON and API data

Examples: weekly activity report generation, automatic merging of several CSV exports, notification when an anomaly is detected.

Who it's for: organisations regularly performing the same manual operations on files or across several tools.

Expected result: less time spent on repetitive tasks and fewer data-entry errors.

Limits: automation reliability depends on the quality and consistency of the source data; a verification step is usually recommended.

Backup, monitoring and reporting

Tools to schedule, monitor and check backups on the client's infrastructure.

• Backup-job launchers
• Status checks and execution logs
• Integrity checks of backup files
• Preparation of restore-test scenarios
• Connection to an existing NAS
• Connection to S3-compatible storage
• Database backups (PostgreSQL, MySQL…)

Examples: dashboard listing the backup status of several servers, checksum-verification script after a backup.

Who it's for: organisations with a NAS, a local server or databases that need regular backups.

Expected result: better visibility on backup status and easier-to-organise restore checks.

Limits: these tools are not a complete security strategy and do not guarantee restoration. See the dedicated page for details on these limits.

Integration, connection and migration

Connecting existing tools to avoid double entry and manual re-keying.

• Connecting to existing APIs
• Receiving and processing webhooks
• Connecting several applications already in use
• Importing data from legacy systems
• Building adapters between two formats
• Preparing data migrations

Examples: synchronising orders between an online store and a management tool, periodic data transfer between two business applications.

Who it's for: organisations using several SaaS tools that should exchange information.

Expected result: consistent data across systems, without manual re-entry.

Limits: integration quality depends on the APIs available on the existing tools' side, which are not always documented or stable.

Maintenance and evolution

Ongoing support for a piece of software after it goes live.

• Bug fixes
• Updating technical dependencies
• Gradual feature improvements
• Maintaining and extending documentation
• Occasional technical support

Examples: annual update of the libraries used, adding a new filter to an existing dashboard.

Who it's for: organisations that already have custom software (built by this practice or by a third party).

Expected result: a tool that stays functional as your business evolves.

Limits: taking over an existing project requires a prior review of the code and the available documentation. See the FAQ.