"Winning Proposals with AI" is out today on Amazon. 24 years of government services and federal proposals, crossed with six years of figuring out where AI actually helps and where it quietly sinks your bid. Not theory. The frameworks, the prompts, the judgment calls I use on real pursuits. If you've followed my posts on the 80/20 split, on what AI should never touch, on the courage to not bid, this is the full system those ideas came from. Written for one person: the practitioner who has to win the work, not just talk about winning it. Here it is, on Amazon: https://www.amazon.com/dp/B0H3ZTD7NG

Hello everyone! 👋 Just wanted to introduce myself. I'm Mary and I'm excited to join the community. Looking forward to learning, sharing ideas, and connecting with like-minded people. Hope everyone is having a great day!

I teach GovCon teams a one‑sentence technique that consistently moves evaluator ratings from Acceptable → Outstanding. Not by rewriting the whole volume. Not by adding more detail. And definitely not by “making it clearer.” Here’s the problem Most teams write federal proposals to describe their approach. That feels logical. It’s also the wrong target. Evaluators aren’t readers. They’re decision documenters. Their job is to justify scores — in writing. If they can’t quote your proposal verbatim to justify a Strength, they won’t infer it. They’ll score conservatively. And they’ll move on. The fix is simpler than most people expect: Stop writing to explain what you do. Start writing to give evaluators the exact sentence they can paste into their scoring notes. One sentence they can point to and say: “This is why we rated them Outstanding.” That single shift does more for proposal scores than rewriting an entire technical approach. I break this down step‑by‑step — with real proposal examples and repeatable workflows — inside my FREE Skool Proposal Development Course. No theory. No generic “best practices.” Just evaluator‑ready language you can apply on your next pursuit. 👇 If you’re tired of Acceptable, this is where to start. Classroom · AI Proposal Wins for GovCon

Two things this week, one useful right now, one you'll want to be early on. First, the useful part. If you haven't pulled the free starter guide from the classroom yet, this is the week. Inside it you've got working prompts you can run on a live solicitation today, the Section L extraction prompt, the L-M-PWS traceability prompt, the narrative accelerator (Claim, Proof, Benefit). Here's the one to try before your next proposal: run the Section L extraction prompt on whatever solicitation is sitting on your desk right now. Then count the requirements you didn't know were there before you ran it. That gap is the whole point. Come back and tell me your number in the comments. The classroom is here: Classroom · AI Proposal Wins for GovCon Now the bigger thing. Tuesday, June 9, my book launches: Winning Proposals with AI, Volume I of the AI for GovCon Series. It's the full version of everything this community is built around, the frameworks, the prompts, the judgment calls, in one place. You're the first to know, and I'm going to ask you something directly. A launch lives or dies on its first week, and the thing that helps most isn't a big audience, it's a handful of real practitioners who show up early. So two asks, only if the book lands for you: Grab it launch day if it's useful to you. I'll drop the link here Tuesday morning. If it helps your work, leave an honest review. Early reviews are what put a book in front of the next person who needs it. Yours would carry real weight, because you're exactly who it's written for. That's it. No hard sell. You're already in the room this book came out of. See you Saturday in The War Room, 9am CST. And I'll be back here Tuesday when it goes live. Best, Lee

You don't need a full pursuit to make progress today. You need one lesson and one document. 👉 Head into the Classroom and complete just ONE lesson on AI-assisted drafting. Then put it to work right away: - Pull up a real Section L excerpt or PWS paragraph you're sitting on - Run the workflow from the lesson on it - Drop what came back in this thread, the good, the rough, all of it That's the whole drill. Lesson, draft, share. The members who post a result get faster feedback, and the rest of us learn from what worked and what didn't. First drafts get better when we build them out loud. What lesson are you starting with? Comment below and go. ✅