How I Built Two Professional Landing Pages in One Day Using Claude

by Jared Little AI Learning
How I Built Two Professional Landing Pages in One Day Using Claude

How I Built Two Professional Landing Pages in One Day Using Claude

The Challenge: My client Karen needed professional ecommerce landing pages for her handcrafted products. Traditional development would take weeks. I delivered two production-ready solutions in a single day using Claude.

Here’s exactly how I did it, what worked, what didn’t, and the real numbers behind the project.

The Client Background

Universal Light Creations is a small craft business in East Aurora, NY. Karen creates beautiful laser-engraved products—slate coasters, wooden kitchen spoons, custom items—and sells them at craft shows and through her Squarespace website.

The Problem:

  • Existing website was basic, no dedicated product pages
  • No clear call-to-action or checkout flow
  • Missing customization workflow for personalized items
  • Limited time and budget for traditional web development

The Goal: Create professional landing pages with Square payment integration, customization forms, and print materials for craft shows—all while maintaining Karen’s artisan brand identity.

Project 1: Christmas Slate Coasters

What We Built

A complete ecommerce solution including:

  • Landing page with pricing tiers ($15 single, $25 for two)
  • Square payment integration
  • Print flyer with QR codes for craft shows
  • Photo upload workflow for custom designs

The Claude-Powered Workflow

Hour 1: Planning & Discovery

I started by having a conversation with Claude about the project requirements:

Me: "I need to create a landing page for custom slate coasters.
Two pricing tiers, Christmas theme, needs to work on Squarespace."

Claude: Analyzed requirements, asked clarifying questions about:
- Target audience (gift buyers, holiday shoppers)
- Brand colors and style (warm, festive, handcrafted feel)
- Technical constraints (Squarespace Code Blocks, inline CSS)
- Payment processing (Square integration)

Instead of spending hours searching Stack Overflow or wrestling with documentation, Claude helped me think through the entire architecture in a 10-minute conversation.

Hour 2-3: Rapid Development

This is where Claude truly shined. I described what I wanted, and Claude generated:

  1. Complete HTML/CSS landing page with:

    • Hero section with compelling copy
    • Pricing cards with hover effects
    • Feature highlights
    • Mobile-responsive design
    • Inline CSS (Squarespace compatible)
  2. Print-ready flyer with:

    • 8.5” x 11” optimized layout
    • QR code placeholders
    • Print-specific CSS (@page directives)
    • Color-accurate rendering

The magic moment: When I asked Claude to “make it feel more Christmas-y,” it immediately adjusted the color palette, added festive emojis, and suggested copy changes like “Perfect Holiday Gift” instead of generic text.

Hour 4-5: Refinement & Documentation

Claude didn’t just write code—it created:

  • Deployment guides (step-by-step Squarespace instructions)
  • Validation checklists (testing all links, mobile responsive, etc.)
  • README files explaining the project structure
  • Even generated the Square payment link setup steps

Hour 6: Deployment & Testing

With Claude’s deployment guide, I:

  • Uploaded to Squarespace Code Block
  • Integrated Square payment buttons
  • Generated QR codes
  • Printed test flyers
  • Validated on mobile devices

Final Result:

Project 2: Kitchen Spoons (The Template Reuse Strategy)

This is where AI-assisted development got really interesting.

The 50% Speed Improvement

Since the coasters project was successful, I asked Claude a simple question:

Me: "Can we use the coasters landing page as a template for
wooden kitchen spoons? Same structure, different product."

Claude’s Response:

  • Analyzed the coasters code
  • Identified reusable components
  • Suggested modifications for the new product
  • Generated adapted code in minutes

What Changed:

  • Color scheme: Christmas red/green → Wood tones (browns, forest green)
  • Pricing: Two tiers → Single tier (3 spoons for $15)
  • Customization: Photo upload → Text engraving
  • Seasonality: Holiday-specific → Year-round appeal

What Stayed the Same:

  • Overall layout structure
  • Mobile-responsive framework
  • Square payment integration pattern
  • Print flyer format
  • Documentation structure

The Customization Form Challenge

The spoons project had a unique requirement: customers needed to specify custom text for each of three spoons after purchasing.

My Ask:

Me: "After payment, I need a form where customers can enter
custom text for 3 spoons. Max 30 characters each.
Should redirect from Square checkout."

