The CRM, and everything after it

Most systems stopat the sale.

Ours keeps going — through the quote, the order, the materials, the purchase orders, the workshop and the invoice. One system, white-labelled as yours, shaped around the way your business already works.

~19,000
Lines of our own PHP in the platform — no framework, no plugins
30,000+
Lines across the platform, the customer website and the design studio
15
Modules, from first enquiry through production to invoice
In use
Live on our hosting, in daily use, released to a schedule
The CRM

Everything you know about a customer, in one record.

It does the job a CRM is bought for, properly: who they are, who you spoke to, what was said, what they were quoted and what they bought. The difference is that every one of those records is wired into what happens next.

  • Customers, sites, delivery addresses and named contacts on one card
  • An enquiry pipeline with an owner, a next action and a date — nothing sits in an inbox
  • Quotes built from your product catalogue and priced from your bill of materials
  • Orders, documents, proofs and job history all hanging off the same customer
  • Search that finds a customer, a quote, an order or a job from one box
  • Roles and permissions, so the workshop sees jobs and the office sees money
Customer record — one thread
ENQ-1088Head covers & bag tags for the pro shop — samples sentPipeline
QUO-104424 × head cover set, embroidered crest — sent 4 MarchAccepted
ORD-1044Same number, now an order — due 2 AprilIn production
JOB-1044/2Station 2 — one cover scrapped, remake raisedRe-scheduled
INV-1044Invoiced — true cost recorded against the quoteClosed
FilesApproved proof, traveller, dispatch note, bench photographsAttached

Illustration of one customer record: the same reference from first enquiry to the invoice.

One database, both sides of the business

From the customer who orders it to the supplier who feeds it.

A CRM that only knows your customers can only ever solve half the problem. Ours holds the other half too — the materials, the suppliers, the lead times and the prices — which is the only way a quote can know what a job really costs before you send it.

Customers

Clubs, companies, contacts

Sites, delivery addresses, named contacts, payment terms, every enquiry, quote, order, proof and document, and the whole conversation history in one place.

Products

Your catalogue, properly described

Specification, materials, finishes, dimensions, prices, production times and the bill of materials behind each one — so quoting is a lookup, not a guess.

Suppliers

Who you buy from, and on what terms

Supplier records, their materials, prices, minimum quantities and lead times, with purchase orders raised against them and deliveries booked back in.

Stock

What is on the shelf, and what is promised

Live stock levels, what is committed to open jobs, what is on order, and what needs ordering today — valued, and reportable.

Jobs

What is being made right now

Every job, its stage, the hours booked against it, what passed, what failed, what was remade, and photographs from the bench.

Money

What it was quoted at, and what it cost

Quoted value, true material and labour cost, scrap, remakes and margin — per job, per product and per customer.

The difference

Where a standard CRM stops.

Buy a CRM off the shelf and it will manage your conversations beautifully, then hand the job to a spreadsheet the moment somebody says yes. That handover is where the money leaks out. The heading on each card is what you normally get; the text is what ours does with it.

Step 01 — a standard CRM gives you

Contacts and companies

Customers, sites, contacts and the history of every conversation — the same as any CRM, and the starting point for everything below.

Step 02 — a standard CRM gives you

A deal in a pipeline

The enquiry becomes a quote with real products, real specifications and a real price, drawn from your catalogue instead of typed in again.

Step 03 — a standard CRM gives you

"Closed won"

The quote becomes an order under the same number, with a required-by date the system checks against the workshop before you promise it.

Step 04 — a standard CRM gives you

An export to accounts

A bill of materials that prices the job before you commit, and stock that comes off as the work goes into production.

Step 05 — a standard CRM gives you

A task reminder

A shortfall that raises the purchase order itself, one per supplier, and holds it for management approval before it is sent.

Step 06 — a standard CRM gives you

A calendar entry

Finite scheduling into the hours the workshop really has, with anything that will miss its date showing red in advance.

Step 07 — a standard CRM gives you

A note on the record

A job pack and traveller printed for the bench, and tablets at each station recording time, quantities, scrap and photographs.

Step 08 — a standard CRM gives you

A report of deals won

What the job actually cost when it was finished — materials, labour, scrap and remakes — set against what you quoted.

None of that is a roadmap. Every line above is built, running and in daily use in a real workshop — which is why the list includes the unglamorous things a demonstration usually skips: the scrapped piece, the short delivery, the purchase order nobody approved.
On the floor, and in the customer's inbox

