🚗 VerityDealer.com — Auto Dealer AI Lead Management

Only Stacey and Carlos are on the invite (end client not included), so plan for a Stacey/Apex alignment call — role boundaries, her margin model, promises already made to the client — with the tech discovery questions ready in case the dealer joins.

Consensus — three moves for 8am

1. Reframe price around the dealer's lost-deal math before any number is spoken.
2. Lock process — deposit, single point of contact, subaccount/A2P ownership, proof rights.
3. Close on the repeatable model — one narrow pilot shipped fast, documented, then "this is how we run every client you bring me."

Pricing structure — board decision

Board of advisors — blind-spot review

1. Hormozi — reject the "cost-friendly" frame. Don't price inside her frame. Missed calls cost small businesses ~$2,400/mo on average, and one recovered luxury-vehicle deal pays for the whole build. Anchor at the TOP of the range. If she says yes instantly, it was too cheap. Bring the 30-day Missed-Call Recovery guarantee as the closer instead of a discount.
2. Lemonis — money flow and process are undefined. First time Stacey has subcontracted, so no process exists. Lock on the call: (a) deposit before build, not invoice after, so Apex gets paid regardless of her collections; (b) ONE point of contact, because if the dealer can text Carlos directly that's unpriced support; (c) whose GHL agency account hosts the subaccount and whose name is on A2P and the phone number. Whoever holds those holds the client.
3. Musk — the single point of failure is human adoption. The whole system assumes the dealer or office manager marks leads "worked." If they ignore reminders, the build gets blamed. Define what stops the nag loop, who's accountable, and the success metric (response time + leads touched). Start access requests day one. Access lead times are the real constraint, not the build.
4. Baker — negotiate proof rights and the model, not just the project. No white-label build without written rights to the anonymized numbers ("auto dealer, capture 45%→95%"). The real asset is the repeatable Stacey→Apex delivery model and her network. Caution: auto dealer is off-ICP, fine as a referral one-off, don't let it redefine positioning.
5. Assaraf — mindset check. Don't walk in seeking approval from the "premium avatar." That version underprices and accepts fuzzy boundaries. Evidence: 1M+ record Salesforce migrations, Fed-grade reliability. Walk in as the reliability she's renting.

Open questions for the call

1. CarGurus lead delivery: email lead, ADF/XML feed, or CRM integration?
2. Wayne Reeves: can we get read-only export or API access to inventory/vehicle data?
3. 3CX: what plan/tier, is API or webhook access available for call/voicemail events, and what call-routing options exist?
4. Website platform for VerityDealer.com + leasing site. How are forms captured today (webhook, Zapier, native integration)?
5. Is the AI answering service in year-end scope, or a phase 2 add-on?
6. What reminder/escalation cadence does he want, and what counts as "worked" (what stops the reminders)?
7. Do the scattered iCloud customer records need migrating into the new system?
8. Role boundaries: Stacey as client-facing PM. Where exactly does Carlos's deliverable end?
9. Budget, timeline, payment terms, revisions, and post-launch support expectations from the end client?

Client profile

• Independent auto dealer who also runs a luxury vehicle leasing business
• Operating 4–5 years
• Site: VerityDealer.com plus a linked leasing site
• Has an office manager, but no one stays on top of inbound leads consistently
• Stated priority: revenue. He sees fixing lead response as the fastest path to it.

Pain point

Leads slip through the cracks. No disciplined CRM. Leads mostly sit inside CarGurus. Customer records live in scattered files in iCloud.

Success definition (client's own words, by year end)

• The moment a CarGurus lead, website inquiry, or inbound call/voicemail comes in, the contact is captured and stored in one place
• He gets a text telling him a lead came in
• If that lead has not been touched, he and his office manager keep getting reminders until someone works it
• He is open to an AI answering service for calls that would otherwise go unanswered

Current stack

Technical feasibility (researched Jul 22)

• CarGurus delivers leads via ADF/XML, the industry-standard lead format every automotive CRM is built to ingest. Known, well-trodden integration path.
• 3CX supports webhooks on call events (ring, pickup, missed, finish-type Ok/Missed, plus voicemail recording links), so instant-text-on-missed-call is buildable, not theoretical.
• Wayne Reeves DMS supports third-party integration via API or CSV, cloud-based and built for independent dealers. Only need read access for vehicle/inventory context, not the CRM itself.
• VerityDealer.com site fetch returned 403 (blocked). Platform and form-capture method unconfirmed. Ask on the call rather than guessing.
• GoHighLevel is the build platform. It covers every piece of the client's success definition natively: lead capture into one CRM, missed-call text-back, SMS and email alerts, reminder and escalation workflows, pipeline stages that define what "worked" means, and A2P registration on the phone number. Sized to an independent lot, not an enterprise license.

Phased build to propose

1. Phase 1 — CarGurus → CRM → text alert → nag loop, plus easy web forms. Live ~2 weeks.
2. Phase 2 — 3CX + Wayne Reeves.
3. Phase 3 — AI voice, priced separately per minute.

Kick off access requests (credentials, A2P, Wayne Reeves permissions) on day one.

Next actions

• Reply to Stacey confirming receipt and requesting a scoping call — done, scheduled Fri 7/24 8:00–8:45am CT
• Accept the calendar invite (still unaccepted as of Jul 23 evening, flagged "unknown sender," not auto-added to calendar)
• Run subcontracting discovery call covering the open questions above
• Before pricing: ask Stacey's margin/referral model and what she has already promised the client on timeline or price
• On the call: lock deposit-before-build, single point of contact, GHL subaccount + A2P ownership, and written proof rights
• Propose the phased build and kick off access requests day one
• Confirm role boundaries in writing (Stacey owns client relationship, Apex owns build, testing, maintenance)
• Quote the board-locked structure only after scope is visible
• Confirm with Muhammad in writing before build start: extra sub-account at $27/mo available, transferable out later, SMS/wallet rebilling mechanics
• Track delivery in Linear — done, APE-396 created Jul 23, linked from APE-326