Hook–Value–Ask thirty-second pitch

So, picture this with me. You're at an event, coffee in one hand, and somebody turns to you and asks the question. What do you do? Now be honest — what comes out of your mouth? Because if your answer is, I'm a project manager at a tech company, I have some news for you. That answer is technically true, and it's a conversation killer. The other person is already scanning the room for the appetizer table. Here's the thing about those thirty seconds. Your pitch isn't a monologue, and it isn't your resume read out loud. It's a conversation opener, and it has exactly one job — to make the other person lean in. That's it. Lean in, ask a follow-up, want more. And today you're going to build one that does that every time, without sounding like you rehearsed it in the mirror. Now, here's something from the hiring side of the desk. Nobody remembers titles. I've watched thousands of introductions, and the people who stick are never the ones who recite their label — they're the ones who name a problem you recognize. And here's a newer wrinkle worth knowing: the clear, specific language you build today doesn't just work in person. It's the same language that belongs in your profile and your summary, and the matching systems reward that clarity too, because one sentence of real meaning beats a page of buzzwords — with machines and with people. So here's your blueprint, three beats, thirty seconds. Hook, value, ask. The hook gets five to seven seconds, and its job is curiosity. You lead with the problem you solve, never the role you hold. So instead of, I'm a marketing manager, you try — you know how most companies waste half their marketing budget and can't tell you which half? That's the problem I solve. Feel the difference? One is a box. The other is a door. The value gets fifteen to twenty seconds, and it's your through line from lesson one plus exactly one proof point. Not ten claims — one story with a number in it. I help growing software companies build marketing engines that pay for themselves, and at my last company I found two million dollars in wasted spend in one quarter. And you scale that proof to the listener, because a peer wants the shop-talk version, an executive wants the business impact, and your neighbor just wants plain English. Same message. Different wrapper. The ask gets the last five to seven seconds, and hear me on this — never ask, are you hiring? That question puts people on the defensive and turns you into a favor-seeker. You end with a real question instead: I'm exploring where I can do this at scale — what's the biggest challenge your team's facing right now? Now they're talking, and a talking person is a door opening. Then you practice, and here's how. Practice ideas, not sentences — memorize the sequence, vary the words, so that you never sound like a robot reading a script. Practice out loud, in the car, in the shower, to your dog, because rhythm only shows up when you speak. And record yourself once on your phone, then play it back for the filler words and the rushing. Twenty repetitions is the floor where it starts feeling natural. Fifty is where it becomes yours. Now let me tell you about a woman I coached, because this is thirty seconds doing its job. She met a chief technology officer at a casual coffee meetup — no interview, no application, just a room and a coffee. And instead of saying, I'm looking for a job, she used her pitch: I help fintech startups scale their engineering teams without losing their culture — do you know anyone wrestling with that right now? He paused. Then he said, yes, me. And that same afternoon, he brought her in as a consultant. No posting. No resume. One good question. Now, the honest part, in two pieces. First, this will feel fake at the beginning — that's the paradox, you practice meticulously so it lands like you never practiced at all, and the awkward reps are the price of the natural ones. Second, that proof point has to be true and yours, because proof gets checked now. Employers verify claims, and plenty will happily test you live — some technical teams will even sit you down and watch how you actually work. So pick the number you can back up in the room, and listen — a modest claim you can prove beats a shiny one you can't, every single time. So here's your assignment, and it's a three-day build. Today, draft your hook, your value, and your ask on one index card. Tomorrow, say it out loud twenty times and make two versions — one for a recruiter, one for an executive. Day three, record it, play it back once, and fix what makes you cringe. Go say it out loud.