Not a rip-and-replace.
Not yet another app.
You already have an ERP — and usually a service app your team was trained on. We're the layer beside it: we find the gap those systems leave, and fill just that.
Your machines are advanced.
The way their service gets documented usually isn’t.
That gap — between what happens on site and what reaches your systems — is where margin, knowledge and compliance quietly leak out.

Reports still travel by paper, fax and email
The real work happens outside the system
Some records now have to survive an audit
And It Isn’t Only About Cost.
With skilled technicians getting harder to hire, getting each visit right the first time matters more every year — so the knowledge in your best people’s heads has to live somewhere your whole team can reach.
We build the field tool your team is missing — around your process, not a template
One mobile tool, shaped to how your technicians actually work and wired into the systems you already paid for. Designed, built and supported with you.

A technician app people open by choice
Offline-first, a few taps to a full report, machine history in hand on site. Consumer-grade UX is our whole DNA — that’s why field teams adopt it instead of routing around it.
Built over your existing systems, not instead of them
Whatever you run today — an ERP, Microsoft, something in-house — we connect the app to it and keep it working offline. Your core stays untouched, and the project stays contained and measurable.
Records that stand up to an audit
Whatever you run today — an ERP, Microsoft, something in-house — we connect the app to it and keep it working offline. Your core stays untouched, and the project stays contained and measurable.
It fits your process — and runs where your data already lives
The value isn’t a model. It’s the awkward, specific work we take off your technicians — your report formats, your parts logic, your checks — built to run inside the stack you’ve already approved. And when an off-the-shelf tool is the smarter buy, we’ll say so and integrate it, instead of reinventing it.
Built to sit on the systems you already run — securely
The first question every IT lead asks is whether we can work inside their world. Here’s the straight answer.
We build on top of what you have
Your world is usually an ERP as the record of truth (SAP or Oracle), Microsoft and Azure for data and day-to-day, and a mobile app someone built years ago. We work natively with Microsoft and Azure, and we read from your SAP/ERP so field data lands where it belongs — without touching your core.
Security first — not an afterthought
From day one we put it in writing: what data flows where, which models run in which region, what stays in your tenant, and who has access. Where it fits, we run inside the environment you’ve already security-reviewed — so there’s no new vendor, and no new review to clear.
Off-the-shelf FSM makes your process fit its data model. We start the other way round.
Packaged suites are strong at scheduling and dispatch. But the field-service market has reached broad functional parity — Gartner retired its Field Service Management Magic Quadrant in 2022 for exactly that reason. When the differentiator is fit and adoption, a tool built around your process wins.
A custom tool with nomtek
Built around your service process, forms and edge cases
Product-grade mobile UX — designed for adoption in the field
You own the codebase — no per-seat licence forever
Mobile, backend and AI under one roof
Sits over your existing systems — nothing to replace
Packaged FSM suite
Your process bends to the vendor’s data model
Add-ons and plugins for anything non-standard
Recurring per-user licensing that never ends
Roadmap set by the vendor, not by you
Great fit — if your process fits the box
Custom has a reputation — long, expensive, uncertain. We work the other way: one workflow, a working version fast, and a number you can plan around — you don’t need a 50-million transformation to start. And we begin every engagement by asking whether you should build at all. If a packaged suite is the right answer, we’ll say so on the first call and point you to it. That honesty is why teams bring us the hard calls.

Validate first. Pilot fast.
Roll out with proof.
We’ve spent years learning to reach product conclusions faster — including telling a client “no” when the data doesn’t support the build. Your budget is a constraint we design around, not against.

Scope & validate
Tell us the one workflow that hurts most. You leave with a scoped plan, a cost range in engineering hours, and a straight answer on whether to build.
Pilot on one workflow
A working, offline-capable app for one team and one workflow — something technicians actually use on site, not a demo. We scope it to reach that first real version fast and measure it against your numbers.
Roll out & scale
Prove it, then extend across teams, sites and languages. You own the product; we stay as the partner who keeps it moving.
Six things you’ll know before you commit
No discovery invoice, no vague “let’s do a workshop”. Before you spend real budget, you’ll have all six of these in hand.
Where you’ll be
What your service looks like 1–2 years in with us — and what that’s worth.
The roadmap
Not a one-off. Where a first win leads, and what the ambition is.
The quick win
The small, real thing we start with — live, not theoretical.
What we need from you
The roles, knowledge and time it takes — during the build and after.
The cost
A number and a range, in engineering hours — not “let’s do a workshop”.
The risks
Named up front, not discovered halfway through.
Case studies
Go beyond the obvious. Co-create with teams who value impactful experiences and products.



Elevating Aircraft Maintenance with Immersive Precision in a Pilot Project
Pilatus Aircraft
Turning Smartphones into Tactile Sensors with AI and 3D Mapping
GelSight



Optimizing sales effectiveness for healthcare services company
Siemens Healthineers: Funnel Review Manager (FRM)



Driving 57% Growth in Active Users with a Scalable Recruitment App for Randstad
Randstad
Send us one workflow. Get a rough scope back. In hours, not weeks.
No workshop to book first, no discovery invoice. Tell us the one thing that hurts most, and we’ll come back with a rough scope, a cost range in engineering hours, and a straight answer on whether custom is even the right call.


