Building a Website When You're Too Busy Running the Business

The Problem: I Can Build This, But I Don't Have Time

I'm a professional developer with 35 years of experience. I've built countless websites, e-commerce platforms, enterprise applications. I know how to pick a framework, set up a deployment pipeline, write responsive CSS, handle forms, optimize for SEO.

But I'm also running a warehouse. Managing clients, overseeing fulfillment, solving operational problems, building automation tools. The warehouse needs a proper website—we're getting serious about bringing in new clients. I could build it myself. Given a few weeks.

I don't have a few weeks.

So I tried something different: using Claude Code as a collaborative partner to build the site in hours instead of weeks.

Here's what that actually looked like.

---

Tool Selection Paralysis

When you're experienced, you know too many options. Static site generator? Astro, Next.js, Gatsby, Hugo, Jekyll. CSS framework? Tailwind, Bootstrap, custom. Deployment? Netlify, Vercel, AWS, custom server. Forms? Netlify Forms, FormSpree, custom backend.

Each choice has tradeoffs. Each requires setup time. Each needs evaluation.

I described what I needed:

• Fast static site (SEO matters for 3PL warehouse)
• 24+ pages with consistent layout
• Contact forms, quote requests
• Blog capability (we have content to share)
• Easy deployment
• No database needed

Claude Code recommended Astro + Tailwind + Netlify. Not because it's the only option, but because it matched my constraints:

• Astro: Component-based like React, but generates static HTML (fast, SEO-friendly)
• Tailwind: Utility-first CSS (rapid prototyping without custom CSS files)
• Netlify: Free tier, instant deployment, built-in forms, custom domain support

Decision made in 5 minutes instead of hours of research.

---

Framework Setup: The Part Everyone Hates

Setting up a modern web framework involves:

• Installing dependencies
• Configuring build tools
• Setting up routing
• Creating base layout components
• Configuring Tailwind
• Setting up development server
• Testing builds

This takes 2-4 hours if you know what you're doing. Longer if you hit version conflicts or configuration issues.

With Claude Code: 15 minutes.

Not because it's magic, but because:

1. I described what I needed
2. Claude Code generated the config files
3. I reviewed and approved
4. Ran the commands
5. Started building pages

The velocity difference is significant. I spent time on business logic and design, not configuration troubleshooting.

---

Content Collaboration: The Touchy Part

Let's be clear about what happened with content:

AI did NOT write our content.

What actually happened:

I Had Content, It Was Just Scattered

