A landing page, a short qualification flow and a reminder ladder that fill a consultant's calendar with the right conversations.
Bring your stack to a call and we will scope it against how your business actually runs.
Book a callAn independent consultant or a small professional services firm sells through conversations. Nothing else converts. Yet the path to that conversation is usually the least designed part of the business: a contact form on a website that emails an inbox, a reply written by hand two days later, three messages trying to find a mutual slot, and a call that eventually happens with someone who turns out to be researching a dissertation. Every step of that path is a place where a qualified buyer quietly leaves.
Two failures compound. The first is latency. A prospect who fills in a form is at peak intent in that moment, and every hour that passes without a confirmed time in their calendar is intent decaying. By the time a reply lands the next morning they have moved on, or they have booked with whoever answered first. The second is the absence of qualification. Because there is no structured intake, the consultant cannot tell a serious buyer from a browser until they are twenty minutes into a call, which means the calendar fills with conversations that were never going to convert while the ones that would have are waiting for a reply.
The cost is specific and measurable. Unbooked inquiries - people who expressed interest and never got a time - are the largest single loss, and most firms cannot even count them because the inquiry lives in an inbox rather than a record. No-shows are the second, running high precisely because nothing was invested by the prospect and nothing was reinforced between booking and call. Then there is the opportunity cost of calendar time spent on poor-fit conversations, which is invisible but real: a consultant who takes eight calls a week to close one is not short of leads, they are short of a filter. And finally, because no stage is recorded, the firm cannot tell which channel produces buyers rather than inquiries, so marketing spend is allocated on anecdote.
A four-step funnel on its own path, separate from the main site so it can be changed without touching anything else and measured without contamination from general traffic.
One pipeline, Discovery, deliberately short. Anything longer belongs in a proposal pipeline downstream.
BO sits on the landing page as a chat widget and in the SMS thread afterwards, for the prospects who would rather type a question than fill in a form.
Trigger: Discovery Qualification form completed.
Branches: on Fit Score, computed from the weighted answers. Three outcomes. High fit - timeline Immediately or Within a month and decision role I decide or I recommend: apply high-fit and show the Extended Discovery calendar. Standard fit - anything in between: show the 30-minute Discovery Call calendar. Out of scope - timeline Exploring only, or the answers match a disqualifier such as a student, a job seeker or an agency pitching services: route to workflow 7 and never show a calendar.
Actions:
Exit: a booking is made, a reply is received, or the contact opts out.
Trigger: screen one of the qualification form submitted and Qualification Complete still off after 30 minutes.
Branches: on how far they got. Abandoning after the open challenge question is a strong signal and gets a personal, specific message. Abandoning at screen one gets a lighter generic one. If the email domain is a known free provider and no company was given, treat as low-intent and send one message only.
Actions:
Exit: Qualification Complete flips on, a reply is received, a booking is made, or the three touches are exhausted - after which the card stays at New Inquiry and is reported as an unconverted inquiry.
Trigger: appointment booked on the Discovery Call or Extended Discovery calendar.
Branches: on time to appointment. If the call is inside 24 hours, the brief request is skipped and only the confirmation is sent - there is no time for homework and asking for it adds friction. If the contact carries high-fit, the confirmation comes from the consultant's own address and names them directly.
Actions:
Exit: the appointment is canceled or rescheduled, which restarts this workflow from the top on the new time.
Trigger: appointment exists on either discovery calendar.
Branches: channel preference and quiet hours. Any reminder that would land outside 8am to 8pm in the contact's own time zone moves to the nearest edge of that window rather than firing. If the contact opted out of SMS, every step runs by email.
Actions:
Exit: appointment status changes to showed, no-show, canceled or rescheduled.
Trigger: appointment marked no-show, or 15 minutes past start with no attendance recorded.
Branches: on whether this is a first or second no-show. A first gets the full rebooking sequence. A second closes the card as Not a Fit with Disqualify Reason set to repeat no-show, and no further invitations are ever sent. On a high-fit contact, the consultant is tasked with a personal call before any automated message goes out.
Actions:
Exit: rebooked, closed as repeat no-show, or parked in nurture.
Trigger: appointment marked showed, which moves the card to Call Held and applies discovery-held.
Branches: on Call Outcome, which the consultant sets from a single task immediately after the call. Proposal requested hands to the proposal process. Follow-up needed runs a short re-engagement. Not a fit closes with a reason. If Call Outcome is not set within 24 hours, the consultant is chased, because an unrecorded outcome breaks every number in the reporting.
Actions:
Exit: an outcome is recorded and the card leaves Call Held.
Trigger: card moves to Nurture - Long Timeline, from any route.
Branches: on Timeline to Act. This quarter gets a 30-day cycle; Next quarter gets 60 days; Exploring only gets 90. Contacts carrying discovery-disqualified are excluded entirely - a disqualification is permanent and nurture is not a loophole for it.
Actions:
Exit: a booking is made, the contact opts out, or the taper completes.
Trigger: Monday at 08:00.
Branches: none. One digest, one recipient, every week, whether the numbers are good or not.
Actions:
Exit: none - this one runs indefinitely.
The gap between intent and a confirmed time collapses from days to seconds. A prospect goes from reading a page to holding a calendar invitation without a human being involved and without leaving the flow, which removes the single largest source of loss in a consultant's funnel. The consultant's reply speed stops being a function of how busy their week is.
The calendar changes composition. Because the page states who the call is not for and the form scores timeline and decision role before a slot is offered, the conversations that get booked are disproportionately with people who can act. The number of calls may fall. The number of proposals will not, and the hours returned to delivery work are real.
Inquiries become countable, which is the quiet structural win. Every started form is a record, so the firm can finally see how many people expressed interest and never booked - a figure that was previously unknowable because it lived in an inbox. That number, and the recovery rate against it, is often the first thing worth optimizing.
Preparation stops being improvisation. The consultant walks into every call already knowing the problem in the prospect's own words, their timeline and who signs. The call starts at minute one instead of minute eight, which makes a thirty-minute conversation genuinely sufficient.
And the firm learns which channels produce buyers rather than clicks. Because Lead Source Detail is captured at the click and carried to the outcome, the weekly digest answers the question marketing spend depends on, side by side with what the prospect said when asked directly.
None of this is legal advice. Messaging consent rules, data protection obligations, recording consent and the professional conduct rules governing what an automated assistant may say on a firm's behalf vary by jurisdiction and by profession. Have the client's own counsel or professional body guidance confirm the consent wording, the privacy notice, BO's scope limits and the retention periods before launch. To scope the build, book a call at bookings.appbo.io.
Every build on this page is something we configure, test and hand over with the SOPs your team needs to run it.
Book a call