The Problem with Traditional Development Timelines

Search "how long does it take to build an MVP" and you'll find estimates ranging from 3 months to a year. That's ridiculous.

Traditional agency timeline breakdown:

• Weeks 1-2: Discovery and requirements (meetings, meetings, more meetings)
• Weeks 3-5: Wireframing and design (waiting for revisions)
• Weeks 6-7: Design revisions (more waiting)
• Weeks 8-9: "Technical architecture document" (unnecessary for MVPs)
• Weeks 10-22: Development (sequential phases, no testing until the end)
• Weeks 23-24: Testing and bug fixing (finding problems you could have caught earlier)
• Weeks 25-26: "Stabilisation" (fixing bugs that shouldn't exist)

Total: 26 weeks (6 months)

This waterfall approach is outdated, expensive, and unnecessarily slow.

Modern sprint approach:

• Week 1: Discovery, PRD, complete UX design
• Week 2: Core development and deployment
• Week 3-4: Additional features and polish (if needed)

Total: 2-4 weeks

We'll show you how this actually works, what can realistically be accomplished each week, and why the traditional approach wastes so much time.

How to Use This Guide

We've broken down timelines by product type and shown you:

• Week-by-week breakdown of what actually happens
• What's being built and when you can test it
• Critical path items that can't be parallelised
• Optional add-ons and when to tackle them
• Common delays and how to avoid them

Product types we'll cover:

1. Simple web applications (2 weeks)
2. Mobile-first applications (2-3 weeks)
3. Marketplace platforms (4-6 weeks)
4. AI-powered applications (3-4 weeks)
5. Complex SaaS products (6-8 weeks)

Timeline assumptions:

• You can make decisions quickly (within 24 hours)
• You're available for daily 15-minute check-ins
• Scope is fixed before starting
• You have content ready (copy, images, etc.)
• You're not building Instagram

Before Your Sprint Starts: The Pre-Work

Free 30-Minute Discovery Call

Your first contact with us. We discuss:

• Your product idea and core problem you're solving
• Target users and market
• Must-have features vs nice-to-have
• Technical feasibility
• Rough timeline and budget
• Whether an MVP sprint is the right approach

Outcome: We both decide if this is a good fit. No commitment, no pressure.

Book your free discovery call

After You Book: The Pre-Flight Call

This happens before Day 1 of your sprint.

Duration: 2-3 hours
Who attends: All stakeholders (founders, product leads, anyone with decision-making authority)

What we cover:

• Deep dive into business goals and success metrics
• Detailed user workflows and journeys
• Every feature requirement in detail
• Technical constraints and preferences
• Existing brand guidelines or design requirements
• Integration requirements
• Success criteria for the MVP
• Any existing designs or specifications you have

Critical: This is where we get everything on the table. The more thorough this call, the smoother the sprint.

After Pre-Flight: PRD and Development Plan

Before Day 1 of the sprint, we create:

Product Requirements Document (PRD):

• Complete feature specifications
• User flows for all core workflows
• Data models and database schema
• Technical architecture decisions
• API endpoint definitions
• Third-party integrations needed
• Success metrics and analytics requirements

Development Plan:

• Day-by-day build schedule
• Technical approach for each feature
• Risk areas and mitigation strategies
• Testing plan
• Deployment strategy

You review and sign off on the PRD. Once approved, this becomes the blueprint for the sprint.

This pre-work typically takes 2-3 days between booking and sprint start.

Week 1: The Sprint (Simple Web Application)

Examples: Booking systems, simple CRMs, form builders, scheduling tools, waitlist managers

Days 1-4: Building Your MVP

We're building, not designing. Using the signed-off PRD as our guide, we're writing code and creating your product.

What's happening each day:

Day 1:

• Project setup (repo, hosting, database)
• Authentication system implementation
• Database schema setup
• Core infrastructure in place

Day 2:

• Main feature #1 development (frontend + backend)
• API endpoints for core functionality
• User interface implementation
• Basic navigation and routing

Day 3:

• Main feature #2 development
• Integration between features
• User settings and preferences
• Email notifications setup

Day 4:

• Remaining core features
• Form validation and error handling
• Loading states and user feedback
• Mobile responsiveness
• Initial testing and bug fixes

Every night, you receive:

• 15-30 minute show-and-tell video showing progress
• What we built that day
• Any blockers or decisions needed
• What's planned for tomorrow

If needed: We schedule stand-up calls to discuss problems, answer questions, or make decisions on trade-offs.

Important: We don't typically create Figma designs during the sprint unless:

• You already have designs we're implementing
• You've completed a UX Sprint with us first (separate 5-day design sprint)

We build functional MVPs focused on workflows and usability, not pixel-perfect mockups.

Day 5: Testing, Polish, and Handover

Morning:

• Final bug fixes and edge cases
• Performance optimisation
• Security review
• Cross-browser/device testing

Afternoon:

• Production deployment
• Set up monitoring and analytics
• SSL certificate and custom domain
• Final testing on production
• Handover session (30-60 minutes)

Handover includes:

• How to access admin areas
• How to make simple content changes
• Overview of the tech stack
• Documentation for common tasks
• Access to all services (hosting, database, etc.)

By End of Week 1, You Have:

A working, deployed MVP that:

• Handles user authentication
• Implements your core workflows
• Stores data in a proper database
• Is accessible via your custom domain
• Has basic analytics integrated
• Is production-ready for beta users

You can immediately:

• Share with beta testers
• Start getting real user feedback
• Test your core assumptions
• Begin validating your business model

Cost: £12,500
Timeline: 5 working days

Week 2 (Optional): For Complex Products or Additional Polish

Week 2 is only needed if:

1. Your product is more complex (marketplace, AI features, advanced workflows)
2. You want additional polish from Week 1
3. You're submitting to app stores and need that preparation
4. You need add-on services (branding, marketing website, etc.)

Week 2: Additional Development

Days 6-9: Advanced Features

• Complex features that couldn't fit in Week 1
• Additional integrations
• Advanced workflows
• Performance optimisation
• Extended testing

Day 10: Final Polish and Delivery

• Bug fixes from Week 1 feedback
• Final refinements
• Additional testing
• Updated documentation

Cost: £12,500

Week 2: App Store Preparation

If you're building a mobile app and want to submit to app stores:

You'll need:

1. Marketing Website (£5,000) - Required by Apple and Google
   • Privacy Policy page (mandatory)
   • Terms of Service page (mandatory)
   • Account Deletion page (mandatory for apps with accounts)
   • Support/Contact page
   • Homepage
2. App Store Assets (£3,000)
   • Screenshots for all device sizes (iOS and Android)
   • App descriptions (short and long)
   • Preview video
   • App icons (all required sizes)
   • Keyword research and optimisation

Timeline:

• Days 6-8: Create marketing website
• Days 9-10: Create app store assets
• Day 11: Submit to App Store and Google Play
• Days 12-14: Address any review feedback

Total with app store prep: £20,500 (£12,500 Week 1 MVP + £5,000 website + £3,000 assets)

Week 2: Launch Package Preparation

If you don't have branding or marketing materials:

Go-To-Market Package - £16,500 (save £3,200)

• Marketing Website (£5,000)
• Branding Package (£5,000)
• App Store Assets (£3,000)
• Email Marketing Setup (£2,500)
• Social Media Setup (£1,200)
• Content Starter Pack (£3,000)

Timeline:

• Days 6-8: Marketing website and branding
• Days 9-10: App store assets and social media
• Days 11-15: Content creation and email marketing setup

Total: £25,000 (Week 1 MVP) + £16,500 (Go-To-Market) = £41,500

‍

Week 1: Mobile-First Application Sprint

Examples: Fitness trackers, habit tracking apps, social apps, content consumption apps

Pre-Sprint (Same as Above)

• 30-minute discovery call
• Pre-flight call (2-3 hours)
• PRD and development plan created
• Client signs off

Days 1-4: Building Your Mobile MVP

Day 1:

• React Native (Expo) or Capacitor project setup
• Authentication implementation
• Backend API setup (Node.js + Supabase)
• Database schema implementation
• Navigation structure

Day 2:

• Main feature #1 (e.g., feed/list view)
• Image upload functionality
• Basic caching for offline functionality
• User profiles

Day 3:

• Main feature #2 (e.g., create/edit flow)
• Push notification setup
• Integration between features
• Data synchronisation

Day 4:

• Remaining core features
• App icons and splash screens
• Loading states and error handling
• Testing on iOS and Android devices
• Performance optimisation

Every night: 15-30 minute show-and-tell video with progress

Day 5: Testing and Handover

• Final bug fixes
• Cross-device testing (various iOS and Android devices)
• Production deployment of backend
• TestFlight and internal testing setup
• Handover session

By end of Week 1, you have:

• Working iOS and Android apps
• Backend API deployed
• Apps installed on your devices via TestFlight/internal testing
• Push notifications configured
• Ready for beta testing

Cost: £12,500

Week 2 (Optional): App Store Submission

Only if you want to submit to app stores immediately.

You'll need:

1. Marketing Website (£5,000) - Required by Apple/Google
   • Privacy Policy, Terms of Service, Account Deletion pages
   • Support/Contact page
   • Homepage
2. App Store Assets (£3,000)
   • Screenshots for all device sizes
   • App descriptions and keywords
   • Preview video
   • App icons (all sizes)

Timeline:

• Days 6-8: Create marketing website
• Days 9-10: Create app store assets
• Day 11: Submit to App Store and Google Play
• Days 12-14: Address review feedback

Alternative: Launch Week 1 build as TestFlight/internal testing, gather feedback, then submit to stores after validation.

Cost Options:

• Week 1 only (MVP for beta testing): £12,500
• Week 1 + marketing website + app store assets: £20,500 (£12,500 + £5,000 + £3,000)
• Week 1 + Week 2 + app store prep: £33,000 (£25,000 + £5,000 + £3,000)

Timeline: 1-3 weeks (depending on options chosen)

Book a free discovery call to discuss your mobile app timeline.

Marketplace Platform Sprint (4-6 Weeks)

Examples: Booking platforms, freelance marketplaces, rental platforms, two-sided marketplaces

Marketplaces take longer because you're building for two user types (buyers and sellers/providers) plus payment processing.

Pre-Sprint

• 30-minute discovery call
• Pre-flight call (2-3 hours) - covering both user types
• Detailed PRD covering buyer journey, seller journey, and platform features
• Client signs off

Week 1-2: Core Marketplace Development

Week 1: Days 1-5

Days 1-2: Foundation

• Authentication for both user types
• Database schema for users, listings, and bookings
• Basic navigation for both user flows
• Role-based routing

Days 3-4: Seller Side

• Seller onboarding
• Listing creation and management
• Image uploads
• Pricing and availability
• Basic seller dashboard

Day 5:

• Testing and refinement
• Show-and-tell video

Week 1 Result: Sellers can create and manage listings

Cost: £12,500

Week 2: Days 6-10

Days 6-7: Buyer Side

• Search and filtering functionality
• Listing detail pages
• Booking flow
• Booking confirmation

Days 8-9: Payment Integration

• Stripe integration
• Checkout process
• Payment processing
• Confirmation emails

Day 10:

• End-to-end testing (browse, book, pay)
• Bug fixes and polish
• Show-and-tell and handover

Week 2 Result: Complete transaction flow working

Cost: £12,500

You can test: Full user journey from browsing to booking to payment

Weeks 3-4 (Optional): Platform Features and Polish

Week 3: Days 11-15

Days 11-12:

• Messaging system between buyers and sellers
• Notification system

Days 13-14:

• Reviews and ratings
• Booking management
• Calendar/availability system

Day 15:

• Testing and refinement

Cost: £12,500

Week 4: Days 16-20

Days 16-17:

• Admin dashboard (basic moderation tools)
• Stripe Connect setup (marketplace payments and payouts)
• Payout configuration

Days 18-19:

• Advanced search features
• Map integration (if location-based)
• User verification features

Day 20:

• Final testing and polish
• Documentation

Cost: £12,500

Total Options:

• Core MVP: £25,000 | 2 weeks (basic buyer/seller flow + payments)
• With Platform Features: £37,500 | 3 weeks (adds messaging, reviews, bookings)
• Complete Platform: £50,000 | 4 weeks (adds admin dashboard, advanced features)
• With Polish and Launch: £62,500-£75,000 | 5-6 weeks

Book a free discovery call to discuss your marketplace timeline.

AI-Powered Application Sprint (2-4 Weeks)

Examples: ChatGPT-style interfaces, document processing, recommendation engines, AI assistants

Pre-Sprint

• 30-minute discovery call
• Pre-flight call (2-3 hours) including AI strategy discussion:
  • Define core AI use case
  • Choose AI provider (OpenAI, Anthropic, or custom)
  • Expected inputs and outputs
  • Accuracy requirements
  • RAG vs fine-tuning vs straight API calls
  • Cost modelling for API usage
• Detailed PRD with AI implementation strategy
• Client signs off

Week 1: Core AI Application

Days 1-2: Foundation

• Frontend setup
• User authentication
• Backend API setup
• AI provider integration (OpenAI/Anthropic API)
• Basic input/output interface

Days 3-4: Core AI Functionality

• Prompt management system
• Input processing
• AI API calls and response handling
• Result processing and display
• Usage tracking and rate limiting

Day 5:

• Testing with various inputs
• Prompt optimisation
• Error handling for AI failures
• Performance optimisation
• Show-and-tell and handover

By end of Week 1, you have:

• Working AI application
• Users can input data and get AI-generated results
• Usage tracking in place
• Ready for beta testing

Cost: £12,500

Important: Budget £500-£2,000/month for AI API costs during development and testing.

Week 2-3 (Optional): Advanced AI Features

If you need RAG (Retrieval-Augmented Generation):

Week 2: Days 6-10

Days 6-7:

• Document upload and processing
• Vector database setup (Pinecone or Supabase pgvector)
• Embedding generation

Days 8-9:

• Retrieval implementation
• RAG pipeline integration
• Context management

Day 10:

• Testing and optimisation
• Result ranking and relevance tuning

Cost: £12,500

Week 3 (Optional): Polish and Monetisation

Days 11-15:

• Credit/token system
• Subscription billing setup (Stripe)
• Usage analytics and monitoring
• Advanced prompt templates
• User feedback system

Cost: £12,500

Total Options:

• Basic AI App: £12,500 | 1 week (straight API integration)
• With RAG: £25,000 | 2 weeks (document processing and context)
• Complete Platform: £37,500 | 3 weeks (adds billing, analytics, advanced features)

Book a free discovery call to discuss your AI application timeline.

Complex SaaS Product Sprint (4-8 Weeks)

Examples: Multi-tenant platforms, team collaboration tools, enterprise features

Our recommendation: Build in phases. Validate single-tenant version first before investing in multi-tenancy and enterprise features.

Phase 1: Single-Tenant MVP (2 Weeks)

Pre-Sprint

• 30-minute discovery call
• Pre-flight call (2-3 hours)
• PRD focusing on single-user workflow
• Ignore team/organisation features for now
• Client signs off

Week 1-2: Days 1-10

Days 1-3:

• Project setup and authentication
• Core feature #1 development
• Database schema (single-tenant)
• User settings and preferences

Days 4-7:

• Core feature #2 and #3
• Integration between features
• Email notifications
• Dashboard and analytics

Days 8-10:

• Billing integration (if needed)
• Testing and bug fixes
• Polish and deployment
• Documentation and handover

By end of Phase 1, you have:

• Working single-user product
• Core workflows functional
• Ready for beta testing

Cost: £25,000

Decision point: Test with 10-20 users before proceeding. Validate that people will actually pay for this.

Phase 2: Multi-Tenancy (2 Weeks)

Only proceed if Phase 1 validates.

Pre-Sprint

• Review Phase 1 learnings
• Updated PRD for multi-tenancy
• Client signs off on Phase 2 scope

Week 3-4: Days 11-20

Days 11-13:

• Refactor for organisation/team structure
• Data isolation architecture
• Team member invitations
• Basic role-based permissions

Days 14-17:

• Shared workspace features
• Team dashboard
• Activity feeds
• Organisation settings

Days 18-20:

• Testing multi-tenant scenarios
• Data isolation verification
• Polish and deployment

By end of Phase 2, you have:

• Multi-tenant platform
• Team collaboration features
• User roles and permissions

Cost: £25,000

Phase 3: Billing and Enterprise Features (2-4 Weeks)

Week 5-6: Subscription Billing

Days 21-25:

• Stripe Billing integration
• Subscription plan management
• Payment method handling
• Billing portal
• Usage-based billing (if needed)

Days 26-30:

• Advanced onboarding flow
• Improved email notifications
• Admin dashboard enhancements
• Analytics and reporting
• Performance optimisation

Cost: £25,000

Weeks 7-8 (Optional): Enterprise Features

Only if selling to enterprises:

Days 31-35:

• SSO integration (SAML, OAuth)
• Advanced RBAC (Role-Based Access Control)
• Audit logging
• Compliance features

Days 36-40:

• API access for integrations
• Webhooks
• Advanced reporting
• Data export features
• Security enhancements

Cost: £25,000

Total Options:

• Single-Tenant MVP: £25,000 | 2 weeks
• With Multi-Tenancy: £50,000 | 4 weeks
• With Billing: £75,000 | 6 weeks
• With Enterprise Features: £100,000 | 8 weeks

Recommended Path: Validate each phase before investing in the next.

Book a free discovery call to discuss your SaaS timeline.

What Actually Causes Delays in MVP Development

1. Unclear Requirements Before Sprint Starts (Adds 1-2 Weeks)

The problem:

• Skipping the pre-flight call
• "We'll figure it out as we go"
• No PRD signed off before Day 1
• Stakeholders not aligned

The solution:

• Thorough 2-3 hour pre-flight call with all stakeholders
• Complete PRD before sprint starts
• Client signs off on exact scope
• All questions answered before Day 1

Time saved: 1-2 weeks of back-and-forth during sprint

2. Slow Decision-Making During Sprint (Adds 3-7 Days)

The problem:

• Taking 2-3 days to review nightly videos
• Can't make decisions on trade-offs
• Multiple stakeholders who aren't available
• "Let me get back to you next week"

The solution:

• Watch and respond to nightly videos within 24 hours
• Attend stand-up calls when blockers arise
• Empower one person to make final decisions
• Be available for quick decisions during sprint week

Time saved: 3-7 days

3. Scope Creep Mid-Sprint (Adds 1-3 Weeks)

The problem:

• "Can we add this feature?"
• "Actually, let's change that workflow"
• "I just thought of something..."
• No discipline around fixed scope

The solution:

• PRD is locked once sprint starts
• New ideas go into "Phase 2" backlog
• Change requests assessed for Week 2 or later
• Sprint scope never changes

Time saved: 1-3 weeks

4. Missing Content or Assets (Adds 3-10 Days)

The problem:

• "We'll get you the copy next week"
• "Logo is still being designed"
• "We need to approve that with legal"
• Waiting for content blocks development

The solution:

• Have all copy, images, and brand assets ready before sprint
• Get legal approvals before sprint starts
• Use placeholder content if needed, replace later
• Don't block development on missing content

Time saved: 3-10 days

5. Unrealistic Feature Expectations (Adds 1-4 Weeks)

The problem:

• Expecting Instagram in 1 week
• Including "nice to have" as "must have"
• Complex features without understanding trade-offs
• Not prioritising ruthlessly

The solution:

• Pre-flight call clarifies what's realistic in 1-2 weeks
• PRD clearly marks P0 (must-have) vs P1 (should-have) vs P2 (nice-to-have)
• Only P0 features make it into Week 1
• Everything else goes into Phase 2

Time saved: 2-4 weeks

6. Technical Surprises (Adds 3-10 Days)

The problem:

• Late discovery of technical constraints
• Required integrations not mentioned
• Legacy system dependencies
• Complex data migration needs

The solution:

• Discuss all technical constraints in pre-flight call
• Mention all required integrations upfront
• Share existing systems and APIs before sprint
• Flag any data migration needs early

Time saved: 3-10 days

Timeline Comparison: Traditional vs Sprint Approach

Example: Simple Booking Application

Traditional Agency Timeline:

Weeks 1-2: Discovery and Requirements

• Multiple stakeholder meetings
• Requirements gathering sessions
• User research
• Competitive analysis
• Written proposal and SOW
• Contract negotiations

Weeks 3-5: Design Phase

• Low-fidelity wireframes
• Wait for client feedback (1 week)
• High-fidelity mockups
• Wait for client feedback (1 week)
• Revision rounds
• Design system documentation

Week 6: Technical Planning

• Architecture document
• Database design
• API specification
• Infrastructure planning
• Technology stack decisions

Weeks 7-12: Backend Development

• Database setup
• API development
• Authentication system
• Business logic
• Third-party integrations
• Testing

Weeks 13-18: Frontend Development

• Component development
• API integration
• Styling and responsive design
• User flows implementation
• Cross-browser testing

Weeks 19-20: Integration Testing

• End-to-end testing
• Bug fixing
• Performance optimisation
• Security review

Weeks 21-22: Deployment and "Stabilisation"

• Production environment setup
• Deployment
• Final testing
• Bug fixes from production issues
• Documentation
• Knowledge transfer

Total: 22 weeks (5.5 months)
Cost: £88,000-£132,000

Precode Sprint Approach:

Before Sprint Starts:

• Day -7: Free 30-minute discovery call → Feasibility assessment
• Day -3: Pre-flight call (2-3 hours) → Deep dive on requirements with all stakeholders
• Days -2 to -1: PRD and development plan created → Everything documented before Day 1
• Day 0: Client signs off on PRD → Locked scope, ready to build

Week 1: Sprint (Days 1-5)

Day 1: Project setup, authentication, database foundation
Day 2: Core feature #1 development
Day 3: Core feature #2 development
Day 4: Remaining features, integration, testing
Day 5: Polish, deployment, handover

Nightly: 15-30 minute show-and-tell videos
As needed: Stand-up calls for blockers

Total: 1 week (5 working days)
Cost: £12,500

What Changed?

1. Pre-sprint PRD replaced weeks of meetings: One thorough 2-3 hour pre-flight call with all stakeholders replaces weeks of scattered meetings and revision rounds
2. No separate design phase: We build functional interfaces based on requirements, not pixel-perfect mockups. You can always add polish post-validation.
3. No technical architecture phase: Modern stacks (Next.js, Supabase, Vercel) eliminate weeks of infrastructure planning. Proven patterns, not custom architecture.
4. Concurrent development: Frontend, backend, and testing happen simultaneously throughout the week, not sequentially over months.
5. Daily feedback: Nightly videos replace formal revision rounds. Issues caught immediately, not after weeks of development.
6. Fixed scope: PRD is locked before Day 1. No scope creep, no feature additions, no timeline drift.
7. Managed services: Supabase for auth/database/storage instead of building custom. Stripe for payments. Weeks of development eliminated.
8. No "stabilisation": Testing happens throughout sprint, not at the end. Deploy on Day 5 with confidence, not hope.

Result: 21 weeks saved (95% faster), £75,500-£119,500 saved (60-90% cheaper)

Add-On Services and Timeline Impact

If You Need Branding (Add 3-5 Days)

What's included:

• Logo design (primary and variations)
• Brand colour palette
• Typography system
• Brand guidelines document
• Social media profile images

Timeline:

• Can run in parallel with Week 1 if needed
• Or complete before MVP sprint starts

Cost: £5,000

If You Need Marketing Website (Add 5-7 Days)

What's included:

• Homepage design and development (Webflow)
• Privacy Policy, Terms of Service, Account Deletion pages
• Contact/Support page
• Copy written for all pages
• Basic SEO setup
• Managed hosting: +£25/month (optional)
• Blog/CMS setup: +£1,500 (optional)

Timeline:

• Week 3 after MVP complete
• Or can start during Week 2 of MVP

Important: Required for app store submission. Apple and Google require publicly accessible Privacy Policy, Terms of Service, and Account Deletion pages.

Cost: £5,000

If You Need App Store Submission (Add 3-5 Days)

What's included:

• App Store Assets (£3,000)
• Screenshots for all device sizes
• App descriptions
• Preview video
• Keyword research
• Submission assistance

Timeline:

• Can start during final days of development
• Submission itself takes 1-2 days
• Apple review: 1-3 days typically
• Google review: few hours to 2 days

Note: You must have a marketing website with required pages before submitting.

If You Need Full Launch Package

Go-To-Market Package - £16,500 (save £3,200)

• Marketing Website (£5,000)
• Branding (£5,000)
• App Store Assets (£3,000)
• Email Marketing Setup (£2,500)
• Social Media Setup (£1,200)
• Content Starter Pack (£3,000)

Timeline:

• Week 1-2: MVP development (£25,000)
• Week 3: Marketing website and branding (can overlap)
• Week 4: App Store submission and content creation

Total: 4 weeks | £41,500 (MVP + Go-To-Market Package)

Book a free discovery call to discuss your complete launch timeline.

30-Day Launch Timeline: Complete Example

Real project: Mobile CRM for tradespeople (SalesLite)

Pre-Sprint (Days -7 to -1)

• Day -7: Free 30-minute discovery call
• Day -5: Client books sprint, pays deposit
• Day -3: Pre-flight call (2-3 hours, all stakeholders)
• Days -2 to -1: Precode creates PRD and development plan
• Day 0: Client reviews and signs off on PRD

Week 1 (Days 1-5): Core MVP Development

Day 1:

• React Native project setup
• Authentication system
• Backend API and database setup
• Voice recording functionality foundation

Day 2:

• Voice note recording and storage
• Customer database structure
• Basic UI for customer management
• Navigation between screens

Day 3:

• AI voice transcription integration (OpenAI Whisper)
• Structured data extraction from voice notes
• Customer profile screens
• Pipeline management foundation

Day 4:

• Quote generation logic
• Pipeline stage management
• Data sync between devices
• Push notifications setup

Day 5:

• Bug fixes and testing
• Performance optimisation
• TestFlight build
• Handover video and documentation

Nightly: 15-30 minute show-and-tell videos sent to client

Deliverable: Working mobile app with core CRM features, AI transcription, and quote generation

Cost: £12,500

Week 2 (Days 6-10): Polish and Additional Features

Day 6:

• Email integration for quotes
• PDF generation for quotes
• Improved UI/UX based on Week 1 feedback

Day 7:

• Customer search and filtering
• Activity history and notes
• Dashboard with key metrics

Day 8:

• Calendar integration
• Reminder notifications
• Data export functionality

Day 9:

• Advanced pipeline features
• Reporting and analytics
• Performance optimisation

Day 10:

• Final testing across devices
• Bug fixes
• App Store preparation
• Updated documentation

Cost: £12,500

Week 3 (Days 11-15): Marketing Website

Days 11-13:

• Homepage design and development in Webflow
• Privacy Policy page (required for App Store)
• Terms of Service page (required for App Store)
• Account Deletion page (required for App Store)
• Support/Contact page
• All copy written

Days 14-15:

• Review and refinements
• Domain setup and hosting
• SEO basics configured

Cost: £5,000

Week 4 (Days 16-20): App Store Submission

Days 16-17:

• Create App Store screenshots (all sizes for iOS and Android)
• Write app descriptions (short and long)
• Keyword research and optimisation
• Create preview video

Day 18:

• Prepare app icons for all required sizes
• Set up App Store Connect and Google Play Console

Day 19:

• Submit to Apple App Store
• Submit to Google Play Store

Day 20:

• Monitor for review feedback
• Address any initial issues

Cost: £3,000

Week 5 (Days 21-30): Launch Preparation and Soft Launch

Days 21-25:

• Beta testing with 20 tradespeople
• Gather feedback and identify bugs
• Make priority fixes

Days 26-28:

• Marketing materials creation (social media posts, launch email)
• Social media accounts setup
• Content calendar for first month

Day 29:

• Apple App Store approval received (typically 1-3 days)
• Google Play Store approval received (typically few hours to 2 days)
• Final pre-launch checks

Day 30:

• Public launch
• Social media announcement
• Email to waitlist
• Product Hunt submission

What was built in 30 days:

• Native iOS and Android apps
• AI voice note transcription using OpenAI Whisper
• Automated quote generation with PDF export
• Customer database with profiles and history
• Pipeline management with custom stages
• Dashboard with analytics
• Push notifications and reminders
• Marketing website with all required legal pages
• Complete App Store presence
• Ready for public launch

Total Cost:

• Week 1-2 MVP: £25,000
• Marketing Website: £5,000
• App Store Assets: £3,000
• Total: £33,000

Timeline: 30 days from kickoff to public launch (plus 7 days pre-sprint preparation)

Traditional agency estimate for same project: £80,000-£120,000 over 12-16 weeks

How to Compress Your Timeline Even Further

Start with Web, Add Mobile Later (Save 1-2 Weeks)

Approach:

1. Week 1-2: Build responsive web app (£25,000)
2. Test with users on mobile browsers
3. If validation succeeds, add React Native wrapper (1 week, £12,500)

Benefit: Launch 2 weeks faster, validate before investing in native apps

Use Pre-Built UI Components (Save 3-5 Days)

Instead of custom design everything:

• Start with Shadcn/UI or Chakra UI
• Customise colours and typography
• Focus on user flows, not pixel-perfect custom components

Benefit: Launch 1 week faster, can custom design later

Launch Without App Store Submission First (Save 1 Week)

Approach:

1. Deploy Week 2 build as TestFlight/web app
2. Test with 50-100 users
3. Submit to App Store only after validation

Benefit: Get user feedback 1-2 weeks earlier, avoid app store delays

Use Managed Services (Save 1-2 Weeks)

Don't build:

• Authentication → Use Clerk or Supabase Auth (save 1 week)
• Payments → Use Stripe Checkout (save 1 week)
• File uploads → Use Supabase Storage (save 3 days)
• Email → Use Resend or SendGrid (save 3 days)

Benefit: Save 2-3 weeks of development time

Have Content Ready (Save 3-5 Days)

Prepare before starting:

• Copy for all pages and screens
• Images and logos
• Product descriptions
• Terms and Privacy Policy (if you have existing ones)

Benefit: No waiting for content during development

Red Flags: When Timelines Are Unrealistic

Too Fast: "We Can Build It in 1 Week"

Red flags:

• Complex features (payments, AI, real-time features)
• "We'll just use templates"
• No design phase
• No testing plan

Reality: 1 week might work for very simple tools (landing pages, basic forms) but not for actual products with user accounts, databases, and business logic.

Too Slow: "It Will Take 9+ Months"

Red flags:

• Building for enterprise from day one
• Custom building everything from scratch
• "Future-proofing" for scale you don't need
• Extensive automated testing
• Multiple rounds of user research

Reality: Unless you're building something genuinely complex (marketplace with video calls, blockchain integration, custom ML models), 9+ months means you're not building an MVP.

Vague: "3-6 Months, Depending..."

Red flags:

• No week-by-week breakdown
• "It depends on requirements" (but no process to define requirements)
• Multiple revision rounds built into timeline
• Unclear milestones

Reality: A professional agency should be able to give you a firm timeline based on your requirements. "It depends" usually means "we don't have a process."

Timeline Decision Framework

If You Need to Validate ASAP (Budget: 2 Weeks)

Timeline:

• Week 1: Discovery and design (£12,500)
• Week 2: Core development (£12,500)Total: £25,000 | 2 weeks

Result: Working product, basic features, test with users

Next step: Gather feedback, iterate if validation succeeds

If You Need Public Launch (Budget: 3-4 Weeks)

Timeline:

• Week 1-2: MVP development (£25,000)
• Week 3: Marketing website and branding (£10,000)
• Week 4: App Store submission and polish (£3,000)

Total: £38,000 | 4 weeks

Result: Publicly launched product ready for user acquisition

If You're Building Marketplace (Budget: 4-6 Weeks)

Timeline:

• Week 1: Discovery and design (£12,500)
• Week 2-3: Core development (£25,000)
• Week 4: Platform features (£12,500)
• Week 5-6: Polish and launch prep (£12,500-£25,000)

Total: £50,000-£75,000 | 4-6 weeks

Result: Two-sided marketplace with payments

If You're Building Complex SaaS (Budget: 6-8 Weeks)

Timeline:

• Week 1-2: Single-tenant MVP (£25,000)
• Week 3-4: Multi-tenancy (£25,000)
• Week 5-6: Billing and polish (£25,000)
• Week 7-8: Enterprise features (£25,000) - optional

Total: £75,000-£100,000 | 6-8 weeks

Result: Full SaaS platform with teams and billing

Frequently Asked Questions

Can you really build a production-ready MVP in 1 week?

Yes, for simple web applications and mobile apps with straightforward features. Here's what makes it possible:

• Pre-sprint PRD: We know exactly what to build before Day 1
• No design phase during sprint: We build functional MVPs, not pixel-perfect mockups (unless you've done a UX Sprint with us first or have existing designs)
• Proven tech stack: We use tools and frameworks we know inside-out
• Fixed scope: No feature additions mid-sprint
• Daily progress: Nightly show-and-tell videos keep everything on track

We've delivered 50+ MVPs using this sprint methodology. It works when the process is disciplined and requirements are clear.

What's the difference between the free discovery call and the pre-flight call?

Free 30-minute discovery call:

• First contact with us
• High-level discussion of your idea
• Feasibility assessment
• Rough timeline and budget estimate
• Decide if we're a good fit
• No commitment

Pre-flight call (after you book):

• 2-3 hours with all stakeholders
• Deep dive into every feature requirement
• Technical constraints discussion
• Integration requirements
• Success criteria definition
• Everything we need to write the PRD

Think of discovery as "Should we do this?" and pre-flight as "How exactly will we do this?"

Do I need to have designs before starting?

No. We build functional MVPs focused on workflows and usability.

However, if you have designs:

• Already have Figma designs → We can implement them
• Completed our UX Sprint (5-day design sprint) → We have complete designs to build from
• No designs → We build functional interfaces based on the PRD

Most clients don't have designs and we build directly from requirements.

How much time do I need to commit during the sprint?

Before sprint:

• 30 minutes: Free discovery call
• 2-3 hours: Pre-flight call (all stakeholders)
• 30-60 minutes: Review and sign off on PRD

During sprint (5 days):

• 15-30 minutes nightly: Watch show-and-tell video and provide feedback
• 15-30 minutes as needed: Stand-up calls if blockers arise
• 30-60 minutes: Final handover session

Total: ~6-8 hours over 2 weeks (mostly in pre-sprint)

What if I need changes during the sprint?

Small changes (copy tweaks, colour adjustments, minor UI changes):

• Incorporated during daily development
• Mentioned in stand-up calls
• No impact on timeline

Major changes (new features, different workflows, scope additions):

• Go into "Phase 2" backlog
• Assessed for Week 2 or later
• Changing scope mid-sprint adds time and cost

Critical: The PRD is locked once the sprint starts. This discipline is what makes 1-week delivery possible.

What happens if we go past the 1-week timeline?

If delays are caused by:

• Client-side: Slow feedback, scope changes, missing content → Charged at £200/hour for extra time
• Our side: Technical issues, bugs, mistakes → We absorb the cost

In 50+ sprints, we've only gone past timeline when clients requested scope additions mid-sprint.

How quickly can we start?

Typical timeline:

• Today: Book discovery call
• This week: Discovery call (30 minutes)
• Next week: Book sprint and schedule pre-flight call
• Following week: Pre-flight call, PRD creation (2-3 days)
• Week after: Sprint starts (Days 1-5)

From first contact to working MVP: 2-3 weeks typically

We usually book 2-4 weeks in advance, but if you're urgent and we have capacity, we can sometimes start within a week.

Do you create Figma designs during the sprint?

Not during the 1-week MVP sprint. We're building, not designing.

If you need designs:

• Book our separate 5-Day UX Sprint (£10,000) which delivers complete Figma designs, prototypes, and design system
• Then book MVP Sprint to build from those designs
• Total: 2 weeks for design + build

Or:

• Bring existing designs and we implement them during the sprint

Most clients choose: Skip designs, build functional MVP, add polish later after validation.

Can you build faster if we pay more?

No. There's a minimum timeline for quality work regardless of budget.

Adding more developers often slows things down (coordination overhead). Our sprint methodology is optimised for speed without compromising quality.

What if we're not ready to start immediately?

Book your slot now (we're typically 2-4 weeks out). Use that time to:

• Prepare all content and copy
• Gather brand assets
• Get stakeholder alignment
• Secure any needed approvals
• Clarify requirements
• Get legal terms/privacy policy drafted (if needed for app stores)

The more prepared you are, the smoother the sprint.

How do the nightly show-and-tell videos work?

Every evening during the sprint, we send you:

• 15-30 minute video walkthrough
• Demo of what we built that day
• Working features you can test
• Any blockers or decisions needed
• Plan for tomorrow

You respond within 24 hours with:

• Feedback on what you saw
• Answers to any questions
• Decisions on trade-offs (if needed)
• Approval to continue or requested adjustments

This daily feedback loop is how we deliver in 5 days without revision rounds.

Do we need all stakeholders on the pre-flight call?

Yes, absolutely critical. The pre-flight call is where we nail down every requirement.

Must attend:

• Founder(s) or product owner
• Anyone with decision-making authority
• Technical lead (if you have one)
• Anyone who will need to sign off on features

Don't skip this: Missing stakeholders means questions arise during the sprint that slow us down. We've learned the hard way that a thorough pre-flight call prevents 90% of mid-sprint issues.

Book a free discovery call to discuss availability.

Ready to Launch Your MVP in 30 Days?

Stop wasting 6 months on slow agency processes.

Book a free 30-minute discovery call and we'll:

• Review your product idea
• Provide a realistic timeline based on complexity
• Show you examples of similar builds and their timelines
• Give you a detailed week-by-week breakdown

Book your free discovery call

What to prepare before the call:

• Brief description of your product idea
• Target launch date (if you have one)
• Must-have features for launch
• Any existing designs or specifications

No sales pressure. Just an honest conversation about whether we can hit your timeline.

Bottom Line

Real MVP timelines in 2025:

• Simple web application: 1 week (5 days)
• Mobile-first app: 1-2 weeks
• Marketplace platform: 2-6 weeks
• AI-powered app: 1-3 weeks
• Complex SaaS: 2-8 weeks

Add for public launch:

• Marketing website: 1 week (£5,000)
• App Store submission: 3-5 days (£3,000)
• Branding: 3-5 days (£5,000) - can run in parallel

Pre-sprint preparation: 1 week

• Free discovery call (30 minutes)
• Book sprint
• Pre-flight call (2-3 hours)
• PRD creation and sign-off (2-3 days)

Traditional agencies will quote 3-5x these timelines.

The difference? Thorough pre-sprint PRD, fixed scope locked before Day 1, nightly show-and-tell videos, modern tech stack, and a battle-tested process.

Most common timeline: 20-30 days from first contact to public launch

• Week -1: Discovery + pre-flight + PRD
• Week 1: MVP sprint (£12,500)
• Week 2: Additional features or polish (£12,500) - optional
• Week 3: Marketing website (£5,000) - if needed for app stores
• Week 4: App Store submission (£3,000) - if launching on app stores

Minimum: £12,500 | 1 week for working MVP
Typical with app store launch: £20,500 | 3 weeks
Full launch package: £33,000-£41,500 | 4 weeks

Get your custom timeline and find out exactly when your MVP can launch.

‍