Half a Day to a Live Site: Claude Code Cuts Solo Dev Time from Days to Hours
A one-person shop can now ship a complete, SEO-friendly static site with a content system in an afternoon at near-zero recurring cost. The bottleneck shifts from coding speed to clarity of specification: the AI handled a real dependency-resolution puzzle that would have burned an hour of a senior dev's time, but it needed a human to define the architecture boundaries that kept `fs` imports out of client components.
Starting from a natural-language prompt in the terminal, Claude Code initialized a Next.js 14 project, installed dependencies, wrote all page and global components, configured SEO metadata, generated a sitemap, and produced deployment docs. The whole build — project setup, content system, Cloudflare adaptation, and responsive layout — finished in roughly 4 hours, compared to an estimated 3–5 days of manual work.
A version-compatibility deadlock with the Cloudflare Pages adapter showed the tool's engineering judgement: Claude Code traversed every historical release of `@cloudflare/next-on-pages` to find a version that didn't declare a phantom peer dependency on a nonexistent Next.js release, then locked the version and restructured the blog list from server-side dynamic to client-side static filtering.
The final stack — Next.js SSG, Tailwind CSS, Markdown with gray-matter, and Cloudflare Pages — keeps annual hosting costs at $11.48 for the domain plus negligible AI token spend. Content updates are a Markdown file and a git push.
The dependency-resolution episode is the most telling data point: the AI didn't just generate code, it performed a bisect-like investigation across package versions to resolve a real-world compatibility deadlock. That's engineering work, not templating.
The 3–5x efficiency multiplier reported here aligns with a pattern seen across AI coding tools — but the multiplier only holds when the developer already knows the architecture (SSG vs SSR, server/client component split, static filtering constraints). The AI executes; the human still draws the boundary lines.
Cloudflare Pages' restriction to fully static output forced a client-side filtering design that is simpler to maintain than a hybrid approach and costs nothing to serve, making it a useful default pattern for content sites that don't need real-time data.