Most agencies quote 3–6 months for a web app. We consistently ship in 4 weeks. Here's the exact framework — from brief to production deploy — including the AI tools that cut our build time by 60%.
Week 1 — Discovery & Architecture
We spend the first week locking down scope. No wireframe gets drawn until we have a one-page product spec the client signs off on. We use Claude to synthesise user-research notes into a requirements doc in under an hour. Stack decisions happen here: Next.js + Supabase for most apps, Django REST for anything with heavy data processing.
Week 2 — Core Build
We scaffold with AI assistance — Cursor IDE with our in-house prompt library handles boilerplate, auth flows and CRUD scaffolding. This is where the 60% time saving lands. Developers focus on custom business logic; AI handles the repetitive plumbing.
Week 3 — Integration & QA
Third-party APIs, payment gateways, and ERPNext hooks get wired in. Our 140-point QA checklist covers performance, security headers, mobile responsiveness and edge cases. AI-generated test suites cover 80% of unit tests automatically.
Week 4 — Deploy & Handover
We deploy to AWS or Hetzner depending on budget, configure CI/CD via GitHub Actions, and run a live walkthrough with the client. Documentation is auto-generated from code comments using a custom script.
Key insight: scope lock before any design work begins is the single biggest factor in hitting the 4-week target. Scope creep in week 2 or 3 is what breaks most project timelines.
Tools we use
- Cursor IDE with custom prompt library for scaffolding
- Claude API for requirements synthesis and test generation
- GitHub Actions for CI/CD pipeline automation
- Supabase for auth, database and storage in one
- Vercel or Hetzner for hosting depending on budget
