01Bespoke software or an off-the-shelf product: how do you choose?
The right answer is often "the market", and we say so before writing a quote. Take an off-the-shelf product when your requirement is standard — accounting, payroll, point of sale, electronic signature, a generic CRM — because a vendor spreading its costs over ten thousand customers will always be cheaper than bespoke work, and because it handles regulatory updates on your behalf. Go bespoke when the way you work is precisely what sets you apart, when your teams paper over the software's gaps with spreadsheets and re-keying, when you pay licences for ten features and use two, or when nothing on the market talks to your other systems. The most reliable signal remains wasted time, measured in hours per week.
The decision grid we use during scoping.| Situation | Our recommendation |
|---|
| Standard, regulated requirement | Off-the-shelf product. We help you choose it and set it up. |
|---|
| Off-the-shelf product 80% suitable | Off-the-shelf product plus a bespoke add-on or a bridge. |
|---|
| A process specific to your trade | Bespoke, starting with the most painful part of the scope. |
|---|
| Shared spreadsheets now business-critical | Bespoke. The risk of error and loss already exceeds the cost of the project. |
|---|
| Requirement still unclear | Neither: a short scoping exercise first, free of charge with us. |
|---|
02How does a bespoke development project run?
In five phases, with something usable to show at every stage rather than one grand reveal at the end. Scoping: one to two weeks to understand the trade, write the user journeys and fix the scope of the first version. Prototypes: one to two weeks, clickable screens signed off by the people who will use them daily — the moment when changes cost nothing. Iterations: two-week cycles, each closed by a demonstration and a deployment to a test environment you can reach at any time. Delivery: migration of existing data, user training, supported go-live. Maintenance: fixes, enhancements and monitoring. A mid-sized business tool is usually delivered in two to four months.
1Scoping
The trade, the user journeys, the scope of version one.
1 to 2 weeks 2Prototypes
Clickable screens signed off by the users.
1 to 2 weeks 3Iterations
Two-week cycles, a demonstration at the end of each one.
4 to 12 weeks 4Delivery
Data migration, training, go-live.
1 to 2 weeks 5Maintenance
Fixes, enhancements, monitoring.
ongoing 03How much does a bespoke business application cost?
The price depends on the number of screens, the number of distinct user roles and the connections to other systems — not on how appealing the project is. Here is how a costing breaks down: scoping and prototypes, the first conversation remaining free; small business tool — one domain, a few screens, a handful of users, delivered in four to six weeks; full business application — several modules, permissions, data migration, two to four months; platform or client portal — external accounts, payments, volume, four to eight months; maintenance and hosting, per month. Every quote breaks the project into batches billed as they progress: you can stop at the end of any batch.
We never put a price on a vague project. If the scope is not clear, we start with a short fixed-price scoping exercise whose deliverable — journeys, prototypes, estimate — remains yours even if you have someone else build it.
04Which technologies do we use?
Proven, documented and widely used technologies — that is the first guarantee of reversibility: any competent developer must be able to pick the code up after us. On the interface: React, Vue and Angular, written in TypeScript. On the server: PHP with Laravel for classic business applications, Node.js when the front end and back end share one language, Python with FastAPI as soon as there is data processing or AI in the project. On data: PostgreSQL, with the Prisma ORM for a versioned schema and clean migrations, and Supabase when a database, authentication and storage foundation has to be running within days. On delivery: Docker and GitLab or GitHub. The final choice is settled during scoping, based on what you already run and the skills already in the building.
Our rule of thumb, stated plainly: Laravel for a business application with a back office and plenty of business rules; FastAPI for a pure API or a project that touches data and AI; Node.js when a single team has to hold both ends. On the interface, React by default, Vue when your in-house team needs to take over quickly, Angular when it is already the company standard. We never mix two front end frameworks in the same product.
Our own development is tooled with artificial intelligence: assisted generation, code review, test writing, documentation catch-up. The gain goes to time and cost, not to rigour — every line delivered is read by a human, and nothing ships without being understood. It is the same standard we apply at your premises on our AI projects: the machine proposes, the person decides.
When a project touches artificial intelligence, it joins our AI pillar: same people, same scoping method.
05Who owns the code at the end?
You do. Entirely, and it is written into the contract in black and white. Assignment of rights: the economic rights over the bespoke code written for you are assigned to you on delivery, at no extra cost and with no time limit. Permanent access: the code repository is in your name from day one; you do not wait until the end of the project to reach it. Hosting in your name: hosting, domain name and third-party service accounts are created under your credentials, not ours. Handover documentation: on delivery we provide the technical documentation another team needs to take the project on. If you ever decide to change supplier, you leave with everything.
- No mandatory subscription in order to keep using your software.
- A maintenance contract you can cancel, with no imposed minimum term.
- An export of your data in a standard format, at any time.