Morning Vibe Hardware crew! I've just added the parts and prompt breakdown for the 'Spotify controller' to the "Classroom" section in here: https://www.skool.com/vibe-hardware-9276/classroom/11241ef4 I'd originally planned to drop it in there on Monday, but yesterday's reel has 'blown up' (albeit on a very small scale) and we've had an influx of new members - so I wanted to make sure the stuff was in there as I promised! If you build one - I want to see pics!!

I think I’ve landed on the concept for the ‘100 member’ giveaway! Rather than simply picking a name out of a hat and sending a random device the winner may not want… 🚨 What if I gave you the chance to ‘pitch your build’? 🚨 I’d create a thread where you could share your build idea and the hardware you’d need, and then I’d pick a winner (or do a vote) for whose project I’ll sponsor out of my own pocket. And because I want to this to be open to everyone, I’ll provide any 1:1 guidance and instruction you need to turn your idea into reality. (Assuming it’s actually possible 😂) The only proviso is you’d have to be willing to share your build details and progress in the group, so we can all follow along. What do you think? Let me know by casting your vote below (or it’s back to the drawing board).

Welcome to the club. Quick version of why this place exists: everyone's using AI to build software, and I think most of them are missing the more interesting move... For less than 50 quid you can buy a little computer, plug it in, and have Claude write the code to make it do genuinely useful stuff. No soldering. No electronics background. I'd know, I haven't got one. I run a marketing agency. Six months ago I couldn't have built any of this. Right now there are devices on my desk that: - Show my Claude Code usage so I can see it working - Scroll through my calendar, the weather, and a client's live ad numbers - Play a fanfare when that client makes a sale (easily the best feature I've built) I'm five devices in and I'm documenting everything here as I go: what I buy, what it costs, what breaks, the prompts I use, the code Claude writes, all of it. The builds that fail go up too, because that's where the actual lessons are. I'm not an expert. I'm maybe three weeks ahead of you. That's the point of the club: work it out in public, together. Do these two things now: 1. Drop a comment introducing yourself: who you are and what you'd put on a little screen on YOUR desk if you could. Best answer gets built on camera. 2. Turn on notifications for this group so you catch the builds as they land. Fish