docs/archive/research/website-refactor-v2-prompt

DaisyAI Website Refactor - Claude Code Execution Prompt

Copy this entire prompt into a new Claude Code session in the daisyai-www repo to execute the refactor.


Context

I need to refactor the DaisyAI website from SaaS-focused to FDE-first (Forward Deploy Engineering) positioning. This is a strategic pivot - we're positioning as an implementation firm that builds production AI for healthcare, with our SaaS product serving as proof of capability.

Tech Stack (Already in Place)

  • Next.js 15 + React 19 + Tailwind CSS v4
  • Framer Motion for animations
  • Three.js (Vortex background effect)
  • Fonts: Playfair Display (headings), Nunito Sans (body)

Strategic Direction

From: "AI-Powered Medical Case Review" (SaaS product focus) To: "We Build AI That Actually Works in Healthcare" (FDE services focus)

Key Messaging:

  • 95% of AI projects fail - we're the engineers who make them succeed
  • Unlike consultants who deliver recommendations, we deliver working software
  • We embed with your team, understand real workflows, and ship production code
  • Our platform is proof we can build - it's running in production today

New Homepage Structure

Replace current sections with this flow:

1. Hero
   - Headline: "We Build AI That Actually Works in Healthcare"
   - Subhead: "95% of enterprise AI projects fail. We're the engineers who make them succeed."
   - CTAs: "Book a Discovery Call" (Calendly) + "See How We Work" (scroll)

2. ProblemStats (NEW SECTION)
   - Title: "The AI Implementation Crisis"
   - Three animated stats: "95%" / "1%" / "800%"
   - Copy about implementation being the bottleneck, not models

3. Approach (NEW SECTION)
   - Title: "Unlike Consultants, We Build Working Software"
   - Three columns: "Embed & Discover" → "Build & Deploy" → "Improve & Scale"
   - Differentiates from consultants and body shops

4. EngagementModels (NEW SECTION)
   - Title: "Three Ways to Work With Us"
   - Card 1: Discovery Sprint ($15-25K, 2 weeks)
   - Card 2: Implementation Project ($75-200K, 2-4 months)
   - Card 3: Embedded FDE ($20-30K/month, ongoing)
   - Each has "Best for:" qualifier

5. ProofOfCapability (MODIFIED from DaisySolution)
   - Title: "We've Already Built It For Ourselves"
   - Simplified product showcase as evidence of building capability
   - Links to /product for details
   - Framing: "We're not theorists. We're builders who ship."

6. TargetMarket (NEW SECTION)
   - Title: "Built for Healthcare Operations Leaders"
   - ICP: Regional health systems, specialty payers, UM/UR companies
   - Common pain points checklist
   - Qualifier: "$50M-$500M revenue - big enough for budget, nimble enough to move fast"

7. Team (ENHANCED)
   - Title: "Wharton-Trained. Healthcare-Focused. Builder-Minded."
   - Thomas Startz (CEO) - Columbia, Wharton, healthcare ops
   - Michael Yuan (CTO) - Princeton, Wharton, engineering/consulting
   - Social links under each name
   - "We left consulting to build something that actually ships"

8. CallToAction (MODIFIED)
   - "Let's Talk About Your AI Challenges"
   - "Book a 30-minute call. No pitch, just problem-solving."
   - Single Calendly button + email fallback

Header Changes

Modify Header.tsx:

  • Add navigation: Services | Product | Insights | About
  • Add social icons (Twitter, LinkedIn, Substack) - small, grouped
  • Change CTA: "Request Access" → "Book a Call"
  • Keep scroll behavior (blur effect)

New Components Needed

1. SocialLinks.tsx (src/components/ui/)

interface SocialLinksProps {
  platforms: ('twitter' | 'linkedin' | 'substack')[];
  size?: 'sm' | 'md' | 'lg';
  variant?: 'header' | 'footer' | 'inline';
  showLabels?: boolean;
}

