Devesh JoshiCo-founder, product
Nine years building AI platforms serving 12,000+ engineers. LLM platforms, agentic systems (MCP), and multi-model safety evaluation.
What is realistic in a six-week MVP
Six weeks buys one core user workflow built properly for production. The primary failure mode is attempting three done poorly.
What six weeks actually delivers
A six-week sprint delivers one end-to-end user workflow, fully engineered, deployed to staging and production, backed by authentic user authentication, role security, and production database architecture. Not a design clickable wireframe — software real users can perform real transactions on.
That represents the complete engineering budget. High-performing product teams select one critical hypothesis and ruthlessly exclude secondary features until validation.
What falls outside a six-week scope
Elaborate multi-tier admin dashboards, complex permission hierarchies, custom billing engines, granular notification centers, and extensive settings pages. Each 'small' feature consumes an entire engineering week — compounding a 6-week scope into a 14-week delay.
Diffused UI polish across dozens of secondary screens. A targeted MVP prioritizes exceptional execution on one primary funnel over mediocre UI across twenty secondary pages.
Topic Focus & Target Concepts
This is the work behind our build practice — pitch-ready MVPs through to production applications, on a stack chosen for whoever maintains it after we leave.
Product and web app buildsRunning into this in your own stack? Twenty minutes, no deck.
Book the call