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?

Hey, I’m Jaymie. I started my Etsy shop, Dragonswood, as a joke for a convention back in 2009. I made felt gnome hats, listed them online, and accidentally sold 200 of them in September/October. I honestly thought that was it. A fluke. A funny story I’d tell later. So I didn’t scale it. I didn’t optimize it. I didn’t “do marketing.” I just… kept the gnome hat stocked. And somehow, it kept selling at about the same rate for 15 years. The shop always had intentional vibes, but not intentional strategy. From the beginning, I ignored Etsy advice about sterile, white-background photos. I photographed everything in the forest because they were gnome hats — and it felt ridiculous to pretend otherwise. It wasn’t supposed to work anyway. It was just a hobby. Recently, I went on maternity leave and finally had the time to slow down and ask a question I’d been avoiding for years: Why is this working? That’s when I leaned in — not by stripping it down, but by giving it what it had always been hinting at. I added the whimsy it deserved, built the world I’d been quietly dreaming about, and got clear about the audience who had been finding it all along. I didn’t change the product. I shaped the story around it. After updating the shop (including SEO) in July, Dragonswood tripled its annual sales in four months. Customers didn’t just buy once — many came back two, three, sometimes four times in the same season. Reviews stopped focusing only on the hat and started talking about how magical it felt. That experience is why I’m here. Brand-Made is about designing brands people recognize and return to — even when they don’t follow the usual rules. We use tools, tactics, and formulas here — but always with intention. Always in service of the customer, not the algorithm. If you’ve ever built something that didn’t follow best practices but refused to disappear, you’re in the right place. ✨ Your turn — introduce yourself below.