A workflow that walks itself, step by step.

Every job moves through stages you define — job pack, cut, assemble, finish, quality, dispatch — and the system knows which station is next, what it needs and whether it can start. Nobody has to chase a whiteboard to find out where something is.

  • Tablets at each station, built for the workshop: big buttons, PIN sign-in, gloves-and-sawdust friendly, and only the jobs that station needs.
  • Time recorded on the job, not on a timesheet written up on Friday — so job costing is real.
  • Quantities passed, failed, reworked and scrapped captured where it happens, with photographs from the bench.
  • Gates that stop trouble early — no approved proof, no printed job pack or no stock means the job cannot start, and someone is told why.
  • Automatic customer notifications as the job passes each stage: order confirmed, proof approved, in production, dispatched — branded as you, sent without anybody remembering to.
  • Exceptions surface themselves — a late job, a shortage or a failed check appears on the dashboard rather than in somebody's head.
Station 2 — assembly — tablet
JOB-104424 × head cover set — pack printed, proof attachedReady
TimerOn the job — 01:42 recorded so farRunning
Counts23 passed · 1 scrapped · photo attachedRemake raised
Customer“Your order is in production” — sent automaticallyNotified

Illustration of a station tablet: one job, what it needs, and what the customer was told about it.

Staying in touch

Your customer never has to ring you for an update.

Most of the time lost in a bespoke job goes on chasing: where is it, what did we agree, can you send that again. Every one of those is answered before it is asked.

  • WhatsApp them from their own record. The message is already written and addressed — add a photo from the bench and send. No copying numbers into your phone.
  • Invite them to their own login. One link, sent by email or WhatsApp. They set it up themselves; it arrives already knowing who they are.
  • Then they can see it all. Their saved designs, their proofs, their quotes, their orders and their documents — at eleven at night if that is when they think about it.
  • Documents sent and signed. A two-way record of what you sent them to review and what came back signed, sitting on the customer record where anybody can find it.
  • Automatic progress notices. Order confirmed, proof approved, in production, dispatched — branded as you, sent without anybody remembering to.
  • And it all comes back in. What they do on their side lands in your pipeline: a design saved, a quote requested, a proof approved.
A customer record in GTI Systems showing the WhatsApp message box, the portal invitation link and the record of documents sent and signed
One customer record: message them, invite them to their own account, and see every document sent and signed
Two things nobody expects

A code on the paperwork, and a line to the bench.

Both of these came out of the same frustration: the answer to “where is that job?” being a walk across the workshop, or a phone call to someone who is holding a glue gun.

Every traveller carries its own QR code

The code is generated with the job — nobody prints labels, nobody sticks anything on. Scan it with any phone and the job opens: what it is, whose it is, which stage it has reached, what has passed and what was scrapped.

  • A sheet of paper on a bench becomes a live record, from any phone in the building
  • The office can scan a job on the way past instead of asking
  • The bench scans to open their own station without typing a job number
  • Customer, product, material, finish, quantity and the approved proof — all on the one sheet

The traveller opposite is straight out of the system — and yes, that code scans.

A traveller worksheet generated by the platform, with a QR code, the job specification, its production stages and sign-off boxes
The traveller — printed with the job, scannable from any phone
The internal team chat, showing messages between the office and the workshop about a live job
The same conversation appears on the tablets at the stations

And a chat that reaches the shop floor

Built into the system, not another app to install. Whoever is out — the owner, the sales side — signs in from anywhere and talks to the people making the thing.

  • It lands on their tablet, at the station, where they are already working — and gets dealt with there and then
  • Message everyone, the office, or one person — an operator only sees what was sent to them or to all
  • About the job in front of them — a question answered in thirty seconds instead of a walk across the building
  • Nothing to buy, nothing to set up — no group chat on somebody's personal phone, and it stays inside the business

On a customer visit and the club asks when their covers will be ready? Ask the bench and answer them while you are still sitting there.

The system itself

Not mock-ups. The actual screens.

These are photographs of the platform running, on sample data. You can sign in and click around the same system yourself — the link is at the bottom of this page.

