Digital quality inspection
Inspection software that replaces the paper checklist, with pass and fail logic against measured values.
Services
Software development services, grouped so you can find yours
Twenty-five pages, in six groups. Every one says plainly what it covers, where we have shipped, and where we have not. If a product already does what you need, that is on the page too.
Book a 30-minute scoping call See all twenty-five
An engineer reads what you send, not a sales rep. Answer within one working day.
| Digital quality inspection Readings, checks, certificates | 3 |
|---|---|
| Building software Web, mobile, product, devices, design | 6 |
| Data and AI Pipelines, models, documents, fleets | 4 |
| Infrastructure and security Cloud, delivery, controls, identity | 4 |
| Testing and ways of working QA plus six engagement pages | 8 |
What we have shipped
- Norwegian EdTechYears of school records migrated, none lost
- Hydrajaws LimitedInstrument readings captured, not retyped
- IoT WorkzESP32 fleets live, zero critical alarms
- German software firmTeam grown to 60+ engineers at peak
Everything we do
Twenty-five services in six groups
Nothing is hidden behind a contact form. Each page names the work, the technology and the cases behind it, and says when we are the wrong choice.
Digital quality inspection
Where a reading, a check or a certificate has to hold up months later.
Digital gauge inspection
Readings taken from torque wrenches, pull testers and gauges over Bluetooth or a vendor SDK, calibration checked at capture.
Digital elevator inspection
Statutory lift examinations under LOLER or ASME A17.1, offline capture in a shaft, certificates in your own format.
Building software
The systems a business runs on, and the interfaces people use to run them.
Custom software development
What to build when no product covers your process, and when to buy one instead.
Web application development
Angular and React over .NET or Node, deployed into your own cloud tenant, including legacy modernisation.
Mobile app development
Field apps for gloves, bad light and no signal, reading instruments over Bluetooth.
Software product development
Building software you sell: tenancy, tiers, self-service sign-up, white labelling and self-hosted delivery.
Embedded and device software
The platform devices report into, over-the-air firmware delivery, and readings pulled from instruments.
UX and UI design
Interfaces that carry work, with prototypes tested before production code and a component library handed over.
Data and AI
The unglamorous layer underneath, and an honest read on whether a model is worth building at all.
Data engineering
Ingestion, storage, movement and migration, plus the monitoring that tells you a feed has stopped.
AI and machine learning
A two-week feasibility read first. Half of them end with advice not to build a model.
Generative AI development
Retrieval over your own documents, with citations and permissions, proved on a two-week pilot.
IoT solutions
Three reasons to connect equipment and three different builds. Pick before you buy sensors.
Infrastructure and security
Who owns the account, who is allowed to deploy, and who is allowed to see what.
Cloud engineering
Azure and AWS in accounts held in your name, with the pipelines and the exit written down at the start.
DevOps
Pipelines, environments, monitoring and a rollback somebody has actually rehearsed.
Security and governance
We build to the controls a framework asks for. We do not issue certificates, and we name the firms that do.
Identity and access management
Access enforced at the server, tenant isolation, and entitlements that cannot be switched on from a device.
Testing
Automation and regression handed over with documentation, rather than a suite only we can maintain.
Software QA and testing
Offshore QA outsourcing, automation, regression and release testing, with the test plan written alongside your people.
How we work together
Five engagement models plus support. They differ in one thing: how much management you hand over.
Offshore software development
The hub comparing all five models, with the situation each one suits and where it stops working.
Offshore development centre
A long-term engineering site under your standards, where we carry recruitment, HR, payroll and equipment.
Dedicated development teams
A team that works only on your product, with a lead on our side running delivery.
Staff augmentation
Engineers inside your process, under your management, when you have capacity to direct them.
Fixed price
One price for a scope that is genuinely settled, with the overrun carried by us.
Build, operate, transfer
A Vietnam team you will own, with the transfer price agreed in the first contract.
Maintenance and support
For the system whose original developer has gone, and which still has years left in it.
Working from the United Kingdom
Working from the United Kingdom? The UK page covers what BS 8539, LOLER and a UKAS calibration certificate actually demand of the record, where your data sits, and the two British builds behind it.
Still choosing
If none of them obviously fits, start from what you know
Nobody arrives knowing which of the twenty-five they need. Most people know one of these three things instead, and any of them is enough to start a useful conversation.
- You know what has to be built
- Go straight to the service group below. If your project spans two groups, which is common, start on the pillar page of the larger one and we will join the rest up on the call.
- You know what is broken, not what to build
- Describe the process that hurts. A spreadsheet four people edit, readings retyped on a Friday, a release nobody trusts. The scoping call turns that into a shape, and sometimes into advice to buy a product instead.
- You know how you want to work
- If the decision is about a team rather than a project, the five engagement models further down compare them, including which situation each one suits and where it stops working.
Our work
Four builds the service pages keep pointing back to
We reference the same engagements across the site because they are the ones we can show. A longer list would be a list of logos.
- Hydrajaws Limited, United Kingdom
- Portable pull testers whose old app could not read the instruments. We rebuilt free and premium apps from one codebase and integrated the KTC SDK, so torque and pull values land in the record as measured. Digital torque testing opened the automotive market for them.
- Norwegian EdTech platform
- A system that could no longer handle its volumes or meet security standards, after a previous vendor missed the date. Rebuilt module by module with a separate team on migration alone, so schools kept working while years of sensitive records moved across. Zero records lost.
- IoT Workz platform
- Device fleets locked into a SaaS vendor with no white labelling and no data ownership. We built a self-hosted replacement on ThingsBoard with Keycloak, a visual rule engine and staged firmware rollout. It runs on their infrastructure with zero critical alarms in live operation.
- German software firm
- A build another supplier had left with poor code quality and missed dates. We staffed a lead and senior engineers first, stabilised it, then scaled. The engagement peaked past sixty engineers across the core team and an on-call group.
Who does the work
Twenty engineers, eight of them senior
Small by outsourcing standards, and deliberately so. Twenty-five service pages does not mean twenty-five teams. It means one team that has shipped across these areas and will tell you which ones it has not.
- Engineers in Ho Chi Minh City
- 20
- Senior engineers
- 8
- Average experience
- 5+ yrs
- Working with US, UK and EU teams
- 10+ yrs
You interview everyone we put forward, on every engagement model. We screen and shortlist, you take the final call.
How we work
Five engagement models, and you pick how much you keep
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.
- Team control
- You manage the day to day
- Pricing
- Monthly per person, by role and seniority
- Minimum
- 1 month
A team that works only on your product, with a lead on our side running delivery.
- Team control
- Shared. Our lead runs delivery, you set priorities
- Pricing
- Monthly per role, lead included
- Minimum
- 3 months
A long-term engineering site under your standards, where we carry recruitment, HR, payroll and equipment.
- Team control
- You direct the work, we run operations
- Pricing
- Monthly per role plus site costs
- Minimum
- 6 months
04
Fixed Price
One price for a scope that is genuinely settled, with the overrun carried by us.
- Team control
- We deliver, you accept against written criteria
- Pricing
- Fixed bid, paid against milestones
- Minimum
- Project based, usually 10 to 14 weeks
Everything in the centre model, with the whole team moving into your own Vietnamese entity on an agreed date.
- Team control
- Transfers from us to you
- Pricing
- Monthly per role, transfer price agreed up front
- Minimum
- 2 to 6 years
FAQs
Questions we get before the first call
Twenty-five services from twenty people. Is that credible?
It is a fair question and the honest answer is that these are not twenty-five separate practices. They are one team writing down what it has shipped, split by what a buyer searches for. Several pages say plainly that we have no published case in that area, the AI pages among them. Read those first if you want to test whether the rest is honest.
Which page should we read if we are not sure?
Start with the pillar page of the group that fits best: digital quality inspection, custom software development, software QA and testing, or the offshore development centre. Each one covers the group and links down to the narrower pages.
Do you only work in the industries you show?
No, but we only claim the ones we have shipped in. Safety testing equipment, education, automotive compliance, construction and work at height, and industrial IoT are where our cases come from. If your sector is not in that list we will say so rather than pretend the experience transfers automatically.
Where is the team, and what are the working hours?
Ho Chi Minh City. A UK team gets a morning overlap, an Australian team gets most of the day. A US west coast overlap has to be engineered rather than assumed, and we agree it in writing before anyone starts rather than discovering it in month two.
What size of company do you usually work with?
Mostly small and mid-sized companies where one person owns the decision, and product teams inside larger firms. The smallest sensible start is one engineer under augmentation or a lead plus two or three under a dedicated team. Both of our largest engagements began around that size.
Can we start with one small piece?
Yes, and we prefer it. A feasibility read, a two-week pilot, one feed end to end, one building running. Every service page has a first step that is small enough to stop after, and that is deliberate.
Do you take over work somebody else started?
Yes, and two of our largest engagements began that way. We read the code first and tell you what is salvageable before quoting, because quoting a rescue without reading it is how the first supplier got into trouble.
Who owns the code?
Your company, from the first commit, in every engagement model on this site. Repositories, pipelines and documentation are handed over on request rather than at the end of the relationship.
Describe the process, not the solution
You do not have to know which of the twenty-five pages you need. Tell us what happens today, who it frustrates and what it costs, and thirty minutes is usually enough to name the shape of the answer.