Overall grade — B-
A functionally solid first in-person meeting that achieved a warm soft yes — but left a tighter close on the table, undersold pricing, and missed the clearest buying signal (Facebook Ads) while introducing cognitive load it didn't need to (Voice AI). The relationship assets were fully deployed; the sales discipline was inconsistently applied. Real upside in the next meeting if you tighten the reflect-before-redirect habit and walk in with a pre-built SOW.
This is a coaching tool. Honest, specific, no grade-inflation. Topher asked for it directly. Page is CF-Access-gated; only Topher + Jaime can see it.
Top 3 wins — keep doing these
Your best questions (vetting process, primary goal, pricing-disclosure posture) were genuinely open and let Amanda drive the frame. That instinct is right.
Multiple times the conversation drifted into warm social territory (cleaning stories, college kids, charcoal soap). You let it breathe — correct for the relationship — then calmly steered back. That's a hard skill and you have it.
When Amanda confirmed her current intake process was working, your response at 13:40 was "then if it's not broke, don't fix it." Not selling for the sake of selling. Amanda noticed — it reinforces trust and makes the things you DO recommend land with more credibility.
Top 3 growth edges — practice these
Every time someone gives you a substantive answer, your next move should be a paraphrase or acknowledgment before you ask the next question. "So what I'm hearing is [X] — is that a fair read?" Practice it in low-stakes conversations until it's a reflex. Single highest-leverage behavioral change from this meeting.
The moment a client signals anxiety about migration or change ("want to puke"), respond with an unambiguous reassurance sentence before you say anything else. Write it before you walk in. Letting it breathe for two minutes while you list CRM alternatives turns a manageable concern into a real objection.
Walk in with a number written down. When price comes up, say it plainly and pair it with the "showcase client" trade framing — confident, not apologetic. Practice the transition out loud so "we're early in our business" never comes out of your mouth again in a pricing conversation.
Dimension-by-dimension grades (13 axes)
Topher accounted for roughly 30–35% of total speaking time. In a cold-market discovery that would be borderline acceptable; in a warm-relationship meeting where trust was already established, it was too high. The first 20 minutes were close to 80/20. From the website walkthrough onward (~22:00 →), Topher + Jaime combined dominated the floor. The custom-framework pitch (21:37–22:25), the SEO content explanation (34:00–35:00), and the Voice AI monologue (55:25–57:00 and 58:20–59:30) were uninterrupted minutes of you talking at them. When the ratio flipped, Amanda's energy visibly flagged.
Next time: Set a personal rule: no speech longer than 90 seconds without a check-in question. "Does that resonate with how you're thinking about it?" forces re-engagement and buys you signal.
Your best questions were genuinely good. "Help me understand that a little more" (10:45 on vetting) was excellent — it invited elaboration. "What would you say is the primary goal?" (20:00) pulled Amanda's singular answer: double the leads. "When you quote people, does it feel expensive or about right?" (27:30) was a sharp pricing probe. The drags: at 14:00 you asked about SEO, she said she's not interested, and you moved on without asking *why* she's satisfied. At 37:20 when Amanda said "I think a minus" on upfront pricing, you said "Okay" and moved on — that deserved "Tell me more about what happened last time someone got sticker shock."
Next time: Write your three must-answer questions before walking in. Each one open-ended with a "what did that feel like" / "what happened as a result" component.
This is the biggest coaching gap in the meeting. You almost never reflected back. There was no "what I'm hearing is..." moment, no paraphrase-check, no summary before pivoting. When Amanda volunteered her clearest emotional signal — "we've been at 20 leads a week since 2020" (15:20) with the implied frustration of six years stuck — the response was a flat "Oh. Okay." and a pivot. Six years is a wound. It deserved "Six years — that has to be frustrating when you know the pipeline is right there." Amanda's "old school" disclosure (63:46) got nodded past. Hannah's "want to puke" (39:05) got a single "Yeah" — that was the hardest no in the meeting and deserved a deliberate close: "Got it — that's off the table."
Next time: After every answer longer than two sentences, summarize what you heard before asking the next question. Practice the formula: "So what I'm hearing is [restate] — is that right?" Even once or twice per meeting, it dramatically increases trust.
You correctly picked up the most important signal early: she's volume-constrained, not capability-constrained. "Only goal is 40 leads" (20:09) and "I don't want to take on something just to keep myself busy" (20:44) were correctly understood and you didn't try to oversell ops automation. Where you missed: Amanda's energy visibly flagged during the demo. The mascot/Converse tangent (23:00–24:00) lit her back up, but the group spent five minutes on bracelets instead of using the re-engagement moment to ask a business question. When she circled back to Facebook Ads (51:35) — "I need help with Facebook ads because I'm trying to do them on my own" — that direct buying signal got a quick "Yep, we can help" and a move-on. She volunteered the one thing she wanted right now; it got one sentence.
Next time: When the client hands you a concrete ask, stop and go deeper: "Tell me more about what you've been trying on the Facebook side — what's working, what isn't?"
Hannah is an underutilized asset. She's technically literate (Salesforce background), the day-to-day ops authority, and the one who will either champion or quietly tank implementation. You asked her directly once ("What about you, Hannah?" at 17:10) and she surfaced the UMA-to-Jobber copy-paste pain. You mapped the stack but never returned to probe time cost or whether she'd manage form integrations. The "want to puke" line (39:06) was met with "Yeah" and then you described Salesforce, HubSpot, and GHL as alternatives — that prolonged the anxiety rather than killing it. The correct response was immediate and unambiguous: "We are not touching Pulse or Jobber. The website wires into Pulse via API, zero migration."
Next time: Always identify the operational gatekeeper before you walk in. Build two or three Hannah-specific questions — her pain points, her workflow, her approval threshold.
The foundational "Pulse stays, Jobber stays" message DID eventually land, but it took too long. Sequence: Hannah says "want to puke" (39:06) → Topher says "Yeah" (39:10) → Topher describes Salesforce, HubSpot, GHL as alternatives (39:16–40:18, the opposite of reassurance) → Amanda asks "what would that look like" (still uncertain) → only at 40:36 does Topher say "if you're happy with it, no need to change." The correct path was to shut that loop the moment Hannah said "puke" — full stop, affirmative, then move on. Two minutes of unnecessary agitation. Recovery at 41:00 was good and Amanda visibly relaxed, but the damage window was real.
Next time: Prepare this sentence in advance and say it the moment system anxiety surfaces: "To be clear — we are not moving you off anything. Your whole stack stays. We're adding a bridge, not replacing a foundation."
This is the weakest moment in the meeting. When Amanda asked "What does a new website cost?" (52:00), you said: "We're still in the early phase of our business with that too… we're really interested in having your business regardless… we wanted to just have an open conversation and see what you'd be willing to pay or if there's a value in trade of services…" Apologetic, not confident. "Early phase," "really interested in having your business regardless," and "what you'd be willing to pay" all signal low leverage. You handed Amanda price authority before she asked for it. When she disclosed $3,000 for her last site, there was no upward anchor — no "this is meaningfully more comprehensive than a $3K template build" frame. The trade-of-services angle is smart positioning, but it was buried under apology and framed as desperation rather than mutual opportunity.
Next time: Have your anchor number AND your trade offer pre-built, in writing, before the meeting. When price comes up, say it plainly: "Our standard for a build like this starts at $X. For a relationship like ours, there's a trade structure we'd like to float too." Confident, clear, no apology.
Solid coverage on lead sources, the CRM tech stack, intake/vetting flow. You surfaced the 20/80 one-time/recurring ratio (Amanda volunteered it) and connected it correctly. Elder care under-indexing was a nice catch from the demo. You learned: 40 jobs/day, manual scheduling is human-critical, six days/week staffed, UMA after-hours gap. Gaps: you never asked about client retention rates or churn signals. Never asked what "20 new clients to start a tech" means for capacity planning. Never pressed on the one-time/recurring conversion math — if she's getting 20 leads at 50% close, what's break-even for a new tech? That math is load-bearing and you could have used it to make the case for her rather than letting her make it herself.
Next time: Prepare a discovery checklist: (1) unit economics of a new client, (2) average client lifetime, (3) biggest operational friction that costs time weekly. Slot those in when the floor is yours.
Facebook Ads was Amanda's single named pain. It got one sentence of validation and a redirect to the demo. You came back to it briefly at 51:35 but never asked the probing questions: What have you tried? What's the current spend? What does a good week look like? That's the data you'd need to write a credible Facebook Ads proposal — and you don't have it. Hannah's UMA-to-Jobber copy-paste frustration was let go too fast. She said "I would love it if everything in UMA automatically went into Jobber without us copying and pasting" (17:23). Your follow-up was clarifying (good) but not probing (missed). How many times a day? Who does it? How long does it take? That manual task becomes a strong line item in the proposal. You left it on the floor.
Next time: When a pain gets volunteered, go three levels deep before moving on: What, How often, What it costs.
Almost no "here's where this goes in 12 months" framing. The meeting stayed feature-and-service level — SEO, blog content, form integrations, Voice AI. Amanda gave you the 12-month narrative for free: "20 to 40 leads, 2 new techs per month." You never reflected that back as a strategic arc — "So what we're actually building is the top-of-funnel infrastructure that gets you from plateau to growth mode — and the website is phase one of that." That frame would have made everything else feel purposeful rather than a feature list. Voice AI especially needed a strategic container — "After the website drives traffic and converts leads, Voice AI captures the ones who call after hours." Instead it was introduced as an add-on.
Next time: Start every client meeting with a one-minute "here's the arc" framing from the client's own language. Restate it at the midpoint and close.
The close was "we'll follow up and schedule a time to go over the changes and talk about timing and next steps" (65:00). That's the minimum viable close, not the available close. The room was warm: Amanda had said "adorable," Hannah had called the meeting "very thorough," Amanda had started problem-solving collaboratively on Pulse wiring. Engagement signals supported a tighter ask. A stronger close, available to you: "Given where we've landed today, I'd like to put together a one-page SOW that covers the website, the Pulse integration, and a trade structure proposal. Can we get back together by the end of next week to put a signature on something?" Not pushy — the relationship can hold it.
Next time: When you hear "adorable," "very thorough," and collaborative problem-solving in the same 15 minutes, ask for the paper.
Handled well structurally. Discovery front half from you, clean handoff to Jaime for the demo. You did not interrupt during her walkthrough; your interjections ("this is the elder care" at 24:50, "the detail pages reinforce SEO" at 34:55) were additive and brief. You reclaimed the floor naturally when technical questions arose. One minor issue: a few times during the demo you jumped in to re-explain things Jaime had just covered, which slightly undercut her authority. Not a serious problem, but noticeable.
Next time: Before the demo, agree on handoff cues: "Jaime, I'll take the technical questions, you own design and content." Cleaner lanes, no doubling.
Voice AI ran about four minutes of uninterrupted Topher talking (55:25–59:30), almost all feature description with minimal discovery. Amanda said "maybe" (57:30); Hannah offered one concrete use case (cancellation deterrent). The room was past its productive attention span — this came after 55 minutes. Amanda's brain was full. More importantly: this introduced a second unfamiliar technology decision on top of website + Facebook Ads. Cognitive load is real. Amanda is self-described "old school" and openly processing whether AI dehumanizes her client relationships (63:00). Introducing Voice AI in visit 1 fed that anxiety. The correct play: leave a one-line mention ("we also work with Voice AI for after-hours gaps — worth a 15-minute conversation at the right time") and let curiosity do the work. Save the full pitch for visit 2 after the website SOW is signed.
Next time: Keep the first meeting to one primary product category. Everything else is a breadcrumb — "we can look at that too, once the core is humming."
Pre-flight for the follow-up meeting
The follow-up meeting is in 7–10 days. Before you walk in:
- Write your price anchor down. Build is \$X. Hosting is \$Y/mo. FB Ads is \$Z/mo. Trade structure: \$N in cleaning credits offsets \$N of the build. Practice saying the numbers out loud — no apology, no qualifier.
- Pre-write your "Pulse stays" sentence. Memorize it. Use it within the first 5 minutes of the meeting, before anyone asks.
- Pre-write your three reflect-back prompts. "So what I'm hearing is…" / "It sounds like the thing that would feel like a win is…" / "Let me make sure I'm getting this right…" — have them ready.
- Three "go deeper" follow-ups for Amanda's Facebook Ads pain. What have you tried? What's your current spend? What does a great month look like? Don't leave that pain on the floor twice.
- Three "go deeper" follow-ups for Hannah's UMA pain. How often per day? How long does it take? What would automation be worth weekly? Make Hannah feel seen — she's the operational gatekeeper.
- One strategic arc sentence to open with: "Last time we landed on the 20→40 leads problem. Today I want to show you the system that gets you there — and ask you to sign onto phase one."
- Lead with the SOW. Walk in with a printed one-pager. The room is warm enough to hold a direct ask.
- Voice AI: one breadcrumb, no pitch. Save the full conversation for after the website SOW is signed.
Reference
- Raw transcript: /info/meetings/2026-06-04-website-redesign-and-lead
- Discovery debrief (strategy + next steps): /info/modern-maid-discovery
- Follow-up research (Pulse / FB Ads / Voice AI / refs): /info/modern-maid-research