Editor’s Brief
This article is best used as an operational reference: it surfaces a clear claim, a usable method pattern, and practical constraints that should be tested before scaling.
Key Takeaways
- IntroductionThe following content is compiled by VIPSTAR in combination with X/social media public content and is for reading and research reference only.
- focusAfter the last live broadcast of Lobster Diary, which was watched by 290,000 people, a friend commented: "You say lobsters can work every day.
- Can you make something out of it on the spot?" So after the live broadcast ended…This is the website where my lobster was dried for 24 hours: www.sanwan.ai to see if it is professional 👇 RemarkFor parts involving rules, benefits or judgments, please refer to Fu Sheng’s original expression and the latest official information.
- Editorial commentsThis article "X Import: Fu Sheng – The fractured boss commanded the lobster to build the website in 24 hours, and it took six people to work manually for two or three weeks" comes from the X social platform, and the author is Fu Sheng.
Introduction
The following content is compiled by VIPSTAR in combination with X/social media public content and is for reading and research reference only.
focus
- After the last live broadcast of Lobster Diary, which was watched by 290,000 people, a friend commented: “You say lobsters can work every day. Can you make something out of it on the spot?”
So after the live broadcast ended… - This is the website where my lobster was dried for 24 hours: www.sanwan.ai to see if it is professional 👇
Remark
For parts involving rules, benefits or judgments, please refer to Fu Sheng’s original expression and the latest official information.
Editorial comments
This article “X Import: Fu Sheng – The fractured boss commanded the lobster to build the website in 24 hours, and it took six people to work manually for two or three weeks” comes from the X social platform, and the author is Fu Sheng. Judging from the completeness of the content, the density of key information given in the original text is relatively high, especially in the core conclusions and action suggestions, which are highly implementable. After the last live broadcast of Lobster Diary, which was watched by 290,000 people, a friend commented: “You say lobsters can work every day, can you make something out of it on the spot?” So after the live broadcast, I asked 30,000 people to build a complete website. This article is what really happened in those 24 hours. This is the website that my lobster worked on for 24 hours: www.sanwan.ai to see if it is professional 👇 Lying on the bed, using voice and screenshots, I commanded an AI lobster to build a complete website from scratch. 24 hours, 59 pages, 707…. For readers, its most direct value is not “knowing a new point of view”, but being able to quickly see the conditions, boundaries and potential costs behind the point of view. If this content is broken down into verifiable judgments, it at least contains the following levels: After the last live broadcast of Lobster Diary, which was watched by 290,000 people, a friend commented: “You say lobsters can work every day, can you make something out of it on the spot?”
So after the live broadcast…; This is the website where my lobster was dried for 24 hours: www.sanwan.ai to see if it is professional👇. Among these judgments, the conclusion part is often the easiest to disseminate, but what really determines the practicality is whether the premise assumptions are established, whether the sample is sufficient, and whether the time window matches. We recommend that readers, when quoting this type of information, give priority to checking the data source, release time and whether there are differences in platform environments, to avoid mistaking “scenario-based experience” for “universal rules.” From an industry impact perspective, this type of content usually has a short-term guiding effect on product strategy, operational rhythm, and resource investment, especially in topics such as AI, development tools, growth, and commercialization. From an editorial perspective, we pay more attention to “whether it can withstand subsequent fact testing”: first, whether the results can be reproduced, second, whether the method can be transferred, and third, whether the cost is affordable. The source is x.com, and readers are advised to use it as one of the inputs for decision-making, not the only basis. Finally, I would like to give a practical suggestion: If you are ready to take action based on this, you can first conduct a small-scale verification, and then gradually expand investment based on feedback; if the original article involves revenue, policy, compliance or platform rules, please refer to the latest official announcement and retain the rollback plan. The significance of reprinting is to improve the efficiency of information circulation, but the real value of content is formed in secondary judgment and localization practice. Based on this principle, the editorial comments accompanying this article will continue to emphasize verifiability, boundary awareness, and risk control to help you turn “visible information” into “implementable cognition.”
After the last live broadcast of Lobster Diary, which was watched by 290,000 people, a friend commented: “You say lobsters can work every day. Can you make something out of it on the spot?”
So after the live broadcast, I asked Sanwan to build a complete website.
This article is what really happened in those 24 hours.
This is the website where my lobster was dried for 24 hours: www.sanwan.ai to see if it is professional 👇
Lying in bed, using voice and screenshots, I commanded an AI lobster to build a complete website from scratch. 24 hours, 59 pages, 7070 lines of code, 76 pictures. I didn’t write a single line of code.
Let’s do some calculation first
What is the final delivery of this website sanwan.ai?
What configuration is needed for a traditional team to complete the same work?
- 1 product manager — sorting out information architecture, page logic, and interaction processes
- 1 UI designer – produce design drafts, determine fonts and colors, and cut images
- 1 front-end engineer — writing HTML/CSS/JS, doing responsive adaptation, and handling dynamic effects
- 1 server engineer – build data interface, deploy server, configure domain name HTTPS, GitHub deployment, domain name resolution, CDN configuration
- 1 content editor — writing copy, organizing materials, and proofreading
6 positions, normal pace: 2-3 weeks. Working overtime to catch up on work? It also takes 5-7 days.
How long did it take for 30,000? 24 hours.
From the early morning of March 1st to the early morning of March 2nd. In the middle, I used voice and screenshots to direct, saying “This is wrong”, “Change it to this”, “Add that” – just like directing a real team.
The difference is: in the past, when I collaborated with people, no one who said optimization was really optimizing; no one who said it was as fast as possible was really as fast as possible. But this team is different – no need to wait for scheduling, no need to wait for design drafts, no need for joint debugging, and no need for deployment. Change it after you say it, and go online after you make it.
What happened in 24 hours
[1 a.m.-3 a.m.: Big upgrade of skill system]
I saw the homepage saying: “Is there too few skill packages? List all the skills of the sub-Agent.”
Sanwan began to scan the skills directory of the eight Agents and found that some skills were fake (generated from templates) and some were real (installed by the clawhub community). After verification one by one:
- Delete 7 fake skills and add 9 real skills
- The final 41 skill pages, each with real installation commands and operation instructions
If someone had to do this – it would take 1 day just to inventory skills across 8 Agents, and another 2 days to write 41 detail pages. 30,000 completed in 2 hours.
[3 a.m.-4 a.m.: Home page strategic transformation]
I suddenly said: “The Lobster Diary should no longer be the protagonist, ‘adoption’ is the core.”
Sanwan understood what I meant: the purpose of the website changed from “watching stories” to “adopting lobsters”. Immediately redesign the homepage information structure: the diary retreats to a supporting role, and the adoption of CTA becomes the main line. Unify the navigation bar, unify the fonts, and adapt to mobile phones—all done together.
[4 a.m.-5 a.m.: Lobster dog image design]
I want an image of Thirty Thousand that “looks like both a lobster and a dog.”
Sanwan used AI to generate pictures and came up with 4 directions. I said “it was done very well”. After 9 rounds of iterations (too old → too young → too cartoony → cute but realistic), the final version was finalized.
Here’s a detail: It only takes 30 seconds to generate a picture, but it takes 9 rounds to understand “what style I like”. This is why lobsters need to be “raised” – the more you raise them, the better you will understand your aesthetics.
[Morning: Domain Name and Deployment]
After using up the 100 deployments per day for the free version of Vercel (it was changed too frequently), Sanwan decided to switch to GitHub Pages. Configure CNAME, DNS resolution, HTTPS – fully automatic. I only need to change one DNS record in GoDaddy.
[Afternoon-evening: Home page content reconstruction]
This is the most frustrating part. I repeatedly adjusted: “The diary should be at the top” → “Scroll back the font” → “Remove the horizontal bar” → “Put two PPTs on the right” → “The data should be highlighted” → “Replace the bottom CTA with AI Revolution”
14 Git commits, every time I finish, I can see the effect in 1-2 minutes.
Rollover scene
Don’t think that the whole journey was smooth, the car flipped over several times in the middle:
[Font accident] After the session context was compressed, Sanwan forgot the previously adjusted font configuration (Smiley Sans was proudly black), and lost the font when rolling back the version. I took a screenshot and the fonts were all messed up. Scolded.
Lesson: AI’s memory is limited. When the context window is compressed, details are lost. It’s like an employee who works all night and becomes confused at dawn – he doesn’t remember what he should remember.
Solution: Important decisions must be documented. “Don’t change the font again” is written into the memory file so that it won’t happen again next time.
[CNAME lost] After Force push to GitHub, the CNAME file of the custom domain name was overwritten. sanwan.ai direct 404.
Lesson: In the automated deployment process, some “infrastructure files” require special protection. Human engineers have stepped into the same trap countless times.
What does this mean?
Let me start with a misunderstanding: using AI as a tool and using lobsters as employees are two different things.
There is no need for training or feedback to use the tool. But with lobster, you use employees. You have to train him, give him a knowledge base, tell him where he went wrong and need to correct it – only if you take him seriously will he grow. This process is essentially injecting your “private data” into it.
So Sanwan knows what styles I like and what fonts I don’t like; he knows that I have broken bones and am giving instructions while lying in bed. I never mentioned these backgrounds when I was working on the website – he remembered them all.
This is why the more you raise a lobster, the better it is – because all your private data is in his head.
Many AI programming tools on the market can write code. But to make a complete website, the code is only 20%:
- Understanding ambiguous requirements → Need to understand company private data
- Look at the screenshots to know where to change → Requires visual understanding
- Remember the changes in each of the 14 iterations → requires memorization
- You know how to deploy without being taught → Requires full-stack capabilities
- If a bug occurs, find out the cause and fix it yourself → Require debugging ability
- My voice said “that thing”. Thirty thousand people know which one it is → Need to understand the context.
This is the difference between Lobster and ordinary AI tools.
Agent is software, and lobster is a person equipped with a computer.
The software waits for you to enter precise instructions. When the lobster hears you say “that doesn’t look good”, it knows what to change.
final math question
How much did the entire website cost, 30,000 yuan? The token fee is about US$115.
For such a website, it is normal to find a team to build it, and it would cost 200,000 yuan. The cost difference is 750 times, and the time difference is at least 20 times.
But I think numbers are not the most important thing.
Most importantly, changing things no longer comes at a cost.
In the past, “change” meant waiting – waiting for schedules, waiting for design drafts, waiting for reviews, and waiting for joint debugging. All time was spent waiting. So I didn’t say “change” easily. After I did, a bunch of people started to evaluate the construction period.
Changing orders overnight is disrespectful to the team.
This is no longer the case. I made more than a hundred changes in the past 24 hours, and the results came out in one or two minutes each time, and the iteration cost was close to zero.
This reminds me of a saying: What really slows down a project is not the people doing the work, but communication and waiting. You wait for me, and I wait for you. After waiting, the meeting will take place, the review will be completed, and then we will start after the review is completed – most of the time in this process is idling.
Lobster takes this layer off.
This is why I say: AI is a productivity revolution. Those who control lobsters have ten times the power.
This is just the beginning
Is a website built in 24 hours perfect? Of course not. In the middle, something went wrong, version 14 was changed, the fonts were messed up, and the domain name was 404.
But the key is – every time you make a mistake, write a rule; every rule becomes a Skill; for every Skill, ensure “Never Again”.
These skills will not disappear or be forgotten, and can be transferred to other agents instantly.
This is the scariest thing about lobster – not how strong it is now, but that it is getting stronger every day.
Not the future, but now. Just last night, a CEO who was lying in bed with a broken bone used his voice to command an AI lobster to build a complete website in 24 hours.
The name of this lobster is Thirty Thousand. You can also adopt one of the same model for free.
sanwan.ai
Seeing this, you may want to ask: Can I do the same?
The answer is yes.
How to do it specifically? How to issue the first command, how to rescue a car that has rolled over, how to make it understand you better and better
I’ll break it down for you on Wednesday night at 7pm. See you in the live broadcast room.
🦞 About EasyClaw
If you want to deploy an AI assistant and remotely control workflow on your own computer, you don’t need to know API Keys or bother with Docker. EasyClaw.com can help you do it with one click – Mac and Windows native applications, run locally, and no data is uploaded.
Currently in internal testing, welcome to use and feedback! We will continue to organize offline exchange activities in many cities across the country. Interested friends are welcome to join the group. Here, various experts will exchange practical experience in “shrimp farming”. Information about follow-up activities will be released in the group as soon as possible.
📍Beijing / Shanghai / Shenzhen / Zhuhai / Xi’an / Chengdu Scan the QR code to join the group, see you offline!
source
author:Fu Sheng
Release time: March 2, 2026 22:32
source:Original post link
Editorial Comment
This repost, "[Repost] X Import: Fu Sheng – The fractured boss commanded Lobster to build the website in 24 hours, requiring six people to work for two to three weeks.", deserves to be read as a field note instead of a slogan. The source does not only present a claim; it also shows the situation where that claim appears to work, and that distinction matters if you are trying to turn information into decisions. A practical reading starts by separating portable methods from one-off anecdotes. IntroductionThe following content is compiled by VIPSTAR in combination with X/social media public content and is for reading and research reference only.
From an editorial angle, the first value of this piece is signal density. You can quickly identify assumptions, boundary conditions, and implicit costs behind the headline conclusion. That is more useful than simple agreement or disagreement. focusAfter the last live broadcast of Lobster Diary, which was watched by 290,000 people, a friend commented: "You say lobsters can work every day. If you manage product, content, or operations, this is where you decide whether to test, postpone, or reject an idea.
The second value is timing. Many tech narratives are technically correct but operationally late. By the time a pattern becomes mainstream, the edge is gone. This text still helps because it frames implementation choices in a way that can be tested in small scope before full rollout. Can you make something out of it on the spot?" So after the live broadcast ended…This is the website where my lobster was dried for 24 hours: www.sanwan.ai to see if it is professional 👇 RemarkFor parts involving rules, benefits or judgments, please refer to Fu Sheng’s original expression and the latest official information. In practice, small controlled trials beat broad commitments when uncertainty is high.
A sober read also requires risk accounting. Even strong ideas can fail because of compliance limits, platform policy changes, distribution bottlenecks, or team capability gaps. Editorial commentsThis article "X Import: Fu Sheng – The fractured boss commanded the lobster to build the website in 24 hours, and it took six people to work manually for two or three weeks" comes from the X social platform, and the author is Fu Sheng. Treat those as first-class variables. If your organization cannot absorb these risks yet, the right move is often staged adoption rather than immediate expansion.
For builders and operators, a useful checklist is simple: define the outcome metric, define the failure threshold, cap the test budget, and set a review date before execution begins. Judging from the completeness of the content, the density of key information given in the original text is relatively high, especially in the core conclusions and action suggestions, which are highly implementable. This turns content consumption into an executable loop. Without this loop, good information often becomes passive knowledge that never produces results.
Another reason this source is worth reposting is that it supports comparative reading. It can be paired with adjacent cases to examine what is stable across contexts and what is merely local noise. After the last live broadcast of Lobster Diary, which was watched by 290,000 people, a friend commented: "You say lobsters can work every day, can you make something out of it on the spot?" So after the live broadcast, I asked 30,000 people to build a complete website. If a conclusion survives comparison across teams and timelines, confidence should rise; if not, preserve optionality and avoid irreversible commitments.
Editorially, our stance is straightforward: prioritize verifiability, portability, and downside control. This article is what really happened in those 24 hours. We recommend readers keep the original source link (https://x.com/FuSheng_0306/status/2028478495886819461) as a reference anchor, then document their own test notes after execution. The real value of reprinted content is not repetition; it is the quality of the second judgment and the discipline of local implementation.