Hi everyone! Finally, I feel like I can share what I’ve been building behind the scenes. AND I AM FUCKING PROUD OF THIS ONE! 🔥 What do you think something like this is worth? I’ve built an end-to-end contract automation pipeline that runs 100% inside the Microsoft ecosystem. The best part? There is ZERO AI in this flow. Just pure, deterministic, enterprise-grade automation that works flawlessly every single time—and costs next to nothing to run! ⚙️ How the Flow Works: Drop & Trigger: You drop a .pdf file into a specific SharePoint folder. This instantly triggers a Power Automate flow that extracts the data and generates a draft contract. Interactive Teams Approval: The person who uploaded the file receives an automated notification in Microsoft Teams. Right inside Teams, they can: - View the uploaded source file. - Review the generated draft contract. - Approve or deny the contract. - Edit key values directly (edits apply to the final executed contract). E-Signing (No Third-Party Fees): Once approved, the contract is automatically emailed to the customer with a unique link to review and e-sign. - Customers can sign using a mouse, touch screen, stylus, or by uploading a signature image. - Note: You can plug in Adobe Sign or DocuSign, but why pay per signature during testing when you can build it yourself? 😉 Legally Sound Audit Trail: The system captures and logs full verification parameters: [Signed By], [Signed At], [Signer Email], [Signer IP], [Signer Device], [Signature Method], [Document Hash], [Reference], [Approved By], [Approved At]. Final Delivery & Auto-Cleanup: Once signed, the finalized contract is emailed to both parties. The flow then automatically deletes all temporary input and output files, leaving a clean footprint where only the two emailed contracts exist. 🛡️ Built for Enterprise & Clients Bulletproof Reliability: Built-in safety features prevent duplicate entries, invalid file formats, or missing data fields.

I never would have thought I’d be doing something like this. Back in February, I was just going about my business working my 9-5 and caring for my wife and daughter. I decided on a whim to start looking more into AI and a few weeks later I ended up here. I am so blessed to have found Jake and this community right at the start of my journey. I skipped all the noise and went straight to drinking from the fire hose of all the great content here. I snuck around for a couple months until the competitions started and then I started building. And posting. And building and posting. And you guys listened, continue to listen and I’m amazed by that. I’m so grateful for all the friends and community members I’ve met here. You all are what keeps me putting coals to the fire. I want to remember this moment 1,2,5 years from now and look back and see where it all started. With all of you. Thank you! We’re just getting started 🚀

This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post.

It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!

Trying something new where I just put everything out there that’s going on in my brain. Let me know if you like it!