a16z speedrun is one of the biggest accelerators in the world. We submitted our application a bit back on the recommendation of one of our friends. Our EdubaWare software has been in closed testing for a bit (get ready, next week thousands of you will get access to it and see our changes) We received and Email yesterday saying they want to hear more from us and to send them a video in under three minutes that explains: - Your backgrounds and greatest accomplishments, professional or personal - What makes you exceptional, and why you're the team to win this market - What you're building and what problem it solves - Why this is a big, underserved opportunity - What progress you've made so far  Now fitting all that into one video is challenging, but we did our best. I hope this gives you a view into the other side of my life which is my company Eduba!

Experience tells us, ideas aren't the same as execution, and most of us aren't inventing something completely new. But there's a difference between discussing a problem and effectively handing someone the blueprint to your proposed solution. One thing I appreciate about this community is how openly people share their knowledge, experiences, and approaches to solving problems. It's actually part of what got me thinking about this. Where do you draw the line between sharing knowledge and protecting something you're trying to build a business around? Do you share early to get feedback, wait until you've built something, or take a more cautious approach depending on the idea? I'm curious how others here handle this, especially now that AI has made it so much easier to turn an idea into a working product.

Hey Clief Notes fam! 👋 I'm Jason. I figured it's finally time to say hello. 🙋 A little about me: I run a few small businesses and do tech consulting on the side. 🎯 My current goal: Turning client discovery from a weeks-long process into hours or days. 💪 What I'm currently building/working on: I have a few active projects. The one I am focused on right now is for the Lyceum. It's a client discovery ICM that works through everything a client can give access to and flags what's missing or doesn't add up. 🤔 My biggest struggle or question right now: Keeping things simple. I tend to over-build, so I'd love to hear how you all keep your scope tight. Let's get it! 🚀

📣 Update (10/22/26): Comp 15 Rules Added Current Challenge: Competition 15 The Challenge 💪 - Rebuild a past comp entry. Yours or someone else's. Then prove that its better. Rules & submissions 🗒️ -https://www.skool.com/cliefnotes/weekly-comp-15-the-rebuild Good luck everyone! --- What this thread is: I’ve seen a number of people either not know competitions are going on or know how to find them so here is a quick single source thread where you can get to them all. I’ll keep this updated as new challenges are released. See the current challenge as well as all past challenges below! Format for community challenges: https://www.skool.com/cliefnotes/how-competitions-work-from-now-on?p=84912d60 Weekly leaderboard competition: Alongside the biweekly challenges, there is a weekly leaderboard challenge where the member at the top of the 7 day rolling leaderboard wins a free upgrade to their membership. This winner is announced on Mondays typically. --- Past Challenges Competition 1 The Challenge 💪 - Build a brand voice document for a pet grooming business Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/first-ever-weekly-competition-is-live?p=90f50bf9 Results🏆 - https://www.skool.com/cliefnotes/weekly-comp-1-winner-ian-barriopedro?p=0501b57e Competition 2 The Challenge 💪 - Build an artifact of a financial advisor client intake system Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-2-the-artifact-sprint?p=15145a68 Results🏆 - https://www.skool.com/cliefnotes/weekly-comp-2-winner-virgilio-robinson

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.