One line from the phone call to the review: request, preventiv, order, the jobs that deliver it, and the money. A board the office plans on, an app the crew works from, and no invoice to chase.
Why Pastrix
Not the cleaning — that part your crews are good at. It is the pricing, the planning and the collecting, and every one of them is usually done on paper.
The price is guessed on the phone from a surface nobody measured. Two people are sent to a four-hour job that turns out to take seven, and the discount depends on who answered.
Every service carries its own rate — fixed, per m², or hourly — and its own duration. The preventiv prices itself from the surface on the location, with the customer's group discount already filled in.
A whiteboard and a group chat. Somebody is ill on Tuesday, two rounds get swapped, and three customers find out when nobody rings the bell.
One board: crews down the side, days across the top, and the work nobody has taken in its own row above them. Drag a job to another day and the customer is told.
The work was done in March, the invoice was written in May, and nobody can say which of the customer's four shops has actually paid for what.
There is no invoice. The order carries total, paid and outstanding, settled by as many payments as it takes — and only a payment the office has confirmed moves what is owed.
The shape of the work
Somebody asks, you offer, they agree, crews go, they pay, they say how it went. Six records, in that order, and every screen in Pastrix sits on one of them.
A website form, a booking in the customer app, or a call somebody wrote down — with the surface, the address and a pin on the map.
A line per service, priced from its own rate. Valid for the days you set, sent by whatsapp or email, answered in the app or on paper.
What was agreed, and where the money lives. A single visit, or a contract repeating daily, weekly or monthly between two dates.
Plan writes a job per occurrence — the place, the service, the surface, the expected duration — and they come out assigned rather than waiting.
One or many against the order — a deposit and a balance, or month by month. Pending is a claim; only confirmed moves the outstanding.
Five stars overall, plus quality, punctuality and behaviour. The work is not finished from the customer's side until they have answered.
The line is the normal path, not a gate. A job can be written for work that was never quoted, and a preventiv for somebody who was never a request. Nothing is forced to have the record before it.
Features
Not a generic field-service tool with the wrong words on the buttons. Every field on every form is one your office already fills in on paper.
A service carries how it is priced — fixed, per m², or hourly — its rate, how long it takes (a fixed duration, or minutes per square metre), how many people it normally needs, its VAT rate and the checklist the crew ticks off. Change a rate and nothing already agreed moves: quotations keep the price they were written with, orders keep what was signed, and only the next preventiv is prefilled differently.
The customer pays; the location is cleaned. A company with four shops is one customer and four places — each with its own surface, access instructions (which bell, where the key is, the code, the dog), preferred days and its own contact.
Work is given to a crew because crews change on the morning and jobs do not. A colour for the board, a supervisor who answers for it, working hours, a daily capacity, and the services it is trained for — attach none and it does everything.
Daily, weekly or monthly between a start and an end date. Planning books a job per occurrence up to a horizon you can actually crew — about a month ahead — and is run again as the work approaches.
Total is what was agreed. Paid is the sum of the payments the office has confirmed. Outstanding is the difference, and it moves by itself the moment a payment is confirmed, refused or refunded. A customer declaring a bank transfer stays a claim — with the receipt they uploaded attached — until somebody has matched it to the bank. Refuse a confirmed payment and the outstanding goes back up, while the refused record stays exactly where it is, so what happened is still readable a year later.
Turn it on and a crew cannot close a job without a picture before and a picture after. It costs them fifteen seconds and it settles most complaints before they are made.
An overall mark and separate ones for quality, punctuality and behaviour. Two stars or less is a complaint — ring them, send a crew back, take it off the bill, then mark it handled. Only what you publish reaches the website.
Jobs, quotations, orders, payments, customers and reviews. Set the filters, choose the columns, save it into a group with a name — then download it, take it as a CSV, or mail it with a note.
Pricing a service
Pick how a service is priced once, on the service itself. From then on every preventiv fills its own lines in — and every price stays editable, because the phone call always changes something.
One price for the visit, whatever the day looks like. The duration is fixed too, so the board knows how much of the crew it takes.
The rate meets the surface on the location. Duration comes from minutes per square metre, so a bigger place books a longer block.
For work nobody can size in advance. Priced on the hours agreed, and the actual minutes are recorded against them.
Planning
Crews down the side, days across the top, every job a block on its crew's row. Open it at a day to see how long the work really is, or at a week to see how loaded everybody is.
Jobs with no crew get their own row above the crews, so what nobody has taken is the first thing on the screen rather than something you find on Friday.
Dropping a job on another day moves it and counts the move. A drop the server refuses springs back rather than lying about where the work is — and dragging can be switched off entirely.
Sliding to another week fetches that week. A year of a weekly contract never has to be on the screen at once, and the board stays quick on a shop laptop.
The board will let you overload a crew — some mornings you have to. The daily capacity is simply the number the load bars are read against, so you can see the cost of it.
Crew App
Your crews should not have to ring the office to find out where they are going or how to get in. Today's round in order, the way in, the checklist, and the four buttons that move a job along.
Their own jobs, for today, sorted by the hour they are due. Not another crew's work, not next week's, and no prices anywhere on the screen.
The address opens in maps and the access instructions come with it: which bell, where the key is, the code, the dog. The office stops taking those calls at eight in the morning.
The service's own checklist is ticked off on the phone. Where the office requires it, the job will not close without a picture before and a picture after — attached to the job, not lost in a chat.
Accept, on the way, start, complete. The board moves without anybody ringing, the customer sees the visit approaching, and the actual minutes are recorded against what the job was estimated to take.
Customer App
Asking for a price needs no account. Everything after it does. They ask for work, answer the preventiv, follow the visit, pay what is owed and say how it went — and they see four states only. Where the crew actually is in the job is nobody's business but yours.
Dashboards
One is a list of phone calls, one is the shape of a year, one is direction, and one is what gets read out at a meeting. Each is a permission of its own.
Today, and the phone calls it implies. The figures of the day across the top, then the work in the order it happens — and down the side the requests that came in, the quotations waiting and the reminders due.
The shape of a year, read per year, per crew and per service. Each panel carries its own filters, so one service can be compared against the whole company without opening a second screen.
Direction rather than size. The current month, quarter, half and year against the one before and against last year — for jobs delivered, value delivered and money collected.
The period in one page — what came in, what was quoted, what was signed, what was done and what was paid — over any range of dates. It is the page that gets read out at a meeting.
Pricing
Both applications are on every plan, and so is the 14-day trial. No card, and nothing to install on anybody's phone but the app itself.
Requests arrive as CRM leads. If you already run the CRM module, they land in the list you are using — if not, Pastrix works without it and the work starts at the quotation.
FAQ
There isn't one, and that is deliberate. The order carries what was agreed and what it is worth, and payments settle it directly — a deposit and a balance, or a contract paid month by month. What is owed is the outstanding on the order, and it moves by itself as payments are confirmed. One record fewer to keep in step with reality.
No — and you shouldn't. A year of a weekly contract is fifty jobs nobody has crews for yet. Planning books up to a horizon: the end date if it is close, otherwise about a month ahead. Run it again as the work approaches and the next block of jobs appears, already carrying the place, the service, the surface and the expected duration.
Nothing breaks, because work is given to a crew and not to a person. Crews change on the morning and the jobs do not — whoever turns up does the round. If you do need to name people, assigning to specific members takes only them; naming nobody takes the whole active crew.
Yes. Asking for a price needs no account — the request arrives with the service, the surface, the property type and a pin on the map. Everything after that does: answering the preventiv, following the visit, paying and reviewing. Winning the request creates the customer, turns the address into their first location, and reuses an existing customer if the phone or email already belongs to one.
Estimated is what the work was planned to take, from the service and the surface. Actual is the minutes between the crew starting and finishing on their phone. The gap between them is the most useful number in the module: a service that always overruns is either priced wrong or crewed wrong, and you will see which within a month.
Yes — Revo is modular and the modules share one data layer. Requests are CRM leads rather than a second, worse list of their own, so the channels, follow-ups and won/lost you already use apply to them. Add accounting, HR or the website module and none of it is entered twice.
14 days free, no card. Bring your customers and their surfaces in from one CSV and plan the week before you close.