Skip to main content

Business Systems

Bespoke business software built around your work.

Built in Horsham for SMEs across Sussex and Surrey. Quoting, jobs, stock, collections, compliance paperwork. When no off-the-shelf product fits how you really work, we build the system that does — on the web, on tablets in the field, or both, talking to one server you control.

Built to be inheritedAnother engineer can pick it up

Fixed priceMeasured scope, agreed in writing

Twenty years of thisWeb, database and embedded systems

Plain-English definition

A business system is the thing your day passes through.

Not a website and not a spreadsheet. It is where the enquiry becomes a quote, the quote becomes a job, the job becomes an invoice, and somebody can answer “where is it?” without ringing round. Most firms have one. Plenty are running it on paper, memory and four spreadsheets that only agree on a good day.

Off the shelf first. Bespoke only when it does not fit.

If a product on the market does the job, buying it is cheaper than commissioning anything — and we will say so. Bespoke earns its place when the way you work is the reason customers choose you. does a product fit? → buy it  |  does it nearly fit? → connect it  |  neither? → build it

What we build

Six kinds of system, and when each is the wrong answer.

Most commissions are one of these. The honest version of each includes the case for not doing it, because that is the conversation you want before the money is committed rather than after.

01 · The one your day runs through

Line-of-business systems

Quoting, job sheets, works orders, stock, scheduling, collections and the compliance paperwork attached to them — one record moving through the stages your business actually has.

Typical shapeA web application your staff sign in to, with the reports and paperwork it produces built in rather than exported and reformatted.
When not to botherWhen a mainstream product covers ninety per cent and the last ten is a preference rather than a difference.
02 · The tablet, phone or scanner

Field and shop-floor apps

Capture at the place the work happens — a collection, a delivery, an inspection, a goods-in check — instead of on a pad that gets typed up hours later.

Typical shapeA web app installed to the home screen of an iPad or Android tablet, working with no signal and sending when it has one.
When not to botherWhen the same person types it up ten minutes later at the same desk anyway.
03 · The bit between two products

System integrations

Two pieces of software you intend to keep, and the one piece of information they will not pass between them without a person in the middle.

Typical shapeA small, boring, well-logged service that moves records one way and tells somebody clearly when it cannot.
When not to botherWhen either product is up for replacement inside a year. Wait, then bridge once.
04 · The one your customers see

Customer-facing portals and ordering

Account customers placing orders, checking prices, tracking jobs or downloading their own paperwork, instead of emailing someone who then keys it in.

Typical shapeA portal on top of the system you already run, so there is one set of prices and one set of stock figures rather than two.
When not to botherWhen your customers order by phone because they want the conversation. Automating that loses you the relationship.
05 · The paperwork mountain

Document and data pipelines

Information trapped in PDFs, emails, scans and spreadsheets, turned into records something can actually query.

Typical shapeAutomated intake with the uncertain cases held for a person to confirm, never silently guessed.
When not to botherWhen the documents arrive in a format the sender would happily change if asked. Ask first.
06 · The one holding it together

Rescuing a system you already have

An old application still doing its job, an Access database nobody dares touch, or a spreadsheet that has quietly become critical infrastructure.

Typical shapeDocument what it does, put it somewhere supportable, then replace it in pieces rather than in one frightening jump.
When not to botherWhen it genuinely still works and the risk is theoretical. Working software is worth more than tidy software.

Systems that work away from the desk

The job happens in a van. The record should start there.

Drivers, fitters, collectors, inspectors and warehouse staff are not sitting at a PC. So the job gets written on a pad, brought back and typed in — the same information entered twice, hours late, by somebody who was not there. That is the single most common thing we are asked to fix, and it is one system in three places: a device where the work happens, a server that holds the truth, and the office screens that need it now.

In the fieldTablet or phone. Works with no signal.
Your serverOne record, one set of figures
The officeOn the PC as it lands

No second keying, and no waiting for the van to come back

Find your workflow

Business software for the job in front of you.

Each page explains the work, the existing software we would check and a sensible first project.

For local projects, see our work across Sussex and Surrey.

The parts that are actually hard

Anything works on a desk with full signal. That is not where it will run.

