Skip navigation, go to main content
Contact

Software written around your organisation's processes

For when your processes do not fit off-the-shelf software, and bending those processes to the software costs more than building anew. We develop to order, deliver in increments, and hand back the source code together with the documentation.

Process

Five steps, delivered in increments

Each step has its own deliverable. Your organisation sees working software early instead of waiting until the final acceptance date to find out what was built.

  1. Clarify the requirements

    We work with the actual users, not only with the person who signs the contract. The result is a description of the business processes, a prioritised list of functions, and the technical constraints.

    Deliverable Specification and estimate

  2. Design and agree the interface

    We build designs of the main screens for your organisation to review and comment on before any coding starts. Changing something at this step costs many times less than changing it once the code is written.

    Deliverable Approved design

  3. Development in increments

    We deliver in increments of two to four weeks, each with working software for your organisation to try. Nothing is held back for a single hand-over at the end.

    Deliverable Working software after each increment

  4. Testing and acceptance

    Functional testing, load testing where the system has requirements for concurrent users, and a security review before it goes into use.

    Deliverable Acceptance record

  5. Hand-over and warranty

    We hand over the source code, technical documentation, operating documentation and user training. Warranty runs for the period stated in the contract.

    Deliverable Source code and documentation

Technology

Technologies in use

We choose technology to suit the problem and what your technical team can take on — not whichever technology is currently in fashion.

Group Technology
Server-side languages PHP, Python, Go, Java, C#, Rust
Web front end JavaScript, TypeScript
Mobile applications React Native, Flutter
Databases PostgreSQL, MySQL, MariaDB, Oracle, MongoDB
Runtime infrastructure Virtual servers, S3 storage, Redis, Kafka

A long list is not a strength if only one person can work in each technology. For a system your organisation will use for years, we recommend choosing a widely used platform so that someone can take it over later — even if that someone is not us.

Scale

Three scales we commonly see

To give your organisation a sense of the workload before we talk. The exact scope and timeframe are agreed after the requirements step.

2–4 months

A single business module

Managing one specific process, a moderate number of users, few integrations with other systems.

4–8 months

Several linked modules

Multiple processes connected end to end, permissions across several levels, integration with existing systems.

Requires bespoke design

A system used across many organisations

High load requirements and complex integrations. A design consulting step is needed before the scope can be estimated.

Before you sign

Three questions worth asking

Why is there no off-the-shelf product?
We develop to order; we do not sell packaged software by industry. If your organisation needs a ready-made product at low cost, buying a commercial product on the market makes more sense — bespoke development is only worth doing when the business processes are genuinely different.
Who owns the source code?
Your organisation does, stated in the contract. It is handed over with technical documentation sufficient for another team to take it on. We do not retain source code in order to tie clients in.
Who operates the system after hand-over?
Your organisation operates it, or signs an operating contract with us. Both options are prepared for from the outset — the operating documentation is part of the hand-over, not a chargeable extra.

After hand-over

Once delivered, the software still needs servers, a database and someone on call when an incident occurs. Your organisation can handle that itself or sign an operating contract — both are prepared for from the outset.

Start with a requirements session

We listen to the business problem, define the scope and give an initial estimate. If an off-the-shelf product solves the problem at lower cost, that is the option we recommend.