Speed Is a Feature
Speedruns
Things I Built Absurdly Fast
Claude Code did 6 months of work in 2 days. I'm still picking my jaw up off the floor. Here's the full list of things that got built at speeds that probably shouldn't be legal.
glenbradford.com
Days, not monthsA 3,143-page personal website with blog posts, billionaire profiles, movie scripts, gear reviews, book recommendations, voting system, leaderboard, and newsletter integration.
How
Claude Code running 9 agents in parallel. I typed instructions. Claude typed everything else. I deployed between Rocket League matches.
Delivery Hub
85 releases in 8 monthsA full Salesforce managed package for software delivery — sprint planning, issue tracking, automation, and reporting. Enterprise-grade. Solo developer.
How
Claude Code for Apex and Lightning Web Components. Test-driven development. Ship daily. Fix daily. Ship again. 90%+ test coverage maintained throughout.
157 Billionaire Movie Screenplays
One sessionFull movie treatments for 157 billionaires and icons. Each one includes a logline, cast recommendations, three-act structure, and dialogue scenes.
How
Claude Code writing in batch mode. I reviewed, edited, and made sure each screenplay captured what makes that person extraordinary. Not AI slop — curated AI collaboration.
2,708 Blog Posts Migrated
HoursA decade of WordPress content — investment theses, market commentary, personal essays — parsed, categorized, and rendered in a modern Next.js site.
How
Markdown parsing, automatic categorization via regex, frontmatter extraction, and in-memory caching. The kind of boring infrastructure work that Claude Code makes painless.
The Billionaire Bookshelf
One afternoon47 book recommendations from the world's richest people, with attribution, quotes, ratings, and Amazon links. Cross-linked to billionaire profiles.
How
Data modeling, affiliate integration, client-side search and filtering. Built the whole system — data, components, pages — in one sitting.
31 Gear Comparisons
Two eveningsHonest product comparisons from my real Amazon purchase history. What I bought vs what I should have bought, with stories and lessons for each one.
How
Structured data with the Amazon affiliate tag baked in. Each comparison has a story, a verdict, a lesson, and ready-to-tweet text. Content + commerce in one sitting.
Cloud Nimbus LLC Website
One weekendA professional business site with product pages, comparison pages (vs Jira, Asana, Monday), demo page, documentation, and contact form.
How
Next.js static export, Tailwind styling, Vercel deployment. The whole thing from zero to live in a weekend because the client was me and I don't do meetings.
9 Books Published
2012 - 2024Act As If, 8 Fanniegate volumes, and Grandma Helen's memoir. Self-published via Amazon and Gumroad. Written with the intensity of someone who has something to prove.
How
Pure stubbornness. I had a thesis that required 8 books to explain properly. Most people would have written a blog post. I wrote a library.
The secret? Start before you're ready.
Most projects die in the planning phase. These all share one thing in common: I started building before I had a complete plan. Speed compounds. Momentum is real. And Claude Code is the best co-pilot a builder could ask for.
The Receipts
The Numbers
This isn't a portfolio of mockups or side projects that never shipped. Every number below represents production code, live on the internet, serving real traffic. Built by one person with an AI co-pilot.
Built with Next.js 16 + Claude Code + Vercel. Deployed via git push. The entire site builds and deploys in under 2 minutes. No CI/CD pipeline drama. No DevOps team. Just git push origin main.
The Playbook
How to Build 170+ Pages in Days
This isn't magic. It's a repeatable methodology. Here's the step-by-step process that turns “that would take months” into “it's already live.”
Start with Structured Data
Don't write freeform content. Model everything as typed arrays in TypeScript. Billionaires, books, gear comparisons, blog posts — they're all arrays of objects with strict interfaces. This is the foundation. If your data is structured, everything downstream is automatable.
interface Billionaire { name: string; rank: number; netWorth: string; screenplay: boolean; }Use Dynamic Routes for Scale
One [slug] route can generate hundreds of pages. Write the template once, feed it different data, and Next.js handles the rest. The billionaire profiles page is a single component that renders 157 different profiles. The gear page is one template serving 61 comparisons. This is how you get scale without repetition.
src/app/billionaires/[slug]/page.tsx → 157 unique pagesParallelize with AI Agents
Claude Code can run up to 10 agents simultaneously, each working on different files. While one agent builds the data layer, another writes the page component, a third handles the JSON-LD schema, and a fourth writes the enrichment content. This is not sequential development — it's parallel construction.
9 agents × simultaneous work = days of output in hoursIterate Fast: Build → Deploy → Improve
Ship the first version immediately. Don't wait until it's perfect. Deploy, look at it live, fix what bothers you, deploy again. The feedback loop should be measured in minutes, not sprints. Vercel's git push deployment makes this frictionless — every push is a live preview.
git push → live in 90 seconds → iterate → repeatSEO from Day One
Don't bolt on SEO after launch. Bake it into every template from the start. JSON-LD structured data, meta tags, canonical URLs, Open Graph images, FAQ schemas — all generated programmatically from your structured data. When you add a new billionaire to the array, they automatically get proper SEO markup.
100+ pages with JSON-LD, FAQPage, Article, BreadcrumbList — all automatedCase Studies
Speed Case Studies
Four real examples of building at absurd velocity. Not hypotheticals — these are things that actually shipped and are live on this website right now.
157 Billionaire Profiles
Built in sessions, not sprints
Started with a simple TypeScript array of 100 billionaires split across four data files. Then added enrichment layers: rich-content.ts for deep profiles, photos.ts for imagery, themes.ts for visual identity, holdings.ts for portfolio data. Then the screenplay layer — 107 premium React components, each one a full movie treatment. Finally, mergeAllContent() stitches all six layers together into a single unified dataset. The architecture is modular, extensible, and each layer was built independently by different AI agents.
39 FRC Teams in One Session
One evening
The FIRST Robotics Competition teams page started as a simple idea: showcase teams I've mentored or followed. Modeled the data as a typed array with team number, name, location, and details. Created one dynamic [slug] route. Fed in 39 teams. Every team got its own page with consistent layout, proper meta tags, and JSON-LD structured data. The template does all the work. The data just flows through it.
Tom Cruise: 16 Subpages in Parallel
One session, multiple agents
The Tom Cruise shrine needed depth — not just one page, but a constellation of subpages covering running analysis, stunts, movies, and more. I spun up multiple Claude Code agents, each building a different subpage simultaneously. One agent worked on running speed analysis while another built the arm pump breakdown. A third handled running companions while a fourth wrote the injury analysis. All working in parallel, all shipping at the same time. This is what parallelized development looks like.
61 Gear Comparisons
Built incrementally, fast each time
Every gear comparison follows the same pattern: two products, a story about why I bought them, a verdict, and Amazon affiliate links. The data model is clean — types.ts defines the interface, data.ts holds all 61 entries, and the [slug] route renders them. Adding a new comparison means adding one object to an array. The page, the SEO, the affiliate links, the category pages — all automatic. This is how you turn a purchase history into a content engine.
The Stack
The AI-Assisted Development Stack
These tools aren't just preferences — they're force multipliers. Each one was chosen because it removes friction and lets you move faster. Together, they form a stack that turns a solo developer into a small army.
Claude Code
AI Co-PilotThe engine behind every speedrun on this page. Runs multiple agents in parallel, writes production-quality TypeScript, understands the full codebase context, and never complains about working at 2 AM. This is not autocomplete — it's a collaborator that can hold the entire project in its head.
Next.js 16
FrameworkApp router, server components, dynamic routes, ISR, and API routes in one framework. The [slug] pattern is the secret weapon for scale — write once, generate hundreds. Server components mean less JavaScript shipped to the browser. The developer experience is unmatched.
Vercel
DeploymentGit push deployment with zero configuration. Every push triggers a build. Every branch gets a preview URL. The feedback loop from code to live site is 90 seconds. No Docker, no Kubernetes, no infrastructure management. Just ship.
Tailwind CSS
StylingUtility-first CSS that eliminates context switching. No separate stylesheet files. No naming conventions to remember. Just write the styles inline with the markup. With CSS variables for theming (text-foreground, bg-card, border-border), the entire site maintains visual consistency without a design system team.
motion/react
AnimationsSmooth, performant animations with minimal code. FadeInUp, StaggerContainer, StaggerItem — reusable wrappers that make every page feel polished. Animations are the difference between a site that feels like a database dump and one that feels crafted.
TypeScript
Type SafetyEvery data structure is typed. Every interface is enforced. When you're building at speed, type safety is not a luxury — it's a guardrail. TypeScript catches the mistakes that velocity creates. It's the seatbelt that lets you drive fast.
The key insight: it's not any single tool that creates speed. It's how they compose. Claude Code writes TypeScript that Next.js serves through dynamic routes that Vercel deploys on git push with Tailwind styling and motion animations. Every layer reduces friction for the layer above it. The whole is greater than the sum of its parts.
Hard-Won Wisdom
Lessons Learned
Building fast isn't free. These are the lessons that cost time, frustration, and the occasional 3 AM debugging session to learn.
Cut Corners on Aesthetics, Never on Data
You can always make a page prettier later. You cannot easily fix a broken data model. If your TypeScript interfaces are wrong, every page built on them is wrong. Spend the extra 10 minutes getting the data structure right. It will save you 10 hours of refactoring.
Ship the Ugly Version First
The first version of every page on this site looked terrible. That's fine. A live ugly page teaches you more than a perfect page in your head. Deploy it, look at it on your phone, fix what bothers you most, deploy again. Three iterations of an ugly page beat one iteration of a perfect page every single time.
Parallelization Has a Coordination Cost
Running 9 Claude Code agents at once sounds amazing until two of them edit the same file. Or one agent's output depends on another agent's work that isn't done yet. The trick is to give each agent a completely independent scope — separate files, separate directories, no shared state. Plan the boundaries before you parallelize.
SEO Debt Compounds Faster Than Technical Debt
Every page you ship without proper meta tags, JSON-LD, and canonical URLs is a page that Google might index wrong — or not index at all. Fixing SEO after the fact means re-crawling, re-indexing, and waiting weeks for Google to catch up. Bake it in from the start. It takes 5 extra minutes per template and saves months of search console headaches.
AI Is a Multiplier, Not a Replacement
Claude Code can write 100 pages of content in an hour. But without editorial judgment, those 100 pages are just sophisticated noise. The human in the loop decides what ships, what gets rewritten, and what gets deleted entirely. Speed without taste produces volume without value. The builder's job is to maintain quality at velocity.
Momentum Is the Most Underrated Asset
The hardest part of any project is the first commit. Once you have something live — even if it's just a homepage with your name on it — the psychological barrier to shipping drops dramatically. Every deploy makes the next deploy easier. Every page makes the next page faster. Momentum compounds. Protect it at all costs.
Questions & Answers
Frequently Asked Questions
Everything you want to know about building at absurd speed with AI-assisted development.
What is speedrunning in software development?
Speedrunning in software development means building production-quality software at extreme velocity. It is not about cutting corners or shipping garbage. It is about removing friction, parallelizing work, using AI-assisted tools like Claude Code, and maintaining a bias toward action. The goal is to collapse timelines from months to days without sacrificing quality.
How do you build 170+ pages in days instead of months?
The key is structured data plus dynamic routes. You model your content as typed arrays in TypeScript, then use Next.js dynamic routes ([slug]) to generate hundreds of pages from a single template. Combine that with AI agents running in parallel — writing content, building components, enriching data — and you can ship an entire site before most teams finish their sprint planning meeting.
Is AI-generated content lower quality than hand-written content?
Not when you do it right. The difference between AI slop and AI-assisted excellence is curation. Every page on glenbradford.com was reviewed, edited, and approved by a human. Claude Code writes the first draft. Glen Bradford decides what ships. The AI handles the tedious parts — boilerplate, repetition, formatting — while the human handles taste, voice, and editorial judgment.
What tools do you use for rapid development?
The core stack is Claude Code (AI coding assistant), Next.js 16 (React framework with app router), Vercel (deployment), Tailwind CSS (styling), and motion/react (animations). Claude Code is the force multiplier. It can run multiple agents in parallel, each working on different files simultaneously. Combined with git push deployment to Vercel, the feedback loop from code to live site is measured in minutes.
Can I use this approach for my own projects?
Absolutely. The methodology is not proprietary. Start with structured data, use dynamic routes for scale, leverage AI for the repetitive work, and deploy continuously. The hardest part is not the technology — it is the mindset. You have to be willing to ship imperfect work, iterate in public, and treat speed as a feature rather than a risk.
How do you maintain SEO quality when building at speed?
SEO is baked into the process from day one, not bolted on after. Every page gets JSON-LD structured data, proper meta tags, canonical URLs, and semantic HTML as part of the template. When you use dynamic routes, the SEO infrastructure is built once and applied to every page automatically. This site has 100+ pages with JSON-LD schemas, FAQPage markup, BreadcrumbList data, and Article structured data — all generated programmatically.
Get Glen's Musings
Occasional thoughts on AI, Claude, investing, and building things. Free. No spam.
Unsubscribe anytime. I respect your inbox more than Congress respects property rights.
Join the Community
Weekly deep-dive analysis, real-time position updates, and direct access to Glen Bradford. $20/month.
Learn moreKeep Exploring
Cobra Kai Philosophy
Strike First. Strike Hard. No Mercy. The philosophy behind the velocity.
Read moreRocket League — bradford86
Champion II. Top 1% in career wins. Competitive spirit in a different arena.
Read morePopularClaude Code
The tool that made most of these speedruns possible.
Read moreThe Win Wall
Every good thing that's happened. The context for the speed.
Read moreGlen's Rules
Rule #11: Ship it before you're ready.
Read moreConsulting
Want this speed applied to your business? Let's talk.
Read more