User
Write something
Pinned
Introduce yourself
New here? Drop a comment and tell me: 1. What are you working on, or what do you do? 2. What brought you to Creator OS? 3. What are you hoping to get out of being here? 4. I read every comment — genuinely curious where everyone's coming from.
0
0
Pinned
Six communities, a handful of tools, and a lot of scripts — this is Creator OS
I'm a software engineer. I do all of this on the side. Over the past few months I've joined six AI communities, bought a handful of tools I'm still figuring out, and built scripts to help me work through it all faster. I've learned from Liam, Zane, Nate, Chase, Alec, and Lindsay. Each one taught me something different. None of them taught me all of it. Creator OS is where I document what I'm putting together from all of that. An honest record of what I'm building, how it's actually going, and what I can't figure out yet. Sometimes I'll post twice a week. Sometimes I'll go quiet because real life gets in the way. But when I do post, it'll be real. If you're somewhere on a similar path, I'd like to hear where you are.
0
0
Pinned
Industry Research - Survey Approach
I built a short research survey to map and understand how your business actually works and where the real challenges are — 7 questions, 5 minutes. https://sarat.sarvepalli.com/research Can you give it a try and share your thoughts on it. I have linked it with Supabase functions to be able to process the questions and then use the Grill me Skill that Nate Herk shared in AIS+ community. Happy to also connect with new members via LinkedIn!!
Industry Research - Survey Approach
Where to Set the Threshold
Spending this week going deeper on the wildlife AI system instead of citing the topline number again. The part I keep coming back to is the confidence threshold: every image gets a classification and a score, and anything below the threshold gets routed to a person instead of logged as fact. Setting that threshold is the part nobody talks about. Get it wrong in one direction and you're back to reviewing almost everything by hand, which defeats the point of building the system at all. Nobody hands you a formula for the right number. It comes down to a judgment call: how much risk of a missed or wrong classification is acceptable before a human needs to look. I don't think there's a universally correct number here. What matters is picking one that's honest about how wrong the model still gets things. Curious how other people building anything with a human-review step think about where to set that line.
0
0
Month 1, All in One Place
I went back through everything I wrote in September and tried to find the thread connecting it, because at the time each piece felt like its own separate rabbit hole. Turns out the thread was simple: check the claim before repeating it, then go find what's already running for real. Week one was about email drafting. I kept seeing the same pitch everywhere, that letting AI draft your replies is basically free productivity. So I went looking for the research behind it instead of the marketing version. One clinical documentation study found unreviewed AI drafts were wrong 42% of the time. That number changed how I build now. The rule I run on is plain: AI drafts, a human sends. No exceptions, no matter how good the model gets. Week two moved off claims and onto client work I can point to directly. Workflow automation projects have been clearing 8 to 20 hours of manual admin a week for the people running them, worth somewhere between £20,000 and £57,000 a year in recovered value, a range that keeps repeating across different engagements rather than one standout client. The number that surprised me most wasn't the money, it was how consistently that range showed up across businesses doing nothing alike. Separate from that, a wildlife conservation project cut manual camera-trap image review by more than 90%, putting over 1,200 specialist hours a year back into people who'd rather be doing conservation work than sorting photos. And on the outreach side, an AI business development pipeline produced 140+ personalised emails across two niches in under two weeks, the kind of volume that used to mean hiring someone just for that. Week three tried to put a shape around all of it, because "AI helps businesses" is too vague to check against anything. I landed on a five-stage maturity model: Stage 0, manual everything. Stage 1, AI bolted on with no integration. Stage 2, AI inside real workflows with a human still reviewing. Stage 3, agents that each own a recurring job with human approval at the decisions that matter. Stage 4, a self-managing operating layer. Most small businesses I talk to sit at Stage 0 or Stage 1, which tells you where the real starting line is before anyone promises Stage 4 results.
0
0
1-12 of 12
powered by
Creator OS
skool.com/creator-os-4248
AI tools, scripts, and workflows — documented as I learn. Honest experiments, not polished courses.
Build your own community
Bring people together around your passion and get paid.
Powered by