User
Write something
Pinned
Why I built this community, and what you can expect here
Look. I’m not a developer, and I’ve never written a line of code in my entire life. I didn’t go to college. I started my first company at 48 with zero experience owning a business, and I’ve started three since then. I’m telling you that up front because I know exactly what it feels like to open up an AI tool and have no idea what you’re looking at. There seem to be all these different versions out there, and everybody’s throwing around words like agents and models and prompts like you’re supposed to already know what those mean. I didn’t know either. It took me a while to kind of figure it out. And you know how I figured it out? Research. YouTube. Books. Asking a LOT of questions when I didn’t have the answers. YouTube is hands down the best place to learn, and it’s free. So I built this community to be the place I wish I’d had when I started. Here’s what you can expect: Plain English. If I use a term, I’ll tell you what it means. Real tools you can actually open up and use, not theory about what AI might do someday. Practical stuff you can put to work this week. Not a semester. This week. Questions welcome, all of them. If you’re wondering what a prompt is, ask. Nobody here is going to make you feel behind for starting at the beginning. AI is not going to do the work for you. Nothing built amazing has ever been done without hard work, and that hasn’t changed. But you do not need a degree, a dev background, or permission from anybody to start. You just need to jump in. Start here: drop a comment and introduce yourself. Tell us what you do, and one thing you’d love AI to take off your plate. That’s it. That’s your first step.
0
0
The proposal loss that changed how I think about this work
I do not talk about this one much but I think it belongs here. A few years ago we were chasing a $3.2 million county transportation contract. Strong fit. Agency we knew. Team we were proud of. Proposal we had put real effort into. We lost. Evaluation feedback: past performance did not meet requirements. Here is what happened. The RFP required three references for projects completed as prime consultant within the past 7 years. We submitted three excellent projects. But one was from 8 years ago. We miscounted by one year. One sentence in an 87-page document. One wrong year. Disqualified before a single evaluator read our technical approach. That loss built the compliance process we use today. Compliance matrix built first, before any writing starts. Every requirement documented. Second-person review before submission. Dates on every past performance reference verified against the exact requirement language. We have not had a compliance disqualification since. I built part of RFP PursuitAI Hub specifically to automate this step because I never wanted anyone else to lose work they earned on a technicality. I am sharing this because I think the best communities are built on real stories, not polished ones. And because every single one of you has a version of this story. What is the proposal loss that taught you the most? Drop it in the comments. No shame here. Just learning.
0
0
The 30-day proposal challenge: one small change, one real result
Here is something I want to try in this community. For the next 30 days, I want every member to make one specific change to their proposal process, track the result, and report back here. It does not have to be dramatic. In fact, smaller changes often produce bigger results because they actually get implemented. Some ideas to get you started: - Build your compliance matrix before you write instead of after - Use AI to generate your first draft of the firm overview section and track how long it saves - Run your next RFP through a Go/No-Go scorecard before committing - Rewrite one project narrative using the Problem/Approach/Outcome/Parallel structure and compare evaluator feedback - Set a submission time of 2 hours before deadline instead of 2 minutes and see what changes Pick one. Do it for 30 days. Come back and tell us what happened. I will go first. This month I am testing AI-generated compliance matrices on every single RFP that comes through our platform and tracking how many requirements human review catches that the AI missed. I will post the results here at the 30 days from now. Who is in? Reply with the one change you are committing to this month. I will check in with everyone at the end of the 30 days.
0
0
The Go/No-Go scorecard we use, free for every member
One of the most common things I hear from AEC firms: "Our Go/No-Go meeting is basically our principal saying yeah go for it." That is not a decision. That is a gut check that commits your team to 25 or more hours of labor. Here is the 5-question scoring framework we have refined over hundreds of pursuits. Score each question 1 to 5. The total tells you exactly what to do. QUESTION 1: Past performance match Do we have 3 or more directly comparable projects, same type, similar scale, similar client? 5 = strong matches / 3 = close but not perfect / 1 = stretch QUESTION 2: Client relationship Do we have an existing relationship with this agency or a real contact there? 5 = known contact, prior work / 3 = indirect connection / 1 = cold QUESTION 3: Team capacity Is our best team available during both the submission window and delivery? 5 = fully available / 3 = partial / 1 = key conflicts QUESTION 4: Competitive landscape Can we realistically win against likely competitors? 5 = clear differentiator / 3 = competitive / 1 = likely wired for someone else QUESTION 5: Strategic value Even if we lose, does pursuing this build something valuable? 5 = strongly strategic / 3 = somewhat / 1 = no case SCORING: 20 to 25: Pursue. Put your best resources on it. 15 to 19: Pursue with conditions. Shore up your weakest factor first. 10 to 14: Serious reconsideration. Below 10: Pass. The firms that improved their win rates the most were not the ones that chased more RFPs. They were the ones that got disciplined about which ones they chased. Drop your questions in the comments and tell me: does your firm have a formal Go/No-Go process right now or is it still gut feel?
0
0
Honest question: where has AI actually helped your proposal process, and where has it let you down?
I want to get a real conversation going here, not a highlights reel. We hear a lot about what AI is supposed to do for proposals. I want to know what it has actually done for yours, good and bad. I will start. Where it has genuinely helped us: - Compliance matrix generation from RFP documents saves 2 to 4 hours per proposal - First draft generation for boilerplate sections like firm overview and management approach cuts writing time significantly when given good source material - Rewriting for page limits: paste in a 600-word section with a 300-word limit and AI does a solid job Where it has fallen short: - Anything requiring real agency-specific context. AI does not know that this particular county program officer cares deeply about local subcontractor participation. - Technical approach sections without strong human input. The drafts are generic and evaluators can tell. - Anything where the firm's voice and differentiation needs to come through. AI writes average. Winning proposals are not average. - Net verdict: AI as an accelerant is real. AI as a proposal writer is marketing. What has your experience been? Drop your honest take below. No judgment here, just real data from real teams.
1
0
1-7 of 7
AI Made Simple
skool.com/ai-made-simple
For people who are brand new to AI. Real tools, real workflows, zero jargon. Taught by a non-technical founder who figured it out too.
Powered by