I do the work I can with a toddler under foot… so when she obsesses for days over “muddy puddles” I use her excitement to my advantage. She sat and watched for 35 minutes as we cut out “muddy puddles” today. I had enough fabric for six sets of three. The first one goes to the commissioner (the toddler), one goes to the photographer, and the rest get inventoried and eventually listed. It’s a test run. We’ll call it limited edition, or limited run and take notes on the analytics. I have to decide if it’s worth storing an entirely new color of felt.

I'm here, bouncing between babies and the computer if anyone is here and wants to chat.

I built something for myself that I’m going to leave here. It’s a business coach AI — but trained through the lens of Andrew Carnegie’s thinking. Not hustle culture. Not “10x growth.”Not startup theater. Long-term leverage.Operational discipline. Capital as a tool. Building something that outlives you. Carnegie believed wealth was a responsibility. Build it well. Structure it well. Then use it to lift others. That philosophy shaped how I think about: - pricing - systems - scale - ownership - power - stewardship So I built a coach that responds from that perspective. It asks harder questions. It thinks in decades. It values structure over noise. I use it when I need clarity, not motivation. If you’re curious, here it is: Carnegie Coach No pitch.Just something I built because I enjoy thinking this way.

It's not really the end of my week today... It was my stepsons 10th birthday so I made Wednesday and Thursday family days instead of work days. I frontloaded the week. I made 5 weeks of homeschool curriculum for my toddler and then listed it in my digital Etsy shop. I built a website, because after sixteen years of relying on Etsy I realize that I NEED to have a direct line to my audience and customer base. I created a couple email campaigns and Pinterest funnels to build an email list, and I checked in with my top five communities on Skool. Then I took a day to rest. I slept in as long as the toddler and baby would let me. I did a load of laundry. I ordered pizza. I only worked on projects for the kids. Both girls got a pair of kitty ears made out of felt, and my stepson got his own personal set of plush knives for his birthday. He's been running around the house cosplaying "Among Us." After all the stuff for the kids was finished, I randomly asked, out loud, "what do I want to do now?" (because I talk to myself like that.) My toddler responded with "sew mommy. You want to sew." Making things for the kids is how I keep from burning out. Protecting energy is part of scaling too.

On the production floor, I learned something by watching a company try to grow: When specs and cost logic get blended together, you eventually build yourself into a corner. I saw it happen when SKUs slowly became information storage. Instead of simply identifying a product, they started carrying meaning like fabric color. It worked for a while. I was even convenient in a lot of ways... Until growth required clarity and separation. When information lives inside identifiers instead of clean documents, every change becomes a workaround. You’re not adjusting the system, you’re navigating through it. Scaling gets heavier than it needs to be. That’s a lesson I’ve been thinking about as I rebuild Dragonswood. Seperation leads to clarity, and you need clarity to scale. Spec Sheet: What the product is. Dimensions. Deliverables. Variants. Limits. BOM: What the product costs. Materials. Quantities. Current pricing. Time test. Labor rate. Different jobs.Different documents.Clear lines. Not flashy. Just structural. In Practice — Assignment: Do you use SKU's yet? Do your SKUs carry more meaning than they should? Where does pricing logic actually live? What part of your system depends on memory?