Business

3 min read

How I Turned a Hobby Into Real Income

Turning a creative hobby into a real business sounds simple. It isn’t. Here’s what worked for me—no theory, just the steps that paid off.

A cozy room with a wooden desk, computer, and warm sunlight streaming through a window.
A cozy room with a wooden desk, computer, and warm sunlight streaming through a window.

The First Signs It Could Be More Than a Hobby

It started as something I did in my free time. No big plans. I wrote, shared ideas, and learned in public. The first time someone replied and thanked me, I realized there was more here. When people asked for recommendations or wanted to pay for my notes, that was the second sign. You don’t need a huge audience—just proof that a few people care.

The Shifts That Made a Difference

I stopped treating it like a hobby. I put my name on things. I set a simple schedule and stuck to it. I built an email list and actually emailed it. I started charging for a few things—a guide, a paid newsletter, a consult call. At first, it felt weird. Then it started to work. I learned to sell without overthinking it. The biggest shift was mental—seeing this as real work, not just a side project.

What Made It Work (and What Didn’t)

Consistency mattered more than any one idea. Small wins added up—one subscriber at a time, one product at a time. I dropped projects that didn’t stick. I doubled down on what people wanted. Not everything worked, but every experiment taught me something. Most hobbies never make money because people never try to charge. If you want it to be a business, treat it like one. Test. Sell. Adjust. Keep going.

Frequently Asked Questions

You need Figma Console MCP installed in Claude Desktop. Once set up, Claude uses the figma_post_comment tool to pin comments to specific layer node IDs. You ask Claude to run a review and post violations — it handles both steps automatically.

Use Figma Console MCP's figma_get_file_data tool via Claude Desktop. It reads all text layers from your open Figma file — including layer names, text content, and node IDs — through the Desktop Bridge plugin. No exports, no copy-paste.

Yes. In your review prompt, ask Claude to review multiple frames by name. Claude reads all of them, checks against your guidelines, and posts comments across all screens. Expect 3–5 minutes for multiple screens.

About 15–20 minutes total — most of that is downloading Node.js if you do not have it. The configuration steps themselves take under 5 minutes. After setup, every content review takes 3–5 minutes.

Be the first to know about every new letter.

No spam, unsubscribe anytime.