QuoteAI — The Andy Meeting#

Status: 🔄 Preparing (meeting not yet scheduled) Authors: Dan Hannah & Clay Created: 2026-04-23 (rewritten 2026-04-23 after deck-format reframe) Parent: Business Model | Project Design

Purpose#

Tactical prep for the Andy meeting — a specific one-time event. Pre-meeting homework, deck spec, in-meeting flow, objection handling, post-meeting archive.

Goal of the Andy meeting (PITCH-D1): secure Andy as a champion who will bring QuoteAI to Brehob leadership for internal buy-in. NOT to close the deal. Meeting succeeds when Andy commits to scheduling a leadership presentation within 2 weeks.

After the meeting, rename this doc (e.g. andy-meeting-2026-05-15.md) and archive. Lessons feed back into business-model.md + successor meeting docs.

Pre-Meeting Homework#

Must-haves (blocking the meeting)#

Priority comes from what Andy will actually care about. Everything else moves to post-Andy.

1. KPIs Andy cares about — confirm with John. What business metrics does Andy watch? Quote throughput per salesperson? Close rate? Turnaround time? Pipeline value? This drives slide 10 in the deck.
2. Per-quote commission estimate — from John. Needed for the ROI uplift math (e.g., 80 → 150 quotes/yr × $X/quote commission = concrete per-salesperson annual value).
3. Record 4 GIFs of the app in action (upload, generate, review, pricing-live) — ~5 sec each
4. Build the deck in PowerPoint, using Claude Design for polish
5. Confirm F1 employer sign-off on what's shareable about Dan's F1 work

Deferred to post-Andy#

Leadership / procurement / legal handle these once the pilot moves forward — no need to pre-empt:

• Vendor onboarding process (NDA, W-9, insurance requirements)
• Contract template (legal)
• Cultural read on AI / software tools at Brehob
• Who else at Brehob needs to approve beyond Andy

Dan's Positioning#

The F1 credibility narrative is the biggest lever for reframing Dan from "John's son moonlighting" to "F1 engineer deliberately choosing this problem." Critical for the pitch to land with leadership.

The language — abundance, not trade-off#

Preferred framing:

"I build AI systems for F1. This kind of work used to take teams of engineers months — I'm shipping a full race strategy app in under 30 days, solo, using agentic AI. That's the same engine building your tool. You're not buying me working harder for you; you're buying into the same 100x leverage that lets one engineer deliver what used to require a whole team."

Tighter version if time is short:

"The same engine letting me ship a production F1 race strategy app in under a month — solo — is what's building your tool."

This is the starting point. Tighten further once it lives in the slides.

Why this framing matters#

The original "I could be working on X but choosing this" is defensive — subtly puts Andy in the position of "why is Dan slumming it?" The abundance reframe does the opposite:

• Dan is demonstrating the thesis on himself (agentic AI → 10x output)
• Brehob is buying into the same engine, not a sacrifice
• The F1 race strategy app is concrete proof of the value prop

Pre-meeting prep#

• Confirm with F1 employer what's appropriate to share publicly
• Line up 1-2 specific F1 wins (appropriate-to-share TBD with employer)
• Rehearse the language above until it sounds natural, not memorized

The Deck#

The single shareable pitch artifact. Replaces the earlier multi-asset plan (separate highlight video + walkthrough + 1-pager + FAQ) with one consolidated deck that works both in-meeting and as a forward-able asset for leadership. See decisions.md § PITCH-D3 for rationale.

Tool + build approach#

• Build + present directly in Claude Design. CD builds the deck from this doc's content spec and Dan presents live from CD in the meeting — removes PowerPoint from the critical path. "CD prompt starter: Use andy-meeting.md as the content spec; build a professional deck suitable for champion-enablement pitch to Brehob leadership."
• Export to PowerPoint after the meeting. Once the deck has stabilized, export to .pptx for Andy to forward to leadership. Brehob's whole company uses PowerPoint, so the post-export artifact has zero handling friction for anyone at Brehob. Dan needs PowerPoint installed for the export step only (buy Office 365, or borrow from a family member).
• Why this order: lets Dan start building and presenting now without the PowerPoint-install dependency; the export step is only needed to hand leadership a forward-able artifact AFTER Andy commits to taking it up the chain.

Slide structure (13 slides)#

GIF specs#

Each GIF is a short (~5-second) silent loop showing one action clearly. Low file size, auto-plays in PowerPoint, readable at deck-viewing scale.

Recording approach:

• Screen capture at 1280×720 or 1920×1080
• Tools: Kap or LICEcap on Mac; ScreenFlow if you want more control; QuickTime + convert works too
• Export as .gif (or .mp4 if PowerPoint prefers — test both)
• Keep each clip focused on ONE moment of "wow" — no extra UI clutter, no dead time

Content guidance for Claude Design#

When prompting CD to build the deck, pass along:

