I have created an automatic Brand Wiki 🚀 The goal is to: - Have my business information available on the web for LLMs to find, - Be able to link it as a brand kit in any llm - A resource to add when applying for grants - Get the SEO and backlinks popping The overall goal is to have Claude use it to make weekly content calendars that I just wake up and see once a week. I am attempting to remove every ounce of decision fatigue, which has become a very noticeable hurdle since being on ADHD medication. Anyway, I give Claude or Chatty some info, we talk it out, I tell it to write an article and push it to the WIki. After a few minutes it is on the site like magic! I showed the ladies during Co-Working on Sunday! By the time I am finished, this will definitely be a service, I am realising I love the technical, system based side of the space more than the digital products that I get bored of after after a few months. 🤭

Most people open a community and immediately think about content. What to post, how often, what the first thing should say. I did not start there. And if you are ever thinking about building a community, I would suggest you do not either. Here is what I set up first, and why the order matters. 🏗️ The foundation before the front door The very first thing I sorted was the community agreement. Not because it is exciting, but because I knew I was going to collect email addresses through the joining questions. You cannot collect data without telling people what you will do with it. In the UK that is not optional. So before a single member joined, there was a plain-language document in the START HERE module explaining exactly what their email would be used for and how to opt out. Skool has its own terms and conditions that cover the platform. What it does not cover is how your specific community operates. That part is yours to write. 📚 The welcome module before the content The second thing I built was the START HERE module. Five short pages covering what Indigo AI is, how the community works, the community agreement, and what is being built. All publicly visible, all in place before the doors opened. The logic is simple. If someone joins and lands somewhere empty or confusing, they leave. The welcome module is not exciting content. It is the thing that makes everything else make sense. 🪝 The copy that does the heavy lifting Once the foundation was in place I worked on the about page description and the hook. These are the words a prospective member reads before they decide to join. The about page has a 1000 character limit. The hook has 150. Every word has to earn its place. The framework I used structures the copy in seven sections: who it is for, why you are credible, what they get, what it is not for, proof, friction removers, and a clear call to action. Even with limited proof at an early stage you can write honestly and still write confidently. ❓ The joining questions

Indigo AI is being built in public. That means you are not just joining a community. You are watching one take shape in real time. Every step of the build gets documented. What is working, what is not, what is being added and why. You will find those posts under the Building Indigo AI in Public category in the feed. You are early. That means your voice carries more weight here than it ever will again. So let's start with something practical. The classroom curriculum is being built right now and I want to know how you learn best so I can build it in a way that actually works for you. Cast your vote below 👇 🗳️ How do you prefer to learn? Results will directly influence how the first classroom modules are structured. This is not a throwaway poll. Vote and then tell me more in the comments if you want to.