Building a 20K+ Line Production SaaS Platform with Claude Code: Lessons from Agentic Engineering at Scale
Project Overview
LastSaaS is a production SaaS boilerplate with every line written through conversation with Claude Code. It's not a demo or toy—it powers a live platform called Flipbook. The stack includes Go 1.25, React 19, TypeScript, MongoDB, and Tailwind, released under MIT license.
What the Project Includes
- Complete SaaS foundation with multi-tenant auth (OAuth, MFA, magic links, JWT rotation)
- Stripe billing (subscriptions, per-seat, credits)
- White-labeling capabilities
- 19 webhook event types
- Admin dashboard and health monitoring
- Built-in MCP server with 26 read-only tools that let AI assistants query dashboards, users, billing, and health data
What Worked
Go's explicitness is an asset for agents: No framework magic means Claude Code doesn't have to guess what middleware is doing behind the scenes. Explicit error handling, clear routing, and predictable patterns help the agent stay on track.
Consistent patterns compound: Establishing patterns early for how handlers, services, and data access are structured allowed Claude to replicate them across dozens of endpoints with high consistency, dramatically reducing the tax on each new feature.
The MCP server was built by Claude for Claude: The 26 read-only tools create a meta interface where the AI built its own way to query the system.
MongoDB's document model simplified multi-tenancy: Claude had no trouble maintaining tenant isolation because the data model makes boundaries explicit, avoiding join-table confusion and leaky abstractions.
What Required Discipline
You still need architectural vision: Claude Code is a brilliant executor but doesn't design systems. The human must provide the architecture—knowing what multi-tenant RBAC should look like, how webhook delivery retries should work, and what the Stripe integration flow needs to be.
Review everything: Especially security-sensitive code like JWT rotation, HMAC signing, rate limiting, and injection protection. Claude gets it right most of the time, but "most of the time" isn't good enough for auth flows—every security-adjacent line needs human review.
Fight pattern drift: Over long sessions, Claude can subtly drift from established patterns. Periodically re-anchoring the conversation helps: "Look at how we implemented the user handler. Follow the same pattern for webhooks."
The "Built for Agents" Concept
The codebase is intentionally structured so that when someone forks it and points their own AI agent at it, the agent can extend it fluently. This includes predictable file structure, consistent naming, and explicit patterns—a foundation designed to be extended through conversation.
The repository is available at https://github.com/jonradoff/lastsaas.
📖 Read the full source: r/ClaudeAI
👀 See Also
Chuck Jones' Road Runner Rules as AI Agent Identity Design Principles
A Reddit post analyzes how Chuck Jones' 9 rules for Road Runner cartoons map to AI agent identity design, highlighting Rule 2 on internal failure modes, Rule 3 on avoiding optimization loops, and Rule 9 on graceful failure.
Building an Agentic Research System with Claude Code: A Practical Implementation
A developer details how they built six specialized agents using Claude Code to create a living map of 250+ real AI implementations, with a human-in-the-loop orchestration pattern.
OpenClaw User Proposes 'Sleep Cycle' Memory Compression for AI Agents
A non-developer OpenClaw user describes implementing a 'sleep cycle' approach to memory management, inspired by human forgetting and neuroscience research on dreams as memory compression. The user faced issues with growing databases, token costs, and agent contradictions.
Optimizing Moltbot with Key Integrations
An evaluation of almost every Moltbot integration reveals which tools actually improve productivity, highlighting integrations like Telegram and AgentPay.