Loading...
Loading...
Turnwrk started with turnover cleaning, and the engine underneath it never knew what a “clean” was. Services, durations and prices are your catalog — so a weekly pool route, a mow cycle and a Tuesday handyman call all book, schedule, dispatch and close out the same way.
None of this is per-vertical. It is the same booking, scheduling and field layer, pointed at whatever you sell.
Services, add-ons, durations and prices are your data, not our code. “Weekly pool service, 45 minutes” prices, schedules, assigns and invoices with nothing special added — the maths is your base price plus your line items plus your extras, and it has no idea what trade you are in.
A hosted page at your own slug with your logo and colours. Customers pick a service, see real open windows against your crew’s actual availability, and book — or you enter the job yourself and skip the page entirely.
A status-coded job queue and a month calendar. Assign one person or a crew — allocated time splits across them automatically, and each gets their own notification, check-in and timesheet.
The same mobile app your techs already use for maintenance work: job card, an “on my way” tap, check in and out on site, photo-verified checklist. Photos taken with no signal queue on the phone and upload when it comes back.
Weekly, every-other-week and monthly plans generate their own future visits on a schedule, and pause or cancel in one place. One-off jobs sit in the same queue alongside them.
Every finished job carries its checklist and its photos. Completed work triggers a review request — a high rating gets pointed at your public profile, a low one comes to you first so you hear it before the internet does.
Hourly rates live on each crew member and check-out times roll into a weekly payout total. No separate spreadsheet, no end-of-week reconciliation — and you pay them however you already do.
Dispatch builds an optimised day route for a tech out of that day’s jobs using Google’s routing, with a supply stop dropped in near the middle when you want one.
These are the shapes we are building service packs for. The engine is the same underneath all of them — a pack is terminology, starter services, checklist templates and cadences.
Weekly and every-other-week stops, plus the filter cleans and repairs that route-only tools drop on the floor.
Mow cycles that repeat on their own, and the cleanups, installs and one-time jobs that carry the better margin.
Quoted work, scheduled work, and the call that comes in at four o’clock — filed, assigned and closed out without a whiteboard.
The vertical the engine was built on. It ships today as Turnwrk Clean, in beta — booking page, dispatch, crew app and the job record.
There is no trade setting to pick. You describe what you sell, and everything downstream follows from it.
Each service gets a name, a duration, a base price, and any per-unit line items you charge for — pools, zones, hours, whatever your unit is. Add-ons sit alongside. That is the whole configuration.
Your booking page prices from that catalog live and only offers windows your crew can actually cover. Or you put the job straight into the queue yourself.
One person or a crew. Allocated time splits automatically, everyone gets a notification, and the customer gets an “on my way” the moment the tech taps it.
Check in on site, work the checklist with photos where you require them, check out. The time lands on the timesheet and the job lands in the record with its proof attached.
Turnwrk Clean is in beta, and everything on the left runs in it now. The right is the trade-pack work in flight. We would rather you knew which was which before you talked to us.
The payments flow — card on file at booking, an authorisation before the visit, capture on completion, then an invoice — is built and runs end to end in beta on a test gateway. Live card processing is in the right-hand column.
Pool, lawn, handyman, cleaning and STR turnover are the packs we are building first. If you run something else on a repeating schedule, this is the form that decides what comes after them. No demo script and no drip sequence — a person reads it.
If your work is a scheduled visit to an address, with a person and a checklist, the engine already handles it — services and prices are yours to define, and nothing in the pricing or scheduling code assumes a trade. What is not there yet is a purpose-built pack: the terminology, starter service list and checklist templates that make it feel made for you. Pool, lawn, handyman, cleaning and STR turnover are the packs we are building first. If yours is not on that list, tell us below — we are choosing what comes next from what we hear.
Tell us what you run, how the work repeats, and what your current tools make you do by hand. That is what decides the order we build in.