Introduction
Recently, I became obsessed with VibeCoding, which involves using natural language to instruct AI to write code. This passion consumed me to the point where my family began to question my whereabouts.
Since realizing that AI has evolved from merely conversing to actually performing tasks, I have been brainstorming ways to monetize AI, exploring various avenues and attempts.
Tools Developed
Before diving into VibeCoding, I invested significant time and energy into OpenClaw, which has now become a reliable assistant for managing content on my geek website and WeChat account.
Earlier, I developed two WeChat mini-programs using Tencent’s Yuanbao. One was a “Pension Calculator” for practice, and the other was a more refined “Personality Type Quick Test Tool.” If you’re interested, feel free to check them out.
The monetization model for such tools is quite straightforward—earning revenue from Tencent’s ad shares. However, to enable this, a mini-program must have at least 500 followers, which I haven’t achieved due to lack of promotion and competition from similar programs.
My experience with mini-program development taught me that if the market already has similar tools, you are essentially repeating previous work. Without significant differentiation or improvement, standing out is challenging.
Developing WeChat mini-programs is relatively complex, tedious, and time-consuming, requiring specialized developer tools for repeated debugging to ensure consistent user experience across various devices. Just creating those two mini-programs left me exhausted.
In contrast, developing PC applications is much simpler. If the program doesn’t require backend support, you can have AI write a front-end HTML code, upload it to a web server, and you’re done. In a smooth scenario, you can complete a program in just ten minutes.
The Development Process
Initially, I asked DeepSeek to write code for a QR code generator. I described my requirements, such as a minimalist style and clear functionality. To my surprise, the first version of the code met my expectations.
This tool allows users to input a URL and quickly generate a QR code that links directly to the original page. It only requires front-end code, with no backend support needed. The code was completed in minutes, saved as an HTML file, and uploaded to the server for immediate use. The entire process exceeded my expectations.
From there, I continued to have AI assist me in developing several tools: a short link generator, text organizer, image compressor, random password generator, IP location finder, pixel avatar generator, image watermarking tool, and image stitching tool.

All nine tools are now live and perfectly adapted for mobile devices. The entire development process took only two working days, including adjustments to webpage background styles and card designs. If you’re interested, you can visit my tools page to try them out.
The short link generator, while appearing simple, is the most complex as it requires domain and backend support, necessitating three files in total. However, the process went smoothly.
I spent more time fine-tuning the features of the watermarking and image stitching tools, as they involved real-time previews to ensure a consistent experience across PC and mobile.
The Joy of VibeCoding
I must admit that VibeCoding, even without considering future monetization, provides a sense of satisfaction. Just by conversing in natural language, I can have AI turn my ideas into tangible products. This was unimaginable just a year ago.
There’s a notion that in the AI era, liberal arts students may have an advantage. My interpretation is that their strong language skills enable them to articulate their needs to AI more clearly, yielding better results. However, when it comes to coding, programmers may still outperform liberal arts students due to their understanding of code and debugging efficiency. As a liberal arts student, I often rely on AI for repetitive tasks, which can lead to AI skipping redundant code.
Monetization Strategies
Now, the serious question is how to monetize these tools. After developing the nine tools, my tools.html page resembles a functional toolbox. I set long-tail keywords for the page title, such as “Comprehensive Tools Collection” and “Free QR Code Generator,” to improve search engine indexing.
Since all tools are free, my current monetization strategy is through ad revenue.

I have integrated Baidu Alliance ads at the bottom of the toolbox homepage and each individual tool page, allowing me to earn revenue from user clicks. I also applied for Google ads, which are currently under review.
However, the challenge is that PC websites have low traffic and click-through rates. Most mobile browsers block ads by default, making it unrealistic to expect user clicks.
To be honest, the tools I’ve developed are not groundbreaking; users can find similar tools online for free. More complex tools like Word to PDF converters often come with a fee. I could develop a free version to attract users, but such tools require a more complex server environment, which I currently lack the resources to tackle.
My only hope is that one of these tools gains good traction in search engines, leading to increased traffic. Since all my tool pages link to each other, this may enhance user engagement and encourage bookmarking, making the ad revenue model viable.
I understand that relying solely on AI to develop tools for passive income is unrealistic. However, I have accomplished this task, which has given me a sense of achievement and satisfaction. There’s also a bit of vanity in the fact that a liberal arts student like me can develop applications.
My journey to leverage AI for profit has just begun. If I find the time, I may have AI help me develop more applications, such as AI tools that integrate large models, or even directly create an app. However, I won’t rush into it without a solid idea.
In summary, I have taken a crucial step toward transforming AI into a profitable tool. I hope this marks a promising start.
Comments
Discussion is powered by Giscus (GitHub Discussions). Add
repo,repoID,category, andcategoryIDunder[params.comments.giscus]inhugo.tomlusing the values from the Giscus setup tool.