A remote component is not a phone-shaped version of the website. These four are where field systems fail, and they are the reason this work is worth commissioning properly.

It has to work with no signalBasements, yards, steel buildings and rural roads. The device holds the work and sends it when it can, rather than showing an error and losing it.
Sending has to be honestA lost reply is not a lost job. The device confirms what the server actually holds before it tells anyone it is done, and says plainly when something is still waiting.
It has to suit the hands using itGloves, sunlight, one hand free and a tablet that is three years old. Large targets, few taps, and text sized for reading at arm's length in a van.
The office has to see it arriveThe point is not the app. The point is that the person on the PC has the collection, the delivery note or the inspection before the driver gets back.

We have built exactly this: collection drivers who used to fill in carbon-copy books and key the same lines into a PC on return now record each collection on a tablet at the customer's premises, with the office holding it minutes later. The old process was the site's first shape of wasted time — typing it in twice — with a half-day delay attached.

Where it runs

Your server, or hosting we manage. Not a decision we make for you.

Field devices have to reach the system from outside your building, and there is more than one honest way to arrange that. We will tell you which one your situation argues for and what each costs to keep running.

On your own serverThe system and its database stay on hardware in your building. Suits firms with a server room, existing on-site systems to sit beside, or data they would rather did not leave.
Hosted and managed by usYour own instance, never shared with another customer, from £45 a month. Suits firms with no server, no IT person and no wish to acquire either.
A mix of the twoThe database stays with you and only the part the field devices talk to is exposed. Common where the office system is already on site.
Written into the quoteWhichever it is, where it runs, who can reach it and what it costs to keep running are agreed before the build, not discovered at handover.

The evidence

The first system we built is still running after twenty-one years.

A Sussex sign maker's quote, job sheet and invoice system went live in 2005 and is still used every working day. We did not host it, licence it back to them or charge them a fee to keep it switched on. That is what owning a system is supposed to look like, and it is the standard the rest of this page is written against.

Read the story of the sign-making system →

Safe to buy from a small supplier

The exit is part of the build.

  • Source code included
  • Documented for another engineer
  • Your data exportable, on request, in a usable format
  • The written right to take it elsewhere, with no exit fee
  • Optional support, not a permission fee

Questions people ask

Before commissioning a system.

Compare bespoke software with an off-the-shelf product.

Is this the same as business process automation?

Related, but a different purchase. Automation removes a repeated task from a process you already have. A business system is the process — the place the work is recorded and moves through its stages. Many projects start as one and turn out to be the other, which is what the audit is for.

Can staff use it on tablets or phones as well as PCs?

Yes, and that is often the point. We build web applications that install to the home screen of an iPad or Android tablet, keep working when the signal drops and send the work through when it returns. The office sees the same records on a PC.

Do you build native iPhone and Android apps?

Usually we do not need to. A web application that installs to the home screen behaves like an app, updates without an app-store review and runs on both platforms from one codebase. Where a job genuinely needs native hardware access we will say so and price it honestly rather than pretending the web can do everything.

Will it work with the software we already have?

That is normally the requirement, not a bonus. Typical connections are Microsoft 365, Sage, Xero, SQL Server, Access, CRM, e-commerce and EPOS platforms, and the spreadsheets between them. Replacing what works is the last resort, not the first proposal.

Do we own what you build?

Yes. Source code and documentation are included so another engineer could support it, and the right to take it elsewhere is written into the terms.

What happens if you are not around in ten years?

That is the right question to ask any small supplier. The answer is architectural rather than reassuring words: you hold the code, the documentation and the data, the system does not check in with us to keep running, and nothing we build expires if you stop paying us.

How is a project priced?

Fixed price, quoted from measured scope. Builds start from £1,495, and larger systems are quoted in stages so each one delivers something usable. See the full pricing path.

Where do you work?

Across Sussex, Surrey and the South East from Horsham, on site where the work needs to be seen in person. See the areas we serve.

Start with the job, not the specification

Describe how the work moves through your business today.

You do not need a written brief. Tell us what gets written down, where it gets typed in again and who is waiting for it — that is enough to say whether this is worth quoting.

Send an enquiry