Build a SaaS with Claude in a week: the real sprint

Building a SaaS in a week used to be a marketing promise. In 2026, with an AI-native boilerplate and Claude Code, it's a realistic timeline. Not a Frankenstein demo: a SaaS with auth, billing, dashboard, and deploy. This guide walks through a 7-day sprint to take a SaaS from idea to first customer. The trick isn't working more hours. It's delegating to the agent everything you can delegate. ## Monday: idea and kickoff - **AM**: define in 5 sentences what problem you solve, for whom, and the first feature worth paying for. - **PM**: clone your AI-native boilerplate. Set `.env`. Launch Claude Code and say: > "Customize this boilerplate for [SaaS X]. Change the branding, rewrite the landing copy for the > given ICP, set up the DB." By Monday evening the boilerplate is running with your name and your landing. ## Tuesday: auth and onboarding Auth comes from the boilerplate. Tuning is what's left: - Allow OAuth? (Google, GitHub, LinkedIn) - 2FA optional or required? - Onboarding flow (wizard, single step)? Tell the agent: > "Configure the onboarding flow per the feature rules. Ask for name, company, plan selection. Send > welcome email via Resend." By evening: users can sign up, onboard, get email. ## Wednesday: core feature The bulk of the product. Whatever the feature, the pattern is the same: 1. Model in Prisma 2. Server actions / API handlers 3. Pages and components 4. Run `/verify` and fix what comes up Give the agent the spec in plain English and let it run. You review commits and feedback. By Wednesday evening, the feature works end-to-end. ## Thursday: billing and plans Polar or Stripe (depends). The boilerplate has the webhooks. What you tune: - Products in the payment provider dashboard - Plan → permissions mapping - Upgrade and cancel UI > "Wire Polar products (free, starter, pro) to the app's permissions. Show upgrade UI in the > dashboard." By evening: someone can pay, their role changes, they see premium features. ## Friday: polish and bugs The ugly but critical day. Test: - Sign up → onboarding → core feature → upgrade - Cancel → downgrade - Edge cases (empty form, duplicate email, payment failure) > "Run @quality-checker. Report what's broken." Fix what the agent finds. Improve copy. Add Sentry or equivalent. ## Saturday: deploy - Set up production (Hetzner + Coolify, Vercel, Railway, whatever). - Real environment variables. - Domain. - SSL. - Production DB. > "Deploy to [provider]. Verify the app responds and webhooks arrive." By evening: you're in production. ## Sunday: launch - Email your list (even if it's 30 people). - Post on LinkedIn / X / IndieHackers. - DM your 5 closest contacts in the ICP. - Enable analytics (Plausible, Umami, Clarity). If one person signs up, you've hit the sprint's goal. ## Typical sprint mistakes **1. Scope creep mid-week**: "since I'm here, let me add X". Kills the sprint. Park extras for v1.1. **2. Using the agent as autocomplete only**: if you type everything, the sprint stretches to 3 weeks. Delegate full blocks. **3. Skipping testing**: the sprint is tight, we know. But Friday's QA day is non-negotiable. **4. Launching without email**: a landing and "we'll see" doesn't work. Sunday's email is mandatory. ## What makes it work - **AI-native boilerplate**: hour 0 starts at km 80, not km 0. - **Solid CLAUDE.md**: the agent doesn't improvise, it follows your rules. - **Real sprints, not marathons**: 8h a day, not 16. If you can't make it, cut scope, not health. ## Bottom line A week for a SaaS in 2026 is viable, not heroic. The epic shift is the model: the human does product and direction; the agent does code and verification. If you didn't ship what you wanted in 1 week, look at the boilerplate and the CLAUDE.md first. That's where the time is usually lost.