Services

Custom systems

Marketplaces, QR menus, email systems, accounting tools and company-specific applications built around the way the business actually works.

The problem we usually find

The business runs on a spreadsheet nobody trusts and a process that only one person understands. Off-the-shelf software forces the operation to change shape around the tool, and the parts that matter most are the parts it does not cover.

How we approach it

We map the workflow as it is actually performed, including the exceptions people work around. Then we build the smallest system that removes the failure points, with real access control and an audit trail, rather than a platform that needs its own administrator.

What you receive

A system built to your operation — marketplace, internal tool, ordering or menu system, business email, or a bespoke application — with the access rules, data handling and support arrangement agreed before a line is written.

Who it suits

Businesses whose operation has outgrown a spreadsheet or a standard tool: companies that run orders, quotes, bookings, stock or email through a patchwork of files, and groups that need a marketplace or a menu and ordering system built around their own rules. It suits a process that only one person understands and that the business now depends on.

What we need from you

The people who do the work, for an hour each, so the process is recorded as it is done. The spreadsheets, forms and documents used today, including the messy ones. A named owner who decides what the system must do first. Where the data lives now, and who may see it.

What this covers

Workflow mapping
The process as it is actually performed, including the exceptions people work around, written down and agreed before anything is built.
The application
The smallest system that removes the failure points: an internal tool, an ordering or menu system, a marketplace or a business email setup.
Access and audit trail
Roles and permissions that match who may see and change what, and a record of who did what and when.
Data and migration
Existing spreadsheets and records imported into a structure that can be searched and reported on, with data handling agreed up front.
Support arrangement
How the system is hosted, maintained and supported, agreed before the build starts so there is no surprise afterwards.

How the work runs

Workflow
We watch and record how the work is really done, including the exceptions, and list what must change.
Scope
The smallest system that fixes the failure points is defined in writing, with the access rules, the data handling and the support arrangement.
Build
The system is built in stages that you can use and test. Each stage is checked against the real workflow, not a demonstration.
Launch and support
Data is moved across, people are shown how the system works, and the agreed support arrangement starts.

Questions before you start

What kinds of systems do you build?

Marketplaces, QR menus and ordering systems, business email systems, accounting tools and internal applications built around one company’s way of working. Some are shown in our work. Confidential ones are described without client details.

Why not use off-the-shelf software?

Often you should. Standard software is cheaper to start with, and we say so when it covers the need. A custom system makes sense when the parts that matter most are the parts the standard tool does not cover, or when the business would have to reshape itself around the tool.

Who owns the data, and who can see it?

The business owns its data. Access is controlled by role, so each person sees and changes only what their job needs, and changes are recorded. Data handling, including how data can be exported, is agreed before the build starts.

What does the quote depend on?

On the number of users and roles, the number of processes the system covers, the data to be imported, any connection to other tools and the support arrangement. A short review of the workflow comes first, so the quote reflects the real process. No price is published.

Who looks after the system after launch?

The support arrangement is agreed before the build starts: hosting, updates, backups and who to call. Active clients keep a direct line for changes and critical support when it matters. This is a working arrangement, not a guaranteed response time.