Episode 3 of our website series is the “not glamorous, insanely essential” one. Hosts Liz and Chelsea walk through the two meetings that make or break a web project before a single pixel gets designed: the Kickoff + Sitemap meeting and the Discovery session.  First, the Kickoff & Sitemap: how we set expectations, timelines, roles, and guardrails... then map the site in a humble Google Sheet with pages, subpages, notes, and any special functionality. We share how we prep before the meeting (competitive analysis, industry language, common CTAs, user goals), the questions we bring (legal footers, integrations, hiring goals, etc.), and the rule that saves everyone’s sanity: don’t design until the structure and purpose are clear. Then, Discovery: when a client’s needs are complex or unclear, we scope paid discovery to co-build high-fidelity wireframes and a true content plan. We cover the difference between basic vs. complex projects, where discovery sits in the contract, and how we keep scope honest (pages promised, templates vs. content volume, and what happens when someone requests “just add a blog” midstream). Along the way, we hit: Why showing up prepared establishes you as the leader (and dramatically improves client experience) How to align business goals with user goals (customer = hero, not you) The psychology behind navigation, CTAs, and clarity (and why “industry boilerplate” often fails) Practical artifacts: sitemap doc, questions list, competitor notes, discovery wireframes Scope control without drama: what’s in, what’s out, and how to price change requests Key takeaway: Preparation is part of the product. If you nail the kickoff, define the sitemap, and run discovery with intention, then your design phase will (usually) fly. Skip it, and you’ll pay for it in confusion, rework, and scope creep. If you like a little structure with your chaos, this one’s for you.