Build Clock

The build clock is the formal start of the build timeline. It begins when the Onboarding Form is returned, not when payment is collected, not when the contract is signed, and not when the quick start call ends. This is a critical distinction that protects both the agency and the client by tying the delivery timeline to information readiness rather than transaction timing.

Why This Matters

Without a clear build clock, agencies and clients end up in disputes about timelines. The client pays on a Monday, the form comes back on Thursday, and the build finishes the following Wednesday. The client thinks it took 9 days. The agency thinks it took 5. Both are right from their perspective, and neither is happy.

The build clock eliminates this ambiguity. You promised a 5-day build. The form came back Thursday. The build is due the following Wednesday. Everyone is working from the same starting point, and there is no room for misunderstanding about when the clock started.

This structure also puts healthy pressure on form completion. When the client understands that the build does not start until they return the form, they are motivated to complete it promptly. Compare that to an agency that starts the clock at payment. The client pays, assumes work has begun, and takes two weeks to return the form. Now the agency is absorbing dead time, the client thinks progress should be further along, and the relationship starts with misaligned expectations.

The build clock also protects the agency operationally. Your build team’s capacity is planned around active builds, not pending forms. If a client pays but does not return the form for three weeks, that is a scheduling problem if you started the clock at payment. With the build clock tied to form return, your team’s schedule stays predictable and manageable.

How to Think About It

The build clock is a commitment mechanism for both parties. The agency commits to delivering within a defined timeline once they have what they need. The client commits to providing that information promptly. It creates mutual accountability.

Think of it like a construction project. The contractor does not start counting build days from the deposit. They start when the permits are approved and the site is ready. The onboarding form is your permit. It tells you the site is ready and you have everything you need to break ground.

Communicate the build clock clearly during the quick start call and reinforce it when you send the onboarding form. The message should be straightforward: “Your build timeline starts when we receive your completed form. The sooner we get it back, the sooner your system goes live.” This framing gives the client agency over their own timeline while protecting your team from scope creep and scheduling chaos.

Automate the build clock start whenever possible. When the form is submitted, a GHL Workflow should automatically update the pipeline stage, notify the build team, log the start date, and calculate the projected delivery date. Human error in tracking start dates leads to missed deadlines and broken promises.

Common Mistakes

Starting the clock at payment instead of form return. This is the single most common mistake and the one that causes the most timeline disputes. Payment happens during the sales phase. Information gathering happens during onboarding. The build cannot start without information, so the clock should not start without information.

Not communicating the build clock clearly to the client. If the client does not understand that the timer starts at form return, they will assume it started at payment and wonder why things are “taking so long.” Explain the build clock during quick start, put it in writing, and reference it when you send the form.

Not automating the start trigger. If someone on your team has to manually log the form return date and calculate the delivery date, mistakes will happen. A form submission should automatically trigger the build clock through a workflow. No manual steps, no room for human error.

Allowing partial form submissions to start the clock. If the client submits half the form, the clock should not start. An incomplete form means the builder will be blocked almost immediately, which defeats the purpose of the timeline. Only a complete, actionable form submission should trigger the build clock.

Not having a defined build duration. The build clock is meaningless without a committed delivery timeline. Whether your standard build is 3 days, 5 days, or 10 days, define it clearly and staff appropriately. A build clock that starts but has no end point creates the same ambiguity it was designed to eliminate.

Tools Involved

The build clock is managed through GoHighLevel’s Workflows and Pipelines. When the Onboarding Form is submitted, a workflow triggers that moves the client to the “Build Active” stage in the pipeline, stamps the start date in a custom field, calculates the projected delivery date, and notifies the build team. Some agencies also use GHL Calendars to block build capacity so they do not over-commit their team. For tracking and reporting, the pipeline view in GHL gives you a real-time snapshot of how many builds are active and where each one stands relative to its deadline.

Where This Fits

The build clock sits in the Information Gathering phase at sequence position 18. It depends on the Onboarding Form being returned, which is its trigger. Everything in the build phase comes after the build clock starts. Before the build clock, your team is doing Pre-Build Work, Domain Setup, and other pre-build setup that does not require client-specific information. After the build clock starts, the team moves into active build execution, using the Business Details and Build Nuances to customize the system.

Common Questions

What if the client returns the form on a Friday afternoon? Define your build clock in business days, not calendar days. If the form comes back at 4 PM on Friday, the build clock starts Monday morning. Document this policy and communicate it upfront so there are no surprises. Some agencies use a cutoff time, like forms received after 2 PM start the next business day.

What if the client submits the form but it is clearly incomplete? Do not start the clock. Respond immediately, noting what is missing and asking for completion. This is different from a form that is complete but has one question you need to clarify via Clarification Contact. Incomplete means the builder cannot start. Needs-clarification means the builder can start and follow up on the specifics.

Should the client see a countdown or progress tracker? Some agencies send automated updates at key milestones: “Build started, Day 1 of 5” and “Build complete, review ready.” This is a nice touch that keeps the client informed without requiring manual outreach. Whether you show a live countdown depends on your workflow setup and how much visibility you want to provide. At minimum, confirm the start date and projected delivery date when the form is received.