Custom field service software for teams that dispatch from a group chat
For HVAC, plumbing, cleaning and maintenance companies we build online booking in your real slots, a dispatch board for the office, job reports filled in on a phone browser, and maintenance contracts that renew on time. Booking is the part closest to what we have built: a car-service site, takes bookings in 45-minute slots, writes them to Google Calendar and messages the team.
The system still runs, but nobody will change it.
Changes take weeks, or nobody answers at all. If it is an off-the-shelf tool, the vendor may just say the change isn’t possible.
We start with what you own: the domain, the hosting, the code and the data export. Then we tell you in writing what it takes to keep it running or build the missing parts. You decide before any work starts.
What slows a service company down, and what we build for it
Mornings go on the phone
Customers can’t book online, so the office spends the first hours of the day finding slots.
What we buildOnline booking in your real slots and service areas, written to the team calendar with a message to the office.
Dispatch runs on a whiteboard
The plan lives in a group chat, and technicians call in for the next address.
What we buildA dispatch board for the office, and a day list per technician with addresses, notes and the job history.
Job sheets turn into invoices days later
Paper sheets and photos come back at the end of the week, and someone types them up.
What we buildA job report on a phone browser: work done, parts used, photos and the customer’s sign-off, ready for invoicing when the job closes.
Maintenance contracts lapse unbilled
Renewals sit in a spreadsheet, and nobody notices a contract has run out until the customer calls with a fault.
What we buildContracts with visit schedules and renewal dates, and reminders to the office and the customer.
The software can’t price the way you do
Zones, call-out fees and contract rates don’t fit the off-the-shelf tool, so quotes get fixed by hand.
What we buildA quote page that reads your rules from a price sheet you edit. The car-service site’s quote page works from Google Sheets this way.
The website doesn’t book anything
It lists services and says “call us”, and it doesn’t answer the questions people search for.
What we buildService and area pages that answer real questions and take a booking. See Search and AI-assistant visibility.
An annual boiler service
The reminder goes out
The contract knows when the service is due and sends the customer a booking link a few weeks before.
The customer picks a slot
Only slots where a qualified technician is free in that area are offered.
The technician files the report
On a phone browser: readings, photos and the customer’s signature.
The invoice is ready
The job report becomes an invoice draft in your accounting tool the same day, not days later.
An example of how it would work, not a client story.
Booking, dispatch and job reports
What we build
What we build for a service company
The booking side follows what we built on the car-service site: slots written to Google Calendar, a message to the team for each booking, and a job every 30 minutes that resends anything that didn’t arrive.
- Online booking in your slots and service areas.
- A dispatch board and a day list per technician.
- Job reports with photos and the customer’s sign-off, ready to invoice.
- Maintenance contracts with visit schedules and renewal reminders.
Booking jobs by phone all morning?
Online booking is often the first piece, because it gives the office its mornings back.
Working with us
Tell us what happens today
Tell us how jobs are booked, dispatched and invoiced now, and which tools your team already uses. We reply within one business day, usually within a few hours.
A free first look
An online call, and an outside check of your site with XRay, our own audit tool. A deeper audit is scoped after the call.
Build, or take over
We build the missing parts, or take over a system someone else built. One team covers analysis, build, testing and DevOps.
Keep it running
Fixes, security updates and new features. Hourly billing, one rate for the whole team, a report every week.
You don’t need to be technical. The scope, the plan and the weekly report are written in plain words: what was done, why, and how long it took.
You own the code, the data and every account. More on how we work and the systems we have built.
What this doesn’t do
No GPS trackers or vehicle hardware. We use the data your existing tools expose. We don’t fit or sell devices.
No replacement for a tool that works. If your field-service software does most of the job, we build the missing parts around it.
No promises about Google rankings. We build pages search engines and AI assistants can read. Positions are not ours to promise.
No prices before we talk. Billing is hourly with weekly reports, scoped after the call.
Questions we get from service companies
Can customers book online in our real availability?
Yes. Booking reads your slots and service areas, writes the job to the team calendar and messages the office. The car-service site takes bookings in 45-minute slots the same way.
Do we have to replace the software we use now?
No. If it has an API, we can build the missing parts around it: online booking, your pricing rules or contract renewals.
Can technicians fill in job reports on site?
Yes, on a phone browser: work done, parts, photos and the customer’s sign-off. The report attaches to the job, and the office sees it is ready to invoice.
Can you connect to our accounting software?
Usually. We connect through its API, or through the exports it already produces. Which one depends on the tool, and we check that on the first call.
Where is our data kept?
In hosting and accounts registered to your company. We can host in the EU if you need the data to stay there, and you can remove our access at any time. If it includes health, financial or other sensitive data, here is what we check first.
Can the site work in our customers’ language?
Yes. The site, the booking pages and the messages customers get can run in more than one language. The car-service site we run, for example, runs in three languages. You supply or approve the text for each language.
Each customer needs their own login, and our technicians sign in with company accounts.
Each customer sees only their own jobs and reports, enforced in the database, not just on the screen. Sign-in through your company identity provider is agreed in the scope, and we check what it supports on the first call.
Who owns the system?
You do. You own the code, the data and every account.
Where to go from here
Dispatching from a group chat?
Tell us how a job moves from the first call to the invoice, and which tools it passes through.
We reply within one business day, Tallinn time (EET), usually within a few hours. No obligation.