Your technicians already chat.
Let the chat do the paperwork.

Field crews already run their jobs in chat groups, while the office still rebuilds every report by hand. In our prototype each work order gets its own chat thread, technicians send voice notes and photos, the office replies in the same place, and AI generates the report from the thread.

Book a 20 min call

Łukasz Kincel

Chief Strategy & Innovation Officer

Trusted by teams at:

One conversation per job, from the first message to the report.

One chat thread per work order

The technician, the office and every photo stay in the same conversation.

Your next service report takes one voice note

Technicians describe the job on site, and nobody types it up later.

The thread becomes the report

Close the job and the PDF report is already drafted from the thread, ready for the technician to confirm.

Built from conversations with service teams

Before we wrote any code, we talked to technicians and service leads in wind energy, heating and ventilation, cogeneration, industrial automation and marine engineering. The same moments kept coming back.

The prototype is our answer to those moments, and every call helps us test it against more of them.

Photos from the job live on private phones

Someone in the office rebuilds the report from a group chat

The technician writes it all up at the end of the day, from memory

Book a 20 min call

Łukasz Kincel

Chief Strategy & Innovation Officer

What happens in the 20 minutes

You tell us about a typical job

A work order, a report template, or simply how your crews work today.

We run it through the prototype live

From the technician's first message to the finished report.

You tell us what is missing

What would stop your technicians or your office from using it.

Talk it through with Łukasz Kincel

He runs nomtek Labs, where the prototype is built, and will walk you through it on one of your jobs in 20 minutes.

Book a 20 min call

Łukasz Kincel

Chief Strategy & Innovation Officer

Trusted by teams at:

A fresh experiment from a team with a long track record.

nomtek Labs is where we test ideas in a few weeks. The rest of nomtek builds mobile and AI products that run in production for industrial and enterprise clients.

Mobile is where we started

nomtek has built mobile apps for 17 years, many of them for people who work on site and on the move. That experience shapes how the prototype handles offline work, photos and long shifts.

AI features that run in production

Our teams build AI into apps that clients use every day, and the way the prototype turns a job chat into a report comes from that work.

Trusted by industrial and enterprise clients

We design and build products for global industrial companies, where security reviews and reliability are part of every release.

A small lab inside an 80-person company

nomtek Labs is a small senior team that tests ideas fast, with designers and engineers who ship client products every day right next to it.

Frequently Asked Questions

Dedicated team

Unpack your idea with dedicated feasibility agents. A team of three experts will work on all angles to check technical feasibility and prepare an initial roadmap. Each iteration lasts one week.

High transparency

The whole process is highly transparent — you’re in the loop at every moment. If the first week reveals additional areas for exploration, we continue iterating. This way we generate enough valuable data to speed up your decision-making.

Rich deliverables

Deliverables — Every tech feasibility sprint ends with a report, roadmap, or prototype, depending on the duration of the workshop and our findings.

Custom Process

Throughout the workshop, we integrate custom processes crafted using collected insights and internal expertise. A tailored approach is optimized for confident execution in the later stages.

Does it replace our field service system?

It is designed as the front end for the system you already run, such as SAP or Salesforce. Everything from the thread ends up as structured documents on the server, ready to integrate, and a reference connector is on our list. Our interviews point the same way: the value sits in connecting the technician’s work to your systems and processes.

‍

Does it work without signal?

Yes. The phone works as the database: messages, photos and voice notes are saved locally, marked as queued and synced by themselves when the network returns, so nothing gets lost in a basement or a wind farm. Transcription and the report run in the cloud, so they happen once the phone is back online.

‍

Where does AI come in?

When the job is done, the server reads the whole thread, including the transcribed voice notes, and an AI model writes the report text. The order type, such as breakdown, inspection or installation, decides which fields the report contains, and the PDF is rendered on the server. AI agents also join the thread like any other participant, for example to point out that the same machine had the same fault in March and which part was replaced then.

‍

Why build it around a chat?

Because that is what our research showed. In our interviews, technicians and service managers described photos, voice notes and quick decisions travelling through chat groups every day, outside the company’s systems. What those chats leave behind is the real problem: photos on private phones, someone in the office assembling the report by hand, and nothing reaching SAP or Salesforce. Our prototype keeps the chat and adds the structure around it.

Bring a job. We will run it with you.

Book A Consultation

A 20-minute call with our Chief Strategy & Innovation Officer