Command Center
Aria chat_bubble Talk to Aria
Briefing

B Clean — Bryan Meeting (PREP)

Tue Jun 9, 2026 · 2:00 PM ET · talking-points sheet prepared before the meeting (private, not for share). The post-meeting recap is a separate page.

Updated Saturday, July 18, 2026

Primary goal

Migration plan

Squarespace → our Astro 6 build

Frame

Consulting, not pitching

Portfolio client · paid in knowledge

Hard ask

Where is the domain?

Registrar = the unlock for cutover

Fallback

MVP-first migration

Ship parity, add the rest later

🧭 The frame for this call

Bryan is family — Jaime's cousin — and a portfolio showcase client, not a retainer. We're getting paid in knowledge: we learn the carpet-cleaning playbook (operations, pricing psychology, third-gen craft), and Aspire builds him a site + CRM + voice agent that actually helps his business. That asymmetry is the deal. Do not pitch. Consult.

Treat this as a working session, not a sales call. Bryan's existing Squarespace site is fine — working software. The burden of proof is on us to show why moving is worth his time. Lead with curiosity ("how do leads find you today?", "what breaks on the current site?") before showing him our build.

Naming note: Bryan knows you as Topher. The "Chris" naming is for arm's-length Aspire client materials only — Bryan is family, so stay Topher.

📋 Where we are with B Clean today

What's built

  • Full Astro 6 site on b-clean-carpet.launch.madebyaspire.com — live, behind launch UAT.
  • Brand locked 2026-04-16: Clean Modern Trust + B Clean teal + Outfit/Recoleta.
  • Page rhythm: alternating light/dark. Charcoal hero → cream services → dark testimonials → cream FAQ → dark CTA.
  • Site reflects his real story: 3-gen craft, IICRC + TMF certs, published pricing, owner-operator promise.

What's open

  • Privacy + Terms pages — required for A2P SMS registration (Vegas to build).
  • GHL calendar embed on /book — pending Bryan's embed code.
  • Contact form wiring — currently the Squarespace form; needs to point at GHL.
  • Instagram section + team profiles: placeholders, accepted for v1.

Quick links

🌐 launch.madebyaspire.com 🌐 bcleancarpet.com (current Squarespace) 🎨 design library 📞 Bryan: (740) 913-4494 📧 bwilson@bcleancarpet.com 📍 Westerville, OH · 20-mi radius

🔑 Goal 1 — Where is the domain registered?

Hard ask

This is the single biggest unblock. Until we know who holds bcleancarpet.com, we can't plan a real cutover. Squarespace probably owns the registrar (their "domain included" plan) — but we need to confirm.

Ask Bryan, in this order:

  1. "When you log into anything to manage bcleancarpet.com — is it Squarespace, GoDaddy, Network Solutions, somewhere else?"
  2. "Do you remember buying the domain separately, or did it come bundled when you set up Squarespace?"
  3. "Do you know what email address the domain account is registered to?" (often a forgotten gmail)
  4. "Who else has access — anyone help you set this up originally?"

Branches: (a) Squarespace-owned → we'll need him to either transfer the domain out (~$10–$20, 5–7 days, doable before cutover) or point Squarespace's DNS at Cloudflare (faster, leaves registrar where it is). (b) Third-party registrar → easy, we ask for nameserver-change access or a TXT record. (c) Unknown → we run a public WHOIS lookup live in the meeting, then walk back to recovery.

Live tool you can run in the meeting: whois bcleancarpet.com in terminal, or lookup.icann.org on phone. Registrar name comes back in seconds.

💻 Goal 2 — Walk the launch site, surface concerns

Share screen. Open b-clean-carpet.launch.madebyaspire.com on your end, and don't editorialize. Ask Bryan to scroll through and react. Note where his eye stops, what he questions, what he wants changed.

What to highlight (his wins)

  • Hero leads with the third-generation story, not stock cleaning copy.
  • Published pricing front-and-center (most competitors hide it).
  • "Bryan answers the phone, Bryan does the work" — his actual differentiator.
  • Service areas as real neighborhoods (Muirfield, New Albany Country Club, etc.) — SEO + trust.
  • IICRC + TMF certs as credentials, with the explanation of what they mean.
  • Phone in the top-right of every page, always tappable.

Likely objections + our answers

  • "I just updated my Squarespace site" — fair. We don't force a move. Migration only when he sees enough lift to be worth the swap. The launch site is built either way.
  • "My customers already know my URL" — we keep the same URL. bcleancarpet.com stays. We swap the engine, not the address.
  • "What if I don't like it / want to change something later?" — Astro = we can change anything, anytime. Squarespace = we can change anything Squarespace allows.
  • "How much does this cost ongoing?" — Hosting via Cloudflare = $0. Domain = same as today. He pays for the registrar + (later) the voice/CRM stack if he wants it.
  • "What about my reviews / SEO / Google ranking?" — keep the same domain + page slugs that matter (/services, /book, /pricing). 301 anything we restructure. We hand him a pre-cutover Lighthouse score so improvements are measurable.

