The 52 Hours That Built a Website
— and What It Taught Me About Sourcing

In late February, I spent roughly 52 hours building TradeFusion's official website from scratch.

That's not a long time, but the process was far from short.

What I want to share is not a technical tutorial on "how to build a website" — because I know almost nothing about the technical side at that time. What I want to share is that this experience reaffirmed something I now see in sourcing work as well: the most time-consuming and important part of any project is often not "how to do it," but "what exactly are we doing?"

Whether it's a website or a sourcing project, the principle is the same.

1. Where Did Those 52 Hours Actually Go?

If I break it down, it looked roughly like this:

Content & copywriting: about 20–25 hours

This was the most demanding and time-consuming part. I needed to get clear on:

• Who am I? Who do I serve?
• What problem does my service solve?
• Why should a client trust me?

These questions sound simple, but translating them into clear, professional, honest language — language that a stranger can understand and trust — is harder than it seems.

I revised countless times. Sometimes a sentence felt too boastful; other times it felt too vague. Every page, every paragraph, every sentence was reworked over and over.

Image selection: about 6–8 hours

Once the text was set, I needed visuals that matched. To avoid copyright issues, I carefully confirmed what I could use — Unsplash's free library, my own photos, and commercially licensed options. It often took dozens of candidates to settle on one image.

Code generation and layout tweaks: about 12–14 hours

With content and images ready, I used AI tools to generate the HTML code. Then came endless rounds of adjustments: font sizes, spacing, alignment, mobile responsiveness — tweak, preview, repeat, until every page looked right.

Server deployment: about 8–10 hours

This was the most frustrating part. I know next to nothing about IT — domain resolution, DNS settings, file uploads, debugging error messages. What a professional could finish in 15 minutes was a major hurdle for me at every step. I had to look up concepts one by one, ask questions, try, fail, try again — and eventually, it went live.

2. An Unexpected Realization: Content Is the Real Core

After finishing this project, one thing became very clear to me:

If content is the skeleton, technology is just the clothing.

In other words: if you know what you want to say, who you're saying it to, and why, then the execution — code, layout, images — can actually move fast, especially with AI tools that can generate code for you.

But if your thinking is vague — if you're unsure what you're trying to convey — then no amount of technical skill or fancy tools will save you. The result will be hollow.

Content first. Form follows. Clarify before you act.

It sounds simple, but I only truly understood it after living through the process.

3. What Does This Have to Do with Sourcing?

As I reflected on this experience, I realized: building a website and sourcing products from China are essentially the same thing — turning a fuzzy need into a clear set of instructions.

In sourcing, we often hear things like: "I need a portable power station." But beneath that simple request lie many unspoken questions:

• Is it for home use or camping?
• What power output is required?
• Which certifications are needed for the European market?
• What languages should the App support?
• Should it be OEM with the buyer's brand or the manufacturer's own brand?

If you don't ask these questions — if you don't help the client unpack their vague request into a concrete checklist — you'll struggle to find the right match among thousands of Chinese factories.

Just like building my website: if I hadn't spent those 20+ hours refining the copy first, all the later work on images, layout, and code would have been built on quicksand.

4. My Working Method: Draw the Map Before You Hit the Road

With this lesson in mind, I now deliberately slow down at the start of any sourcing project.

Instead of rushing to search for suppliers the moment I receive a request, I first have an in-depth conversation with the client — usually via video call — to clarify these key points:

1. Who is the end user?
2. What are the core functions? (Must-haves vs. nice-to-haves)
3. What certifications are required for the target market?
4. Does installation or use require professional support?
5. What is the client's long-term goal? (A one-off purchase or an ongoing partnership?)

Once these are clear, I create a written requirements document. That document becomes my map — it gives direction and criteria for every subsequent step, so I'm not just browsing aimlessly from one factory to another.

5. What This Taught Me

Launching the website reinforced one principle I now carry into everything I do:

"Fast" isn't the first step. "Right" is.

Taking the time to think clearly, refine the content, and set the right direction upfront makes everything that follows smoother and more efficient.

If you cut corners at the "requirements" stage, all later efforts — whether building a website or finding a supplier — will come back to cost you many times over.

So now, when a client says, "I need to source this product," my first reply isn't "OK, I'll start looking right away." It's:

"Let's schedule a proper conversation first — and really get clear on what you actually need."

It may look like slowing things down. But in reality, it's how I save time for both of us.