Talk to us

Work

Real systems, shown as they are.

Our own system is shown in full, screen by screen. Client projects belong to somebody else’s business, so here we describe what each one was built to do, and talk them through in a conversation.

The route from public work to a released demonstration:

  1. Public work: What can be shown without conditions
  2. Request: You say what you want to see
  3. Release: We choose what fits your situation. Released by a person.
  4. Private demonstration: Access for a limited time

Shown in full

From a messy customer request to a reviewed quotation.

The system we run our own quotations and invoices on, followed through one quotation. A loosely written email goes in; a structured draft comes out; a person checks it and decides.

  1. The request arrives as an ordinary email.
  2. The system structures it and flags what it could not confirm.
  3. A person reviews it. Nothing is saved yet.
  4. Saving creates the draft and its number.
  5. The work continues, recorded rather than remembered.

Demonstrated in a controlled test environment with an invented customer.

Follow it step by step
The quotation form before saving, with three positions and a total of 3,380.00 euros.

Client projects

Two client projects, and what they were built to do.

Both are described without the client’s name and without figures. What we can say publicly is where the work started and what the system was built to change. We are happy to talk either one through.

OPERATIONS

Built so incoming reports are read and filed without anyone retyping them.

Starting point

  • Records were cross-referenced by hand across multiple spreadsheets.
  • The process was error-prone and kept the team off its delivery work.

What the system was built to do

  • Incoming reports are extracted, validated and categorised automatically.
  • A workflow routes the data into the correct database.
  • Summaries reach programme managers without manual intervention.

LOGISTICS

Built so the day’s data becomes a draft invoice that a person approves.

Starting point

  • Invoices were assembled from driver reports, fuel logs and delivery confirmations.
  • Late invoices were causing cash flow problems and client dissatisfaction.

What the system was built to do

  • Driver apps, GPS, fuel cards and delivery data run into one pipeline.
  • Draft invoices are compiled automatically and exceptions are flagged.
  • Approved invoices go out through the existing billing system.

What we can show, and what we cannot

Some of this work can be shown publicly. Running systems carry a business on them.

  • Published here

    Our own system, screen by screen. For client projects: where the work started and what was built. Figures only once we can evidence them.

  • Shown on request

    A walkthrough of how a project was approached, with no client data on screen.

  • Not shown

    Live customer environments, real records, anything that would put somebody's operation on display.

Demonstration

Tell us what you want to see.

We pick an existing demonstration that matches your situation and release it to you. We do not build a prototype for every request, and we do not put a client’s system on display.

Request a demonstration

Access is personal and time limited. You see only what has been released to you.