The GTI Systems dashboard showing stock warnings, open quotes, active orders and jobs in production
Dashboard — what needs attention this morning, before anybody asks
The production schedule calendar with jobs booked across the working week
Production schedule — jobs booked into the hours the workshop really has
The production jobs list showing each job, its stage, quantity and due date
Every job, its stage, its quantity and its date — one screen
The stock screen showing materials, quantities held and one material below its minimum
Stock — what is on the shelf, what is committed, and what needs ordering today
The product catalogue with SKUs, categories and prices
The catalogue — every product with its specification, price and bill of materials behind it
A quotation document generated by the platform on branded letterhead
And what the customer receives — generated from the same record, on your letterhead
One configuration file per client
NameYour company, on every screen and documentYours
BrandYour logo, your colours, your typefaceYours
WordsJob bag, traveller, docket — whatever your floor calls itYours
RulesWorkshop hours, lead times, approval limits, tax treatmentYours
DataYour database, exportable any day you ask for itYours
White label

It arrives with your name on it, not ours.

The platform is built so that everything identifying it lives in one configuration file. Your staff never see our branding, your customers never see it on a quote, and the words on screen are the words your business already uses.

Underneath it is the same tested code that runs a manufacturing business today — so you get something proven wearing your own badge, instead of a first draft written from scratch at your expense.

  • Your branding on every screen, document and email it sends
  • Your terminology on the buttons — we rename screens to match the floor
  • Your rules as settings: hours, lead times, approval limits, tax
  • Your own database, and your own server if you want it
  • No "powered by" badge anywhere on it
How we tailor it

We work out how you run, then make the software fit.

No two workshops run the same way, and the expensive mistake is bending a business to fit a package. We start from what your people actually do — including the parts held together by memory, a whiteboard, and one spreadsheet nobody else can open.

A day on your floor, not a questionnaire

We sit with the office, the buyer and the bench and watch a real job go through: where it stalls, where it gets typed twice, and where the arguments start.

Your process on one page, agreed before we build

Swim lanes, decisions, documents, who does what. Cheap to change at this stage and expensive later, so this is where we spend the time.

The awkward parts built first

Not the easy screens. Scrap, remakes, shortages, part deliveries and the proof nobody approved — because those decide whether a system gets used or worked around.

Released in modules, in use as they land

Every couple of weeks something real goes live and your team uses it. You steer while steering is still cheap, instead of waiting a year to find out it was wrong.

Trained, documented and supported by whoever wrote it

Time on site with the office and the shop floor, written guidance in plain English, and one number to call — answered by the person who built the thing you are asking about.

What it costs

Bespoke, without the bespoke bill.

A system built from nothing by a development house is routinely quoted in the tens of thousands, takes a year, and lands after the business has moved on. The off-the-shelf alternative looks cheap until you count the seats, the add-on modules, the integration that never quite works and the annual rise you cannot argue with.

We sit in between, deliberately. The platform already exists and is proven, so nobody is paying us to invent a quoting screen for the thousandth time. What you pay for is the part that is actually yours: your workflow, your documents, your rules, your data.

  • Fixed scope, fixed price, module by module — agreed before each one starts, so nothing runs away with itself.
  • Stop when it stops paying — each module is useful on its own; there is no two-year programme to sign.
  • No charge for hiring people — no per-seat licence, so growing the team does not grow the bill.
  • Your data, exportable any day — no lock-in dressed up as a subscription.
  • Hosting and support priced plainly — servers, certificates, backups, releases, and the phone call when something is wrong.
The honest test. Add up the hours your office spends retyping things that are already in the building, and the jobs that went wrong because two systems disagreed. That number is what a tailored system is really competing with.
Built and running

What we have actually delivered.

Project 01

A manufacturing platform, built and running

A manufacturing business running on spreadsheets, email threads and paper. Replaced with one system, built module by module and in daily use as each part landed — enquiry to invoice, including the tablets on the shop floor.

Project 02

A customer website with a real account behind it

The public site for the same business, and behind the sign-in an online design studio: registration, email verification, password reset, saved designs and issued proofs, feeding straight back into quoting.

Project 03

Our own products, on the same platform

GTI Proof Studio and our own copy of the platform, run by us, for us. We use what we sell — which is the quickest way to find out whether it is any good.

Go and use it. The system in those screenshots is running at gti-global.co.uk/gti-systems — sign in with demo@gti-global.co.uk and ShowMe2026. It opens every screen and changes nothing, and every customer, supplier and order in it is invented.