Skip to content

105 playbooks, each written for a trade

A workflow written for one trade, in that trade’s words. They come in 22 shapes. One shape, such as lead rescue or a booking brief, is written once for each trade that needs it, so a salon and a law firm each read their trade’s words.

Each shape below says what it does and why, then links to each trade it is written for.

After-hours answering

Answer customer messages at any hour from the business’s own facts, and hand anything else to a person with a holding reply.

Most messages ask what the business has already written down: hours, area, prices, how to book. Left until morning they go cold; answered by a bot that guesses, they create promises nobody made. An answer limited to the business’s own facts, with a clean hand-off to a person for everything else, does the first without the second.

Applicant intake

Acknowledge every job application at once, check it against the must-haves, log it, and send it to whoever hires.

Hiring in a small business is done between jobs: applications pile up unread, applicants hear nothing and accept elsewhere. An instant acknowledgement keeps them warm, a check against the hard requirements only (never a judgement of the person) sorts the pile, and the hiring person gets each one with that summary.

Approval chase

Send each request to the approver, go to the deputy if there is no answer in a day, and tell the requester the outcome.

An approval by email or chat has no deadline and no record: the approver is away, the requester does not like to chase, and the work waits. A request with a one-day window, a named deputy and an answer back to the requester keeps things moving and leaves a trail.

Booking brief

When someone books, send the owner a four-line brief: who they are, what they want, what they said, and one question worth asking.

The booking form asks good questions and nobody reads the answers: they sit in the scheduler’s event details until the call starts. A short brief in the owner’s inbox at booking time turns those answers into preparation.

Booking confirmation

Confirm every booking by text and email the moment it is made, with what to bring, and put the person in the CRM.

A booking made online lands in a calendar and nowhere else: the customer gets the scheduler’s generic email, the business’s own instructions are never sent, and the person never reaches the CRM, so nobody can follow them up later. A confirmation in the business’s own words, with the forms and directions, and a CRM record, closes all three gaps.

Cancellation recovery

When someone cancels, offer them a new time an hour later and tell the owner who cancelled and why.

A cancellation is usually a scheduling problem, not a lost customer, but the scheduler only frees the slot: nobody asks the person to rebook, and a week later they have gone elsewhere. A friendly offer of a new time, sent soon but not instantly, recovers a share of them, and the owner sees the reasons.

Conversation triage

Sort every new conversation in the support chat inbox by topic, page someone for the urgent ones, and put each in front of the team that handles it.

A shared support inbox has no order but arrival: a customer who cannot work waits behind a billing question, and each person assumes someone else has it. Sorting each conversation as it starts, with an explicit urgent flag, gives every one an owner and gets the bad ones seen in minutes.

Enquiry triage

Sort every enquiry by what it is, so the owner’s phone only rings for the kinds that need the owner and the rest land with the office.

A small business’s contact form takes everything: new work, existing customers, suppliers, sales pitches, job seekers. When one person reads them all in order, the job that matters waits behind the noise, and when everyone reads them, nobody owns any. Sorting on arrival puts each kind in front of the one person who handles it.

Failed payment recovery

When a card payment fails, send the customer a plain, kind message with the link to pay, by email and text, and tell the owner.

Most failed payments are expired cards and bank checks, not customers leaving, but the processor’s notice is cryptic and easy to miss. A human-sounding message with one link, sent at once, recovers many of them; the owner hearing about it means nobody discovers the gap at year end.

Feedback routing

When a customer scores the service, a low score reaches the owner’s phone the same day and the customer hears a person will call; every score is thanked and logged.

An unhappy customer usually tells the business first, if asked, and goes public when nobody answers. A score that reaches the owner the same day, with a promise of a call, turns the complaint into a recovery; a log of every score shows the trend. This shape never decides who is asked for a public review.

Lead rescue

Answer every new lead within a minute, get the owner on the emergencies, and chase anyone nobody has called back within the hour.

Most small businesses lose a lead within the first hour. The enquiry lands while the owner is on a job, and by the time anyone calls back the customer has booked someone else. An instant reply buys time, an alert gets the urgent ones answered, and a check an hour later catches the leads that slipped.

Meeting follow-up

Turn the notes from a client meeting, pasted into a form, into a recap the client receives and the actions as a task.

What was agreed in a meeting exists only in memory and scribbles until someone writes it up, which is the job most often skipped. A recap sent the same day fixes the agreement in writing, and the actions in the task list give each one an owner.

Order hand-off

When an order is paid, send it to the supplier, add it to the order log, and tell the team.

In a small shop each order is retyped two or three times, and the miss happens on the busiest day, when it costs most. Passing the paid order on automatically removes the retyping and the miss.

Overdue invoice chase

Remind customers of unpaid invoices one, seven and fourteen days after they fall due, firmer each time, and hand the twenty-one-day ones to the owner.

Chasing an invoice is awkward, so it is put off, and an invoice that is not chased in the first weeks becomes much harder to collect. A schedule that sends the polite reminder, then the firmer one, then hands over to the owner, does the awkward part every time and stops the day the invoice is marked paid.

Payment thank-you

When an invoice is paid, thank the customer, mark them a paying customer in the CRM and tell the team.

A payment is the best moment in the relationship and usually the quietest: the processor sends a receipt, the CRM is not updated, and the team finds out at month end. A short thank-you, a CRM that knows who pays, and a note to the team cost nothing and are rarely done by hand.

Quiet lead follow-up

Follow up a lead nobody has reached on day one, day three and day seven, then stop and hand it back to the owner.

A lead who did not answer the first call is not lost, but nobody owns the second and third attempt: they depend on someone remembering, and the follow-up dies on the first busy day. A fixed, short sequence that stops the moment anyone makes contact gets the second chance without pestering, and tells the owner when to let go.

Quote follow-up

Nudge every unanswered quote two, five and ten days after it was sent, and tell the owner which are going stale.

Most quotes are decided in the first days and many are lost to silence rather than price: the customer meant to reply. One follow-up is often forgotten, a third almost always. A short timetable that stops as soon as the quote is marked won or lost gets the answer without the owner having to remember.

Request to task

Turn every request posted in the requests channel into a task in the team’s list, and reply in the channel with the link.

Chat is where requests are made and where they are lost: a message scrolls away, and an emoji is not an owner. Turning each request into a task with a title, and saying so in the thread, moves it from conversation to the list the team actually works from.

Review request

Two hours after every job, ask the customer for a review; a week later, ask who else they know.

Reviews come from asking, and asking depends on someone remembering at the right moment, which is the moment the owner is already on the next job. A timed ask after every job, to every customer, builds the review count without ever choosing who is asked: Google treats screening customers before asking as review gating and can strip a business’s reviews for it.

Ticket triage

Acknowledge every support ticket at once, sort it by topic and urgency, page someone for the urgent ones, and tell the team.

A ticket queue is first-in, first-out by default, so severity is invisible until someone opens each one; a customer who is stopped waits as long as one with a question. Sorting and acknowledging on arrival tells the customer they were heard and puts the urgent ones on a phone.

Weekly enquiry numbers

Every Monday morning, send the owner how many enquiries came in through the client’s forms last week, and how many nobody has reached yet.

Numbers that have to be looked up are not looked at. A short report that arrives on its own, the same day each week, makes the trend visible and puts the uncalled leads in front of the owner while they can still be called.

Won-deal kickoff

When a deal is won, open the kickoff task, tell the team, and hand the owner the welcome to send, the same minute.

The days after a client signs set the tone, and they are when the seller has moved on and delivery has not started. Opening the kickoff work the moment the deal is won, with the team told, removes the silent week.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.