Dev.to AI ๐Ÿค– Ai ๐Ÿ‘ 0 ๐Ÿ“– 3 min read

I Built a Zero-Budget AI Copywriting Toolbox for Small E-commerce Sellers

Small e-commerce sellers wear too many hats. They source products, answer customers, pack orders, and still have to write product titles, detail pages, customer-service replies, and social posts. Most of them are not cop

Small e-commerce sellers wear too many hats. They source products, answer customers, pack orders, and still have to write product titles, detail pages, customer-service replies, and social posts. Most of them are not copywriters, and hiring one is expensive.

I wanted to see how far I could get with a simple idea: a free AI copywriting toolbox that a store owner can use without signing up, without installing anything, and without paying for a subscription.

So I built ๅฐ็”Ÿๆ„ AI ๅทฅๅ…ท็ฎฑ (Small Business AI Toolbox), a Chinese-language toolkit with eight generators:

  • Xiaohongshu (RED) note writer
  • Taobao product-title generator
  • Customer-service scripts
  • Negative-review replies
  • Shop-name generator
  • WeChat Moments copy
  • Product detail-page copy
  • Short-video scripts

The interface is deliberately boring: choose a tool, describe the product, click generate, copy the result. Five free generations per IP per day, with a global daily cap to keep the API bill under control.

The stack is intentionally small

I did not want a framework or a database for the first version. The whole app is:

  • A single Node.js HTTP server (no Express, no build step)
  • A static HTML/CSS/JS frontend
  • A local API gateway that routes requests to a chat model
  • A Python script that builds SEO article pages and a downloadable PDF
  • Surge for static hosting

The production URL is xiaoshengyi-toolbox.surge.sh. The Node server handles generation and lead capture; the static site handles the landing pages and tools.

Why this stack? Because the goal was to validate demand, not to build a startup. Every extra dependency would have slowed down the first release.

What I learned

1. A narrow tool beats a general assistant.

A generic chat box is intimidating for a shop owner. "Write a Xiaohongshu note for a 260g cotton hoodie, three colors, 59 yuan" is immediately useful. The constraint is the product.

2. Free needs a hard boundary.

Without a daily cap, one crawler or one curious user can burn through the API budget. I added a per-IP daily limit and a global daily limit. It is not elegant, but it keeps the service alive.

3. Distribution is harder than the code.

The app took a weekend. Getting anyone to see it took much longer. I submitted it to free directories, wrote long-tail articles, and built a small static site with tool pages. The first external referral came from a directory listing, not from a search engine.

4. Do not promise what you cannot deliver.

The first version had a "9.9 yuan per month" plan. I removed it because there was no automated payment callback or account system. Now the tools are free, and the paid service is a human-assisted AI customer-service setup with a three-day free trial. It is better to under-promise and keep the promise.

5. Content is part of the product.

Every tool has a matching article: how to write Taobao titles, how to reply to negative reviews, how to name a shop. The article explains the job; the tool does the job. Together they are more useful than either alone.

What I would do next

  • Add a simple account system so users can save their favorite prompts
  • Add output history and one-click export
  • Test more distribution channels that do not require a phone number or a company account
  • Measure which tools people actually use, not just which pages get pageviews

If you run a small store, try the toolbox and tell me which tool is missing. If you are building something similar, I would love to compare notes on distribution.

Try it: https://xiaoshengyi-toolbox.surge.sh/

Free PDF with 100 copywriting templates: https://xiaoshengyi-toolbox.surge.sh/dl/็”ตๅ•†ๆ–‡ๆกˆๆจกๆฟ100ๆก.pdf

๐Ÿ“ฐ Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes โ€” full credit and traffic to the original publisher.