Guides
Long reads for owners, written from what we run, updated in place.
Each guide answers one question at length, with a device you can use on the page and a section on what we do of it. Numbers only with a source; the date is the date it was checked.
- The enquiry answered while you are on site.drafts · approvals · handovers · one process at a time
- The booking button that books nothing.92.4% have the button · 36.7% have the booking
- From €500 to from €3 000, on one ladder.one page · a site · a store · a catalogue
- Be the page an assistant can quote.facts · structure · a facts file · a monthly measurement
- A script answers what it expected. An agent reads what you have.chatbot · agent · handover · a person approves
- Map first. Automate second. Measure always.processes · maps · tools vs custom · results
Questions
About these pages
How are the guides written?
From the systems we run for ourselves and the projects we have published, not from other guides. Every number has a source named next to it: our price ladder or a study we ran. Where we have no number, the guide says so.
When are the guides updated?
When the fact behind them changes: a price on the ladder, a rule on the trust page, a platform that changed its limits, a law that came into force. The date on each guide is the date it was last checked, not a decoration.
Why is there no blog on this site?
Because a blog fills up with posts nobody asked for. A guide exists when a question repeats and deserves a long answer; an answer page exists when it deserves a short one. Both are updated in place instead of republished.
Missing a guide you needed?
Tell us the question. If it repeats, it becomes a guide; either way you get an answer by email.