Bespoke web applications

Starting from your process, not a template

Off-the-shelf software imposes a way of working. When your business does not fit, teams recreate the real process alongside it, in a spreadsheet. A bespoke application starts from what you actually do.

What we build most often

• Client portals: documents, case tracking, correspondence
• Management tools: cases, stages, assignments, deadlines
• Dashboards aggregating data from several tools
• API connections to your existing software
• Fine-grained roles and permissions, down to field level
• Export and activity log, for audit

Progressive rollout

We ship in usable increments rather than all at once: your teams learn as it grows, and the switch from the old tool happens without stopping work.

Timeline and budget

From €20,000 and six to ten weeks for a first scope in production.

The signs that a bespoke tool is justified

Your teams keep a spreadsheet alongside the official software. The same information is entered twice in two different tools. One step of the process happens by email because the software does not allow for it. You pay per-user licences for features nobody opens. An Excel export serves as the monthly report, rebuilt by hand every time.

Each of these symptoms costs hours, almost never quantified. Quantifying it is the first step of scoping, and it is also what honestly says whether the project is worth starting.

The screens where adoption is won

An unadopted internal tool is entirely wasted money, and adoption is decided on three screens: the list that lets someone find a case in two seconds, the daily data-entry form, and the view that tells each person what to do today. That is where most of the design time goes — not on the management dashboard, which impresses in a demo and serves nobody day to day.

Data migration, the most underestimated line

Ten years of spreadsheet data contains duplicates, fields repurposed from their original use, dates in three formats and comment rows in the middle. We always plan a consistency check and an anomaly report before switchover, rather than discovering the problem in production — where it costs ten times more.

What is included

• Scoping workshop with your actual users, not just management
• Mockups of every screen, desktop and mobile
• Development, roles and permissions down to field level
• Migration of your existing data, with an anomaly report
• API connections to the software you already run
• Export and activity log, for audit
• Training in groups and written documentation
• One month of warranty after go-live

What is not included

Redesigning your business processes. We start from what you actually do, we flag steps that look avoidable, but we do not run your organisational project — that is a different trade from ours.

Progressive rollout

We ship in usable increments rather than all at once: your teams learn as it grows, and the switch from the old tool happens without stopping work. A big-bang go-live on a Monday morning is the scenario that fails most often.