GIFFInternal systems
and automation

GIFF LTD / Leicester / Internal business systems

Software machined to fit how your business actually runs.

Illustrative photograph of blue anodised machined parts on a dark workbench
Builds
Internal systems
Removes
Repeated manual steps
Owned by
You, outright
Image
AI-generated, illustrative

GIFF designs and builds internal business systems and process automation for organisations that have outgrown spreadsheets, email chains and copy-and-paste. Purpose-made tools for stock, orders, jobs, approvals, scheduling and reporting, built with the people who use them every day.

Put a process on the benchSee the systems

01 / The job

Most businesses run on a hidden machine.

Behind every order, invoice and job sheet is a sequence of manual steps: a spreadsheet exported from one system and pasted into another, an email that has to be forwarded to the right person, a figure checked by eye every Friday. Each step is small. Together they eat days every month and make the business depend on whoever knows the sequence.

We find that machine, take it apart and rebuild the parts that are worth rebuilding as reliable software. Some of it becomes a proper internal system with its own database and screens. Some becomes automation that moves data between tools you already own. Some stays manual, because it should.

We are a software company. We do not sell a platform, a subscription or a set of templates. Everything we build is made for the client and handed over in full.

02 / Parts list

What comes off our bench

Types of system GIFF builds
PartWhat it doesTypical inputs
Operations systemsTrack jobs, orders, stock or assets through each stage with clear owners and states.Your current spreadsheets, forms and job sheets
Workflow automationMove data between your accounting, CRM, email and storage tools without retyping.Access to the tools' APIs or exports
Approvals and requestsPurchase requests, holiday, expenses or changes routed to the right approver with a record.Your approval rules and thresholds
Scheduling toolsAllocate people, vehicles, rooms or machines with conflict checks and a shared view.Resources, constraints and booking rules
Reporting pipelinesPull figures from several systems into one consistent, scheduled report.The reports you assemble by hand today
Internal portalsA single place for staff to find forms, records and current procedures.Documents and the questions staff ask most
Detailed specifications
Illustrative macro of a blue anodised part with drilled holes

We measure twice. Build once. Then hand you the drawings.

Every project starts with measurement: the real steps, the real volumes, the exceptions that happen every week. Only then do we decide what to build. And when it is built, you get the source code, the documentation and the knowledge to run it.

03 / Interactive

Put a process on the bench

List the steps of one process that annoys you, mark how often each happens and whether it follows a rule. The process bench sorts them into automate now, systemise, and leave manual, with a reason for each. It runs in your browser and stores nothing.

Open the process bench
  1. Export orders to CSVAutomate
  2. Check stock by eyeSystemise
  3. Call customer about delayKeep manual
  4. Copy totals into reportAutomate

04 / Shop-floor method

From survey to handover

Op 10

Survey

We spend time with the people doing the work, watch real cases and collect the spreadsheets, forms and exports involved. Output: a process map and a list of candidate improvements with rough effort.

Op 20

Drawing

A written specification and screen prototypes for the parts worth building, with data model, integrations, exclusions and a price. You approve before we cut anything.

Op 30

Machining

Fortnightly releases to a test environment your staff can use. Real data imported early, so problems with it surface early.

Op 40

Fit and handover

Go-live with a fallback plan, training at the bench, a short operator manual and full technical documentation.

The full method

05 / Good fit, poor fit

Good fit

  • Ten to a few hundred staff with processes that have grown by accretion
  • Data spread across a few tools that do not talk to each other
  • Someone in the business who owns the process and can make decisions
  • A willingness to simplify the process, not just digitise it

Poor fit

  • Needs a regulated system certified to a specific standard we do not hold
  • Wants a public consumer app rather than an internal tool
  • Expects a fixed price before any survey of the process
  • Needs round-the-clock on-call engineering

06 / Tolerances

Stated tolerances

Ownership You own the code, data and hosting accounts. No lock-in clauses.

Estimates Given as ranges with stated assumptions, revised in writing if assumptions change.

Integrations Built only on documented APIs or agreed exports; fragile links are flagged before build.

Security Least-privilege access, encrypted transport, secrets out of code. Not a certified security provider.

Hours Monday to Friday, 09:00 to 18:00 UK time (Europe/London, GMT/BST). No 24/7 promise.

Claims No invented clients, savings figures or case studies on this site.

All tolerances

07 / Spec library

Notes from the workshop

08 / Inputs and outputs

What goes in, what comes out

You supply

  • A process owner who can decide within a couple of days
  • Real examples, including last month's awkward cases
  • Test access to the tools we need to connect
  • A few hours of staff time each fortnight to try releases
  • Honest answers about which steps people quietly skip

You receive

  • A working system in hosting accounts registered to you
  • Source code in your repository with a readable setup guide
  • An operator manual written in your team's own terms
  • A data and integration map showing what talks to what
  • A walkthrough so a different developer could take over

The usual trade-off is between speed and fit. A connector service can join two tools in an afternoon, but every edge case becomes a manual workaround. A purpose-built system takes longer, yet absorbs those edge cases properly. We price both routes where both are realistic, and say which we would choose with our own money.

09 / Questions at the bench

Questions we are asked

Should we buy software rather than have it built?

Often, yes. If an established product covers most of your process, buy it and we can automate the gaps around it. We build when your process is genuinely specific or when joining several tools is the real problem.

Which technologies do you use?

Mainstream, well-supported ones, chosen so that another developer can maintain the result. We explain the choice in the specification and avoid anything exotic without a clear reason.

Can you work with our existing database?

Usually. We assess its structure and quality during the survey and will tell you if cleaning or migration is needed first.

What happens after go-live?

Optional maintenance from the maintenance bay: fixes, updates and small changes during working hours, under a written agreement.

Already running a GIFF system?

Report faults or request changes at the maintenance bay. We need the screen, the time and what you expected, never passwords.

Maintenance bay

Bring us the process nobody wants to own.

Describe it in a few sentences. We reply within two working days with questions or a suggested survey.

Open a job ticket