Sicc Media // Break the Mold \\ DARE TO BE EXTRAORDINARY.

Blog

  • Automating Field Intake and Estimate Follow-Ups

    Automating Field Intake and Estimate Follow-Ups

    Quotes do not lose because of price nearly as often as they lose because of delay and silence.

    TL;DR Send the estimate from site or same day. Then run a fixed four-touch follow-up automatically. Add digital signature so accepting takes one tap. Most quotes that go quiet were never chased more than once.

    Speed matters, and here is the honest version

    The widely circulated figures about response speed multiplying conversion odds by specific factors trace back to the Lead Response Management Study by Oldroyd, McElheran and Elkington, built on data from roughly 2007 to 2011. It is real research, it is frequently misattributed to recent years by vendor blogs, and the specific multipliers should be treated as period-specific rather than a current law.

    What holds regardless of the numbers: the first credible responder has a large advantage, and that advantage decays quickly. Do not quote a percentage you cannot source. Act on the direction, which is well established.

    Practical targets

    • Acknowledge every enquiry within an hour during business hours, automatically if needed.
    • Get the estimate out same day where scope allows.
    • Quote from site for straightforward jobs.

    Structured field intake

    The estimate is only as good as the information captured on site.

    A standard intake form on mobile

    • Job type, from a fixed list.
    • Access notes and parking.
    • Measurements and quantities.
    • Photos, minimum three.
    • Condition flags that change the price.
    • Customer’s stated priority. Cost, speed, or quality. Ask directly.
    • Decision timeline and who else is involved.

    The last two are the most commercially useful and the most often skipped. Knowing whether they need a partner to agree changes the entire follow-up.

    Fixed lists over free text wherever possible. Free text does not aggregate and cannot drive automation.

    Instant quote calculators

    For standardised work, price on site.

    Where they work

    • Jobs with predictable scope and pricing rules.
    • Per-unit work. Per metre, per window, per unit.
    • Standard servicing.

    Where they do not

    • Anything where condition drives cost.
    • Older properties with unknowns.
    • Jobs requiring specialist assessment.

    Build in a range, not a point, for anything uncertain.

    Based on what I have measured, this comes to between $840 and $1,150. The variable is the state of the pipework behind the panel, which I cannot see until we open it. I will confirm before doing anything beyond the lower figure.

    Honest ranges convert better than precise numbers that later change.

    The four-touch follow-up

    Set this up once and it runs on every quote.

    Touch When Content
    1 Immediately on send The quote, with a one-line summary and the accept button
    2 Day 3 “Any questions on this?” Nothing else
    3 Day 7 Something useful. A relevant photo, a note about timing
    4 Day 14 The close-out. “Filing this unless I hear otherwise”

    Stop the sequence on any reply, and on acceptance. Automatically. Nothing damages a live conversation like an automated chase arriving mid-negotiation.

    Touch 4 does more work than touches 2 and 3 combined.

    Hi Sarah, I am going to file this one as a no for now, which is completely fine. If the timing changes, the price holds until the end of next month and you have my number.

    No pressure, a real deadline, and permission to say no. It produces replies from quotes that had gone completely silent.

    Digital signature

    Removing the print-sign-scan-return sequence measurably increases acceptance.

    What to look for

    • Works on a phone. Most acceptances happen on a phone.
    • No account creation.
    • Legally valid in your jurisdiction. Electronic signatures are broadly recognised, but check the requirements for your document types.
    • Automatic copies to both parties.
    • Notification to you on signature, immediately.

    Put the accept button at the top and the bottom of the quote. Not only after four pages of terms.

    What the quote document should do

    • Lead with the outcome, not the line items. “A new combi with a ten-year warranty, fitted in two days.”
    • Then the breakdown. Labour, parts, disposal, compliance.
    • State what is not included, explicitly.
    • Give the timeline and your current availability.
    • One page of terms, not six.
    • A clear expiry date. Not artificial urgency, just a real validity window.

    Handling the response

    Accepted. Confirm within the hour, book the date, send the welcome kit.

    Question. Answer by phone, not email. A question is a live buying signal and text loses it.

    Too expensive. Ask what they compared it to before adjusting anything. Frequently the comparison is a different scope, and the answer is explanation rather than discount.

    Silence. Let the sequence run. Do not add manual chases on top of it.

    Measure it

    • Time from site visit to quote sent. The number to attack first.
    • Quote acceptance rate, by job type and by value band.
    • Time from quote sent to decision.
    • Acceptance rate by touch. This tells you which follow-ups earn their place.
    • Reasons for loss, recorded. Ask, and log the answer.

    Build the four-touch sequence this week and switch it on for every quote. The day-14 close-out message alone will recover jobs you had already written off.

    Need a pro to automate it? [BOOK A CALL]

  • Transitioning from Service Technician to CEO

    Transitioning from Service Technician to CEO

    The business that cannot run without you is not an asset. It is a job with unusually bad hours.

    TL;DR Audit your time before changing anything. Delegate the highest-volume lowest-skill work first. Hire your first manager before you feel ready. Replace your presence with a small set of numbers you check weekly.

    The time audit

    You cannot delegate what you have not measured.

    Do this for two full weeks. Every task, in fifteen-minute blocks. Tedious, and there is no substitute.

    Then sort every entry into four buckets

    Bucket Definition Action
    Only you Genuinely requires the owner Keep, protect the time
    You are best You are better but others could learn Train and hand over
    Anyone could No special skill required Delegate immediately
    Should not exist Adds no value Stop doing it

    Most owners find 40 to 60 percent of their week in the bottom two buckets. That is the recoverable time and it is usually more than expected.

    The uncomfortable finding: much of the “only you” bucket is not. It is work you enjoy, or work you have never trusted anyone else with. Be honest in the sort or the whole exercise is wasted.

    Delegate in the right order

    Wrong order: hand over the parts you dislike first.

    Right order: hand over the highest-volume, lowest-judgement work first.

    Typical sequence

    1. Administration. Data entry, filing, scheduling logistics, invoice chasing.
    2. Routine field work. The jobs any competent technician does.
    3. Customer communication, on routine matters.
    4. Quoting, within defined bands.
    5. Complex field work.
    6. Team management.
    7. Pricing and commercial decisions. Last, and possibly never.

    Each step requires the previous one to be genuinely stable. Skipping ahead is how businesses end up with an overwhelmed owner and a confused team.

    Your first hire off the tools

    Not another technician. An administrator or a coordinator.

    Why this before another technician

    • Another technician gives you more revenue and more admin.
    • An administrator gives you back time, which is the constraint.
    • Part-time is often enough at first.

    What they take over

    • Phone answering and enquiry handling.
    • Scheduling and diary management.
    • Invoicing and payment chasing.
    • Supplier orders.
    • The reminder and follow-up sequences.

    This role usually pays for itself in recovered billable hours alone, before counting the jobs that stop being missed.

    Your first manager

    Hire before you feel ready. Waiting until it is obviously necessary means hiring under pressure, which produces bad hires.

    Signs it is time

    • You are the bottleneck on daily decisions.
    • Quality varies by who turns up.
    • You cannot take a week off without the diary emptying.
    • You spend more time coordinating than doing.

    What to look for

    • Judgement over technical skill. You can teach the trade. Judgement is harder.
    • Willingness to make a call and own it.
    • Somebody who will tell you when you are wrong. A manager who only agrees with you is an expensive assistant.

    Then actually let them manage. Overruling your manager in front of the team destroys the role you just created.

    Replace presence with numbers

    You stayed in the middle of everything because that is how you knew what was happening. Replace that with a small set of numbers.

    A weekly dashboard, under ten items

    Metric Why
    Jobs completed Volume
    Revenue, and against target The obvious one
    Average job value Pricing and upsell health
    Enquiries received and converted Front of the funnel
    First-response time The strongest leading indicator
    Complaints and callbacks Quality
    Diary fill, next two weeks Forward visibility
    Cash position and overdue invoices Survival

    Fifteen minutes a week reading these replaces being present for everything.

    Set thresholds, not just values. “Response time over four hours” should trigger a conversation. A number without a threshold is trivia.

    What you should be doing instead

    The work only the owner can do

    • Pricing and margin. Nobody else can decide what you are worth.
    • Hiring. Especially the first few of each role.
    • Key relationships. Largest accounts, best partners, main suppliers.
    • Direction. Which services, which markets, what next.
    • Culture. Set by what you tolerate, not by what you write down.

    Block time for this. It has no deadlines and no one chasing it, so without a protected block it never happens.

    The hard parts nobody mentions

    You will be worse at some things than you were. The first quotes your team writes will be worse than yours. Accept a temporary quality dip or you will never get out.

    Identity. Being the person who fixes things is often the whole self-image. Being the person who runs a business that fixes things is different, and the adjustment is genuine.

    Loneliness. The team stops telling you things. That is normal and it is also a real information loss. Build deliberate channels to replace what you used to overhear.

    Correcting a good decision you would have made differently. Do not. If the outcome was acceptable, leave it.

    Measure the transition

    • Hours on the tools per week, tracked. The headline number.
    • Decisions escalated to you per week. Should fall steadily.
    • Revenue per owner-hour. The number that proves the point.
    • Days you can be absent without disruption. Test it deliberately.

    Do the two-week time audit starting tomorrow. Nothing else in this article is actionable until you can see, in writing, where your week actually goes.

    Need a pro to plan it? [BOOK A CALL]

  • Selecting the Ultimate CRM and Dispatch Stack

    Selecting the Ultimate CRM and Dispatch Stack

    Most software disasters in small service businesses start the same way: buying the platform before writing down what it needs to do.

    TL;DR Write the requirements first. Test the field experience before the office one. All-in-one is right for most businesses under twenty staff. Migrate clean data or the new system inherits the old mess.

    Write requirements before you look at anything

    Two hours of writing saves a year of regret.

    Answer these, honestly, from how you actually work

    • How many jobs a week, and how many are same-day?
    • How many people need to see the schedule?
    • Do technicians work in areas with poor signal? This one is decisive.
    • Do you invoice from site or from the office?
    • Do you need parts and stock tracking, genuinely?
    • Recurring contracts or one-off jobs, or both?
    • What must it connect to? Accounting, payments, phone system.
    • What are you doing on paper today that you want to keep doing on paper?

    Mark each as must-have or nice-to-have. Vendors sell to nice-to-haves. You need the must-haves to work.

    The categories

    Category What it covers Who it suits
    Field service management Scheduling, dispatch, job records, mobile app, invoicing Most trades. The default
    General CRM Contacts, pipeline, marketing Sales-heavy, quote-heavy businesses
    All-in-one marketing platform CRM plus email, SMS, funnels, automation Businesses where marketing is the bottleneck
    Accounting-first Invoicing and books with light job features Very small operations

    Most service businesses need field service management as the core, with everything else attached to it.

    All-in-one or best-in-breed

    Under roughly twenty staff: all-in-one, nearly always.

    Why

    • One system to learn, one to administer.
    • Data lives in one place, so reporting works without integration work.
    • One vendor to chase when something breaks.
    • Integration maintenance is a job nobody at your size has time for.

    Best-in-breed makes sense when

    • One function is genuinely specialised and central to your business.
    • You have somebody responsible for the systems.
    • The all-in-one option is materially worse at the thing you do most.

    The honest trade-off: all-in-one is worse at everything and better overall, at small scale.

    Test the field experience first

    This is where implementations fail, and it is almost always tested last.

    Trial checklist, done by an actual technician on an actual job

    • Does it work with no signal? Offline mode that genuinely queues and syncs, not a spinner.
    • How many taps to complete a job? Count them. Over about fifteen and it will not get used properly.
    • Photo upload. Fast, and does it compress sensibly on mobile data?
    • Can they see the customer history without leaving the job screen?
    • Battery drain over a full day.
    • Does it work with cold hands and gloves? Not a joke. Small touch targets fail in real conditions.

    If the technicians hate it, the data will be wrong, and everything downstream depends on that data.

    Integration bridges

    For the connections the platform does not offer natively.

    Tools like Zapier or Make connect systems without code. Useful and genuinely powerful.

    Caveats worth knowing before you build on them

    • They break silently. Build a failure notification, or you will find out from a customer.
    • They cost more at volume than the plan you sign up on.
    • They add latency. Fine for a follow-up email, not for anything time-critical.
    • Every bridge is a thing to maintain, indefinitely.

    Rule: prefer a native integration even if it is slightly worse. Fewer moving parts wins over years.

    Data cleanliness

    Migrating bad data into good software produces bad software.

    Before you migrate

    1. Deduplicate. Same customer under three spellings and two phone numbers.
    2. Standardise phone formats. This breaks SMS and click-to-call otherwise.
    3. Delete the genuinely dead. Contacts with no activity in five years and no service history.
    4. Fill the fields you will filter on. Acquisition source, customer type, service type. Retrofitting these later is painful.
    5. Decide what not to bring. History from a system you barely used is clutter.

    Set the rules for the new system on day one. Required fields, naming conventions, who can create records. Systems degrade from the first week if nobody sets standards.

    Evaluating vendors

    Ask these

    • What does export look like? Get a straight answer. Difficulty leaving is a real cost.
    • What does it cost at double our current size? Per-user pricing scales unpleasantly.
    • What is included versus an add-on? Especially SMS, payments and reporting.
    • Where is support based and what are the hours? If your emergency is at 6am, their 9-to-5 support in another timezone matters.
    • How often does the mobile app get updated?

    Talk to a business your size in your trade. Vendor reference customers are chosen for a reason. Find your own through a trade group.

    Migration

    Run parallel for two to four weeks. Painful, and cheaper than a failed cutover.

    Sequence

    1. Configure and test with a small dataset.
    2. Train the office team.
    3. Train the field team, on site, with real jobs.
    4. Migrate the data.
    5. Run both systems briefly.
    6. Cut over, with the old system readable for a year.

    Pick a quiet period. Migrating during peak season is a decision people regret specifically and loudly.

    Write your must-have list this week, before you book a single demo. Every bad software purchase in this industry traces back to skipping that document.

    Need a pro to choose it? [BOOK A CALL]

  • Building SOPs That Allow Your Business to Scale

    Building SOPs That Allow Your Business to Scale

    You cannot delegate a process that only exists in your head. Everything else about growing is downstream of that.

    TL;DR Record yourself doing it rather than writing it from memory. One page per process. Written for the person who has never done it. Store where the work happens, not in a folder nobody opens.

    Record first, write second

    Writing an SOP from memory produces a document that skips the steps you no longer notice you take.

    The better method

    1. Screen record or film yourself doing the task once, narrating as you go.
    2. Get it transcribed.
    3. Edit the transcript into steps.
    4. Have somebody else follow it and note every point where they had to ask a question.
    5. Fix those points. That is the actual SOP.

    Step four is where the value is. The gaps are invisible to the person who wrote it and obvious to the person following it.

    Which processes first

    Not everything needs an SOP. Prioritise ruthlessly.

    Priority Type Why
    1 Done often, by several people Highest total impact
    2 High cost when done wrong Compliance, safety, invoicing
    3 Only you know how Single points of failure
    4 New hires need it week one Onboarding bottleneck
    Last Rare and low stakes Rarely worth documenting

    Start with the five things that happen every single day. Booking a job, arriving on site, handling payment, closing a job, handling a call-out.

    The format

    One page. Every time.

    Process: Closing out a completed job
    Owner: Field technician
    When: Before leaving site
    Time: 10 minutes

    Steps
    1. Walk the customer through what was done. Point at it.
    2. Take the after photos, same angles as the before set.
    3. Complete the job record in the app: parts used, time on site, anything noted for next visit.
    4. Hand over the care sheet and explain the first-48-hours section.
    5. Ask the pencil-it question for the next service.
    6. Mark the job complete. This triggers the invoice and the feedback request.

    If something is not right: do not promise a fix on the spot. Say you will confirm by end of day and flag it to the office before you leave the street.

    Common mistakes: forgetting the after photos, marking complete before the record is filled in.

    The “common mistakes” section is the most valuable part and the one everybody omits.

    Write for the person who has never done it

    Assume no context.

    • Name the actual buttons and screens, not the concept. “Tap Jobs, then the job, then Complete” not “close the job in the system”.
    • Say where things are. Physical location, folder path, drawer.
    • Include the decision points. “If X, do this. If Y, do that.”
    • Say who to ask when the SOP does not cover it.

    Avoid “as appropriate”, “use judgement”, “as normal”. These are the phrases that mean the writer could not be bothered to specify, and they are exactly where new people fail.

    Process mapping before writing

    For anything with branches, sketch it before you write it.

    Simple mapping

    • Boxes for actions.
    • Diamonds for decisions.
    • Arrows for sequence.
    • Mark handoffs between people, because handoffs are where things get dropped.

    Do this on paper. Software mapping tools slow this down and the map is a working tool, not a deliverable.

    What mapping reveals, reliably: steps that exist for no reason, handoffs with no confirmation, and approvals nobody actually performs.

    Where to store them

    The location determines whether they get used.

    Good

    • Linked directly from the job in your field app.
    • A QR code in the van or on the equipment.
    • A pinned channel in whatever your team already uses to communicate.
    • Printed and laminated, for physical processes.

    Bad

    • A shared drive folder nobody has opened since induction.
    • A wiki with a search that does not work.
    • Anything requiring a separate login.

    The rule: the SOP must be reachable from where the work happens, in under ten seconds.

    Keeping them current

    An out-of-date SOP is worse than none, because it teaches the wrong thing with authority.

    • Date every document and show the date prominently.
    • Name an owner per SOP.
    • Review annually, or whenever the process changes.
    • Make correction easy. Anyone who follows an SOP and finds it wrong should be able to flag it in one message, and be thanked for it.
    • Version the video too, if the interface changed.

    Delegation and accountability

    An SOP without an owner is a suggestion.

    For each process, be explicit about

    • Who does it. By role.
    • Who checks it, if anyone.
    • What the standard is, measurably.
    • What happens when it is not met. Retraining first, always.

    Delegating properly

    1. Show them.
    2. Do it together.
    3. They do it, you watch.
    4. They do it, you check the output.
    5. They do it, you check the metric.

    Most delegation failures are jumping from step one to step five.

    Measure it

    • Time to competence for a new hire, before and after.
    • Repeat questions. The same question asked twice is a missing SOP.
    • Error rate on documented versus undocumented processes.
    • Hours you personally spend on work that has an SOP. If it is not falling, the SOPs are not being used.

    Record yourself doing your most repeated daily task tomorrow, narrating as you go. That recording is the raw material for your first SOP, and it takes no extra time because you were doing the task anyway.

    Need a pro to build them? [BOOK A CALL]

  • Practical AI Use Cases for Daily Operations

    Practical AI Use Cases for Daily Operations

    Most AI advice for small business is written by people who have never had to answer a phone at 7am with a van already loaded.

    TL;DR Use it where a human checks the output before it leaves. Drafting, triage, transcription and repurposing. Do not let it speak to customers unsupervised, and do not let it near your pricing without review.

    The rule that decides everything

    Does a human see the output before a customer does?

    If yes, AI is usually worth it. If no, the failure mode is a customer receiving something wrong in your name, and that costs more than the time saved.

    Task Human checks first? Verdict
    Drafting a quote Yes Good use
    Summarising a call Yes Good use
    Sorting enquiries by urgency Yes, before action Good use
    Turning one article into five posts Yes Good use
    Answering the phone out of hours Partially Careful
    Sending pricing directly to a customer No Avoid
    Handling a complaint No Avoid

    Proposal and estimate drafting

    Where it saves real time. Not calculating the price, writing the words around it.

    The workflow

    1. You dictate the notes on site. “Combi swap, 1930s semi, existing pipework needs replacing to the airing cupboard, two days, awkward loft access.”
    2. AI drafts the proposal using your template and your standard clauses.
    3. You add the price yourself.
    4. You read it, correct it, send it.

    What this saves. Twenty to forty minutes per proposal, mostly on the descriptive sections you rewrite from scratch every time.

    What it must not do. Generate prices, invent specifications, or promise timescales you did not state. Give it your template and your notes, not a free hand.

    Call and meeting summaries

    The highest-return low-risk use.

    Record the site visit or the call, with consent, and get a structured summary out: what was discussed, what was agreed, what needs quoting, what the customer was worried about.

    Why it works. The notes get written, which they otherwise do not. The information that usually lives in one person’s head ends up in the record.

    Consent matters. Recording rules vary by jurisdiction and some require all parties to agree. Ask, plainly, and note the answer.

    Enquiry triage

    Sorting, not answering.

    Incoming enquiries get classified: emergency, quotable job, existing customer, out of area, supplier, spam. Tagged and routed accordingly.

    What this fixes. The emergency sitting unread in a shared inbox at 8am behind fourteen marketing emails.

    Keep the action human. The AI sorts. A person decides.

    Build in an escalation default. Anything it cannot classify goes to the top of the pile, not the bottom. Uncertain should mean urgent, not ignored.

    Content repurposing

    One piece of work becomes several.

    A completed job with photos becomes a social post, a newsletter item, a website case study and a short video script.

    Rules that keep it usable

    • Feed it your own material. Your notes, your photos, your voice. Not a topic prompt.
    • Give it your voice rules. No exclamation marks, no corporate padding, whatever your standards are.
    • Never let it generate a statistic. This is the single biggest risk with AI-written marketing. It will produce plausible, specific, entirely fabricated numbers and they will look exactly like real ones.
    • Rewrite the first and last line yourself. Openings and closings are where generated text reads most obviously as generated.

    The statistics problem, in detail

    This deserves its own warning.

    AI models generate text that resembles true statements. A fabricated statistic looks identical to a real one: specific figure, plausible source, confident phrasing.

    Practical policy

    • No number goes into published material without a named primary source you have personally opened.
    • If it cannot be verified, describe the direction instead. “Response speed materially affects conversion” rather than an invented percentage.
    • Be suspicious of round, memorable figures, particularly ones attributed to a well-known institution with no link.

    This is not a theoretical risk. A single fabricated statistic in a published article damages your credibility more than the article gained you.

    Where not to use it

    Complaints. A generated apology is detectable and makes an upset customer angrier.

    Pricing decisions. It has no idea what your costs are.

    Anything legal or compliance-related. Certificates, regulations, contract terms.

    Fully autonomous customer contact. Covered next, with caveats.

    Getting started without a project

    Pick one task you do more than five times a week and do it with AI for a fortnight.

    Most likely candidates: proposal drafting, or turning job notes into a follow-up email.

    Measure the time honestly, including the correcting. If editing takes as long as writing did, the task is a bad fit or the prompt needs work. Usually it is the prompt.

    Do not buy a platform first. Start with a general assistant and your existing templates. Buy tooling only when you know exactly which repeated task justifies it.

    Pick your most-repeated writing task this week and run it through an assistant with your own template attached. Measure the time saved after correction. That single test tells you more than any amount of reading.

    Need a pro to set it up? [BOOK A CALL]

  • Creating Behind-the-Scenes Transparency

    Creating Behind-the-Scenes Transparency

    Nobody trusts a service business because it says it is trustworthy. They trust it because they can see what it is doing.

    TL;DR Photograph everything, including the ugly middle. Send a short video update from site instead of a text. Show your material sourcing and your pricing logic. Imperfect and real beats polished and generic.

    Why the ugly bit matters most

    Before-and-after alone is not transparency. It is advertising.

    The middle is where trust is built, because the middle is where the customer imagines something going wrong.

    Photograph and show

    • The corrosion behind the panel.
    • The mess at the point of maximum disruption.
    • The unexpected problem you found.
    • The bit you had to redo.

    Day 2: worse than we thought behind the panel. That is thirty years of scale. Adds about half a day but it needs doing properly, otherwise we are back in eighteen months. No change to the price, it is within what I quoted for.

    Volunteering a problem builds more credibility than any number of clean finished photos. It also removes the possibility of it being discovered later, which is where relationships break.

    The photo vault

    Build it as a matter of routine, not as a project.

    Standard set on every job

    • Before, wide and detail.
    • During, at least one per day.
    • The problem, whatever it was.
    • After, from the same angles as before.

    Practical rules

    • Same angle, before and after. Different angles make comparison impossible and look evasive.
    • Use the flash. Dark photos read as concealment.
    • No filters. The instant something looks processed, people discount it.
    • Get consent before publishing anything identifiable. A blanket line in your terms is not enough for a recognisable property.

    Organise by job reference from day one. A folder of ten thousand unsorted photos is worth nothing.

    Video updates from site

    Thirty to sixty seconds, filmed on a phone, sent directly to the client.

    Sarah, quick update. Old unit is out, you can see the state of the pipework here. New one goes in this afternoon, testing tomorrow morning. Any questions, ring me.

    Why this outperforms a text

    • Voice carries competence in a way text does not.
    • It is unmistakably live. Nobody stages a video of a half-finished job.
    • It answers questions before they are asked.
    • It is fast to make. Faster than writing a careful update.

    Do not edit them. No captions, no music, no intro. The roughness is the credential.

    Ask permission before using any of it publicly. A private update is not consent to post.

    Honest material sourcing

    Increasingly what people ask about, and rarely answered well.

    What to show

    • Where the parts come from, and why you chose that supplier.
    • The difference between the options. The budget part, the mid-range and the premium, and what each actually changes.
    • Your markup logic. Not the number, the logic. “We charge trade plus a margin that covers sourcing, collection and the warranty we carry on it.”
    • Disposal. What happens to what you take away.

    People ask why we do not use the cheapest valves. This is one that failed after fourteen months alongside the one we fit, which carries a ten-year warranty. The difference in the part is about eleven pounds. The difference in a call-out to replace it is four hundred.

    Explaining your price openly is more persuasive than defending it when challenged.

    Live progress and time-lapse

    Higher effort, use selectively.

    Time-lapse on a visually dramatic job. Cheap to produce with a phone on a tripod, and highly shareable.

    Live streaming is rarely worth it. The audience is small, the risk of catching something awkward is real, and the effort is high.

    A daily photo update is 90 percent of the value at 10 percent of the effort.

    Transparency on the difficult things

    Pricing. Publish ranges even if you cannot publish fixed prices. “Most jobs of this type come in between $400 and $900, depending on access and condition.” Vague pricing loses more enquiries than honest ranges.

    Availability. “We are booked three weeks out” is better than a slow reply.

    Mistakes. Post about one occasionally, with what changed as a result. It is the single most credibility-building content a service business can publish and almost nobody does it.

    Limits. Say what you do not do. It makes what you do claim believable.

    What transparency is not

    • It is not oversharing. Financial difficulties, staff problems and client disputes are not content.
    • It is not performance. Staged “candid” photos are recognisable and counterproductive.
    • It is not a substitute for quality. Documenting bad work transparently is still bad work.
    • It is not consent-free. Other people’s property and faces require permission.

    Measure it

    • Client questions during a job. Should fall as updates increase.
    • Reviews mentioning communication or honesty.
    • Engagement on before-during-after posts versus before-and-after only. The three-part version generally performs better.
    • Quote acceptance rate after introducing published price ranges.

    Start photographing the middle of the job, not just the ends, and send one thirty-second video update on your next multi-day job. Those two habits produce more trust than any amount of polished marketing.

    Need a pro to build it? [BOOK A CALL]

  • Managing Client Retention KPIs in GA4 and Your CRM

    Managing Client Retention KPIs in GA4 and Your CRM

    Retention metrics live in your invoicing system, not in your analytics. GA4 tells you about sessions. Your books tell you about customers.

    TL;DR Four numbers: lifetime value, repeat rate, average gap between visits, and retention cost. Calculate them from invoices. Use GA4 only for the acquisition half. Review quarterly, not weekly.

    Where each number lives

    Metric Source
    Customer lifetime value Invoicing or accounting system
    Repeat booking rate Job records
    Average time between visits Job records
    Cost per retention Marketing spend plus job records
    Acquisition cost Ad platforms plus GA4
    Which channel brought them GA4, imperfectly

    GA4 is an acquisition tool. It struggles with the offline, multi-year, phone-heavy reality of service work. Do not try to force retention reporting into it.

    Customer lifetime value

    The simple version, which is good enough

    Average value per job × average jobs per year × average years retained

    Example: $180 average job, 1.4 jobs per year, 4.2 years retained = $1,058 lifetime value.

    Use gross profit, not revenue, if you want the number that informs your ad budget. Revenue LTV overstates what you can afford to spend.

    Segment it, because the average hides everything

    • By service type. Emergency-only customers have very different LTV from maintenance customers.
    • By acquisition channel. Referred customers frequently show markedly higher LTV than paid-search customers. If yours do, that changes where the budget should go.
    • By membership status.
    • By first-job value. Sometimes small first jobs produce the best long-term customers, which is the opposite of what people assume.

    The channel comparison is the single most useful cut, because it can invert a decision made on cost per lead alone.

    Repeat booking rate

    Customers with two or more jobs, divided by total customers, over a fixed window.

    Fix the window or the number is meaningless. Customers acquired in the last month have not had a chance to return.

    Better: cohort it.

    Of customers first served in 2024, what proportion booked again within 12 months?

    Then compare cohorts. 2023 versus 2024 versus 2025 tells you whether retention is improving. A single blended figure tells you nothing.

    Average time between visits

    Underrated and highly actionable.

    Calculate it per customer, then average.

    What it tells you

    • The gap is widening. Early churn signal, before anybody cancels.
    • A customer well past their personal average. A specific, timely reason to contact them.
    • Where the frequency opportunity is. If your average gap is 14 months on a service that should be annual, there is a reminder problem.

    Use it to trigger outreach. Personal average plus 20 percent is a good trigger point, and it beats a blanket six-month rule.

    Cost per retention

    Retention spend divided by retained customers.

    Retention spend includes loyalty rewards, gifts, newsletter tools, portal software, staff time on check-ins, referral payouts.

    Compare it against acquisition cost. Retention should be dramatically cheaper. If they are close, either your retention spend is inefficient or your acquisition is unusually good.

    A caution on the widely quoted claim that retaining is five times cheaper than acquiring. The figure circulates everywhere with no consistent primary source and the real ratio varies enormously by business. Calculate your own two numbers and compare those. Do not repeat the ratio as fact.

    What to actually track

    Keep it to a single sheet.

    Metric Frequency Where
    Customers served Monthly Job records
    New vs returning Monthly Job records
    Revenue per customer Quarterly Invoicing
    Repeat rate by cohort Quarterly Job records
    Average gap between visits Quarterly Job records
    Churn, voluntary and involuntary Monthly Billing
    LTV by channel Annually Combined

    Quarterly for most of it. Retention moves slowly and weekly review produces noise and bad decisions.

    Getting the data out

    You do not need a data warehouse.

    1. Export jobs or invoices to CSV, with customer ID, date and value.
    2. Pivot by customer to get job count, total value, first and last date.
    3. Calculate the gaps and the averages from those columns.
    4. Repeat quarterly and keep the history.

    A spreadsheet with four years of quarterly snapshots is more useful than any dashboard, because trend is the whole point.

    Where GA4 fits

    Use it for

    • Which channels bring enquiries.
    • Which pages precede a booking.
    • Acquisition cost when paired with ad spend.

    Do not use it for

    • Lifetime value. It cannot see your invoices.
    • Repeat purchase, for offline service work.
    • Anything requiring a customer identity across years.

    Bridge the two by recording the acquisition source on the customer record in your CRM at first contact. That single field is what lets you calculate LTV by channel later, and it costs one dropdown at booking.

    What to avoid

    • Vanity metrics. Total customers ever served tells you nothing about the business today.
    • Blended averages that hide segment differences.
    • Weekly retention reporting. The signal is not there at that resolution.
    • Benchmarking against published industry figures. Definitions vary so widely that the comparison is usually meaningless. Compare against your own previous quarters.

    Export twelve months of jobs to a spreadsheet this week and calculate the average gap between visits per customer. That one number will show you exactly where your reminder programme is leaking.

    Need a pro to set up tracking? [BOOK A CALL]

  • Gamifying Referral Programs for Staff and Clients

    Gamifying Referral Programs for Staff and Clients

    Most referral programmes fail for one reason: nobody can see what is happening. Points accumulate invisibly and interest dies.

    TL;DR Visibility is the mechanic, not the prize. Staff leaderboards work well, customer leaderboards do not. Use a monthly draw for reviews. Reward the referrer and the referred. Pay out fast.

    Visibility over value

    A $50 reward nobody remembers earning is worth less than a $10 reward with a visible progress bar.

    What makes a programme visible

    • Immediate acknowledgement. A message within the hour of a referral landing.
    • Progress shown, not just totals. “Two more and you hit the next tier.”
    • Something changes when they act. A count, a bar, a rank.
    • Public recognition where appropriate, with consent.

    Invisible programmes are just discounts with extra paperwork.

    Staff leaderboards work

    Field technicians are in more homes than any marketing channel you own, and a visible board changes behaviour quickly.

    How to run it

    • A physical board in the yard or workshop. Whiteboard, updated weekly. Physical beats an app for this.
    • Count what you want more of. Referrals passed, reviews generated, upsells accepted.
    • Monthly reset, so it stays winnable for everyone.
    • Small prizes, frequently. A voucher, a lunch, first pick of the following month’s rota.
    • Recognise the top three, not just the winner.

    Watch for

    • The same person winning every month, which demotivates everyone else. Add a most-improved category.
    • Gaming. Referrals that are not real, or pressure applied to customers. Only count referrals that convert.
    • Blame for the bottom of the board. Recognise the top, never publicise the bottom.

    Customer leaderboards do not work

    Do not put customers on a public board. It reveals their business, invites comparison and reads as slightly desperate.

    What works for customers instead

    • Private progress. “You have referred two people this year, one more and the next service is on us.”
    • Tiers with names. Silver, gold, or something less corporate.
    • A monthly draw, which creates recurring interest without ranking anybody.

    The monthly draw

    Particularly effective for reviews, where individual rewards can be problematic.

    How it works

    Every customer who leaves a review that month is entered into a draw for one meaningful prize.

    Why the draw structure

    • One decent prize costs less than many small ones and is more motivating.
    • It avoids paying for reviews directly, which most review platforms prohibit and which corrupts the reviews you get.
    • It creates a monthly rhythm.
    • Announcing the winner generates a natural piece of content.

    Be careful with the wording. Entry should be for leaving a review, not for leaving a positive one. Incentivising positive reviews specifically breaches platform terms and is transparently dishonest.

    Check local promotional rules. Prize draws are regulated in some jurisdictions, particularly around purchase requirements.

    Tiered staff bonuses

    For referrals passed by technicians, escalating tiers beat flat rates.

    Referrals converted in a month Bonus per referral
    1 to 2 Base rate
    3 to 5 Base plus 50%
    6+ Double base

    Why tiers. A flat rate rewards the accidental referral. Tiers reward the habit, and the habit is what you are trying to build.

    Pay monthly with the wage run, not quarterly. Delay kills the connection between action and reward.

    Reward both sides

    The referrer and the referred.

    Sarah, thanks for sending the Hardwicks our way, $40 credit is on your account. And they get their first call-out free as a new customer.

    Why both

    • It gives the referrer something to say. “Mention me and you get your call-out free” is easier to pass on than “please use my plumber”.
    • It removes the sense that they are doing you a favour for money.
    • It converts better on the receiving end.

    Pay out immediately

    The single biggest killer of referral programmes is slow payout.

    • Acknowledge within the hour.
    • Pay on conversion, not on invoice settlement, if you can absorb the risk.
    • Tell them it has been paid, do not just credit it silently.
    • No expiry, no minimum threshold, no conditions in small print.

    A referral reward paid three months later teaches people not to bother.

    Visual dashboards

    If you use software, keep the display simple.

    Show

    • Referrals this month, this year.
    • Progress to the next tier.
    • Rewards earned and rewards paid.

    Do not show conversion rates, funnel stages, or anything that reveals your commercial data. It is a progress bar, not a report.

    Measure it

    • Referral volume, monthly, split staff and customer.
    • Conversion rate of referrals versus other lead sources. Referrals should convert far better. If they do not, the quality is wrong.
    • Cost per acquired customer through referral versus paid channels.
    • Participation rate. What proportion of staff and customers ever refer once. Low participation with high volume means a handful of people carrying it.

    What to avoid

    • Complicated rules. If it takes a paragraph to explain, it will not spread.
    • Rewarding leads rather than conversions. You will get names, not customers.
    • Pressure on staff. Referrals should be a bonus, never a target that affects appraisal.
    • Forgetting to thank people who refer but decline the reward. Many will. Thank them anyway, in writing.

    Put a whiteboard up this week with one column for referrals passed and one for reviews generated. Update it every Friday. The board itself does most of the work.

    Need a pro to build it? [BOOK A CALL]

  • Reclaiming Lost Contracts During Economic Downturns

    Reclaiming Lost Contracts During Economic Downturns

    In a downturn the choice is rarely you versus a competitor. It is you versus nothing.

    TL;DR Offer a reduced scope before they ask. Pause rather than cancel. Restructure payments rather than discount. Lead with the cost of not doing the work, in their numbers not yours.

    Reach out first

    The businesses that survive downturns well are the ones that raised it before the customer did.

    Things are tight for a lot of people at the moment. Before anyone has an awkward conversation, I would rather ask: is the current arrangement still working for you? There are smaller versions of it if that would help, and I would much rather keep working with you at a reduced level than not at all.

    Why go first

    • It removes the embarrassment, which is what usually causes silent cancellation.
    • You control the options rather than reacting to a decision already made.
    • It is remembered. Businesses remember who was reasonable when it was hard.

    Scope down, do not discount

    Discounting the same service is the worst response available. It cuts your margin, it sets a new anchor price you will never recover, and it teaches the customer that your original price was inflated.

    Reduce the scope instead.

    Instead of Offer
    20% off the monthly fee Fewer visits at the same rate per visit
    Cheaper rate per job A narrower list of included work
    Discounted contract Essentials-only tier, clearly defined
    Free extras to retain Remove the extras and reduce the price accordingly

    The principle: less service for less money, not the same service for less money. Your unit price survives, and it goes back up when they scale back up.

    Pause rather than cancel

    A pause retains far more customers than any discount.

    Rather than cancelling, want me to pause it for three months? Nothing charged, you keep your slot and your terms, and I will check in at the end of it. If things are still tight then, we pause again.

    Why it works

    • It removes the immediate cost pressure completely.
    • It requires no decision about the future.
    • It keeps the relationship, the data and the habit intact.
    • Restarting is one message. Re-signing is a purchase decision.

    Set a specific end date and honour it. An indefinite pause is a cancellation with extra steps.

    Payment restructuring

    Sometimes the problem is timing, not amount.

    Options

    • Move from annual to monthly. Same total, easier cash flow for them, better for you than losing it.
    • Shift the billing date to align with their own receivables.
    • Split a large job across two or three payments.
    • Defer, with a written schedule, for a customer with a track record.
    • Extend terms from 14 to 30 days for a commercial account.

    Put anything deferred in writing, with dates and amounts. Verbal arrangements in a downturn become disputes later.

    Know your own limits. You cannot fund a client’s cash flow problem out of your own. Be generous within what you can actually absorb, and be straight when you cannot.

    Demonstrate the cost of stopping

    Not scare tactics. Arithmetic.

    Understood, and no pressure either way. Worth knowing the numbers: the annual service is $180. The last three emergency call-outs we attended on unserviced systems came to between $600 and $900 each, and two of them were in the middle of winter when nobody is available. That is the trade-off, and it is your call.

    Rules for this

    • Use your own real figures, from your own jobs. Never a statistic you cannot source.
    • Give the range honestly, including the low end.
    • State it once, then leave it.
    • Accept the answer. Repeating it becomes pressure and pressure loses the relationship.

    Prioritise where the effort goes

    You cannot save everyone. Be deliberate.

    Account Effort
    High value, long tenure Maximum flexibility. Call personally
    High value, new Real effort. Not yet proven, but worth it
    Low value, high maintenance Let them go gracefully
    Consistently late payers Restructure only with firm terms, or let go

    A downturn is a legitimate moment to shed accounts that were never profitable. Do it politely and completely, not by degrading the service.

    What not to do

    • Do not go silent. Uncertainty makes customers cancel pre-emptively.
    • Do not cut quality to protect margin. They will notice and it justifies the cancellation.
    • Do not discount publicly. A visible price cut damages your position with every customer who is still paying full rate.
    • Do not chase debt aggressively from a long-standing customer in temporary trouble. You will win the invoice and lose the account.
    • Do not pretend nothing is happening. It reads as out of touch.

    Coming out of it

    Track everyone who paused or scoped down, with the date.

    Reach out at the end of the pause, not months later.

    Three months is up. No pressure at all, but do you want to pick things back up, extend the pause, or leave it for now? Any of those is fine.

    Restore the original price when scope is restored. Because you scoped down rather than discounted, this is a straightforward conversation rather than a negotiation.

    Draft your scope-down tier and your pause offer this week, before you need them. The businesses that handle a downturn well are the ones that had the options ready before the first customer asked.

    Need a pro to structure it? [BOOK A CALL]