My Claude Pro Subscription Paid for Itself Twice During Four Weeks of Personal Leave

Apr 16, 2026 min read

I took four weeks of personal leave. My goal was to stay off laptops, not think about work, and be present.

That lasted about a week.

Then a DreamHost renewal notice landed in my inbox and I thought — before I click pay, let me ask Kiro if there’s a better way. Two hours later I had cancelled the subscription, migrated two websites to a faster stack, and was back on the couch. A few days after that, an amended tax return I’d filed with Claude’s help had put $500 back in my bank account.

The Claude Pro subscription I’d picked up during the break had already paid for itself several times over. And I hadn’t written a single line of code.

This post is for business people — sales, ops, finance, HR, anyone — who assume AI coding tools are for engineers. They’re not. Here’s what actually happened.


A quick note on the tools

I use several AI tools through work. This experiment was personal — I wanted to understand what the consumer versions of Claude and Kiro could do for everyday tasks when I was the one prompting, not a developer on my team.

Kiro is an AI-powered IDE (development environment) that can reason about technical problems, research options, and execute multi-step tasks autonomously. Claude Code is Anthropic’s AI that runs in the terminal and can read, write, and modify files with precision. Together they’re a formidable pair — Kiro figures out the strategy, Claude executes the details.

But neither of these require you to know how to code. You just need to know what you want.


Example 1: $120/year saved — two websites migrated in under two hours

The situation

My personal website and my wife’s portfolio site both ran on WordPress, hosted on DreamHost. Renewal was coming up — around $120 a year combined. They worked fine, but they were slow, required occasional maintenance, and cost money for no particular reason.

What I asked Kiro

I described the situation: two WordPress sites, $120/year, renewal due. I asked whether there was a faster, cheaper, more secure way to run them.

Kiro came back with a clear recommendation: migrate both sites to Hugo (a static site generator) and host them on Cloudflare Pages for free. It explained the trade-offs, confirmed this was appropriate for portfolio/blog sites, and then — this is where it gets interesting — it just started doing it.

Kiro scraped my existing website, converted the content and structure into the Hugo format, selected an appropriate theme, and had a working local version running in minutes. It then did the same for my wife’s site, which had 15 UX case studies, hundreds of images, and more complex content. Everything was converted, organized into the right folder structure, and ready to deploy.

Where Claude came in

Once the sites were built, I wanted refinements. The blog post card previews were truncating titles and not showing preview text correctly. The cover images across my wife’s posts were visually inconsistent — different colors, different styles, different sizes.

I opened Claude Code and described what I wanted: consistent grayscale hero images across all posts, fix the card previews, add infinite scroll to the blog list. Claude made those changes precisely — it diagnosed the root cause of each issue (in one case, a nested HTML bug in the theme’s template), fixed it, and committed the changes cleanly.

I didn’t write code. I described outcomes. The tools did the implementation.

The result

Both websites are now live on Cloudflare and GitHub. They load faster than before, cost nothing to host, and I own the setup entirely. DreamHost account: cancelled.

Saving: $120/year. Time: under two hours.


Example 2: $500 in amended tax refunds — found by asking the right questions

The situation

I thought I had a straightforward tax situation. My daughter had aged out of daycare, I’d moved to a new state mid-year, and I assumed the only complexity was the dual-state filing I’d already handled. I’d filed both years myself and figured I was done.

What I asked Claude

On a whim, I pointed Claude at my last two years of tax returns and asked it to review them for anything I might have missed.

It read through everything and then asked me a series of targeted questions. Did your daughter attend any summer camps last year? Any after-school programs? Any enrichment activities while you or your spouse were working?

I hadn’t thought of these as tax-relevant. My mental model of the Child and Dependent Care Credit was daycare-only. Claude explained that the credit applies to a broader set of qualifying expenses — summer camps, before/after school programs, and similar childcare while parents are working — up to $3,000 for one child per year, with a credit of 20–35% depending on income.

What happened next

I pulled together receipts and program records. I gave Claude the numbers. It walked me through the amended 1040X process, calculated the credit amounts for both years, and produced the completed forms. I reviewed them, verified the numbers against the IRS instructions it referenced, and filed.

Combined refund across both amended returns: approximately $500.

The whole process — from “let me try this” to mailing the forms — took one afternoon.


What this means for business users

I spend a lot of time talking to enterprise customers about AI strategy. The conversation is almost always about automation at scale, developer productivity, large language model integration. These are real and important conversations.

But the everyday productivity story gets undersold.

A few observations from this experiment:

The value isn’t in the automation. It’s in the questions you didn’t know to ask. Kiro didn’t just execute a migration — it reframed the problem. I was about to pay for something I didn’t need to pay for. The AI surfaced the option I didn’t know existed. Claude didn’t file my taxes — it asked about summer camps. That question was worth $500.

“I don’t code” is not a barrier. I gave Kiro a problem statement in plain English. I gave Claude a tax return. Neither required technical fluency. The bottleneck is knowing what outcome you want and being willing to engage with the tool’s follow-up questions.

These tools compound. The website migration saved money and time. The tax review recovered money I’d already spent. Neither outcome was the kind of thing I’d have put on a formal AI use case list. Both required maybe three hours of my attention combined.

The subscription math is different from software you buy. A fixed-cost AI subscription that surfaces one insight — a credit you missed, a cost you were overpaying, a process that can be simplified — can pay for months or years of the subscription in a single conversation. That’s not a typical software ROI calculation.


The honest caveats

I’m not suggesting you fire your accountant or assume AI tools are infallible. I verified the tax calculations independently before filing. Claude cited the relevant IRS publications and I read them. On the website side, Kiro’s initial migration needed refinement — that’s where the Claude Code work came in.

These are tools that make you more effective, not tools that replace judgment. But they dramatically lower the cost of asking “is there a better way to do this?”


The bottom line

Claude Pro costs $20/month — $240/year.

In the first few weeks of paternity leave, using it for personal tasks with no engineering background and no prior experience with either tool, I saved $120 in recurring costs and recovered $500 in tax refunds.

That’s a 2.6x return before I’d finished my first month.

The question worth asking isn’t whether AI tools are for technical people. It’s whether you’re leaving money on the table by assuming they are.