Why I Started Beads of Hope

I did not start Beads of Hope because I had a neat little business plan and a tidy list of features.

I started it because of my son.

Type 1 Diabetes became part of our family story when he was two. That is still the sentence underneath this whole project, even when I’m talking about bracelets and badge reels and checkout buttons. He was two when everything changed.

Beads of Hope T1D is my attempt to make something useful from that feeling. It’s a small philanthropic shop and community site built around handmade, custom bead products — bracelets, necklaces, badge reels, pens — with the goal of raising money and awareness for Type 1 Diabetes.

I wanted it to feel hopeful without being cheesy. Personal without being sad all the time. Real enough that someone could land on the site, understand why it exists, buy something meaningful, and feel connected to the cause.

The problem was obvious: I had the idea, the purpose, and the desire to make it beautiful.

What I did not have was any idea how to build an online store.

On June 2, 2026, I opened the AI builder and gave it what I now recognize was a wildly oversized first prompt. I basically asked for the whole world in one breath:

“Build a fully functional, production-ready ecommerce and community website for a philanthropic organization called Beads of Hope. Brand purpose: raises money and awareness for Type 1 Diabetes through handmade/custom-designed bead products.”

Then I asked for the shop, the customize page, community features, checkout — everything.

Looking back, it makes me laugh a little. I had no coding background, but there I was, asking for a production-ready ecommerce site like I was ordering a sandwich.

And then, about 20 minutes later, something real appeared.

The AI had created what looked like the bones of an actual business: a shop page, Google login, a Stripe checkout setup, and 22 database tables. A database is basically where the site stores information, like products, orders, users, and carts. I did not fully understand that then, and honestly I’m still learning.

But I understood this: I was looking at a real-looking storefront for an idea that had only existed in my head.

It was thrilling.

It was also completely disorienting.

That first version made me feel like the future had arrived in my living room, but it also made me feel about five steps behind my own project. I remember thinking, “Wait… is this actually a store now?”

Of course, it was not that simple.

That same day, I hit the first big wall. None of my uploaded product images were showing on the published site. The shop page had duplicate category buttons. Every time I clicked where a product image should have been, the page snapped back to the top of the “all” category.

I told the AI, “images are still not visible and each time I click on the box the image should be in, the screen immediately reverts back to the top.”

And then I kept telling it variations of that for hours.

This is the part I think people don’t always understand about building with AI. It can feel magical one minute and maddening the next. One moment it builds a store. The next moment you are arguing with invisible missing pictures and wondering if you should just go make tea and never come back.

A few days later, the customize page threw an error I could not even pronounce with confidence: “Cannot find module '@/assets/blue-ribbon.png.asset.json’.”

I had no idea what an asset.json was. I still barely do. I only knew something was broken and the thing I wanted people to use was not working.

But underneath all the errors and tiny fixes, I kept coming back to the same hope: could this tool help me make something that looked and felt legitimate?

Not perfect. Not fancy for the sake of fancy. Just real.

That is why the little design details mattered so much to me. Moving a blue ribbon graphic down a quarter inch. Making the T1D Hope text stand out with white shading. Getting hover-zoom right on badge reel photos. I know those sound like tiny things, but they didn’t feel tiny at the time.

They felt like the difference between “someone’s hobby page” and “this cause matters.”

What I hoped the AI builder could do was simple and enormous at the same time: help me get past the blank screen. Help me build the shop I could picture but could not code. Help me turn a personal reason into a place people could actually visit.

It did do that.

Not without confusion. Not without security scans that made me feel wildly out of my depth. Not without the later realization that a built app is not the same thing as an open business — I still had Stripe, bank information, shipping, and tax to face in the real world.

But it got me further than I could have gotten alone.

And the store now exists. It is live-ready. I’m still nervous about the first real order. I’m still nervous about whether anyone will buy.

But I’m proud that it exists at all.

Small takeaway: AI did not remove the fear, but it gave me a place to put it.