Digital quality inspection
We build custom inspection platforms for manufacturers and equipment makers in the UK and US. Readings pulled straight off your testers, capture that keeps working with no signal, certificates your auditor accepts.
Book a 30-minute scoping call See the Hydrajaws build
No sales deck. We map your current checks and tell you whether a licence would do the job.
| Anchor pull test M12 resin fixing, 6 kN target | 6.4 kN Pass |
|---|---|
| Torque check Read from KTC tester over Bluetooth | 112 Nm Pass |
| Substrate condition Photo attached by inspector | Pass |
| Fixing depth Below spec, corrective action raised | 48 mm Fail |
The honest question first
Most teams asking us about inspection software should buy something off the shelf. Here is how we tell the two cases apart, before anyone writes a proposal.
Buy off the shelf when
If this is you, we will say so on the first call and point you at the tools that fit. It costs you nothing and saves both sides a month.
Build custom when
This is the work we do. Hydrajaws came to us in exactly this position: their testers produced readings no generic app could read.
Case study, United Kingdom
Hydrajaws Limited makes portable pull testers used in construction and safety compliance. Their existing app was poorly documented, they did not control the code, and the interface was holding back sales. They also wanted to move into digital torque testing, which meant reading live values from the instrument rather than having an engineer copy numbers onto a form.
We rebuilt it as two apps, a free tier and a premium tier, put user management behind Azure AD B2C, and integrated the KTC SDK so torque and pull readings flow straight into the record. The same build opened the automotive market for them.
Two more builds in the same space: Verify Auto and a work-at-height testing platform.
What we build
Every platform we ship is different. These are the parts clients come to us for, because a licence will not cover them.
Plain definitions
These come up on almost every first call, and getting them clear saves a wasted procurement round.
It is software that replaces the paper checklist an inspector carries. Instead of writing readings on a form and typing them into a spreadsheet later, the inspector records the check on a phone or tablet, the reading is captured at the moment it is taken, and a report or certificate is produced from that record.
Three things separate it from a general checklist app. It knows the asset being inspected and its history. It applies pass and fail logic to measured values rather than just collecting ticks. And it produces a document somebody is accountable for signing.
A quality management system is the paperwork layer: procedures, documents, non-conformance registers, audits, corrective actions. It is where an ISO 9001 auditor looks. Inspection software is the capture layer: the thing an inspector actually touches while standing at the machine.
Most companies need both, and they need them connected. A failed check should raise a non-conformance in the QMS without anyone retyping it. Keeping your existing QMS and adding capture underneath it is usually cheaper than replacing both.
Where we have done this
We list four because we have shipped in four. A longer list would be a list of industries we would like to work in.
How the work runs
We put a working platform in one team's hands early, then widen it. That way the expensive decisions get made with real inspection data behind them.
Week 1 to 2
We sit with your inspectors, walk the floor or the site, and write down what actually happens, including the workarounds.
Week 3 to 4
Forms, pass and fail logic, certificate layout, integration points, and what the offline rules need to be.
Week 5 to 12
Two-week sprints with a demo each time. One site runs the pilot on real jobs while we are still building.
Ongoing
Site by site, then region by region. We hand over the code and the documentation whenever you want them.
Technology and integration
Every item here comes from something already shipped, not from a list of things we could learn.
Who does the work
A small team by outsourcing standards, and deliberately so. The people who scope your project are the people who build it, and you meet them before you sign anything.
How we work
The models differ in one thing: how much of the management you hand over. Everything else, including who owns the code, is the same in all five.
Changing model later is normal. Augmentation into a dedicated team is the common direction, and the people stay.
Engineers join your team and work inside your process, your board and your code review.
A team that works only on your product, with a lead on our side running delivery.
A long-term engineering site under your standards, where we carry recruitment, HR, payroll and equipment.
04
One price for a scope that is genuinely settled, with the overrun carried by us.
Everything in the centre model, with the whole team moving into your own Vietnamese entity on an agreed date.
FAQs
Yes. Inspectors capture checks, photos, readings and signatures on the device, and the records sync when they get coverage again. We design the conflict rules with you, because what should happen when two people edit the same record depends on how your team works.
If the instrument exposes a Bluetooth profile or a vendor SDK, yes. We did this for Hydrajaws using the KTC SDK for digital torque measurement. Send us the model numbers and we will tell you what is possible before you spend anything.
You do. All intellectual property in the software we build for you belongs to your company, in every engagement model. We hand over repositories and documentation on request, not at the end of a contract term.
Wherever you need it. We usually deploy to your own Azure or AWS tenant, in the region your policy requires. For UK clients that normally means UK or EU regions with GDPR obligations written into the architecture rather than added later.
Yes, and this is usually the reason clients come to us rather than buying a licence. We have built API integrations against ERP, MES and IoT systems, including legacy ones with no modern interface.
A pilot on one site typically runs 10 to 14 weeks from kickoff. You see working software at a demo every two weeks from around week five, so you are never waiting until the end to find out what you are getting.
Many clients do, and some should keep it. If the tool covers 80 percent of your checks, we can build only the part it cannot handle and connect the two. That is cheaper than replacing something that works.
A single-site pilot is usually 10 to 14 weeks. A multi-site platform, with integrations and reporting behind it, runs longer, and an enterprise rollout across regions longer again. Instrument integration and migration move the number more than screen count does. How it is billed follows the engagement model above, and the scoping call ends with a figure for your build rather than a range.
Usually yes, and it is often the cheaper answer. We build the capture layer and push results into the QMS you already run, so a failed check raises a non-conformance without anyone retyping it.
They can be imported if they exist in any structured form, and we treat that as its own workstream with reconciliation on both sides. If they only exist as scans, we will say so rather than promise a clean migration.
Our engineers in Ho Chi Minh City, working in your hours for the overlap you need. The same team that built for Hydrajaws and Verify Auto works on inspection projects. You meet them before you sign anything.
The one with the spreadsheet, the photos on someone's phone and the certificate nobody can find. Thirty minutes on a call and you will know whether it is worth building.
