Answers to the questions we get most often about building custom software: when it makes sense, what it costs and how the process works.
Custom software makes sense if you find yourself in one or more of these situations:
A good rule of thumb: if you are adapting your processes to the software rather than the other way around, it is time to weigh the options.
Off-the-shelf package: designed for a broad audience. You adapt your processes to the software.
Custom software: the software adapts to you, not the other way around.
The downside of custom software is the higher initial investment. But in the long run you have full control over functionality, roadmap and costs. You are not dependent on the decisions of a package vendor.
We build a range of software solutions, depending on what your organisation needs:
Because we own the full stack, you have one point of contact for the entire software solution.
We choose the technology based on your specific requirements. In most projects we work with:
During the intake meeting we always explain why we make a particular choice, so you understand what you are getting.
Yes. We have extensive experience integrating with systems such as AFAS, Exact, SAP, Salesforce and custom APIs. Middleware that automatically synchronises data between systems is one of our specialities. This prevents double data entry and manual transfers.
During the intake meeting we assess which integrations are needed, which APIs are available and what limitations exist on the side of the existing systems. This information goes into the quote.
Integrations with poorly documented or legacy systems require more work and can affect the timeline. We are upfront about this.
Yes, both. Many of our projects consist of a combination: a web application for the administrator and a mobile app for the end user. Because we own the full stack in-house, you have one point of contact.
The price depends on the complexity and type of solution. As a guideline:
Factors that drive the price: the type of solution (web, mobile or platform), the number of screens and workflows, the desired integrations and the complexity of the design. We work on a fixed day rate and produce a detailed quote per phase. After an intake meeting we know enough to give you a realistic estimate.
It varies per project. As an indication:
We work in two-week sprints. After each sprint you have a working version to test and provide feedback on. That way you do not discover something works differently than expected only at the end of the process.
Absolutely. We work in two-week sprints. After each sprint you receive a working version to test and can give feedback directly.
You do. The source code is entirely yours after delivery and payment. We hand over the code via a Git repository of your choice.
It depends on the scale of the software. Average annual maintenance costs range from €2,000 to €8,000.
Each quarter we issue an advisory report with recommended work:
You decide which work to commission. There is no mandatory maintenance contract. Deferring maintenance builds up technical debt that requires a larger catch-up effort later.
Yes, we do this regularly. We always start with a technical review: code quality, architecture, dependencies used and known pain points. Based on that we give honest advice: continue on the current codebase, partially refactor, or start fresh. That advice is always in your interest.
Bring as much as possible to the first meeting: access to the repository, technical documentation and a list of known issues or limitations in the current software.
Let's grab a coffee. Tell us about your idea and we'll give you our honest take on what's possible.
Schedule a call →