I was on the MRT from Woodlands to City Hall — laptop open, AirPods in — and I was building the official ANCHR AI Labs website. Not writing a brief for a developer. Not adding it to the “someday” list. Actually building, in real time, in stolen pockets of a chaotic travel day. By the next morning, it was live.
Full website, migrated from Lovable, done in under 24 hours. In the spirit of building in public — here is exactly what happened, the honest version.
There is this unspoken rule we have all absorbed: building something real takes time. Weeks of back-and-forth with developers, rounds of revisions, mood boards nobody ends up using, and a Notion doc that quietly grows to 47 pages before anyone admits it has gotten out of hand.
I used to accept all of this as just the cost of doing things properly — the tax you pay for wanting something good. But here is the question that has been sitting with me: what if the bottleneck was never the building? What if it was always the knowing — being clear enough about what you wanted to actually get it done?
I had started this project on Lovable. It was functional, decent enough. But the vision in my head was sharper than what was on screen, and that gap kept nagging at me. So I made the call to migrate everything and start fresh with Claude Co-Work — and what sounded like a massive undertaking on paper took a few focused hours and one very productive MRT ride.
I want to share the real process. Not the cleaned-up highlight reel. The messy middle is where the actual lesson lives.
I started on the train. Forty minutes, unstable balance, laptop open. I described what I wanted in Claude Co-Work and started directing the build. I want to be really clear that directing is the right word, because I was not coding anything. Think of it like briefing a contractor when renovating your flat: you do not need to know how to lay tiles, you just need to know what you want the space to feel like.
Then the train arrived. The laptop closed. The day moved on.
Later that night I picked it back up, refined the layout, pushed the design closer to what I had in my head — and then hit Claude’s usage limits. This happened not once but multiple times across the build. Each time, I waited, came back, and kept going, because the vision was clear enough that I always knew exactly where to pick up.
“The vision was clear enough that I always knew exactly where to pick up.”
By the next morning, the ANCHR AI Labs website was live. Migrated, designed, done. I am not a developer. I do not write code. I could not tell you what is happening under the hood of these tools. And none of that mattered.
The AI conversation tends to swing between breathless panic about robots replacing everyone and shallow listicles about saving twenty minutes on your emails. What I actually want to talk about is something more fundamental — especially for people who have always assumed that building things was someone else’s job.
You do not need to know how to build. You need to know what to build — and how to direct AI to execute it.
When I was working on this site, my brain was not occupied with anything technical. I was thinking about what the page needed to communicate in the first three seconds, what feeling I wanted people to walk away with, and where the most important information needed to live. These are not technical questions. They are human questions. Clarity questions. The kind anyone who has ever tried to communicate something well already knows how to ask.
The part AI cannot do for you is the vision. It can build fast, iterate quickly, and execute with precision — but it needs you to be clear about the destination. That clarity, not coding ability or technical fluency, is the actual skill that determines whether you ship something good or spin in circles.
I run AI training for corporate teams across Singapore and Malaysia — people in sales, marketing, HR, and leadership who are sharp, experienced, and have spent years being told that tech is not their lane.
What I keep seeing, again and again, is that the people who get the most out of AI tools are not the most technical people in the room. They are the clearest. They know what they want. They can describe the gap between where they are and where they need to be. They give direction well enough for AI to run with it — and that is just good communication, which is something you have probably been doing your whole career.
You are not missing a technical skill. You are missing the confidence to start. So consider this your permission.
When a task that used to take weeks now takes hours, the question stops being “cool, we saved time.” It becomes something bigger — what do we do with everything we get back?
For me, the ANCHR AI Labs website is one piece of a much larger picture: the platform, the training programmes, the content, the community. Every hour I get back from execution is an hour I can redirect into strategy, into the people I am building for, into thinking harder about what comes next. That is the real win. Not the website. The reclaimed space to think and build bigger.
Speed used to be the advantage. Now speed is table stakes. Clarity is the edge.
In the spirit of building in public, this is me showing you it is possible. Not because I am technical, but because I got clear. Start there, and the tools will do the rest.
Want to learn how to use Claude Co-Work to build your own workflows? Come to one of our workshops: Claude Cowork Workshop Singapore. Or join our community of non-technical professionals already doing this: WhatsApp Group.