You inspect.The AI writes the report.And runs your back office.

Enquiries out of your mailbox

Mail from the connected Gmail mailbox, the website form and phone calls you type in all arrive in one list, new ones first, with the pest it recognised and the client matched on email address or phone number. You can see a colleague already in one; nothing is locked.

Triage in four buttons

From an enquiry you book a visit, build a quote, raise a task, or answer it inside the app. The reply goes through your own mailbox and stays attached to the thread. Closing one always takes a reason.

Tasks with an owner and a date

Tasks arise where they belong: from an accepted quote, from a recommendation somebody took on, from an enquiry, and from the nightly contract run when nothing fits. A 'book the visit' task closes when the visit is booked, not when somebody ticks a box.

Notifications that are actually about something

Booked, moved or cancelled; a visit that was not charged and why; an invoice gone overdue; a licence about to expire; a tablet stuck with a refused write. No noise, and none of the things somebody has to chase left out.

Offline is not an emergency mode

Every write goes through the queue, from the very first screen. A whole visit done in a cellar (findings, photos, products, signature, completion) lands exactly once when the signal returns, even after the app has been killed and reopened. Only a handful of things genuinely need the server, and each says so in a sentence.

Checkpoints in walking order

Floors as tabs with a counter, markers on the floor plan, and per point the status, a consumption slider, the species, a note and photos. A point that could not be reached asks for a reason and for how to get in next time, and that sentence prints under the row on the next visit.

Placement on the first visit

On visit 1 you put the stations on the floor plan, in walking order. A chemical states the removal date it brings with it and books its own removal visit: a legal date you may bring forward, but never cancel.

Findings, risks and recommendations

The per-pest findings are derived from the checkpoint logs; nothing is typed twice. Out of those the AI writes the risks and the recommendations, with the catalogue as a fallback when the model does not answer. You accept, rewrite in one language, or dismiss. Only what was accepted reaches the report.

A signature at the door

The client sees a summary in their own language: what was done and found, the accepted risks and recommendations, and the products used with their removal dates. No price and no billing. If nobody is available you record why and how you got in, and that goes into the report.

The report the same day, and the completion check

Every step carries what is still open and which section clears it, so you know while you are still standing there. Once it is clear the report goes out as a PDF: built from the accepted rows, in the client's language, with Reply-To set to your own address.

A quote in ten steps

Client, site, pests, pest details, risks, measures, recommendations, products, notes, review. The AI writes the risks and the measures out of the pest details; product suggestions are something you ask for, so the price stays yours. Every step is saved, so walking away halfway costs nothing.

An acceptance link for the client

The quote goes out as a PDF with a link beside it. The client accepts or declines with no account and no login, leaving a note or a reason. An acceptance raises a task with that note on it; a decline reopens the task the quote came from. A quote is never signed. The click is the record, and the visit is what gets signed.

Billing decided at the door

The technician decides on the spot whether this visit is billed; a contract sets the default, not the decision. The line editor is the only place a price changes, with the agreed contract rate as the starting price and the catalogue figure beside it. Cash or card at the door simply queues when there is no signal.

The money list: seven stages

Report not sent, billing not decided, draft, sent, overdue, disputed, and contract period due for invoicing. Each with a count, a euro total and the age of the oldest item. Ordered by how long the money has been sitting, never by invoice number.

Reminders, disputes and credit notes

The reminder sends itself seven days after the due date; the formal notice stays a person's decision, with a business text and a private one. A dispute pauses the ladder, a part-payment keeps the invoice open, and a credit note reverses a whole invoice in its own number series.

VAT, the quarter and the bookkeeper

VAT per rate on every line and in the totals, the quarter on an invoice basis, and an export for the bookkeeper that includes cancelled numbers. The server recomputes every total and its figure wins; the screen only adds up what you see.

Clients and sites

A client with their sites, contacts and language. The KvK number fills in the name and the address, and per site you record the preferred day and the treatment hours: the window the planner fits a visit into. A bakery is treated before it opens, a kitchen after it shuts.

Floor plans with checkpoints

Upload a plan per floor (a photograph of the plan on the wall is enough) and place the checkpoints on it in walking order. A marker's colour is the latest status, its position is the route, and one tap opens that point's history.

A year per checkpoint

Per station: date, visit, status, consumption band, species, photos and who was there, with the chemical log and its registration numbers below. As a PDF for the client's folder: exactly the question an inspector asks, on one screen.

Contract health

Four numbers in place of a renewal calendar: behind schedule, ending inside 60 days, next visit not booked, and delivered and current. Each with the money per year at stake. A contract that is behind and renewing sorts to the top, because that is the one you lose.

Products and chemicals

Registration number, unit, price and VAT rate; a chemical gets a removal period. What was used on a visit is copied rather than looked up, so a report from September does not change when you edit the catalogue. A technician can create a product at the door; the office reviews the price later.

Proof in three taps

The signed report for a visit is three taps away, with one pill that says the same thing on every screen: signed, unsigned, or unsigned with the reason beside it.

Ask in plain language

What is my next visit? Who is free on Monday in Utrecht? Which invoices are overdue? Typing is the default; speaking sits beside it, and what was heard is printed first, with a button to correct it.

Reading is free, writing takes a tap

The assistant reads for itself, but books, moves or cancels nothing until you tap a confirmation card. One card per action, never a batch, and the confirmation is not a button the model can press.

Every answer says what it checked

Under every answer sits 'Checked: Jan's day · 3 times · De Vries (1 match)'. Every fact in an answer came from something looked up in that turn, not from a model's memory.

It follows your role, not your device

A technician in the van has the same abilities on their phone as on the tablet: their own day, a client, a site's history, and 'I'm on my way'. Invoices and enquiries are there for the office, on whatever device they happen to be holding.

One app for the office and the field

The office portal and the field app are the same web application, designed for a tablet held upright; a desktop gets the same screens with more room. For Android there is an installable build, so the tablet in the van keeps working offline and photos stay on the device until they are sent.

Moving your current system across

Switching is a step we run, not a self-service import: we go through your clients, sites and contracts with you, move them over, and check them together before anybody relies on them.