I’m Joy, thrilled to join this community. I’m with DropSure, an automated SaaS tool built for Shopify dropshipping stores. I’m looking forward to connecting with more Shopify and dropshipping sellers to exchange actionable store growth strategies and operational optimization tips. I can share hands-on experience with DropSure: our tool streamlines the entire order fulfillment process, cuts down tons of manual busywork for store owners, and effectively boosts profit margins. I’m eager to learn how you build efficient operating systems from all of you, and grow and succeed together side by side!

Two weeks ago I stood in this room and begged you all to stop using big words like "orchestration." This week I "accidentally" built one. La ironía. Quick reminder of who's talking: I'm not a coder. Built my company on Excel, faith, and the kind of stubbornness my pregnant wife tolerates because I bring snacks to bed at 1 AM. In a room full of software engineers, I'm the guy who snuck into Harvard on a clerical error. So grade this on a curve. Here's the thing I built. I'm calling it the 8 SIGNAL Operating System (my fancy words for 8 SIGNAL's implementation of ICM). If you've been around in the community long enough, you know the drill. It's one place where my whole team and I work alongside AI. Not a chatbot in the corner. Not eleven different tools nobody remembers to open. One environment, and every department lives inside it. Marketing. Client work. Accounting. This week, legal. The part that still makes me a little dizzy: it routes itself. --- Hand it a legal document and it walks itself to the legal corner of the OS, does the work there, and still carries the context of the whole company with it. --- This morning, mid leadership meeting, I fed it notes on a job candidate. Never told it where to look. It went and found the job descriptions on its own and started scoring the fit while I was still talking. --- It's tool-agnostic. Whatever model is best in that moment, Claude, Gemini, Codex, it's supposed to reach for that one. I'm not married to a vendor. I'm married to the result. (I should probably test this out for myself, but I'm taking Jake's word on this one.) And the boring win I love most: every week somebody on my team used to pull our accounts receivable and payable out of QuickBooks by hand and type them into a task before our leadership meeting. Tedious. Easy to forget. As of last week, the system reads it, organizes the numbers the way my team likes to see them, drops them in the right place (Asana task description) on its own, and moves last week's data to a new place (Asana comments on that same task). Nobody touches it. Three months ago I could not have built that. I learned how by building it.

We all learn differently and sometimes you may be "stuck" and with a such a large community, and counting. Do you find the community to "listen" to you?

Most of what I see in here is about automating tasks. Building workflows, connecting tools, making things run faster. I've been learning all of it and it's clicking.But I kept hitting a wall that I couldn't name for a while. I was using an LLM app as my operating system. Not just for tasks but for decision-making, project navigation, thinking through problems, tracking where things stood across different work. And it kept falling apart. Sessions ended, context disappeared, drift compounded quietly. By the time something felt wrong, I was already deep in the wrong direction. I lost real work to it. The problem wasn't the tool. The problem was the category error. A workflow system automates a process you already understand. You know the steps, you know the inputs and outputs, you want to run it reliably and faster. It's execution. It shines when the process is stable. A reasoning system is what you need before that. It's the thinking partner that helps you figure out what the process should even be, especially when you're building something from scratch and the process doesn't exist yet. You can't automate your way to a decision you haven't made yet. I was treating a reasoning tool like a workflow system. No persistent state, no routing logic, no structure, just conversation. It can't hold a project together. That's not what it's for. So I've been building what I'm calling CoworkOS, based on ICM principles, a folder architecture that gives Claude a stable structure to operate within across sessions. Routing tables, layered context files, memory that persists. The idea is: before you build workflows inside your projects, you might need an operating layer that actually runs the reasoning coherently. I don't know if this is the right approach yet. Still figuring it out. But the distinction feels important, especially if you're newer to this and trying to figure out where to start. Workflows are powerful once you know what you're automating. The reasoning layer is what gets you there.

May 29, 2026. Today the State of California approved our Initial Filing. Orca Child in the Wild is now a recognized Nonprofit Corporation, California Public Benefit. ⚠️ Edit: I need to ask you a favor, if you see this, can you please leave a comment for my daughter, It will mean the world to me! 🐬❤️‍🔥 Her name is Jordyn I need to take a second to let that sink in. We have been at this for a while now, my daughters dream is to be a marine biologist! 🐬This is not a pet a dolphin passion, although I know she still loves that part. Jordyn is passionate about saving the ocean! 🌊 We have been grateful enough to be able to send her to sea camp a few years in a row and we challenge her to be her dream today, not to wait for it to come true tomorrow. We believe that dreams are meant to be lived! And straight out, So should you! 🔥🌟❤️‍🔥 What started as a kid who loves the ocean and a family who believed her is now an official organization, recognized by the state, built to protect the waters we all share. From the Los Angeles coast down to San Diego. The tide pools, the kelp forests, the rivers, the lakes, the ponds, and every creature that calls them home. This is a legal status on paper, yes. But here is what it really means: - We can apply for grants and bigger partnerships, so our impact reaches further. - Donations to our mission carry real weight now, backed by a recognized public benefit nonprofit. - The work we have been pouring our hearts into has a permanent home. This was a family effort and a major win and milestone. We are on our way to cleaning up and protecting 120 miles of California coastline. 🏖️ We are now officially the Orca Child in the Wild Family https://www.orcachildinthewild.com (Jordyn created this site, with a little help from dad and Claude Code.)