Custom software · for field teams

Field service software. Build or buy

Buy field service software when your jobs follow a standard process: a visit, a checklist, an invoice. Build your own when the app needs to follow your rules, work without a signal, or send data to your accounting system or ERP. Amazing Soft, based in Bucharest since 2016, builds these custom apps for companies in Romania, Europe, the Middle East and North America. Our work for Romexpress includes an internal dispatch system with a weekly planning board.

The decision. Eight questions

A ready-made product handles standard jobs. Compare the following situations with the way your team works.

01

How standard is a job?

A product is enough for a visit, a checklist, a signature and an invoice. Your own app makes sense when a job involves several visits, parts with serial numbers, approvals and a different checklist for each type of equipment.

02

Where do your technicians work?

A product that needs a connection can serve technicians working in town with a signal. Your own app makes sense when technicians work in basements, plant rooms, rural areas or sites without coverage and need to work offline and sync later.

03

What needs to happen to the data?

A product is enough when the data can stay there and an occasional CSV export meets your needs. Your own app makes sense when the data needs to reach accounting, ERP or stock systems the same day, without retyping.

04

How many systems do you already run?

A product is enough when it replaces paper and becomes your only system. Your own app makes sense when quoting, stock, invoicing and payroll already run in other systems that the app needs to connect to.

05

How often does the process change?

A product is enough when the process rarely changes. Your own app makes sense when the process changes every season or with each new service or customer contract.

06

Who else needs to see the job?

A product is enough when only the office needs access. Your own app makes sense when customers, subcontractors, equipment owners and auditors each need their own view and access rights.

07

What does a mistake cost?

A product is enough when correcting a mistake takes a phone call. Your own app makes sense when a mistake means missed maintenance, an incomplete safety record or a fine. The app needs to require the necessary steps, not merely suggest them.

08

How long will you use it?

A product is enough when you want to try it for a year or two before deciding. Your own app makes sense when you plan to use it for years and want to decide what changes and when, without waiting for a vendor’s roadmap.

If many of your answers point toward your own app, a custom build is worth discussing. If few do, buy the product and come back when it starts getting in the way.

Say you run a field team. Twelve technicians, one job flow

Say you run a heating and plumbing company with twelve technicians. Job requests would arrive by phone and email. The office would write them on a whiteboard and send each technician a WhatsApp message in the morning. Job sheets would be on paper. Photos would arrive in separate chats in the evening. Someone would write the invoice later, from memory.

The app would start with one workflow: the job. The office would create it once, with the address, customer, equipment and checklist for that type of work. The technician would see today’s jobs on a phone and open the assigned job. They would follow the checklist, add photos, and type or scan the parts used. The customer would sign on the screen. In a basement without a signal, the app would save everything on the phone and send it when the connection returned.

The office board would show each job’s status throughout the day: scheduled, on the way, in progress and done. The job sheet would become a PDF as soon as the customer signed. If the accounting program supported it, an invoice draft would reach that program before the van left the street. The customer would receive a message with the report, so they would not need to call to ask whether the job was done.

When comparing HVAC software or software for plumbers, you would follow this workflow from the first request to the completed report.

Route optimization, payroll and stock forecasts would stay outside the first version. They would come later if the team needed them, or remain in the products that already handled them well.

What we have built. A weekly board for dispatch

Field service and freight dispatch share a planning need: seeing scheduled work by day.

Romexpress
A road freight carrier in Cleveland, Ohio. In 2020–2021, we built its internal dispatch system. The dispatcher enters an order once, with all its stops. The application places it on the appropriate days of the week on a large office screen. See this work →

Offline first. Work without a signal

Fieldwork often takes place where the signal is weak: plant rooms, basements, new buildings and farms. An app that only works online becomes a form the technician fills in afterward from the van, relying on memory.

The app needs to:

  • Show today’s jobs, customer history and checklists without a connection.
  • Save photos, signatures and parts used on the phone, then send them when the signal returns.
  • Clearly show the technician which records have not been sent.
  • Resolve conflicting changes when two people edit the same job, such as an office reschedule made while a technician is closing the job.

Offline work is the first thing we test with your team in the field.

Build the part that is yours. Connect the rest

You do not need to build a complete field service suite from scratch. Existing products handle scheduling optimization, payroll, accounting and GPS tracking. These functions are not what makes your company different.

Your own app covers your job workflow, checklists, approvals and reports. It connects to the other systems you use.

Examples include accounting programs such as QuickBooks, Xero and Sage, an ERP, a CRM, your calendar or your existing invoicing system. We check their APIs and available access before specifying the connections.

Our custom software development services cover the custom application and its connections.

Job management software. Same question, three markets

In the UK, the category is called job management software. In the US and Canada, names include field service software, contractor software and an app for contractors. Trade-specific names include HVAC software, plumbing business software and software for electricians.

The question stays the same: does the product fit the way your jobs run, or do you have to change your jobs to fit the product?

Who it's for. Teams on the road

This service is for companies with technicians on the road: HVAC and heating, plumbing, electrical work, installations, maintenance contracts, cleaning and inspections. Teams can range from a handful of technicians to several hundred.

If you run two vans and follow a standard job process, buy an existing product. A custom app makes sense when that product starts getting in the way of your work.

How we work. Tested with your field team

We spend a day in the field with your team to see the actual workflow, beyond what the written procedure describes. We prototype the app around their real cases and test it with them.

We then build in versions. The first version goes into the field within weeks. The exact delivery plan is in the proposal. You see and test every version along the way.

Our internal apps for field teams also cover warehouse and sales work. The service page explains what we deliver and how we work.

When not to build. Four cases

  • A product on the market covers almost all your jobs. Buy it. We tell you that in the first conversation.
  • You need it next week. A first version takes weeks, not days.
  • Your team will not use a phone at work. No app fixes that. Start with the process.
  • You want to pay monthly and cancel at any time. A subscription product serves that need. An app of your own pays back over years.

The cost is established after consultation. It depends on the workflows in the first version and the systems the app connects to. After the free 30-minute consultation, you get the written proposal with a fixed price.

If the proposal suits you, we sign the contract and start work.

Questions. Short answers

Both exist. A small company with a standard job process is well served by a subscription product. An app of your own makes sense when the work is not standard, regardless of company size. We have built internal apps for companies ranging from a handful of users to several hundred.

The cost is established after consultation and depends on the workflows in the first version and the systems it connects to. After the free 30-minute consultation, you get the written proposal with a fixed price. You approve the work stage by stage.

We build in versions. The first version, with the main job workflow, goes into the field within weeks. After the first conversation, the proposal sets out the full delivery plan.

If your office assigns jobs to technicians and tracks them throughout the day, the dispatch board is part of the app. It shows the office the same job data that technicians enter in the field. Trucking and freight dispatch follow different rules. See our guide to dispatch software for carriers and freight dispatch offices.

Yes. We test offline work in the field with your team. Jobs, checklists, photos and signatures are saved on the phone and sent when the connection returns.

The system runs on hosting in your name, in a location you choose. At the end, we hand over the domain, hosting, accounts, files and documentation.

Amazing Soft. The facts

Amazing Soft SRL is a software company based in Bucharest, Romania, since 2016. VAT no. RO35387202.

Our time zone is Eastern European Time. We are usually two hours ahead of London and seven hours ahead of New York and Toronto. We work in English and Romanian.

Our data processing agreement is published on our legal page. After consultation, you receive the price in the written proposal with a fixed price.

Tell us how your jobs run. Written proposal with a fixed price

During the free 30-minute consultation, we discuss whether to build or buy and what the first version would contain. Afterward, you get the written proposal with a fixed price.