Custom Software Development
We work with businesses and the public sector, starting from their processes, data and procedures. We design custom software that fits the organization already in place and can evolve when needs, systems or ways of working change.
Clients who come to us are not simply looking for someone to write code: they are looking for a partner able to understand the process before building it, and to stay with it after release.
How the software is built, stage by stage.
AI supports the team across the stages of development, from analysis to testing.
Analysis
A study of processes, users, data, existing systems, integrations and goals.
Design
Solution architecture, components, integrations, security and development planning.
Development
The software is written following what was laid out at the design stage.
Testing
Functional and integration testing before release, to check behavior, flows and interoperability with the other systems.
Release
A gradual, controlled go-live, including training for the people who will use the software.
Maintenance
Fixes, updates and further development when needs or regulations change.
Go-live is not the end of the project.
The same team throughout
Whoever ran the analysis stays the point of contact afterwards: there is no need to explain the company from scratch at every call.
Fixes and adjustments
Problems are fixed and the software is adjusted when the company’s needs or the regulations change.
The project does not rest on one person
Environments, versions and changes stay documented, so the software does not live in the memory of whoever wrote it.
Response times agreed up front
How and how quickly we respond is agreed together with the project, not at the moment it is needed.
Before you start
How long does it take to go live?
The timeline is defined during the analysis phase, before development starts. Timescales stretch when there are many processes to cover or when multiple system integrations are required, and shorten when the scope is clear-cut. The date comes from there, not from a rough guess.
Does it integrate with the systems we already use?
With ERP systems, accounting and the other systems already in use, and with external services. Integrations are defined during design, not after release.
Do we have to change the way we work in order to use it?
Not necessarily. The software is designed around the procedures and roles already in place. If the analysis brings to light a step that could be improved, we point it out and weigh up the best answer together.
Where is our data hosted?
It depends on the project. The software can sit on the company’s own servers or on cloud infrastructure, and the choice is made at the design stage, taking into account the constraints of whoever will use it.
How do you handle security, access and permissions?
Access and permissions are designed alongside the company’s roles, at the design stage: each user sees and can do what their role allows. Authentication, activity logging and backups are part of the project, not late additions, and data is processed in line with GDPR obligations.
Do you use AI in software development?
Yes. AI supports the team in analysis, design, development and testing, improving the efficiency and quality of the process. Design decisions and responsibility for the result stay with the team.
Who looks after the software after release?
The project stays with the team that knows it. Environments, versions and changes stay documented, so maintenance and support do not depend on one person being available.
Have a business process that off-the-shelf software can’t handle?
It starts with a conversation about the process: if the right answer is a product that already exists, we say so.