Build-Specific Walkthrough

The build-specific walkthrough is the custom portion of the onboarding call where you train the client on everything that was built specifically for them. No two walkthroughs are the same. If you built a booking funnel, you walk through the booking funnel. If you configured automated follow-up workflows, you explain those workflows. If you built a membership site, you show how it works. This segment adapts entirely to what was defined in the Build-Specific Scope and delivered during the build phase.

Why This Matters

The standard training segments — conversations, mobile app, reviews, pipelines — cover the platform features that most clients use. But the build-specific walkthrough covers the custom value you created for this particular client. This is where they see the return on their investment. This is where the system stops being a generic CRM and starts being their business operating system.

When you skip this segment or rush through it, the client does not understand what was built for them. They have a system full of custom workflows, funnels, and automations that they do not know how to use, monitor, or troubleshoot. They will either ignore the custom work entirely (wasting the build effort) or accidentally break something by changing settings they do not understand.

The build-specific walkthrough is also your moment to demonstrate craftsmanship. The client sees the standard features during the rest of the training and might think “I could have set this up myself.” The custom walkthrough is where they see work that clearly required expertise, planning, and execution. It reinforces the value of your agency and their decision to hire you.

How to Think About It

Prepare for this segment before the call. Review the build-specific scope document and create a checklist of every custom element you need to walk through. Trying to remember what you built on the fly during the call leads to missed items and a disorganized presentation.

Organize the walkthrough around outcomes, not components. Instead of “Here is Workflow #1, here is Workflow #2,” frame it as “When a new lead fills out your contact form, here is what happens automatically. Let me show you the entire sequence.” Walk the client through the customer journey as it flows through the system. They care about what happens to their leads, not about the technical architecture of your workflow nodes.

For each custom element, cover three things. First, what it does and when it triggers. Second, what the client needs to do (if anything) to keep it running. Third, what the client should not touch because changing it could break the automation. This three-part framework gives the client confidence to operate the system while respecting the boundaries of the custom configuration.

Common Mistakes

Winging it without preparation. Every custom build is different, which means this segment requires more preparation than the standard training segments. Review the scope, test every custom element the morning of the call, and have your walkthrough order planned. Improvising leads to skipped elements and confused clients.

Getting too technical about the build. The client does not need to know how many workflow nodes you used or how you configured the conditional logic. They need to know: “When X happens, Y follows automatically. Here is where you can see it working.” Keep explanations at the business-outcome level unless the client asks for technical detail.

Not showing the client what not to change. Custom builds include settings, workflow configurations, and automation rules that the client could accidentally modify. Point these out clearly: “This section powers your automated follow-up sequence. If anything here looks different from what I am showing you now, reach out to us before making changes.” This prevents accidental breakage and reduces support tickets.

Rushing because you spent too long on standard training. Budget your time before the call. If you have a 60-minute onboarding call, the standard training should take 30 to 35 minutes, leaving 20 to 25 minutes for the build-specific walkthrough. If you hit the 40-minute mark and have not started this segment, you spent too long on conversations or pipelines.

Covering features the client did not pay for. If the client’s package includes a booking funnel and automated follow-ups but not a membership site or course platform, do not show them the membership features “just in case.” This creates confusion about what is included and what is not. Worse, it can feel like an upsell attempt, which violates the No Upsell principle.

Tools Involved

The tools involved depend entirely on what was built. Common elements include GHL workflows for automation, funnels and websites built in the page builder, calendar configurations for booking, and custom pipeline stages in Opportunities. If the build includes integrations with external tools, walk through those connection points as well. Reference the Build-Specific Scope document to ensure nothing is missed.

Where This Fits

Sequence position 24, during the Live Onboarding Call. This segment comes after all the standard training segments — Conversations Deep Dive, Mobile App Training, Teach Review Requests, Pipeline Training, and Quick Actions Bar. By this point, the client understands the platform fundamentals and is ready to see how their custom build sits on top of those fundamentals. The walkthrough should be one of the last segments before you wrap the call.

Common Questions

What if the build includes elements the client did not request? If you added bonus elements during the build (extra workflows, additional automations), mention them briefly and frame them as included value. Do not dwell on them or position them as something extra the client should be grateful for. Just show what it does and move on.

How detailed should the walkthrough be for complex builds? For builds with many custom elements, prioritize the ones the client will interact with daily. Walk those through in detail. For elements that run in the background (automated workflows, trigger-based sequences), a high-level overview is sufficient. The client needs to know they exist and what they do, not how every node is configured.

What if something in the build is not working correctly during the walkthrough? It happens. If you find a bug during the live walkthrough, acknowledge it calmly, note it, and move on. Do not try to debug on the call. Fix it after the session and follow up with the client to confirm it is resolved. Spending 15 minutes troubleshooting during a training call is a poor use of everyone’s time.