Pre-Build Work
Pre-build work is everything your team can do between sub-account provisioning and the onboarding form coming back. Template configuration, default workflow installation, branding asset preparation, calendar setup, pipeline creation. None of it requires client-specific content decisions, and all of it saves time during the actual build.
Why This Matters
The gap between quick start and onboarding form return is dead time if you let it be. The client is filling out their form, your team is waiting, and the build clock has not started yet. That gap is usually 2 to 5 days, sometimes longer. Agencies that use this window productively can shave days off their build timeline. Agencies that do not are leaving their team idle and their delivery dates later than they need to be.
Pre-build work also reduces the pressure on the build phase itself. When your builder sits down to customize the client’s system, half the grunt work is already done. Default workflows are installed. The calendar is configured with standard settings. The pipeline structure is in place. Branding colors and logos are uploaded. The builder can focus on the client-specific customizations instead of spending the first two hours on boilerplate setup.
There is a compounding effect here too. If you systematize pre-build work across every client, your team develops a rhythm. New account comes in, pre-build checklist gets executed, builder is ready to go the moment the form returns. That consistency is what separates agencies that deliver in 5 days from agencies that deliver in 15.
How to Think About It
The dividing line is simple: if a task requires knowing the client’s specific preferences, services, or content, it waits for the form. If it can be done with defaults and adjusted later, it belongs in pre-build. Most of your GHL sub-account configuration falls into the second category.
Think of pre-build work as setting up a furnished apartment before the tenant moves in. You install the appliances, paint the walls a neutral color, set up the utilities. The tenant will rearrange the furniture and hang their own art, but they are moving into a functional space, not an empty shell.
Your pre-build checklist should be standardized. Every new client gets the same base configuration, and your team should be able to execute it without thinking. This is not the place for creative decisions or custom architecture. It is assembly line work, and that is a good thing. Standardization means fewer mistakes, faster execution, and easier training when you bring on new team members.
The key principle: do not sit idle while the client fills out their form. Every hour of pre-build work done now is an hour saved during the build phase.
Common Mistakes
Treating pre-build as optional. Some agencies jump straight from quick start to waiting for the form. That wait time is wasted potential. Even if your pre-build checklist only takes 30 minutes per client, that is 30 minutes your builder does not have to spend during the build phase when the clock is ticking.
Making client-specific decisions without client input. Pre-build work uses defaults and templates. Do not pick the client’s brand colors based on their website, write their email copy, or choose their calendar availability. Those decisions belong in the build phase after the Onboarding Form comes back. Pre-build is infrastructure, not customization.
Not having a standardized checklist. If every team member does pre-build differently, you lose the consistency benefit. Document the checklist, assign ownership, and track completion. When pre-build items get missed, the builder discovers it mid-build and has to context-switch to fix it.
Doing too much too early. There is a balance. Installing default workflows is smart pre-build work. Building out a full website with placeholder content is wasted effort if the client’s form reveals a completely different service structure than you assumed. Stick to configuration that will survive the customization phase.
Tools Involved
Pre-build work happens almost entirely inside GoHighLevel. You will be working with Workflows for installing default automations, Calendars for scheduling setup, Pipelines for deal tracking structure, and Sites for any template-level website preparation. Branding assets like logos and color palettes can be uploaded to the sub-account’s media library. For agencies using snapshot-based provisioning, much of this work may already be handled by the snapshot applied during Sub-Account Provisioning.
Where This Fits
Pre-build work sits in the Pre-Build Setup phase at sequence position 15. It depends on Sub-Account Provisioning being complete because you need an active sub-account to configure. Pre-build work runs in parallel with Domain Setup, Reviews AI, and the Unanswered Review Drip. All of these pre-build elements happen simultaneously while the client works on the Onboarding Form. The build phase begins when the form returns and the Build Clock starts.
Common Questions
What if the snapshot already handles most of this? Great, then your pre-build checklist is short. But snapshots rarely cover everything. There are always account-level settings, integrations, and configurations that need manual attention. The checklist should include both “verify snapshot applied correctly” items and “configure what the snapshot does not cover” items.
How do I know what counts as pre-build versus build work? Ask one question: “Do I need information from the onboarding form to do this?” If the answer is no, it is pre-build. If the answer is yes, it waits. Calendar availability settings need client input. Calendar creation does not. Email template customization needs brand voice. Email channel setup does not.
Should I assign pre-build work to the same person who does the build? Not necessarily. Pre-build work is standardized and lower-skill, which makes it ideal for junior team members or a dedicated onboarding coordinator. Your senior builders should spend their time on the custom work that requires judgment and experience, not on checklist execution.