Claude Delivered:

  • Beautiful form with real-time character counter
  • Click-to-fill example tags (“Mom’s Kitchen”, “Est. 2020”)
  • Color-coded warnings when approaching character limit
  • Integration instructions for Square redirect
  • Three different implementation options (Formspree, Squarespace Forms, Google Forms)

Development Time: 4 hours total (vs 6 hours for first project)

Final Result:

The Real Numbers

Time Investment

Traditional Development Estimate:

  • Planning & design: 4-6 hours
  • HTML/CSS coding: 8-12 hours
  • Payment integration research: 2-3 hours
  • Form development: 3-4 hours
  • Documentation: 2-3 hours
  • Testing & debugging: 4-6 hours
  • Total: 23-34 hours (3-4 days of work)

Actual Time with Claude:

  • Coasters project: 6 hours
  • Spoons project: 4 hours
  • Total: 10 hours (1 day of work)

Time Saved: 13-24 hours (57-71% reduction)

Quality Metrics

Both projects achieved professional-grade quality:

  • Average score: 96.5/100
  • Zero broken links
  • 100% mobile responsive
  • Cross-browser compatible
  • Fast load times (< 1 second)

Code Volume

Total delivered:

  • 7,000+ lines of code and documentation
  • 16 complete files
  • 5 live web pages
  • 3 Square payment integrations

What Claude Handled Exceptionally Well

1. Boilerplate Elimination

No more writing CSS resets, responsive breakpoints, or standard HTML structure from scratch. Claude generated production-ready boilerplate instantly.

2. Context Retention

Claude remembered details from earlier in the conversation:

  • Brand colors
  • Target audience
  • Technical constraints
  • Previous design decisions

When I said “use the same footer as the coasters page,” it knew exactly what I meant.

3. Documentation Generation

This was unexpected but incredibly valuable. Claude created deployment guides, validation checklists, and even troubleshooting sections without being asked.

Example:

## Troubleshooting

### Issue: QR Code Doesn't Scan
Solutions:
- Increase QR code size (min 1.5" x 1.5" for print)
- Use higher DPI (300 DPI minimum)
- Ensure high contrast (dark on light background)

This kind of thoughtful documentation would take hours to write manually.

4. Adaptive Problem-Solving

When I mentioned Squarespace’s requirement for inline CSS, Claude immediately:

  • Restructured all styles to be inline
  • Namespaced everything to avoid conflicts
  • Added helpful comments explaining why

No tutorial searching. No trial and error. Just immediate, correct implementation.

What I Still Had to Do (The Human Touch)

1. Strategic Decisions

Claude can’t decide your business strategy. I made all the calls on:

  • Pricing structure
  • Which products to prioritize
  • Payment processor choice (Square vs Stripe)
  • Form implementation (native Squarespace vs custom HTML)

2. Client Communication

AI can’t replace the human relationship. I:

  • Interviewed Karen to understand her needs
  • Presented options and trade-offs
  • Made recommendations based on her goals
  • Coordinated deployment timing

3. Final Testing

While Claude generated validation checklists, I did the actual testing:

  • Clicked through every link
  • Tested on real mobile devices
  • Completed test purchases
  • Printed and scanned QR codes
  • Verified email notifications

4. Design Taste

Claude can generate designs, but I made the aesthetic calls:

  • “This green is too bright, make it more forest-like”
  • “The hero section feels too busy, simplify it”
  • “Can we make the pricing cards pop more?”

Claude executed perfectly, but I provided the creative direction.

Lessons Learned: The AI Development Workflow

What Works

1. Start with Clear Requirements

Bad: “Make me a landing page” Good: “Create a Squarespace-compatible landing page for custom slate coasters with two pricing tiers, Square payment integration, Christmas theme, mobile-responsive, and inline CSS”

2. Iterate in Conversation

Don’t expect perfection on the first try. I would say things like:

  • “The color scheme is too harsh, soften it”
  • “Add more whitespace between sections”
  • “Make the call-to-action button more prominent”

Each iteration took seconds, not hours.

3. Leverage Template Reuse

The second project took half the time because we had a proven template. Claude understood the pattern and adapted it intelligently.

4. Ask for Documentation

Simply saying “create deployment documentation” resulted in comprehensive, step-by-step guides that I could reference later.

What Doesn’t Work

1. Vague Requests