• Old website copy (saved in Google Docs)
• Email responses to client questions (saved in files)
• Notes about services we offer (scattered across documents)
• Pricing conversations (email threads)
• Client testimonials (actual emails from clients)
• My own story (I'd written it before, just not for a website)

The content existed. It just wasn't organized, structured, or website-ready.

Claude Code as Structure Partner

I'd say: "Here's what I want on the services page" and paste fragments from different sources. Claude Code would:

1. Structure it into sections
2. Suggest organization (hero, features, benefits, CTA)
3. Flag missing information ("You mentioned FBA prep but didn't explain what it is")
4. Draft structure with placeholders

Then I'd:

• Edit the copy
• Rewrite sections that sounded wrong
• Add details only I knew
• Remove marketing fluff I didn't want
• Make it sound like me, not a corporate website

Actual Copywriting

Some sections I wrote from scratch:

• Homepage hero copy (that's pure positioning, had to be me)
• "Why Choose Us" section (our actual differentiators)
• Case study narratives (based on real projects, my words)
• Blog posts (these are MY stories, MY perspective)

Claude Code helped with structure and suggestions, but the voice and substance came from me.

---

Technical Decisions That Would Have Taken Days

Component Architecture

I described the layout pattern I wanted: "Most pages need a hero section, then content sections, then a CTA block at the bottom."

Claude Code generated reusable components:

• Hero.astro - Configurable hero sections
• FeatureGrid.astro - 2/3/4 column feature layouts
• CTABlock.astro - Call-to-action sections
• BaseLayout.astro - Consistent header/footer

This would have taken hours to design and build. Instead: described what I wanted, reviewed the code, shipped it.

Form Handling

Needed contact forms and quote requests. Options:

• Build custom backend (hours)
• Third-party service like FormSpree (integration time, monthly cost)
• Netlify Forms (free, built-in, no JavaScript required)

Claude Code: "Since you're deploying to Netlify, use Netlify Forms. Here's the implementation."

Forms working in 10 minutes.

SEO Foundation

Later, we added comprehensive SEO:

• Sitemap.xml with all 24+ pages
• RSS feed for blog
• robots.txt with AI search engine permissions
• JSON-LD structured data (LocalBusiness, BlogPosting schemas)
• Canonical URLs

This would have taken a full day of research and implementation. With Claude Code: described what I needed, it generated the files, I reviewed and deployed.

---

Deployment: From Code to Live in Minutes

Setting up deployment traditionally involves:

• Creating GitHub repository
• Configuring build settings
• Setting up Netlify/Vercel account
• Connecting repo to deployment service
• Configuring custom domain
• Setting up SSL
• Testing deployment pipeline

Claude Code walked me through each step with exact commands and configuration. No documentation hunting. No troubleshooting obscure errors.

Result: Push to GitHub, auto-deploy to Netlify, live at custom domain with SSL.

---

What This Approach Is Good For

This worked because:

1. I Knew What I Wanted

Not vague "I need a website" but specific:

• 24 pages covering services, industries, case studies, blog
• Professional but not corporate
• Focus on unusual fulfillment capabilities
• Contact forms for lead generation
• SEO-optimized for 3PL searches

I brought clarity. Claude Code brought speed.

2. I Could Review Technical Decisions

When Claude Code suggested Astro + Tailwind, I understood the tradeoffs. When it generated components, I could review the code and know if it made sense.

This isn't for non-technical founders. This is for technical founders who don't have time.

3. I Had Content (Just Not Organized)

If you're starting from zero with no idea what to say about your business, this approach won't work. But if you have:

• Old website copy
• Email responses to common questions
• Sales documents
• Your own story written somewhere

Claude Code can help structure and organize it. You still need to edit, approve, and add your voice.

4. I Was Willing to Iterate

This wasn't "Claude Code, build me a website." It was:

• "Let's set up the framework"
• "Now let's build the homepage"
• "Actually, change that section"
• "Add a services page"
• "Make the CTA less pushy"

Dozens of small iterations, each reviewed and approved by me.

---

What This Approach Is NOT

This is not "AI wrote my website."

I wrote the content. Claude Code helped structure it.

This is not "Anyone can build a professional site now."

I made hundreds of decisions. What framework? What architecture? What content goes where? How should this sound? Does this technical approach make sense?

Without technical background and business clarity, you'll struggle.

This is not "No human effort required."

I spent hours editing content, making decisions, reviewing code, testing, refining. The difference is focused effort on high-value decisions instead of boilerplate setup.

---

The Time Breakdown

Traditional Approach (with my experience):

• Framework research & decision: 2-3 hours
• Setup & configuration: 2-4 hours
• Component architecture: 4-6 hours
• Building 24 pages: 20-30 hours
• Content organization: 10-15 hours
• SEO setup: 4-6 hours
• Deployment configuration: 2-3 hours
• Testing & refinement: 5-10 hours

Total: 50-80 hours (2+ weeks part-time)

With Claude Code:

• Framework decision: 5 minutes
• Setup & configuration: 15 minutes
• Component architecture: 1 hour
• Building 24 pages: 8-10 hours (with iterations)
• Content organization: 4-6 hours (with editing)
• SEO setup: 30 minutes
• Deployment configuration: 15 minutes
• Testing & refinement: 2-3 hours

Total: 16-22 hours (2-3 days part-time)

Reduction: 70% faster than building solo

---

The Business Impact

Instead of taking 2+ weeks (which I didn't have), the site went live in days.

What that enabled:

• Professional presence when talking to prospective clients
• Case studies to show what we've built
• Blog to share our story and attract similar clients
• Lead generation forms (already getting inquiries)
• SEO foundation (indexed by Google within days)

The alternative was either:

1. Delay the site for weeks (lost opportunities)
2. Hire an agency for $10K-20K and wait months
3. Use a template that doesn't fit our unique positioning

Instead: Professional custom site, deployed quickly, minimal cost.

---

What I'd Do Differently

Looking back after a few weeks:

1. Start With Sitemap Planning

I built pages as I thought of them. Better approach: map out all 24 pages upfront, then build systematically.

2. Content First, Then Structure

I built some pages, then realized I needed different content. Should have gathered all content fragments first, then structured into pages.

3. SEO From Day One

I added SEO (sitemap, structured data, RSS) after launch. Would have been easier to build it in from the start.

That said: the site shipped quickly and I iterated. Perfect is the enemy of done.

---

The Pattern for Technical Founders

If you're technical but don't have time to build what you need:

You bring:

• Business clarity (what do you actually need?)
• Technical judgment (can review and approve decisions)
• Content substance (scattered is fine, structure comes later)
• Willingness to iterate

Claude Code provides:

• Decision velocity (framework, tools, architecture)
• Boilerplate elimination (setup, config, deployment)
• Content organization (structure what you already have)
• Technical implementation (write the code you'd write, faster)

You get:

• Professional results in hours instead of weeks
• Focused effort on high-value decisions
• Custom solutions that fit your business
• No outsourcing, no waiting, no expensive agencies

---

The Bottom Line

I'm a professional developer who didn't have time to build a website. Claude Code didn't replace my expertise—it amplified it.

The site you're reading right now is the result: 24 pages, professional design, SEO-optimized, deployed to production. Built in days instead of weeks.

Not because AI did it all. Because AI eliminated the parts I didn't have time for (setup, boilerplate, research), letting me focus on the parts that matter (decisions, content, voice, positioning).

For technical founders running businesses: this is the unlock. You don't need to choose between a great website and running your business. You can do both.

---

Built in November 2025 using Claude Code. Deployed to Netlify. Still iterating based on client feedback.

---