Build Nuances

Build nuances are the specific requirements, preferences, concerns, and edge cases that your team captures during the quick start call. These are the things the onboarding form will not cover because they come out in conversation, not in form fields. The client mentions they had a bad experience with automated texts. They explain that their receptionist only works mornings. They tell you their biggest competitor just opened a location two blocks away. This is the human intelligence layer that separates a good build from a generic one.

Why This Matters

The onboarding form collects structured data. Build nuances capture context. And context is what turns a template-based setup into a system that actually fits the client’s business. Without build nuances, your builder is working from a spreadsheet. With them, your builder is working from a story.

Consider the difference. A form tells you the client offers emergency plumbing service 24/7. Build nuances tell you that the client’s previous marketing company set up after-hours calls to ring a number that nobody answered, which cost them several angry customers and three one-star reviews. Now your builder knows to triple-check the after-hours call routing and test it before launch. That context changes how the build gets executed.

Build nuances also prevent the kind of mistakes that damage the client relationship early. If the client mentioned during quick start that they do not want text message marketing because their last provider spammed their customers, and your builder configures an SMS drip campaign because nobody documented that preference, you have a problem. The client feels unheard, and trust takes a hit right when you need it most.

How to Think About It

Build nuances are not a transcript of the quick start call. They are a curated set of notes that highlight anything the builder needs to know that will not appear on the Onboarding Form. Think of them as the footnotes to the form data. The form says what. The nuances say why, how, and watch out.

The person running the quick start call is responsible for capturing these notes. That means active listening during the call, not just running through the agenda. When the client goes off-script and starts telling you about their frustrations, their past experiences, or their specific way of doing things, that is where build nuances live. Train your team to recognize these moments and document them immediately.

Structure the notes around categories that matter to the builder: communication preferences, past bad experiences, competitive concerns, workflow quirks, personality traits that affect how feedback should be delivered, and any hard limits or requirements the client mentioned. Keep it concise. Your builder needs actionable context, not a novel.

The goal is to ensure that nothing said during the quick start call gets lost between the call and the build. In agencies where the person running the call is not the person doing the build, this handoff is critical. Build nuances are the bridge between those two roles.

Common Mistakes

Not capturing nuances in real time. Relying on memory after the call ends is unreliable. By the time you sit down to write notes, you have forgotten the subtle things. The client’s hesitation about chatbots, the specific way they described their scheduling process, the competitor they mentioned by name. Capture notes during the call or immediately after.

Burying nuances in a long document nobody reads. If your build nuances are a 3-page wall of text, your builder will skim it. Keep it to a focused list of 5 to 15 actionable items. Bold the critical ones. Format it so a builder can read it in 2 minutes and know what matters.

Treating nuances as optional information. When a builder skips the nuances and relies only on the form, they will eventually build something the client explicitly said they did not want. Then you spend time redoing work and repairing trust. Nuances are not bonus information. They are build requirements that happen to be captured in conversation instead of a form.

Not distinguishing between preferences and requirements. “The client prefers blue” is a preference. “The client will not accept any automated texts” is a requirement. Your builder needs to know the difference. Preferences can be adjusted. Requirements are non-negotiable. Label them clearly.

Failing to update nuances as things change. New information surfaces during Clarification Contact and throughout the build. If build nuances are a static document that never gets updated, it becomes outdated and unreliable. Add new context as it emerges and flag anything that contradicts earlier notes.

Tools Involved

Build nuances are typically documented in your project management system or directly in the client’s GHL contact record using custom fields or notes. Some agencies use GHL Conversations to log internal notes alongside client communications. For agencies with structured onboarding workflows, build nuances can be attached to the client’s pipeline card in GHL Pipelines so the builder sees them alongside the deal stage. The key is making nuances visible and accessible, not buried in a separate tool the builder has to go looking for.

Where This Fits

Build nuances sit in the Information Gathering phase at sequence position 14, which means they are captured early, during the quick start call, before most other information gathering happens. They depend on the expectations setting during the quick start call being complete. Build nuances complement the Onboarding Form and Business Details, providing the qualitative context that structured data collection misses. They are referenced throughout the build phase and should be accessible to anyone working on the client’s account.

Common Questions

Who is responsible for capturing build nuances? The person running the quick start call. In most agencies, this is the account manager, onboarding specialist, or the agency owner for smaller operations. If the person running the call is not the person doing the build, the handoff of these notes is one of the most important moments in the onboarding process.

How do I get clients to share nuances without making the call feel like an interrogation? Let the conversation flow naturally. Nuances come out when clients feel comfortable enough to go off-script. Ask open-ended questions like “What frustrated you about your last marketing setup?” or “Is there anything you definitely do not want us to do?” Then listen. The best nuances are volunteered, not extracted.

What if the nuances contradict what the client puts on the form? This happens more often than you would think. When it does, go with the form for factual details and the nuances for preference-based decisions. If the contradiction is significant, flag it for a Clarification Contact to confirm the client’s current position.