“Make it better” or “fix this” don’t work. Be specific about what you want changed and why.

2. Expecting Mind Reading

Claude can’t see your vision. You need to describe colors, feelings, target audience, use cases.

3. Skipping Testing

Just because Claude generated it doesn’t mean it works perfectly in production. Always test.

4. Forgetting Context Limits

Long conversations can lose early context. When starting a new feature, I’d sometimes need to re-establish key requirements.

The Business Impact

For Universal Light Creations

Before:

  • Generic product listings
  • No clear purchase path
  • Missing customization workflow
  • Limited craft show materials

After:

  • Professional dedicated product pages
  • Clear Square checkout integration
  • Seamless custom order workflow
  • Print-ready QR code marketing materials

Projected Impact:

  • $600+ monthly revenue potential from these two products alone
  • Professional brand presentation competing with larger businesses
  • Scalable framework for adding more products
  • Time savings for Karen (automated order collection)

For My Consulting Practice

Time Efficiency:

  • 10 hours delivered vs 23-34 hours traditional estimate
  • 57-71% time reduction
  • Ability to take on more clients
  • Faster turnaround = happier clients

Quality Improvement:

  • Professional-grade deliverables
  • Comprehensive documentation
  • Fewer bugs (Claude caught edge cases I might have missed)
  • Better accessibility and mobile responsive design

Competitive Advantage:

  • Can quote faster delivery times
  • Lower rates without sacrificing profit
  • More time for client relationships vs coding
  • Ability to deliver complete solutions (landing page + forms + print materials + docs) in one package

The Bigger Picture: AI as a Development Partner

This project changed how I think about AI in development.

Claude isn’t replacing me as a developer. Instead, it’s eliminating the tedious parts so I can focus on what humans do best:

  • Understanding client needs
  • Making strategic decisions
  • Providing creative direction
  • Building relationships
  • Solving unique problems

The analogy I use: Claude is like having a senior developer on your team who:

  • Never gets tired
  • Has encyclopedic knowledge of web technologies
  • Can write documentation faster than you can think
  • Doesn’t mind doing the boring stuff
  • Always asks clarifying questions

But this “senior developer” still needs a project manager (you) to provide direction, make decisions, and ensure quality.

What’s Next?

This success has opened up new possibilities:

Short-Term (Next Month)

  • Use this same template for 3-5 more Universal Light Creations products
  • Estimated time per product: 2-3 hours
  • Create a reusable template library

Medium-Term (Next Quarter)

  • Offer this as a service to other small businesses
  • “Professional landing page in one day” package
  • Use Claude to scale to multiple clients simultaneously

Long-Term (This Year)

  • Build a comprehensive ecommerce toolkit
  • Template library for common use cases
  • Documentation generator
  • Automated testing frameworks

Key Takeaways

If you’re considering using AI for client work:

✅ Do This:

  1. Start with a clear scope and requirements
  2. Use AI for boilerplate, structure, and documentation
  3. Iterate in conversation until it’s right
  4. Test everything thoroughly in production
  5. Maintain human oversight and creative direction

❌ Don’t Do This:

  1. Blindly deploy AI-generated code without testing
  2. Skip the requirement-gathering phase
  3. Expect AI to make strategic business decisions
  4. Forget to add your own creative touch
  5. Overlook client communication and relationship building

The Bottom Line

Time: Cut from 23-34 hours to 10 hours (71% reduction) Quality: 96.5/100 average (professional-grade) Cost: Fraction of traditional development Client Satisfaction: Two new revenue streams activated Learning: Insights about AI-assisted workflows that apply to future projects

This isn’t about replacing developers. It’s about augmenting our capabilities and focusing on what we do best—understanding human needs and delivering value.

Would I do it again? Absolutely. In fact, I already am. Two more products launching next week using this same workflow.


Tools Used:

  • Claude Sonnet 4.5 (via Claude Code extension in VS Code)
  • Squarespace for hosting
  • Square for payment processing
  • Git for version control

Project Files: All code, documentation, and project artifacts are version-controlled and available in my private repository for future reference and template reuse.

Want to try this yourself? Start small. Pick a simple landing page project and use Claude to generate the boilerplate. Iterate in conversation. Test thoroughly. You’ll be amazed at how much faster you can move while maintaining professional quality.

The future of development isn’t human OR AI. It’s human AND AI, working together as partners.