The questions that matter.
If you've read all twelve modules, you know how the platform works. You know what a 3-table CRM schema looks like and why. You know how marketplace syndication fans out to six destinations from a single source of truth. You know what a compliance layer looks like in an insurance vertical. You know what OPCache is and why it matters.
That knowledge is not what most clients bring to the first conversation. Most clients bring a problem: leads are disappearing, response times are terrible, inventory is in a spreadsheet and a separate website and neither is current. The platform is the solution. The scoping conversation is how we get from the problem to a build plan.
The scoping conversation has two failure modes. The first is scoping too broadly — promising every possible system before understanding what the client actually needs in the first 30 days. The result is a sprawling spec that takes six months instead of 30 days. The second is scoping too narrowly — building a website when the client needed a sales department. The result is a client who gets what they asked for and not what they needed.
The six questions below are designed to avoid both failure modes. They surface the real requirements without manufacturing scope.
Six questions. In this order. The order matters because each answer shapes the next question.
Specifically: How many items do you have active at any one time? What fields describe each item? Where does that data live today? Who updates it and how often?
This question determines the catalog complexity. What I'm listening for:
If the catalog is complex and the update workflow is broken, the Inventory OS is a high-priority early deliverable. If the catalog is simple and static, it's a later phase.
This surfaces the syndication requirement. Not every vertical has a dominant marketplace. Marine has several; health insurance leads go through aggregators, not traditional marketplace feeds; real estate has MLS/IDX.
What I'm listening for:
If they're manually updating four marketplaces with a two-week lag, the syndication engine is a clear early win. If the vertical has no dominant marketplace, the catalog work feeds directly into lead capture surfaces instead.
Draw it out. From the moment a prospect first contacts them to the moment money changes hands — what are the steps? Who touches the lead? What information is collected at each stage? What triggers a close?
What I'm listening for:
The journey definition shapes the CRM schema complexity, the portal requirements, and the automation opportunities. The same platform builds both — the scoping conversation determines which shape.
I don't ask "do you have compliance requirements" — everyone says no until they learn they had them all along. I ask the vertical-specific questions directly:
The answers shape whether the build starts with a standard consent layer or needs a custom compliance architecture designed before the first lead form goes up.
Not what they wish they had. What they actually have, running today, with real data in it.
What I'm listening for:
The migration scope is often where build timelines expand unexpectedly. Surfacing it early lets us plan for it.
Not in 30 days — in 12 months. Thirty days gets you live. Twelve months tells me what the platform needs to be able to do at scale.
What I'm listening for:
The answers don't always change the first 30 days. But they shape the architectural decisions that are cheap to make now and expensive to retrofit later.
A scoping conversation done well produces three deliverables before a contract is signed: a catalog schema draft (what fields, what CPT), a system priority list (what gets built in what order based on where the biggest pain is), and a compliance scope statement (what regulatory layer this vertical requires).
Those three deliverables are what the contract is based on. What's promised, what's in scope, what's out of scope. The contract isn't written from a template and hoped for the best — it's written from the scoping conversation.
The client who goes through this conversation understands what they're buying before they buy it. That's the correct outcome. Surprises after the contract is signed are expensive for both sides.
The Anchor build's scoping conversation produced: a 38-field catalog schema, a priority list starting with the hosting migration and inventory OS (because the 745-second page loads were the most acute pain), a compliance scope confirming no specialized vertical regulations beyond standard TCPA/CAN-SPAM, and a 12-month vision that included marketplace syndication, customer portal, and AI layer as phased deliverables.
That scoping conversation is why the build happened in phases rather than as a single sprawling project. Phase by phase, the priority list determined what got built when. The catalog and lead engine came first because they were the most broken. The marketplace syndication and AI layer came later because they were valuable but not urgent.
The result is a platform that was generating real leads before the portal was built, and had real data in the CRM before the AI intelligence layer was added to query it. Sequential, high-priority-first delivery is how you avoid building features that sit idle.
You know how the foundation is built. You know how the catalog, lead engine, email, portal, syndication, and AI are wired. You know the conversion tools, mobile layer, and production hardening. You know how all of it adapts to your category.
That's a complete picture of how a digital sales department gets built. If you're ready to build yours, the next step is a 20-minute call. We'll go through the six questions, look at where your leads are currently escaping, and map what the first 30 days look like. No slides. No pitch deck. Just the scoping conversation.
Book the call →Every lesson stays free — no account, no paywall, no email gate, ever. But if you’d rather have this system standing on your business than wire all 48 lessons yourself, leave your email. We’ll send you a direct line to a build — and you’ll be first to hear when we add new tools to the curriculum.
None of this gates a single lesson. The curriculum was free before you got here and it stays that way.
You came here to understand the system, and now you do. If you’d rather have it standing on your business than spend the next three months wiring it yourself, GAP Concierge is the same architecture from these lessons — a white-label AI agent that knows your catalog and captures your leads — set up for you, from $97/mo.
See GAP Concierge →