Build in Public: The Fastest Way to Launch a Solo Company — AgentClaw's 4-Hour Launch Playbook
From buying a domain to 55 articles live — 4 hours of work achieving what would traditionally cost $2,200 and two weeks. The Build in Public philosophy and practical how-to guide.
Have you ever had this thought: I'll launch when the product is perfect? I'll go live when the website looks beautiful? I'll start promoting when I have enough articles?
If your answer is "yes," you might be trapped in perfectionism. Too many aspiring solo entrepreneurs talk about it for a year, bookmark hundreds of articles, buy several courses — but never take the first step.
Build in Public has the opposite philosophy: share your project and process openly, don't wait until it's perfect. Start sharing from Day 1. Go live from Day 1.
This article documents my AgentClaw project's journey from buying a domain to launching 55 articles, 1,992 product data records, and a complete operations system — all in just 4 hours.
Why Build in Public Works for Solo Entrepreneurs
For solo companies, Build in Public has three direct benefits.
First, it forces action. When you publicly commit to a project, you create accountability. With eyes on you, you'll feel more motivated to keep moving forward.
Second, it attracts like-minded people. Publishing your data and experiences attracts others doing similar work. They could become your users, collaborators, or first loyal readers.
Third, it creates content itself. The process and story of your Build in Public journey is worth writing about. This very article — about a 4-hour launch — is both a record and part of the website's content.
Five Core Principles of Build in Public
Principle one: Start from Day 1. Don't wait until the product is perfect. As soon as you register a domain and publish your first page, start sharing. You can update along the way.
Principle two: Share real numbers. Revenue, traffic, user feedback — real numbers are more compelling than anything else. You don't need to share specific numbers you're uncomfortable with, but stay transparent.
Principle three: Share the process as much as the results. People don't just want to see your success — they want to see how you got there. The journey and lessons are more valuable to learn from than the final outcome.
Principle four: Embrace imperfection. Your site might not be perfect. Your articles might not be good enough. That's okay. Build in Public is literally "under construction" — users understand you're growing.
Principle five: Document consistently. Establish a simple recording habit. Share progress every week or two. Not everyone will follow every step, but consistent documentation builds a valuable archive.
AgentClaw Day 1: Complete Record
11:00 AM — Buy the domain. Opened Alibaba Cloud, bought agentclaw.sale. Why .sale? Cheap — 45 yuan per year. Domain registration took 5 minutes. This was the day's only expense — and the only expense so far.
11:05 AM — Build the site. Used a starter template with basic page structure, SEO config (next-seo, next-sitemap), Tailwind CSS, and article reading logic. Cloned locally, changed site name and basic info, initialized a Git repo. The template is tiny — under 200 lines of core code.
11:20 AM — Deploy to Vercel. Opened Vercel, clicked New Project, imported the GitHub repo, waited for build. Build completed in under 20 seconds. Added a CNAME record pointing the domain to Vercel.
11:25 AM — Register AdSense and CPS affiliates. Submitted AdSense for review. Also registered on Taobao Alliance and JD Alliance. Register first, configure later.
11:30 AM — Start batch-generating articles. Activated previously prepared keyword research and content templates. 55 articles covering sports suit buying guides, brand comparisons, scenario recommendations, fabric education, size selection, care tips, price analysis, etc. Each ~3000 words. AI generation plus formatting: about 2 hours.
1:30 PM — Import articles to GitHub. Each article as an MDX file. Batch processing script auto-formatted AI content. Git push. Vercel auto-detected the new commit — 30 seconds later, all 55 articles went live.
2:00 PM — Process product data. Previously collected Taobao and JD sports suit product data was in CSV files. Integrated into the site's data pages showing price distribution, fabric statistics, sales rankings. Also imported into Feishu's multidimensional tables as baseline operational data. About 1 hour.
3:00 PM — Build Feishu operations system. Created a new Feishu table with fields for article ID, title, target keyword, status, publish link. Imported all article metadata. Also imported product data into another view, linked with articles.
3:30 PM — Final check. Browsed the entire site. Checked page loading, link validity, image loading, SEO configuration. Submitted sitemap to Google Search Console.
From 11 AM to 4 PM, actual work time: 4 hours. Output: 55 articles, 62 pages, 1,992 product data records, AdSense and CPS affiliate registrations submitted, Feishu operations system established.
What Would 4 Hours Achieve With Traditional Methods?
The traditional cost for similar output: 55 articles from professional writers at $28 each ($1,540 total), minimum one week. Website development outsourced: $280 to $700, one week. Product data analysis: around $280, several days. Feishu system setup: $140. Total: at least $2,200 and two weeks or more.
I did it in 4 hours for 45 yuan ($6). The gap comes from three factors: AI tools drastically reduce content production costs; Vercel and GitHub make deployment incredibly simple; free SaaS tools like Feishu replace systems that previously needed custom building.
How to Start Your Own Build in Public
Choose a platform. Twitter (X) is the most popular Build in Public platform globally. For Chinese audiences, use Jike (即刻), Xiaohongshu, or your own blog. Pick one you're comfortable with.
Set your sharing frequency. You don't need daily updates. Weekly or bi-weekly progress updates are sufficient. Consistency matters more than frequency.
Decide what to share. Your data (traffic, revenue, user counts), your experience (what worked, what failed), and your learnings (new techniques, tools, strategies discovered).
Build a feedback loop. The value of public sharing lies in getting feedback. Take every comment and message seriously. These could be important clues for product improvement.
Ongoing Operations: Not a One-Day Thing
Day 1's 4-hour launch was just the start. In the following two weeks, I added 20 more articles. After one month, total articles reached ~100. Now total articles are 255.
Daily operations is just a Feishu table + a git push. The Build in Public documentation continues. And these shared stories themselves keep bringing traffic and building trust for the site.
FAQ
Q: Is Build in Public suitable for all types of solo businesses? A: For most, yes. If your business serves high-end clients or involves trade secrets, you may need selective sharing. But most solo companies can benefit.
Q: What if my data looks bad — should I still share? A: Honesty is more compelling than perfection. Share your real numbers and journey, including failures and setbacks. These often get the most engagement.
Q: Which platform is best for Build in Public? A: Depends on your audience. For global audiences, Twitter (X). For Chinese audiences, Jike, Xiaohongshu, or your own blog. Pick one you'll actually use.
Q: Do I need to update daily? A: No. Weekly or bi-weekly is sufficient. Quality matters more than frequency. Consistency is the real key.
Q: Will Build in Public leak business secrets? A: Share methodology and experience, not core algorithms or customer data. Just maintain clear boundaries.
Q: What if nobody pays attention to my Build in Public? A: That's normal. Few people will notice at first. Keep sharing consistently, and people will gradually take notice. The key is to start sharing first, not to wait for an audience.
Summary
Build in Public isn't a marketing strategy — it's a way of working. It minimizes the gap between having an idea and taking action.
Don't wait until your site is perfect to launch. Don't wait until you have 100 articles to promote. Buy a domain, set up a template, write a few articles, and go live. User feedback and data will help you adjust direction along the way.
AgentClaw's Day 1 data says it all: 4 hours total, $6 in costs, 55 articles, 62 pages, 1,992 product data records. This is the real speed of a solo company in the AI era.
If you're still hesitating about starting a project, try the Build in Public approach. Buy a domain today, set up a website, write one article, and publicly share your progress. You'll find that starting is far easier — and far more effective — than waiting for perfection.