Currently building
Process

Claude Code to production. No terminal heroics.

The actual stack and pipeline behind every product on this site. Nothing theoretical, just what runs.

09 Process

How I build. Claude Code to production, no terminal heroics.

I'm a department of one. I ship like a team of ten. The difference is the pipeline, not magic.

I don't build in a terminal. I build with Claude Code in project repos, push to GitHub, deploy via Vercel. Nothing's riding on a local environment, everything is backed up, every change has a preview URL before it touches production.

01 Claude Code → GitHub. Everything in version control, nothing lives only on my laptop.
02 GitHub → Vercel. Preview deploys per branch, staging, production. Rollback is one click.
03 Vercel AI Gateway in front of every model call. Fallback models without juggling SDKs.
04 Supabase for the database. Postgres, auth, row-level security, edge-friendly.
05 Integrations as needed: APIs, MCPs, Resend for email, anything else the product calls for.

Languages and frameworks

  • TypeScript
  • Next.js
  • React
  • Tailwind
  • Node

Infra and data

  • Vercel
  • Vercel AI Gateway
  • Supabase
  • Resend
  • Upstash
  • Stripe

AI and agents

  • Claude Code
  • Claude.md
  • MCP integrations
  • Notion KB
  • Groq
  • ElevenLabs

Research and data

  • Tavily
  • Exa
  • Firecrawl
  • Bruno
  • DataForSEO
  • Companies House
  • DEFRA
  • TPS
  • Vapid push
Talk

Got a problem worth shipping? Let's talk.

Send a noteUse the contact form
OrPress ⌘K and ask my agent
LinkedIncallumwells93
ReplyWithin a day, usually faster
Every product on this site was built with Claude as a daily collaborator
LinkedInWeb Hero Limited / 15866557 / Leeds, UK