User
Write something
What part of your build do you need a second opinion on?
One of my favorite parts of our Houston hangout was getting to ask each other, "Where are you at with everything?" When you're building something on your own, you can spend hours going back and forth on a decision. You know all the details, but sometimes that makes it harder to explain where you're stuck, or see what to try next. Talking it through with someone gives you a chance to lay out your thinking. They might spot something you missed, share a similar experience, or ask a question you hadn't considered. Let's use this group for more of that. Bring one decision you're working through right now. It could be pricing your first offer, choosing who to serve, deciding what belongs in your first version, or figuring out whether something is ready to put in front of a customer. Give us three things: - What you're building and who it's for. A couple of sentences is enough. - What you've tried so far. Share a screenshot, rough draft, or what happened when you tested it. - The specific decision you need help with. Tell us the options you're considering and what makes the choice difficult. For example: "I'm building a tool for local service businesses. I've shown the demo to three owners, and two asked about pricing. I'm considering a setup fee or a monthly subscription, but I don't know how much ongoing support they'll need. What would you want to find out before choosing?" That gives people enough context to offer something useful. If you've dealt with someone's situation, jump in with what you tried, what happened, and what you'd do differently. And if you ask for feedback, come back and tell us what you tested. That's how everyone gets to learn from it. What's one decision you could use a second opinion on this week?
0
0
New free course: The Language of What We Do
Ever been on a call where someone says API, webhook, LLM, or MRR and you just nod along? This course fixes that. The Language of What We Do is live in the Classroom, and it's free. It covers 78 terms we use all the time in this group, explained in plain English with real examples from what we're building. No coding needed. Six short lessons: 1. How AI Actually Works 2. How Tools Talk to Each Other (including what it means to run Claude in the terminal) 3. Keep Your Keys and Secrets Safe 4. Data, Leads, and Memory 5. Business and Money Words 6. Put the Words to Work Each lesson ends with a quick self-check and a practice prompt you can paste into ChatGPT or Claude to quiz yourself. Start here before anything else in the Classroom. Then drop a comment with the one word that always confused you. I'll make sure it's covered.
0
0
Welcome to AI Outliers kings 👑
Hey, I'm Hanson. Welcome in. AI Outliers is for people who want out of the rat race and see AI as the opening to do it. Most people are still watching from the sidelines. That gap is the blue ocean, and it won't stay open forever. Here's how to get the most out of this place: 1. Start with The Language of What We Do in the Classroom. It's short, free, and teaches the words we throw around here (API, webhook, LLM, MRR, LTV, and the rest) in plain English. 2. Then open "Start here." It takes a few minutes and shows you how everything works. 3. Post what you build. Rough is fine. Shipping beats perfect. No hype and no income promises here. Just real builds and honest progress. Your first move: reply below with - Your name and where you're from - What you do right now - What you want AI to help you escape or build I read every reply. Let's go.
0
0
1-3 of 3
powered by
AI Outliers
skool.com/ai-outliers-8502
Spot the AI opportunity. Own your freedom.
Build your own community
Bring people together around your passion and get paid.
Powered by