Rapid MVP Architecture Decision Framework

How to use

1. Describe your product and its core components in {{product_description}}.
2. List your real constraints (team size, timeline, budget, existing skills) in {{constraints}} — this materially changes the right recommendation.
3. Pay close attention to the 'deliberate technical debt' section and write those items down somewhere you'll actually revisit them, not just this conversation.
4. Treat the scaling cliff as an early warning system — check your actual usage against that threshold periodically.

Example input

Act as a pragmatic technical advisor... Product: A marketplace connecting freelance photographers with small businesses needing product photos, with booking, messaging, and payment. Constraints: solo founder, some coding ability, need to launch in 4 weeks, budget under $200/month for tools.

Example output

1. Build vs. buy vs. no-code: Auth — use a managed service (e.g. Clerk or Supabase Auth) rather than building custom, since auth security mistakes are costly and this is a solved problem. Payments — use Stripe Connect for marketplace payouts rather than building custom payment splitting logic, since payment compliance is high-risk to build yourself. Booking/scheduling — build a simple custom calendar component rather than a heavy no-code tool, since booking logic is core to your product's differentiation. Messaging — use a managed chat API (e.g. Stream or a simple in-app messaging table via Supabase) rather than building real-time infrastructure from scratch.
2. Speed-to-ship estimate: this stack likely ships in roughly one-third the time of a fully custom build, primarily because auth and payments (the highest-risk, highest-effort components) are offloaded to managed services.
3. Deliberate technical debt: (a) hardcoding a flat platform fee percentage instead of building a flexible fee configuration system is fine for launch but should be revisited once you have pricing experiments to run, (b) using a single database table for all messages without conversation threading optimization is fine under a few thousand users but will need indexing work later, (c) skipping automated testing initially is reasonable for a 4-week MVP but should be added before onboarding paying customers at scale.
4. Scaling cliff: the most likely breaking point is the simple messaging table once you exceed roughly 10,000 messages, since query performance will degrade without proper indexing and pagination, requiring a messaging architecture revisit.
5. Final stack recommendation: Next.js for the frontend/backend, Supabase for database and auth, Stripe Connect for marketplace payments, and a simple custom-built booking calendar component, deployed on Vercel.

Customization tips

• — If you have strong opinions about certain tools already (e.g. 'I only want to use Python'), state this as a constraint so recommendations respect it.
• — Ask for a second version optimized purely for lowest cost if budget is the primary constraint rather than speed.
• — Follow up by asking for a more detailed breakdown of just the highest-risk component identified (often auth or payments).

Tags

FAQ

Related Skills