⚠️ Watch for these — do not pretend they're solved

  • Privacy + Terms pages: not built yet. Honest answer = "Vegas is on it, ~2 days."
  • Online booking form: still pointing at the old Squarespace form. We need his GHL embed code, or we wire ours.
  • Instagram feed: placeholder. We're not going to pay Behold $30/mo for him until we evaluate the homegrown route (see Modern Maid open question).
  • Team profiles: placeholder — fine, since Bryan IS the team.

📞 Goal 3 — The AI Voice Assistant (Aspire Concierge)

Why this matters for Bryan specifically: he's on jobs all day. He misses calls. Missed Call Text-Back is the #1 workflow Circa flagged for B Clean. The voice agent is an upgrade on the same problem — instead of texting back, it answers.

The two-minute pitch (do not exceed)

"We've built an AI receptionist that knows your business cold — pricing, services, areas, your story. It answers every call, even at 9 PM. It quotes the job using your real published rates. It books straight into the calendar. If the caller asks something it can't handle, or sounds like a complicated job, it texts you and offers to warm-transfer. You decide whether to take the call live, or let it leave a detailed message."

What it knows (already in the KB)

  • Full pricing matrix ($59/$109/$139 + add-ons + $119 minimum)
  • Three carpet packages (Regular / Plus One / Full Reset)
  • Service areas with ZIPs + response windows + neighborhoods
  • Bryan's three generations + IICRC + TMF story
  • Products (Bio Conqueror 105, Carpet Armor, etc.)
  • Guarantees (30-day, 60-day, wicking return)
  • 30+ FAQ answers from his actual playbook
  • Brand voice: direct, warm, unsalesy — never pushes add-ons

The warm-transfer flow

  1. Caller dials Bryan's number.
  2. AI answers in B Clean's name. ("Thanks for calling B Clean, this is the team...")
  3. If standard question → AI handles it, books if asked.
  4. If complicated → "Let me see if Bryan's free right now." Calls Bryan, plays the caller's question.
  5. Bryan presses 1 to take the call, or 2 to have AI take a detailed message + text him.
  6. Every call → transcript + summary + lead capture in CRM.

Honest about timing:

We have it built and trained — knowledge base is loaded, voice is configured. What's still pending: LC Phone number provisioning + A2P 10DLC registration (for the SMS side). Realistic go-live = 1–2 weeks after he gives the green light, mostly because A2P approval takes 5–10 business days.

Decision Bryan needs to make: use the AI as primary (answers all calls), after-hours-only (his cell rings first, AI catches misses), or just-text-back (no voice, only Missed Call Text-Back). Recommend after-hours-only as the v1 — lowest risk, biggest immediate lift, lets him hear the AI in his own voice before trusting it on primary.

🗂️ Goal 4 — CRM (how leads populate, how he uses it)

Circa has B Clean's GHL sub-account already configured. The pipeline mirrors his actual workflow:

Booking → Service → Re-book pipeline

  1. New Lead (form / phone / Missed Call Text-Back)
  2. Quoted
  3. Booked
  4. Confirmed (24h out)
  5. Service In Progress
  6. Service Complete
  7. Closed Won (invoice paid)
  8. Closed Lost
  9. Re-book Pending (5–6 months from last service)

The 6 workflows we'd turn on: Missed Call Text-Back (priority #1 — auto-SMS in 30 sec); New Lead auto-reply + Bryan SMS; 24h reminder + day-of "on my way"; Service Complete → invoice + review request (Google + Facebook); 5-month re-book reminder; annual customer anniversary.

Bryan's view = simple. Sidebar locked to: Dashboard, Contacts, Conversations, Calendars, Opportunities, Forms, Reputation, Reporting. Funnels/Sites/Memberships/Communities/everything-else turned OFF so he sees only the parts that matter for a single-tech service business.

Confirm with Bryan:

  • What does he use today for booking/scheduling? (Squarespace form? Pen and paper? Texts and a calendar app?)
  • What does he use today for invoicing/payments? (Stripe? Venmo/Zelle direct? Square reader?)
  • How does he track who needs a 6-month re-book today? (Memory? Notes? Nothing?)
  • Does he want LC Phone as a new public number, or keep his current cell and use SMS-first?

💸 Goal 5 — What platforms is he paying for? Where can we save him money?

This is the consulting angle — and the learning angle. Most service-business owners are bleeding $200–$500/mo on overlapping SaaS they signed up for at different points. Get the list.

The audit questions

  1. Website: Squarespace ($16–$23/mo) — what plan?
  2. Email marketing / review requests: any service? (Birdeye, Podium, NiceJob, Mailchimp?)
  3. Booking / scheduling: Calendly? Squarespace Scheduling? Nothing?
  4. Invoicing / payments: Square? Stripe? QuickBooks? Direct only?
  5. Phone / VoIP: just his cell? Or a business line through Grasshopper / OpenPhone / Google Voice?
  6. SMS marketing / appointment reminders: anything? (Or just typing them by hand?)
  7. Accounting: QuickBooks? Wave? Excel? Notebook?
  8. Customer database / contacts: anywhere besides his phone?
  9. Social scheduling: Buffer / Hootsuite / Later? Or post-as-you-go?
  10. Google Business Profile: who manages it? (We can.)

