I told my team our AI pipeline processed images in batches of 50. The real number was 5. They built a sprint plan around my wrong answer, and nobody questioned it, because I said it with confidence.

This talk is about technical leaders who optimize for sounding certain instead of being accurate. I'll share the moments where my unverified claims shaped real product decisions. I'll show the codebase audit I ran that same day to fact-check myself, and the pre-meeting system I now use before every architecture discussion.

You leave with:
- A way to calibrate technical confidence at an early-stage startup
- A pre-meeting checklist you can use Monday morning
- Permission to say "let me verify that," and proof that it builds more trust than having every answer

For first-time CTOs, tech leads, and anyone who has ever guessed a number in a meeting.

Adaptable to 5, 15, 20, 30, or 45-minute slots. Drawn from my time as CTO of an AI-powered creative workspace. Target audience: engineering leaders, startup founders, and tech leads.