Skip to content

Services

Subscribe to something already built, or commission software to your own requirements.

Two commercial models, one delivery discipline. Which one fits depends on how close your operation is to the way the catalogue already works — and we will tell you honestly which side of that line you are on.

What we do

Two ways to work with us

Subscribe to something already built and supported, or commission software to your own requirements. The delivery discipline is identical — only the commercial model changes.

Server racks in a data centre
Subscription

SaaS products

Hosted, maintained and updated by us. Your team gets the capability without the upkeep, on a monthly subscription with no large up-front build.

  • Live in days, configured to your operation
  • Updates and security patches included
  • Your data exportable at any point, in full
A team scoping work at a whiteboard
Tailored

Custom software

Built to your requirements, from a single internal tool to a platform your business runs on. Scoped with you, built in stages you can see, handed over documented.

  • Fixed written scope, signed before any build
  • Progress visible throughout — slippage flagged early
  • Source, documentation and training at handover
How we work

A delivery process you can see into

No black box. Every project runs through the same six stages, and at each one you know what we are doing and what we need from you.

Stage four is a gate, not a milestone: nothing reaches you until it has been tested by someone who did not build it.

  1. Step 1 Requirements & scoping

    We write the scope down — including the assumptions and what is explicitly out of it — and you sign it off before a line of code is written.

    We do
    Draft the scope, the assumptions and the exclusions
    From you
    One decision-maker who can sign it off
  2. Step 2 Allocation & scheduling

    Every deliverable gets a named owner and a date. You know who is building your work and when it lands.

    We do
    Assign the build owner and publish the dates
    From you
    Confirm the dates work around your operation
  3. Step 3 Build

    Progress is visible throughout. If something is going to slip you hear it early, not on the due date.

    We do
    Build in stages and show you each one
    From you
    Answer questions within two business days so the build does not stall
  4. Mandatory gate

    Step 4 Internal testing

    A mandatory gate, tested against the signed scope by someone who did not build it. Nothing reaches you until it passes.

    We do
    Test independently, log every defect and fix it
    From you
    Nothing — this one is entirely on us
  5. Step 5 Your acceptance testing

    You test a working product and log anything you want changed. Every item is tracked to closure, in writing.

    We do
    Provide a test environment and a shared defect log
    From you
    People with time actually set aside to test it
  6. Step 6 Go-live & handover

    Deployment, documentation and training, then transition into the support agreement with your response times in it.

    We do
    Deploy, document, train and hand over
    From you
    Sign the support agreement and name your contact
Next step

Tell us what is not working

A short conversation is usually enough to tell whether one of our products fits, whether it needs configuring, or whether you are better off with something built to order. We will say which.