How I Shipped 4 Full-Stack Platforms in 25 Days
Four production-ready sites. One developer. Twenty-five days. Here is the exact stack, timeline, and workflow — including what broke and what made it possible.
Table of contents
In June 2026 I set a constraint: ship four production-ready full-stack platforms in 25 days.
Not demos. Not landing pages. Four live sites — each with a real database, a real admin panel, real SEO infrastructure, and real users or clients waiting on the other side.
Here is what I built, how long each piece took, and the three things that actually made it possible.
The Four Platforms
santoshpaudel.me — My portfolio site, rebuilt from the ground up as a platform that runs like a business. It has a full admin panel with dashboard, CMS, CRM, lead management, AI content agents, and an API key vault. Not a static page with project screenshots.
agenticai01.tech — An agent OS for the Web3 era. Developers publish AI agents; users discover and deploy them. Required a multi-subdomain architecture with both Azure and Vercel layers.
TheWestNepal.live — A complete rebuild of an existing Nepali news platform, migrated from WordPress to Next.js in under 48 hours. Now runs 60+ posts and programmatic landing pages with AI SEO built in from day one.
A full gaming platform backend for a US client — Admin panel, user dashboard, Telegram bot layer, wallet system, and webhook integrations. The most technically demanding of the four.
The Stack
Every project ran on the same five-tool core:
| Tool | Role |
|---|---|
| Next.js 15 | Frontend — App Router, server components, fast by default |
| Supabase | Database + auth — PostgreSQL, row-level security, real-time |
| Vercel | Deployment — CI/CD, edge functions, instant rollbacks |
| Claude Code | Building — whole features from a prompt, not just autocomplete |
| Antigravity | Multitasking — IDE-level context management across 3 open projects |
The GitHub Student Pack covered domain credits and most hosting costs. Total out-of-pocket infrastructure spend across all four sites in month one: close to zero.
Timeline Breakdown
| Days | Work |
|---|---|
| 1–5 | santoshpaudel.me — scaffold, Supabase schema, admin panel modules |
| 6–7 | TheWestNepal.live — WordPress migration, stack rebuild, 60+ pages |
| 8–15 | agenticai01.tech — multi-subdomain architecture, Azure integration |
| 16–22 | Gaming platform backend — client project, full API layer |
| 23–25 | SEO pass across all 4 sites, sitemap automation, final deploys |
Days 8–15 had me actively switching between two or three projects daily.
What Actually Made It Possible
AI tooling changed the ratio of thinking to typing. With Claude Code, a feature that previously took 3–4 hours to scaffold — database schema, API routes, frontend component, error states — now takes under an hour. I still review and edit every line. But the gap between decision and running code collapsed.
The mental model I kept returning to: I am the architect. Claude Code is the contractor.
A repeatable build sequence per project. Every site followed the same order: schema → Next.js scaffold → Supabase wiring → admin panel → content → SEO → deploy. I never had to redecide the sequence. By project three, I was reusing Supabase table structures, component patterns, and environment variable conventions across projects.
The GitHub Student Pack removed the cost constraint. Free domain credits and hosting meant I could run four projects simultaneously without choosing which one to prioritize based on budget.
What Broke First
Context-switching. The first day I worked on two projects, I spent 30 minutes re-reading my own code. Antigravity helped by preserving state between sessions, but the early cost of switching was real. The fix: one project gets the first two hours of the day, always.
Treating SEO as an afterthought. On the first project, I added sitemaps, schema markup, and meta tags at the very end. Six hours of cleanup that should have been automated from day one. By project three, auto sitemap generation was built before the first content page went live.
Lessons
- —Build the admin panel first. Every project ends up needing one.
- —Automate SEO scaffolding on day one — sitemap generation, schema injection, robots.txt.
- —The stack matters less than the sequence. What determines speed is how fast you move from idea to database record to deployed feature.
- —Parallel projects need hard time boundaries. Without them, every project gets half-attention for the full day, which is slower than giving one project full attention for half the day.
What Is Next
The build sprint is done. The growth sprint has started. The four sites are live. Now the focus shifts to programmatic content, LinkedIn distribution, and automating the lead funnel so new inquiries do not sit in a database waiting to be noticed.
Frequently Asked Questions
How long does it take to build a full-stack site with Next.js and Supabase? With a defined build sequence and AI tooling, a production-ready full-stack site takes 3–7 days. Without that structure, budget 2–4 weeks.
Is the GitHub Student Pack worth it for developers? Yes, especially for anyone running multiple projects. Free domain credits and hosting remove the cost constraint entirely during a build sprint.
Can one developer realistically run 3–4 projects at once? With strict context management and a daily schedule (project A owns the morning, project B owns the afternoon), yes. Without those constraints, the context-switching cost eats most of the time you save with speed tools.
What is Claude Code? Claude Code is an AI coding tool by Anthropic that runs from the terminal. It handles whole features from a prompt — scaffolding routes, writing Supabase queries, wiring components. It is closer to pair programming with someone who is fast and never gets tired, as long as you review the output carefully.
Resources
- —Next.js App Router — the framework powering all four platforms; server components and ISR are the core features
- —Supabase pricing tiers — what the free tier covers and when to upgrade
- —Vercel hobby tier — what is included at zero cost and where the limits are
- —GitHub Education — how to verify student status and claim the pack; takes 1–7 days
Related Posts
- —The GitHub Student Pack Stack: Free Domain, Free Hosting, Real Production Sites — the exact tools from the pack I used to keep infrastructure cost at zero
- —Case Study: santoshpaudel.me — A Portfolio That Runs Like a Business — deep-dive on the first and most complex platform from the sprint
- —My Claude Code and Antigravity Workflow for Running 3 Projects at Once — the daily system that made parallel project work manageable without losing state
Need a full-stack platform built fast? This is exactly what I do — Next.js, Supabase, Vercel, admin panel included, production-ready in days not months. See my services or get in touch directly.
Get the free AI Prompt Pack + weekly frameworks
30+ tested prompts for images, captions, scripts & keywords, delivered instantly. Plus real insights on AI + marketing — no generic tips.
Want to implement this with guidance?
Santosh helps founders turn insights like this into real systems.
External Resources
Further Reading & Tools
Content Marketing Institute
Annual content marketing benchmarks — budgets, channels, and outcomes
HubSpot Marketing Blog
Data-driven marketing research, inbound strategy, and content guides
Semrush Blog
SEO, content, and digital marketing research and strategy guides
Marketing Week
UK's leading marketing news, strategy insight, and industry research