T40 Systems · Bespoke Business Systems

“Off-the-shelf software does not fit how our business works.”

We build the focused tool, portal or system that off-the-shelf software does not cover.

Start a conversation How we fix it

Sound familiar?

The knot.

The work your business does best does not fit the software you can buy, so people fill the gaps with spreadsheets, email and memory.

Every workaround costs a little time and a little accuracy. Files live in five places. Clients email for updates because there is nowhere else to look. Registers are current the week before an audit and stale the week after. A bigger platform would make you change how you work to suit it, and still leave the awkward part by hand.

Three signs it’s this

  1. 01 People keep a spreadsheet open beside the software, because the software cannot do the job.
  2. 02 Clients ask for files, updates and reports by email, because there is nowhere else to get them.
  3. 03 Every product you trial solves most of the problem and none of the awkward part.

T40 answer · Bespoke Business Systems

The fix.

We build what is missing, and only that: a small tool for one awkward job, a secure space for your clients, a register or dashboard your team keeps up to date, or a system shaped to your process. Everything is built from proven parts, tested on real work, commissioned in the live business and handed over with documentation and training.

After Software shaped to your process, built from proven parts and handed over properly.

What we build

One method. Different jobs.

Find the sentence that sounds like your business. Each part is built the same way: inspected, scoped, built from proven parts, tested, commissioned and handed over.

01

Mini tools & workflow apps

“One awkward task wastes hours, but a full platform would be overkill.”

A small app for one job: a calculator, a checker, an intake form that routes itself, a quote builder. Small enough to ship quickly and simple enough for your team to run.

See one working · our own indicative estimator

02

Client portals & private workspaces

“Customers need one secure place for files, requests, tools and reports.”

One login for each client, with their files, requests, tools and reports in one place. Access rules are agreed before the build, not bolted on after.

03

Reporting dashboards & evidence systems

“Nobody trusts the numbers, and pulling the report together takes days.”

One view of the numbers, pulled from the systems you already run. Where a figure matters to a board, an auditor or a client, the evidence behind it is kept with it.

04

Compliance & operational registers

“Our registers are only up to date just before an audit.”

Registers for risks, checks, incidents and actions, with owners, due dates and reminders, so they stay current between audits rather than only before them.

05

Rapid prototype & proof build

“We have a promising idea, but we cannot justify a full build on a hunch.”

A working version, tested on real work, before anyone commits to the full build. You decide with evidence rather than a slide deck.

06

Retail risk, incident & security systems

“Incidents, cases and risk reports are scattered across forms, emails and spreadsheets.”

Incident logging, case tracking and risk reporting for retail and security teams, shaped by years inside retail loss prevention.

In writing

What you get.

The deliverables, plainly listed. If it's not here, ask — we'll tell you honestly whether it's included.

  • 01 A written scope: the finished job, what is in and out, the range and the assumptions
  • 02 A working system built from proven parts, around your data and your process
  • 03 Testing on real work before go-live, with the results written down
  • 04 Commissioning in the live business, with your team alongside
  • 05 Documentation, admin training and a support period of 30 to 90 days, depending on complexity
  • 06 Optional ongoing care: monitoring and planned improvements, only where the system needs them
A short process on purpose

How this one works.

No discovery phases that outlive the project. Just the steps that earn their place.

  1. 01 Inspect We watch how the work actually flows, follow real examples from start to finish and find where it breaks. Sometimes the answer is a product you can already buy; we will say so.
  2. 02 Design, scope and price The smallest system that fixes the problem, drawn before anything is built. You get the finished job, the range and the assumptions in writing.
  3. 03 Build from proven parts Standard components for the parts every system needs, so the budget goes on what is specific to your business.
  4. 04 Test and commission Tested on real work and real data, then switched on in the live business with your team alongside.
  5. 05 Hand over, then care if needed Documentation, training and an agreed support period. After that, ongoing care is available if the system needs it.

Why this matters

Off-the-shelf software is the right answer more often than not, and we will tell you when it is. When it is not, the gap gets filled by people: copying between tools, chasing updates and remembering what the system cannot hold. A focused build closes that gap without asking the business to reorganise around a platform.

Who this suits

  • Businesses running a core process on spreadsheets and email because no product fits it
  • Service firms whose clients need one secure place for files, requests and reports
  • Teams that must keep registers, evidence or audit trails current, not just before inspections
  • Founders with a promising internal tool idea who want to prove it before committing

When we would advise against it

  • A product you can buy already does the job. We will point you to it.
  • You want one large platform replaced across many departments at once. That starts with a Systems Diagnosis, not a build.
  • Nobody in the business will own the system once it is live. We would help you settle that first.
See the thinking at work

Proof and useful reading.

Examples and practical guides that help you judge the work before starting a conversation.

Asked, answered

The questions everyone asks.

If yours isn't here, ask it — we answer emails within 24 hours.

Q1 Why not just buy software?

Often you should. A Systems Diagnosis includes a build-versus-buy recommendation, and we recommend buying whenever a product fits. We build when the awkward part of your process is the part that matters.

Q2 How long does a build take?

Focused tools can ship in weeks. Portals and larger systems take longer, because testing, commissioning and handover matter. You get a written timeline with the scope before any build starts.

Q3 What does it cost?

We price the job rather than a package, so it depends on what the system has to do. Most Systems work starts with a Systems Diagnosis at £750, which ends with a costed next step. You can also get an indicative estimate straight away.

Q4 What happens after launch?

Every build includes a support period of 30 to 90 days, depending on complexity, set out in the scope before work starts. After that, ongoing care is available if the system needs monitoring and planned improvements.

Sound like your problem?

Tell us where it hurts. We’ll tell you honestly whether we can help — and what we’d do first.

Start a conversation Get an indicative estimate

First paid step · T40 Systems: Systems Diagnosis · £750

Every T40 Systems problem