The five flows most businesses are missing

  • First reply: a text within a minute of any new lead, from any source.
  • Reminders: the day before and the hour before every booking, with a reschedule link.
  • Second nudge: a follow-up three days after a quote that got no answer.
  • Review request: the evening a job is done, once, with one link.
  • Monday summary: the week's numbers, sent to you, without a login.

How a flow is built

  1. A triggerSomething that happens in a tool you use: a form, a booking, an invoice paid, a stage change in the CRM.
  2. A checkOnly during business hours, only if no one replied yet, only for this service.
  3. An actionSend a text or an email, create a task, update the record, post to Slack.
  4. A recordEvery run is logged, so you can see what was sent to whom and when.

What it connects

Flows are built on the tools you already use, such as HubSpot, Calendly, Stripe, Shopify, Twilio, Slack or Google Sheets, with Make or Zapier as the glue where that is enough and custom code where it is not. Who owns each account, and what happens to the flows if the work ends, is set out in the agreement.

What it looks like on the leak map

Automation touches every gate, but mostly the second and third: leads that get a timely reply, and bookings that turn into customers because the reminder went out. In the illustrative model those two gates together take a business from 4 customers a month to 11 on the same traffic.