Service · Custom development

The application youwill findnowhere else.

When your trade has rules, steps and obligations no vendor has coded, two options remain: bend your organisation to the software, or build the software around your organisation. We do the second — always starting by redesigning the process, never by opening a code editor.

Describe your process
Typical duration

3 to 18 months, delivered by increments

First increment in production

Well before the end of the project

At the end

Code, data and documentation handed over

Foundations

What is in it, every time.

Eight foundations. They are not options: without them, a business application becomes the next problem to solve.

01

Single entry

A record is entered once and travels. That is the foundation: without it, everything else contradicts itself.

02

Versioned business rules

Scales, conditions, thresholds: configurable and dated. Next year's regulation is not a rebuild.

03

Approval chains

Who approves what, in what order, within what deadline. And what happens when that person is away.

04

Role-based permissions

Everyone sees what concerns them. Sensitive data does not wander off in an export.

05

Complete history

Every action logged: who, when, on what basis. Readable by an auditor, years later.

06

Integrations

Accounting, invoicing, payroll, directories, public systems. Your good tools stay — better wired in.

07

Generated documents

Decisions, certificates, contracts: versioned templates, justified content, evidential archiving.

08

Dashboards

Calculated at source, per role, in real time. Regulatory records come out of the same place.

Sequence

How an engagement runs.

The same sequence every time, whatever the size. You can stop at any step; so can we.

  1. Weeks 1 – 3

    Analysis of the real process

    At your offices, beside the people who do the work — not in a meeting room with an org chart. We record the friction, the manual tasks, the duplication, the error risk, and we cost them in hours per month.

    You receive: the map of the current process and of the target process.

  2. Week 4

    Written scoping and increments

    Scope, increments, delivery order, timeline and firm budget per increment, named team. The first increment is always the one that relieves fastest, not the one that is easiest to code.

    You receive: the scoping document. You decide with it, not on an impression.

  3. Increment by increment

    Building and go-live

    Each increment is used in production while the next one is built. Your teams watch the software grow and correct course along the way — that is where projects are saved.

    You receive: the code in your repository from the first increment delivered.

  4. At every switch

    Data migration and training

    History is migrated and reconciled, without loss. Training happens on your real cases. No downtime: the old and the new coexist for as long as it takes.

  5. End of engagement

    Handover

    Architecture and operations documentation, reproducible environments, data. Any competent developer can take over. That has been the goal since day one — not an exit clause.

Formats

Three shapes an engagement takes.

Not all of them need an eighteen-month project. Some are settled in a few weeks.

A few weeks to 3 months

The targeted integration

Two systems that do not talk to each other, a weekly export done by hand, re-keying that costs two days a month. We wire, reconcile and log. Your off-the-shelf software stays in place.

The best return, and the most often neglected.

3 to 8 months

One department's process

A spreadsheet that has become critical, a process that lives in email. We redesign it and carry it into a dedicated application, wired into the rest of the information system.

The most common case.

More than a year

The application that carries the business

The core of the business: several departments, thousands of cases, accounts to render, a history to migrate. Delivered in increments over more than a year, in production within the first months.

The most demanding. We take them.

Technology

And the technology?

Common, well-documented technologies, easy to hire for. We discuss them at scoping, never before: a supplier who opens with their technology stack has the wrong subject.

HostingOn your premises or with a European host, on an account in your name.
ComplianceGDPR by design, role-based permissions, every action logged.
Taking overReproducible environments, tests on the business rules, operations documentation.
MaintenanceA separate contract that can be ended. It never gates your access to the application.

Describe the process. We will tell you straight whether it should be coded.

hadi@peregrinesystem.io

A written reply within two business days. Signed. If an off-the-shelf product is enough, we give you its name.