Find the moment worth removing
Which routine act of checking, waiting or being present costs you most? If nobody would act differently on the information, it is not worth connecting yet.
Something happens in the real world. Your systems find out immediately.
That is the whole idea. A door, a sensor, a meter or a machine tells your software what just happened, and your software does something useful about it — without anyone walking over to check. We build these systems, and we run one ourselves.
Explained in plain terms
Proven in our own premises
Off-the-shelf where sensible
Built where it is not
THE SITUATION
Most operations still run on someone going to look.
Somebody walks the floor to check a reading. Somebody stays back because a customer is collecting at seven. Somebody notices the freezer failed on Monday morning. Every one of those is a person acting as a sensor — expensive, slow, and only accurate while they are actually there.
The technology to remove that has been ordinary for years. What stops most businesses is not cost or complexity; it is that nobody has explained it in terms of their own operation. So it stays filed under future technology, while the same person keeps walking over to check the same thing.
SYMPTOMS WE HEAR MOST
Someone must be physically present for a routine handover You find out about a failure long after it happened Readings are recorded on a clipboard and typed in later Operating hours are set by staffing, not by customer demandHOW THE WORK RUNS
Start with the outcome, not the hardware.
Every failed project we have seen started by buying devices. Every successful one started by naming the moment that should stop requiring a person.
Choose devices, mostly off the shelf
Readers, sensors, meters, controllers and gateways from established suppliers wherever they exist. We only design custom hardware when nothing suitable does.
Build the rules and the connections
Secure ingestion, provisioning, and the logic that turns a raw signal into a decision — connected to the systems you already run, not a separate island.
Watch it, and widen it
Dashboards, alerting and device health monitoring. Most clients add a second use case within a year, because by then the possibilities are obvious.
HOW IT ACTUALLY WORKS
Four steps. That is genuinely all it is.
Internet of Things sounds like a research project. In practice every one of these systems is the same four links, and only the middle two are ours to design.
Something happens
THE REAL WORLDA person arrives. A temperature drifts. A machine stops. Something changes in the physical world that your business cares about.
A device notices
HARDWARE — MOSTLY OFF THE SHELFA reader, sensor, meter or controller detects it. Usually inexpensive, and usually already made by someone who does nothing else.
A rule decides
SOFTWARE — OUR PARTYour software applies your logic. Is this person authorised? Is this reading outside range? Has this been paid for? This is where the value sits.
Something useful happens
THE OUTCOMEA door unlocks. An alert reaches the right person. An order is raised. The business responds without waiting for someone to notice.
If you can describe steps one and four, we can usually build two and three.
LIVE CASE STUDY · DAVIS MATERIALWORKS
A customer collected at 2:14am on a Sunday. Nobody was there.
This is not a concept. It is running in our own premises today, and you can test it yourself.
Davis Materialworks is our parent company, and for years it had the same problem every trade supplier has. Customers finish their own jobs late. They want to collect on the way to site at six in the morning, or after a shift ends at nine at night. We were open eight-thirty to six, so somebody either waited, made a second trip, or we kept a person back to hand over a single box.
We could have extended opening hours. Instead we removed the need for anyone to be present at all. Now when an order is ready it is placed in a locker, the system issues the customer a single-use credential, and they come whenever it suits them. The building is dark. The system does the handover.
The busiest collection window turned out to be after 8pm — hours we were never open for. Nobody asked us for this, because most customers had simply accepted the inconvenience as normal.
WHAT HAPPENS ON A COLLECTION
Customer completes their purchase online
Payment
Order is marked ready and assigned a locker
Our platform
Customer receives a single-use access credential
Messaging
They arrive at any hour and present it to the reader
Device
The system checks it is paid, valid and unused
Rules
That locker — and only that locker — opens
Device
Collection is timestamped and the credential expires
Audit
COLLECTION HOURS
24 / 7
STAFF REQUIRED AT HANDOVER
None
DISPUTES ABOUT COLLECTION
Settled by the log
CUSTOMER WAITING
Removed entirely
It is not a large system. It is a payment, a rule, a credential and a lock — joined up properly. That is what most of these are.
Try it yourself, properly.
The most useful thing we can show you is not a demonstration. Place a real order with Davis Materialworks and collect it at whatever hour suits you — an unfamiliar building, at night, with nobody to ask. That experience is what your own customers would get.
WHAT ELSE COULD IT DO
Cause something to happen. Watch the system respond.
Press a control below and you are the physical event. The signal travels, your rules decide, and something happens — or does not. Try the second control on each: a system worth having is one that can say no.
Locker reader · Bay 3
Wireless probe · Freezer 2
Weight sensor · Bin A7
Door controller · Rear entrance
Plate reader · Gate 1
Occupancy sensor · Room 4
Sub-meter · Unit 12
Run-hour meter · Pump 3
ACTION TAKEN
HAPPENS
Real world
NOTICES
Device
DECIDES
Your rules
ACTS
Outcome
Nothing is happening. Press a control below to become the physical event.
- Credential presented at reader
- Reader transmits token — 40ms
- Order paid · token unused · within window
- Locker 14 released · collection timestamped
- Credential presented at reader
- Reader transmits token — 40ms
- Token already redeemed at 19:42 yesterday
- Refused · attempt logged · no locker opened
- Freezer 2 drifts to −16°C
- Probe reports every 60 seconds
- Above range for 12 minutes · not a door event
- Duty manager called · escalation started
- Freezer 2 rises to −16°C
- Probe reports every 60 seconds
- Door contact open · recovery within 4 minutes
- No alert · logged as routine access
- Bin A7 falls below its minimum level
- Weight sensor registers the drop
- 14-day lead time · no open order · usage rising
- Purchase order raised for approval
- Bin A7 is still below minimum
- Weight sensor registers the level
- Order placed yesterday · arriving Thursday
- No action · duplicate order prevented
- Contractor badges at the rear door
- Controller reads the credential
- Booked 08:00–12:00 Thursday · valid now
- Entry granted · logged with photo
- Same contractor badges at the rear door
- Controller reads the credential
- Access window closed at 12:00 Thursday
- Refused · facilities notified of the attempt
- Vehicle stops at the yard gate
- Plate reader identifies it — 200ms
- Matches delivery 4471 · bay 2 free
- Barrier lifts · receiving alerted with docket
- Vehicle stops at the yard gate
- Plate reader identifies it — 200ms
- No delivery booked · not a known carrier
- Barrier held · intercom opened to security
- Room 4 booked for 10:00 · still empty
- Occupancy sensor confirms no presence
- 10-minute grace elapsed · no check-in
- Booking released · room returned to the pool
- Room 4 booked for 10:00 · still empty
- Occupancy sensor detects presence at 10:06
- Within grace period · booking stands
- No action · meeting proceeds
- Unit 12 water use doubles overnight
- Sub-meter reports continuously
- Sustained 9 hours · no occupancy · likely leak
- Flagged to maintenance · billing apportioned
- Unit 12 water use rises sharply
- Sub-meter reports continuously
- Matches occupancy · returns to baseline overnight
- No alert · pattern recorded for the baseline
- Pump 3 reaches 800 running hours
- Run-hour meter counts real use, not days
- Service due at 800 · parts in stock
- Job created with the correct parts listed
- Six months elapse since last service
- Run-hour meter shows only 210 hours
- Well inside tolerance · no fault indicators
- Service deferred · reviewed again at 800
OPERATING HOURS NO LONGER SET BY STAFFING
Locker 14 opens. Your premises just served a customer at 2am.
THE RULE IS THE SECURITY, NOT THE DOOR
Nothing opens. The attempt is on record with time and location.
ONE PREVENTED LOSS USUALLY PAYS FOR THE SYSTEM
Someone is woken at 3am and the stock survives the night.
GOOD RULES ARE MOSTLY ABOUT NOT ALERTING
Nobody is woken. A system that cries wolf gets switched off.
NO STOPPAGES FROM A BIN NOBODY CHECKED
The reorder happens whether or not anyone remembered.
KNOWING WHEN NOT TO ACT IS PART OF IT
You do not end up with twice the stock you needed.
NO KEYS HANDED OVER, NONE TO CHASE BACK
They get in without anyone meeting them at the door.
NO PERMANENT KEYS FOR TEMPORARY PEOPLE
Access expired by itself. Nobody had to remember to revoke it.
ARRIVALS HANDLED WITHOUT A GATEHOUSE
The driver never stops. Receiving already knows what is coming.
EXCEPTIONS REACH HUMANS, ROUTINE DOES NOT
A person is involved only when a person is actually needed.
CAPACITY RECOVERED WITHOUT BUILDING ANYTHING
You stop needing more rooms than you actually use.
AUTOMATION PEOPLE DO NOT RESENT
The rule accommodates real behaviour instead of punishing it.
BILLING BY MEASUREMENT, NOT BY FLOOR AREA
A leak is found in hours rather than at quarter end.
CONTEXT IS WHAT MAKES DATA USEFUL
The system learns what normal looks like for each tenant.
FEWER BREAKDOWNS, LESS UNNECESSARY SERVICING
Servicing follows real wear instead of a calendar guess.
MAINTENANCE SPEND FOLLOWING REALITY
You stop paying to service equipment that has barely run.
If one of these is nearly your situation, the gap is usually smaller than it looks. Describe yours to us and we will tell you what it would take.
WHAT WE BUILD ON
Established platforms, joined to your systems.
We do not ask you to adopt a proprietary ecosystem. These are the layers a connected system needs, and the options we typically use at each.
DEVICES
Readers, sensors, meters, controllers, cameras, smart locks
Established hardware suppliers, selected per use case
CONNECTIVITY
How devices reach the network
Wi-Fi, Ethernet, 4G and 5G, LoRaWAN, Zigbee, Bluetooth LE
INGESTION
Receiving and queuing messages reliably
MQTT brokers, AWS IoT Core, Azure IoT Hub, Google Cloud IoT
RULES AND LOGIC
Where your business decisions live
Custom Laravel and PHP — built and owned by you
INTEGRATION
Connecting to what you already run
APIs into your CRM, ERP, accounting and payment systems
VISIBILITY
Seeing state and being told about exceptions
Dashboards, alerting and device health monitoring
We integrate existing platforms, innovate where nothing fits, and supply the hardware where that is simpler for you.
WHAT YOU ACTUALLY GET
A working system, not a pilot that stalls.
- Use-case definition and feasibility assessment
- Device selection, sourcing and supply
- Connectivity design for your site conditions
- Secure ingestion pipeline and device provisioning
- Business rules built into your own platform
- Integration with your existing systems
- Dashboards and exception alerting
- Device health monitoring and offline handling
- Installation coordination and commissioning
- Documentation and staff handover
HONEST SCOPE
Is this the right thing to buy?
GOOD FIT WHEN
A person is currently required at a moment that could be automated Something physical determines a decision your software should be making You are opening hours, holding stock or staffing shifts around checkingWAIT, OR DO SOMETHING ELSE FIRST
Nobody would act differently on the information — measuring it changes nothing It happens rarely, and a person checking occasionally is genuinely cheaper The site has no viable connectivity and no budget to provide itCOMMON QUESTIONS
The things people ask first.
What does IoT actually mean, in plain terms?
Physical things that can report what is happening and be controlled remotely. A lock that can be opened by your software, a sensor that reports a temperature, a meter that sends its reading. The phrase covers a lot, but every individual system is small and specific.
Do we need to buy special hardware?
Usually you buy ordinary hardware that already exists — readers, sensors, meters, smart locks — from suppliers who make nothing else. We only design custom hardware when nothing suitable is available. The engineering value is almost always in the rules, not the device.
Is it secure? It is a door lock connected to the internet.
It is a fair question and the answer is architectural. Devices hold no business logic and cannot make decisions on their own. Credentials are single-use or time-bound. Every action is logged. If a device is stolen or a credential leaks, it opens nothing it was not already entitled to open, and only within its window.
What happens when the internet goes down?
Designed for, not hoped about. Devices buffer and resend, critical functions have a local fallback so a door still works, and you decide up front whether a given failure should fail open or fail closed. We agree that behaviour before anything is installed.
How much does a first system cost?
Less than most people expect, because the hardware is commodity and the first use case is deliberately narrow. A collection or access system is typically four to eight weeks of work plus devices. We would rather prove one moment works than sell a site-wide rollout.
Can you connect equipment we already have?
Often yes. Newer machines expose data already. Older ones can usually be read externally — a current clamp, a run-hour meter, a contact sensor — without modifying the equipment or voiding anything.
Do you supply the devices, or only the software?
Either. We integrate with platforms and hardware you already have, supply and commission the devices ourselves where that is simpler, and build custom where nothing off the shelf fits. Most projects are a mix.
Tell us the moment that still needs a person.
Describe the thing someone currently walks over to check, wait for or unlock. We will tell you honestly whether connecting it is worth doing, and what it would take.