What we can collapse into GHL (one bill): CRM, calendar/booking, SMS reminders, email follow-ups, review requests, invoicing, payment links, lead-source tracking. Frame it as "instead of $X across 4 vendors, one platform we already operate for you." Resist the urge to sell the bundle — let him see the math himself when you write it on screen.

Watch-out: Modern Maid's Pulse CRM is rumored-but-not-confirmed to be a GHL white-label. If Bryan mentions a vendor we don't recognize, ask login URL + screenshot before promising migration. Same trap potential.

🎓 Goal 6 — What WE'RE here to learn (the knowledge pay)

Bryan is a master craftsman with 20 years of operating experience in a single vertical. He IS the playbook every other service-business client is going to want a piece of. Mine it.

Operations & craft

  • How does he decide between steam vs. low-moisture in real-time?
  • What does a typical week's calendar look like — how many jobs, what mix?
  • How does he handle pricing pushback? (His "no discounts, ever" rule.)
  • What's his #1 reason customers don't re-book? (And what did he try that failed?)

Marketing & demand

  • Where does his best lead source come from today? (Nextdoor? GBP? Word of mouth?)
  • How often does he run out of capacity vs. need more leads?
  • What did he try for marketing that didn't work? (Ads? Mailers? Flyers?)
  • How does he get reviews — does he ask every time, or hope for organic?

Capture this verbatim. We're building a "service-pro playbook" knowledge layer that every other client (Modern Maid, NRX, Heel Quik, Tees Flooring, Patina) will benefit from. Bryan's answers become our IP.

🚚 The migration playbook (full path) + MVP fallback

Path A — Full migration (preferred)

  1. Day 0 — Domain reconnaissance. Confirm registrar (WHOIS). Get Bryan logged in. Document where DNS is currently hosted.
  2. Day 1 — DNS handoff. Either transfer domain to Cloudflare ($8/yr, 5–7 day window), or point existing nameservers at Cloudflare. Domain stays Bryan's; we get DNS write access.
  3. Day 2–3 — Privacy/Terms. Vegas ships the missing legal pages with A2P-compliant SMS language.
  4. Day 3 — Form wiring. Replace the Squarespace contact/quote form with the GHL embed. Test end-to-end.
  5. Day 4 — Pre-cutover Lighthouse + SEO snapshot. Baseline performance, accessibility, GBP / GSC state. So improvements are measurable.
  6. Day 5 — Production cutover. Switch DNS from Squarespace IP to Cloudflare. TTL 60s. Site live on Astro 6 + Cloudflare Pages in <5 min.
  7. Day 6 — Squarespace pause. Don't cancel immediately — keep it dormant for 30 days as rollback insurance.
  8. Day 7+ — 301 redirects audit. Catch any old Squarespace URL patterns that aren't matching the new site, redirect them.

Path B — MVP-first (fallback if Bryan resists)

Use if he's nervous about touching anything Squarespace does today.

  1. Ship a one-page MVP on a subdomain — book.bcleancarpet.com or new.bcleancarpet.com — that hosts the GHL booking form + the "why B Clean" story.
  2. Keep Squarespace as primary — change nothing user-facing on bcleancarpet.com.
  3. Drive a subset of leads through the new flow (e.g. all MCTB recovery links point to book.).
  4. Measure the lift over 30 days — better conversion? Faster booking? Fewer no-shows? Real data.
  5. Then re-pitch the full migration with numbers, not promises.

Which to recommend live: read the room. If Bryan's enthusiastic and asks "what's the timeline?" → Path A. If he flinches when you mention "your Squarespace site goes away" → Path B. Either way is a win. Path A = full lift faster. Path B = lower risk + we build the case before the swap.

📝 After-meeting capture (drop these into Linear)

  • Domain registrar + account email (the unlock).
  • Current platform stack inventory + monthly spend per item.
  • Bryan's preference: full migration vs MVP-first vs "let me think on it."
  • Bryan's preference: AI voice primary / after-hours / SMS-only.
  • Bryan's preference: keep cell number vs new LC Phone number.
  • Any specific site concerns / change requests from the walkthrough.
  • His best-lead-source answer (for the service-pro playbook).
  • His pricing-pushback technique (for the service-pro playbook).
  • Open invitation — anything else he wants help with that we didn't cover.

🎯 The one-sentence frame to keep coming back to

"Bryan, we built this for you because we want to learn — let's walk through what we made, you tell us what's right and what's wrong, and we'll figure out together whether and when it makes sense to switch."

🤖 Aria · Aspire Digital · B Clean Meeting Prep · 2026-06-09