// URLs to configure:
const SOCIAL_URLS = {
  twitter: 'https://twitter.com/daisyai',      // NEEDS ACTUAL URL
  linkedin: 'https://linkedin.com/company/daisyai',  // NEEDS ACTUAL URL
  substack: 'https://substack.com/@tstartz',
};

2. ProblemStats.tsx (src/components/sections/)

  • Three stats with count-up animation on scroll
  • Use ScrollReveal for entrance
  • Dark background, large numbers

3. Approach.tsx (src/components/sections/)

  • Three-column grid (responsive)
  • Icons: Eye, Code, TrendingUp (from Lucide)
  • Card styling consistent with existing

4. EngagementModels.tsx (src/components/sections/)

  • Three pricing cards
  • Show price ranges publicly (builds trust)
  • "Best for:" helps self-qualification
  • Could link to /services for details

5. TargetMarket.tsx (src/components/sections/)

  • Two-column: org types + pain points
  • Icons for org types
  • Checkmarks for pain points

6. TeamHighlight.tsx (src/components/sections/)

  • Side-by-side founder photos
  • Social links under each
  • Credentials emphasized

Design Constraints

  • KEEP dark theme (#0a0a0a background)
  • KEEP Vortex particle background on hero
  • KEEP yellow-400 accent color for CTAs
  • KEEP ScrollReveal animations pattern
  • KEEP existing typography scale
  • KEEP white/opacity text variants

Files to Modify

  1. /src/app/page.tsx - New section composition
  2. /src/components/sections/Hero.tsx - New messaging
  3. /src/components/layout/Header.tsx - Nav + social + CTA
  4. /src/components/layout/Footer.tsx - Social row
  5. /src/components/sections/CallToAction.tsx - New copy

Files to Create

  1. /src/components/ui/SocialLinks.tsx
  2. /src/components/sections/ProblemStats.tsx
  3. /src/components/sections/Approach.tsx
  4. /src/components/sections/EngagementModels.tsx
  5. /src/components/sections/TargetMarket.tsx
  6. /src/components/sections/TeamHighlight.tsx

Reference Components

Look at these existing files for styling patterns:

  • DaisySolution.tsx - Section layout, mockup styling
  • ScrollReveal.tsx - Animation pattern to use
  • ProblemStatement.tsx - Text section styling
  • RequestAccessModal.tsx - Modal pattern if needed

Execution Order

  1. First: Create SocialLinks component (needed by Header)
  2. Second: Modify Header (nav + social icons + CTA)
  3. Third: Create new sections in order (ProblemStats → Approach → EngagementModels → TargetMarket → TeamHighlight)
  4. Fourth: Modify Hero with new messaging
  5. Fifth: Modify/create ProofOfCapability from DaisySolution
  6. Sixth: Update page.tsx with new section order
  7. Seventh: Modify CallToAction
  8. Eighth: Update Footer with social row

Content Placeholders

For now, use these placeholder values (owner will confirm):

  • Twitter: https://twitter.com/daisyai
  • LinkedIn: https://linkedin.com/company/daisyai
  • Calendly: https://calendar.app.google/aVV7SrwdnLTsvxyL6
  • Email: thomas@daisyai.ai

Success Criteria

When done, the homepage should:

  • Lead with "We Build AI That Actually Works in Healthcare"
  • Show the 95%/1%/800% stats prominently
  • Explain the Embed→Build→Scale approach
  • Display three engagement tiers with pricing
  • Show product as proof of capability (not primary offering)
  • Help visitors self-qualify with ICP section
  • Feature founders with credentials and social links
  • Have clear "Book a Call" CTA throughout
  • Have social links in header and footer

Start

Begin by exploring the current codebase structure, then start with the SocialLinks component. Ask me if you need clarification on any content or design decisions.

Daisy

v1

What do you need?

I can pull up the fundraise pipeline, CRM accounts, hot board, meeting notes — anything in the OS.

Sonnet · read-only