I’ve been quietly working on an idea that I’m very excited about. It’s an initiative that will bring more of 60 Decibels data to life and will make this data—and the lived experience of the people it represents—more useful to more people.
The basic concept is that AI is being trained on data from a narrow slice of humanity. The voices of billions are missing.
This initiative, called The Global Majority Data Project, will build the infrastructure to make the lived experiences of the world’s most underserved communities both vivid and accessible, so that these experience can influence how decisions are made.
I’m in the early stages of fundraising for this work, and I’ve been talking about it with folks I know in the AI for good space.
After a few great conversations last week, the thought occurred to me: a nice website for this initiative would help move it forward.
But who has time to build a website? Certainly not me (time, or know-how).
And then I thought about the AI Hackathon we’re doing this Friday at 60 Decibels and realized it was time to eat my own cooking.
I had the idea for the website at the end of the day on Friday.
On Saturday, I sat down at noon with Claude CoWork.
At 3pm the site was live.
This is a massive step change in leverage for me (and it could be for you).
What I had on hand at noon was a whitepaper describing the project and existing branding from 60 Decibels.
Three hours of conversation with Claude (including a decent amount of waiting, because it was ‘thinking,’ so I cleaned up the kitchen) to make a high-quality website.
Think of what else it can do.
For those of you who have been using these tools, this is not a surprising outcome. For those who haven’t, I hope this serves as a concrete example of what is now possible.
Normally I’d end the post here, but I thought some specificity would help.
If you’d like to read on, here’s a detailed summary of what I told Claude and how the whole process unfolded.
I hope you’ll take this as inspiration to go build something meaningful.
And if you have ideas for folks who might want to make this idea come to life, please send them my way! (the contact form is on the website).
My Claude Prompts to build globalmajoritydata.com
- My initial prompt
OK I want your help building a website to support the Global Majority Data Project. Here’s the white paper that it is based on.
I already have a company – 60 decibels – so I don’t need this to be a new company,
it is an initiative of 60 decibels. I am raising money for this and want to see if I can make a decent website easily. Ultimately I expect that if it’s good, the pages will move to the 60decibels.com domain, but I just purchased globalmajoritydata.com on GoDaddy.
So what I want to do is:
- I’ll share the brief
- I’ll share a few websites that look like what I’m interested in – obviously the branding should mostly align with 60 decibels
- I want you to give me some options for how to approach this, ask questions, etc…I don’t want you doing too much work building until we are aligned on how it’s going to be structured and what it will look like
- I’ll want you to create the structure of the site and the draft copy for me to approve
- Once that’s sorted, we’ll work on look and feel
- Then you’ll do the homepage
- Finally, you’ll do the rest of the site
How does that sound?
Any questions?
- Claude asked two rounds of clarifying questions—tone, structure, site size, audience, etc.—which I answered. I also uploaded my existing Global Majority Data Project whitepaper.
- I had to fiddle with the Chrome for Claude extension, which wasn’t behaving. Claude suggested skipping it; I insisted we fix it. We did.
- With Step 1 done, Claude asked for reference sites (Step 2). I shared a few. It reflected back what it inferred from them and proposed two structures: single long scroll or multi-page.
- I reacted to the structure, added a missing page, and outlined what it should contain.
- Claude drafted full-site copy, page by page. I reviewed it, gave specific comments, and it incorporated them.
- It asked for images. I found ~30 from internal documents and from various 60dB published assets and uploaded them.
- It produced a first draft of the site. Some of it was jaw-droppingly ugly. I gave pointed feedback. We went ~4 rounds on design, then I did smaller copy tweaks.
- The site was nearly ready. Claude generated HTML pages for browser preview with no images. It said mine were too low-res, so I bundled them into a PPT and re-uploaded.
- A few more rounds of feedback about the images on the site: adding variety, eliminating repetition, tightening a few style choices.
- (Fun moment.) I said, “Looks great, let’s publish.” Claude replied, “You’ve flagged a style issue three times that I haven’t fixed. Want me to try another approach?” I said yes.
- I asked how to publish. It gave instructions, which I followed. I was mostly lost at this step, but it walked me through them (with me pasting a bunch of screen shots and saying, ‘what does this mean’?). I had a handful of DNS issues that took some time to resolve.
And that was that. The site is live. Pretty cool, huh?