• Aesthetic: dark mode matches Dan's preference + the QuoteAI app's visual identity
• Brand colors: ask John for Brehob's brand palette if available; otherwise neutral professional
• GIF slides: big GIF + 1-2 lines of caption. No dense text competing with the animation.
• Thesis + KPI slides: text-heavy but clean. Andy should be able to read on his phone while forwarding.
• FAQ slide: can be denser — 4-6 questions, short answers, legible at deck-viewing scale

In-Meeting Flow#

Conversational, not rigid. No stopwatch. The deck provides structure; Dan navigates through it in response to the room.

Opening (~2 min)#

John opens:

"This is Dan, who builds AI systems for F1 teams. He saw this problem and built this specifically because I know the pain better than anyone else."

Reframes "introducing a vendor" as "my collaborator solving our actual problem."

Dan's opener (ties into slides 2-3):

"Before the demo — I want to be clear about what's different here. Ten years ago, getting software tailored to your workflow meant spending half a million on Salesforce consultants or a couple million building internal. Neither fit Brehob. Agentic AI changes the economics by about 100x. I'm going to show you what that unlocks for your team specifically."

Walking the deck#

Key moments to emphasize as you navigate:

• Slide 2 (pain): Let Andy nod in recognition. If he adds color to the pain, engage with it — he's validating the problem for you.
• Slide 3 (thesis): The reframe moment. Watch whether Andy latches onto the economics argument.
• Slide 4 (live demo): Run the live demo here. Upload a real Brehob spreadsheet → draft generates → slide margin → commission live. "This is the feedback loop that makes salespeople want to use this."
• Slides 5-8 (GIFs): Redundant with live demo in-meeting, but these exist for leadership forwarding. "These GIFs capture each of those moments — they're for when you want to share this with your team."
• Slide 9 (positioning): Use the Dan's Positioning language. The ethos / credibility slide.
• Slide 10 (KPIs): Frame as proposals — "What matters most to Brehob? Let's refine these together."
• Slide 11 (Quote Log): Concrete near-term feature preview. "If leadership wants to move forward, this is probably the first new thing you'd see in month 1."
• Slide 12 (ask): Direct. "Can you bring this to your leadership team?" Hand him the Drive link.
• Slide 13 (FAQ): Don't read it — just point at it. "For when your team asks, here's the starter FAQ. I'll extend it based on what they care about."

Leadership-forwarded version#

Slide 4 (live demo placeholder) gets skipped when leadership opens the deck solo. Everything else stands alone — the GIFs carry the demo story without Dan present.

Objection Bank#

Pre-rehearsed responses to likely leadership questions. Andy may field these solo, or bring Dan back in:

1. "$5K/mo is a lot for unproven tech"

   "3-month trial with explicit success criteria — the KPIs we discussed. If it misses targets, we renegotiate or terminate. Risk is bounded at $15K total, with signed commitments each month. And you keep the code regardless."

2. "What if Dan leaves?"

   "Buy-out price is pre-agreed. Documentation and handoff are part of every month's deliverables. Brehob owns the code via non-exclusive license. Worst case: hire anyone to maintain it."

3. "How do I measure value?"

   "Monthly scorecard with the KPIs we proposed. I give you the data; you judge."

4. "Why not hire a full-time AI engineer?"

   "You could — it'd cost $200K+/year. I'm $60K/year for access to someone 90% of the way there, with 22 years of your data modeled. When scope grows to need a full-timer, I'll help you scope that role — I want you to eventually outgrow this."

5. "What about security?"

   "App is local-only for the pilot — no hosted deployment until we've defined encryption, backups, and incident response specs with your IT team. Security is a first-class scope item for the move to production."

6. "Is this just buying your time, or are we buying software?" (from Dan's review, 2026-04-23)

   "You're buying software that solves this specific problem for Brehob, with dedicated engineering support from me to keep it working and extending it as your needs evolve. Structurally it's a Master Services Agreement — but in practice you get a working tool plus an engineer who cares about making it better for you."

7. "Why not Salesforce / Hubspot?"

   "Salesforce is a generalized tool designed to be customized. Brehob's 22 years of quote history doesn't live there, and making it fit costs $500K+ in consultants. What I'm building fits your existing workflow because I've spent time learning it with John — not because I built a customization layer. Agentic AI changes the math on who can afford bespoke software."

What "Meeting Succeeded" Looks Like#

• Andy commits to scheduling a leadership presentation within 2 weeks
• Andy has the deck (Drive / email link)
• Dan and Andy agree on whether Dan is included in the leadership meeting
• John confirms availability for follow-up questions

Fallback: if Andy says "interesting, let me think" without a commit — follow up in 1 week with a soft check-in. Don't push for a close in this meeting.

Post-Meeting Archive#

Once the meeting happens:

• Rename this doc → andy-meeting-YYYY-MM-DD.md
• Back-port lessons into business-model.md (stakeholder framework, common objections, cultural reads)
• Create leadership-meeting.md for the next tactical prep cycle (if Andy brings it to leadership)

This doc is tactical and time-limited. Strategic / persistent content lives in business-model.md.