Software development
Build software around your business, not the other way round.
A business application exists to remove one specific friction: duplicate data entry, a spreadsheet the whole company depends on, a process nobody follows end to end. We build those tools, and we also know how to work with what is already there.
The situations we see most often
The need rarely arrives as a specification. It arrives as a symptom.
Your business runs on a spreadsheet nobody dares to change any more.
Your teams re-enter the same data into several tools.
The off-the-shelf product you use covers most of it, and you bend your business around the rest.
An internal application works, but its author has left and nobody can evolve it.
You have a clear project and no team available to build it.
A critical process depends on what two people remember.
What we take on
From building a complete application to picking up code written by someone else.
Business applications
- Internal web applications and user portals
- Management tools fitted to an existing process
- Roles, permissions and approval workflows
- Document generation and exports into your formats
Taking over existing systems
- Onboarding onto an application you inherited
- Maintenance handover on code written by a third party
- Progressive modernisation rather than a full rewrite
- Extraction and migration of historical data
- Reinstating tests and automated deployments
Integrations
- Connection to an ERP, a CRM or an accounting system
- APIs for your partners or for your own applications
- Automation of recurring file and data exchanges
- Taking over fragile flows built up over the years
A business application is not an interface
What you see on screen rests on layers that decide how long the product survives. We handle all of them, and we connect them to what you already run.
- UsersWho uses it, with which permissions, under which conditions
- InterfaceScreens and journeys, built around what has to be fast to enter
- Business logicYour rules, your approvals and your edge cases
- APIs & integrationsThe exchange point with the rest of the information system
- DataThe model, the history, and what you must be able to export
- InfrastructureWhere it runs, how it ships, how it is restored
What you already run
- ERP, CRM, accounting
- Existing internal applications
- Your partners' tools
The integration layer is what decides whether a new tool joins your information system or merely sits on top of it.
How a project runs
We deliver in usable increments. You see the software working during the project, not only at the end.
- 01
Understand the business
We observe the real process, including the workarounds teams have invented. That is often where the actual requirement is hiding.
- 02
Set the scope
What is indispensable on day one of production, what comes next, and what turns out never to be needed.
- 03
Build in increments
Usable versions at short intervals, tested with the people who will actually use them.
- 04
Go live
Data migration, cutover, training and close support during the first days.
- 05
Keep it moving
Business software lives. Fixes and new functions decided from observed usage.
At the end of the project
You must be able to hand the work to your own team or to another supplier without a negotiation. This is what is handed over.
- 01
The source code
Repository, history and access rights come to you in full.
- 02
Documentation that helps
What is needed to pick the project up, not a binder nobody will open.
- 03
A reproducible environment
Installation, configuration and deployment described and automated.
- 04
Your data
Structured, exportable, with no dependency on a proprietary format.
- 05
A handover
Transfer of access, a walkthrough with your teams, and answers to the questions that come with taking over.
What we build on
We pick technologies you will still be able to have maintained in five years.
Web applications
Fast, accessible interfaces that run in a browser, with nothing to install on workstations.
Back-end and APIs
Structured, testable, documented services built to outlast a technology fashion cycle.
Databases
Data models shaped around your business, relational by default.
Continuous integration
Automated tests and deployments, so that releasing stops being an event.
How we can work together
Depending on whether you need a project delivered, reinforcement inside your team, or a technical partner over time.
Custom project
We take responsibility for the whole thing: analysis, design, development, integration, delivery and evolution.
Learn moreConsulting & team extension
Our consultants join your team to bring the skills you need: development, functional analysis, technical analysis, business analysis or architecture.
Learn moreIT partner
A lasting point of contact to maintain, evolve and connect the software and systems your business runs on.
Learn more
Related use cases
Modernise business software
The application still works but is becoming expensive to maintain, hard to change and dependent on a handful of people.
Automate a business process
The same information is entered several times, approvals happen by email, and nobody can say where a file currently stands.
Connect systems that don’t talk to each other
Your ERP, your CRM and your business tools each hold part of the truth, with no reliable exchange between them.
Frequently asked questions
Do we have to rewrite everything?
Rarely. A full rewrite is expensive, slow, and loses business rules accumulated over years. In most cases it is better to isolate the part that genuinely causes problems, rebuild that, and let it coexist with the rest. We will tell you when a rewrite is the best option — and, more often, when it is not.
Can you take over an application written by someone else?
Yes, this is a frequent request. We start with an onboarding phase: reading the code, mapping dependencies, checking what is actually deployed and what is actually tested. That phase gives an honest picture of what can be taken over as is and what needs work first.
How are timelines estimated?
After scoping, not before. An estimate given without understanding the business process commits nobody. We break the work into deliverable increments and re-estimate as the scope firms up — a change of priority mid-project costs far less than a gap discovered at delivery.
Do you work with our in-house developers?
Yes. Depending on the case we reinforce an existing team, take a scope autonomously, or do both at once. The model is decided at scoping and can change.
What happens if we want to stop?
You leave with the code, the data and the environments. That is why we automate deployment and document the handover from the start: a transition should not be a project in itself.
Let’s talk about your project
Tell us which process is getting in the way today. We will tell you frankly whether custom software is the right answer.