cd /news/ai-tools/i-built-and-published-a-small-busine… · home › topics › ai-tools › article
[ARTICLE · art-161902] src=dev.to ↗ pub= topic=ai-tools verified=true sentiment=↑ positive

I built and published a small business website with Claude Code: the exact workflow

A developer published a step-by-step workflow for building and deploying a small business website using Claude Code in the Claude desktop app, taking users from an empty folder to a live, version-controlled site on Vercel without hand-writing code. The guide emphasizes scoping the project folder, writing specific prompts, testing the local preview as a visitor would, making one change per message, and using GitHub for version history before deploying. The developer notes the result is a marketing site only, with booking, payments, email notifications and client login left as separate future projects.

by read4 min views6 publishedNov 1, 2026

You can build a small business website without writing code by hand. You still have to make decisions and check the result yourself. This is the workflow I use with Claude Code in the Claude desktop app. It takes you from an empty folder to a live site on Vercel. I've written it for people who have never coded.

Create an empty folder with a plain name, for example anna-first-site. Every file for the site will live there.

Open the desktop app, sign in and go to the Code tab. Choose that folder as the project. Before you build anything, ask:

Which folder are you working in?

If Claude names a different folder, stop and fix that first. A wrong folder is the most common way beginners lose work or mix two projects together. A vague prompt like "make me a website" gets you a generic page. A good first prompt says what the business is, which sections the page needs, what it should look like, what one button must do, and what Claude must not do. Here is the kind of prompt I start with, using a fictional photographer:

In this empty project folder, build a responsive Next.js website for Anna, a fictional family photographer. Include an opening section, services, three stages of a session and contacts. Use a dark graphite background, warm light text and a copper accent. The "Discuss a session" button must scroll to the contact section. Label sample content; do not invent reviews or contact details. Keep it local, with no accounts or payments. Explain any missing setup simply, then start the preview and give me its exact address.

These lines do most of the work:

Let Claude finish. If it asks you to install something or approve a step, read what it says before you agree. Claude starts a local preview, usually an address like http://localhost:3000, and you can open it in the app's Browser pane. A localhost address only works on the computer running the project. You can't send it to anyone yet.

Test it the way a visitor would:

Only call it done when it passes these checks. "Claude said it works" isn't a check.

Ask for one specific change per message:

Make the main heading shorter and keep the "Discuss a session" button working.

Then check that change yourself. Asking for one change at a time makes it obvious which change broke something, if anything does.

When something does break, give Claude a proper bug report, not just "it's broken":

I opened http://localhost:3000, clicked "Discuss a session", expected to land on Contacts, but nothing happened. Next time, keep working in the same project folder. Don't start over in a new one.

While the site lives only in a folder, you have no history and no backup. GitHub fixes both. Create a free account, then ask Claude in the same project: Put this project on GitHub as a new private repository. Explain each step before you do it, and tell me what I need to approve.

After that, make each change on purpose and save it with a clear description, for example "Shorten hero heading". If a later change goes wrong, you can go back to a version you know was good. That's the main reason to use GitHub in the first place.

Sign in to Vercel with your GitHub account. Import the repository and keep the defaults Vercel detects for a Next.js project, then deploy. You get a public *.vercel.app address.

Now test the hosted site like a stranger would, on your phone too. Run the Step 3 checks again on the public address. From now on, each change you save to GitHub creates a new deployment. Look at it before you call it released.

Adding your own domain comes later. You set it up in Vercel's domain settings once the site is in a state you're happy with.

At the end of this, you have a working, published, version-controlled marketing site. You don't yet have online booking, payments, email notifications or a client login. Each of those is a separate project with its own setup and its own ways to go wrong. Get the simple site live first.

I've turned this workflow into a written course, Build & Launch Your First Website with Claude: 16 practical lessons in English and Russian. It covers the steps above in more detail and then adds sign-in and a private client area with Supabase. The first lesson is free to read at https://g-lab.agency/learn/welcome. The full course is $19, one-time: https://g-lab.agency/courses/build-with-claude.

── more in #ai-tools 4 stories · sorted by recency
── more on @claude code 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/i-built-and-publishe…] indexed:0 read:4min 2026-11-01 · —