AI Indie Hacking: How a Frontend Engineer Uses AI, Code, and Content to Productize Himself
The real reason I am exploring AI indie hacking is simple: I do not want to rely only on salary for the long term.
Salary is important. It provides stable cash flow and a sense of security for a family. But if a person’s income depends only on salary, then time, energy, and income ceiling are all tied to one job.
I want to externalize my abilities and turn them into products that other people can read, use, buy, and reuse.
These products do not all have to be SaaS. A product can be an ebook, a content system, a blog tool, a Chrome extension, a GEO optimization tool, or one day a small software product that generates steady revenue.
For me, AI is an amplifier. I have frontend engineering skills, and I also have interests in investing, writing, and product ideas. In the past, turning these abilities into products as a solo builder was expensive. Today, AI lowers the cost of research, writing, rewriting, design, coding, testing, and publishing.
That does not mean success becomes easy. It only means an ordinary person gets another chance to productize his abilities.
My core belief
AI indie hacking does not mean “use AI and money will come.”
What AI really changes is the cost structure. In the past, many tasks required a team: research, prototyping, development, copywriting, design, support, and distribution. Now, one person with AI can handle part of this work.
But once costs go down, competition also becomes more intense. The scarce skill is not simply knowing how to use AI. The scarce skill is continuously finding problems, understanding users, shipping products, getting feedback, and turning feedback into the next iteration.
So my current understanding of AI indie hacking is:
Do not chase trends.
Productize your own abilities.
Do not only build tools.
Build a system of content, products, distribution, and cash flow.
Do not go all in on SaaS too early.
Start with small products that can validate real revenue.
That is why I am currently more interested in ebooks, blog GEO, Xiaohongshu content, and small tool experiments, instead of immediately building a large SaaS product.
Why I do not want to rely only on salary
Employment has stability, but it also has limits.
No matter how high a salary is, it is still mainly an exchange of time for money. If most income comes from salary, it is hard to avoid depending on a single organization, a single role, and a single industry cycle.
I now have family responsibilities. I want more freedom not only for myself, but also to take better care of my family in the long run.
So what I want to build is a second curve while still keeping my main job and stable cash flow.
This second curve does not need to be huge at the beginning, but it has to be real.
It should generate income, even if it is small at first. It should accumulate assets, even if those assets are only articles, manuscripts, tools, and user feedback in the beginning. It should gradually reduce my dependence on a single salary source.
The most realistic product right now: ebooks
At this stage, the product format I care about most is ebooks.
The reason is simple: ebooks are the only project that has already brought me real revenue.
I have written an ebook about options. The monthly income is still occasional and not enough, but it proves one thing: a person can use knowledge, writing, and distribution to create income that is not completely dependent on salary.
The advantage of ebooks is low cost, reusability, long-term sales potential, and a small amount of compounding.
If an ebook is truly useful to readers, then as long as people keep discovering it and being convinced by it, it may keep generating revenue. It is not like a one-off service. It is more like a small asset that can be discovered, bought, and read repeatedly over a long period of time.
After combining ebooks with AI, the production threshold becomes even lower.
AI can help me with many steps:
track market trends
analyze topic opportunities
generate outlines
organize materials
rewrite content
optimize title and description
assist with cover design
assist with publishing input
generate ad keywords
review sales data
I also built an ebook generation SaaS tool before. Now AI can already generate ebooks directly from Markdown, which makes me more convinced that the ebook production workflow itself can be toolized and systematized.
Ebook topics: AI and investing are my focus
So far, I have only formally written one ebook about options.
In the future, I am more interested in writing about AI and investing.
Frontend technology and personal growth are also possible topics, but from the perspective of long-term accumulation and personal interest, AI and investing fit me better.
AI is the core variable in my current professional ability and tool stack. Investing is a field I have followed for a long time, and it is closely related to ordinary people’s wealth anxiety, family cash flow, and asset allocation.
So my future ebook topics may focus on:
AI tools and workflows
AI indie hacking
long-term investing for ordinary people
options basics and risk control
index funds and asset allocation
how technical people can productize themselves
I do not yet have a very clear topic matrix. A more realistic approach is to choose topics based on current trends and real needs: what problems are being discussed repeatedly, where information gaps exist, what can be supported by data and examples, and what can truly help readers.
If the content is genuinely useful, I believe there is a chance that people will pay for it.
What I mean by scaling ebook production
When I say I want to scale ebooks, I do not mean producing low-quality books in bulk.
What I mean is that the success of a single book is uncertain, so I need more attempts to improve the hit rate.
Writing 10 books a year is probably too much for my current stage. If I can consistently produce 5 good ebooks a year, that would already be a major improvement.
The key is not blindly chasing quantity. The key is building a reusable workflow:
topic research
→ outline design
→ material collection
→ draft generation
→ human judgment and rewriting
→ cover and listing copy
→ KDP publishing
→ ad testing
→ sales review
→ next book iteration
If this workflow works, ebooks are no longer one-off creations. They become a repeatable and improvable content product system.
The biggest problems with ebooks today
The biggest problem right now is not that I do not want to write. It is that my material system is not mature enough.
When the material system is incomplete, the production process becomes slow. If every book starts from zero — finding sources, building structure, writing content — the efficiency is very low.
The second problem is unstable sales.
I currently mainly earn revenue through KDP, and most of the income comes from the Chinese market. So in the near future, I may focus more on Chinese content instead of going directly into the English market.
The third problem is that ads have not yet shown strong scaling effects.
I have tested ads before, but the return is not obvious. The reason may not be that ads are useless. It may be that the book’s quality, cover, title, description, reviews, and conversion rate are not strong enough to be scaled reliably by ads.
So at this stage, I should not blindly increase ad budget. I should first improve the quality of the books and the accuracy of topic selection.
Content channels as long-term compounding traffic assets
WeChat Official Account, Xiaohongshu, Substack, blog, and YouTube are not just content platforms for me.
They are long-term compounding traffic sources.
Without traffic, it is very hard to promote products. For solo builders, the biggest problem is often not that a product cannot be built. It is that nobody knows it, nobody trusts it, and nobody is willing to try it.
The meaning of content is to continuously show my judgment, experience, methods, and real experiments, so that potential readers and users know what I care about, what I am solving, and what value I can provide.
Different platforms play different roles:
Blog: long-term asset and search entry
Xiaohongshu: short-term feedback and finance content testing
WeChat Official Account: Chinese long-form writing and trust building
Substack: English content and email subscription experiment
YouTube: video expression and long-term search, but I currently lack time and energy
My blog is currently going through SEO / GEO optimization, and I have also tested using Google Ads to bring traffic. The revenue from blog SEO is basically negligible right now, but it is a testing ground.
On Xiaohongshu, I am running some accounts mainly around finance information.
YouTube currently does not receive much time or energy.
My WeChat Official Account is not doing well either. My analysis is that many articles do not have strong traffic characteristics, so click-through is low.
These channels are not mature yet, but they are part of my long-term system.
My attitude toward SaaS: cautious, but not giving up
SaaS is a long-term direction for me, but it is not the most certain direction right now.
My judgment that SaaS has a low success rate is more of an intuitive one. SaaS is not only a development problem. It also involves acquisition, demand validation, payment conversion, ongoing maintenance, competition, and even early costs such as domain names, deployment, and infrastructure.
As a frontend engineer, I am not worried that I cannot build software at all. What worries me more is: what if I build something and nobody uses it, or people use it but do not want to pay?
I previously built an English learning tool called gosayo.cc. It is useful for me personally, but I think it may be hard to monetize because English learning tools are highly competitive, and user willingness to pay is not easy to capture.
So I will not start by building a large, all-in-one SaaS.
A more realistic path is to extract a small tool from my own real workflow, use it myself first, and then see whether it can serve people similar to me.
In the future, I do not want to limit the type of SaaS I build. I may consider:
content tools
investing tools
developer tools
Chrome extensions
plugins around existing ecosystems
ebook production tools
GEO / SEO optimization tools
But for now, I will choose the entry point carefully.
What I want to build next: a GEO optimization tool
If I can only choose one software direction to test in the next three months, I may start with a GEO optimization tool.
The reason is that this direction is strongly connected to my current personal website practice.
I recently went through a round of GEO / SEO optimization for my own blog, including:
site positioning
About page
Person schema
Article schema
llms.txt
robots.txt
sitemap
pillar pages
internal links
page descriptions
Bing Webmaster Tools
IndexNow direction
These experiences did not come from imagination. They came from modifying my own website step by step.
So there is a natural productization path:
Input a personal website URL
→ Check sitemap / robots / llms.txt
→ Check About page and author entity
→ Check schema structured data
→ Check page titles and descriptions
→ Check pillar pages and internal links
→ Output a GEO optimization report
The target users are also relatively clear:
indie hackers
AI creators
personal bloggers
Substack writers
knowledge product sellers
people who want AI systems to better understand their websites
It does not have to charge money from day one. The first version can be a free audit tool used to validate demand, collect cases, and attract similar users.
If the direction proves useful, it can later become templates, reports, consulting services, or a more complete SaaS product.
My staged roadmap
My current path is not to go all in on one product. It is more about gradually building cash flow and personal assets.
I see three stages.
Stage 1: validate cash flow with ebooks
Ebooks already bring small but real revenue, so they are the most worthwhile direction to continue investing in.
The next focus is not blindly writing more, but improving topic selection, production efficiency, content quality, and listing conversion.
Stage 2: build traffic and trust through content channels
Blog, Xiaohongshu, WeChat, Substack, and YouTube are all long-term traffic assets.
They may not produce obvious short-term revenue, but over time they can help me promote ebooks, tools, and future products.
Stage 3: extract software products from real workflows
After content, cash flow, and real needs become clearer, building software will be more stable.
I will not build SaaS just for the sake of building SaaS. I will extract tools from my real pain points: ebook production systems, KDP review tools, GEO optimization tools, content distribution tools, Chrome extensions, and similar products.
What role AI plays here
AI does not start the business for me, and it does not automatically make money for me.
AI is more like an amplifier.
It helps me reduce the cost of trial and error, increase production speed, and expand the range of tasks one person can handle.
For ebooks, AI can help with topic selection, outlines, rewriting, covers, publishing, and ad keywords.
For blogs, AI can help with SEO / GEO analysis, structured data, page rewriting, and internal link suggestions.
For products, AI can help write code, generate plans, debug, and test.
For content, AI can help organize materials, generate outlines, rewrite expression, and support multi-platform distribution.
But the most important things still require human judgment:
what topic to choose
whose problem to solve
whether the product is worth building
why users would pay
whether the content is genuinely useful
whether the direction is worth long-term commitment
FAQ
What is AI indie hacking?
AI indie hacking means using AI, automation tools, and internet distribution to build products, content systems, and small businesses with one person or a very small team. It is not passive income by default. It is using AI to amplify personal capability and reduce the cost of experimentation.
Why am I doing AI indie hacking?
The real reason is that I do not want to rely only on salary for the long term. I want to externalize my technical skills, investing experience, writing ability, and product ideas into ebooks, tools, content systems, or SaaS products, gradually forming income sources that are not completely salary-dependent.
What is the most important project right now?
The most important project right now is ebooks, because they are the only project that has already brought me real revenue. The income is still small, but it proves that the knowledge product path may work.
Why not build SaaS directly?
Because SaaS is not only a development problem. It also involves acquisition, demand validation, payment conversion, and ongoing maintenance. Instead of building a large SaaS directly, I prefer to extract small tools from my own real workflow, use them myself first, and then validate whether others are willing to use and pay.
What software experiment do I want to try next?
I may start with a GEO optimization tool. I recently optimized my own blog for GEO / SEO, and that experience can be productized into a website audit tool that helps indie hackers, AI creators, and personal bloggers check whether their websites are easy for search engines and AI assistants to understand.