# Building the MVP – Gründerkurse

> Scope, tech, budget: how small a first product can be.

- [MVP Development Cost: Hours, Rates and What to Cut](https://gruenderkurse.de/en/building-the-mvp/mvp-development-cost/): MVP development cost is the number of build hours multiplied by the hourly rate, plus running costs. A lean web app with accounts, payments and an admin area plausibly needs 400 to 800 hours, so the total swings from about $20,000 to well over $100,000 depending on whether you pay $50 or $150 an hour.
- [No-Code MVP: Five Patterns and Where They Break](https://gruenderkurse.de/en/building-the-mvp/no-code-mvp/): A no-code MVP works when your product is mostly forms, a database, workflows and notifications, and your first hundred customers will not stress it. It breaks down with compute-heavy or highly custom logic, strict compliance demands, or when the code itself is your competitive edge. Plan the rebuild before you need it.
- [How to Find a Technical Co-Founder (and Keep One)](https://gruenderkurse.de/en/building-the-mvp/find-technical-cofounder/): To find a technical co-founder, go where engineers already spend their spare time: university entrepreneurship programmes, hackathons, open-source projects, co-founder matching platforms and your own network of former colleagues. Lead with evidence such as customer interviews or pilots, run a paid or clearly scoped trial project, then agree equity with vesting.
- [Product Requirements Document Template for an MVP](https://gruenderkurse.de/en/building-the-mvp/product-requirements-document/): A product requirements document describes which problem the software solves, for whom, and how you will know it is finished, without prescribing how to build it. For an MVP, five to ten pages are enough: goal, user roles, user stories with acceptance criteria, non-functional requirements, integrations, scope boundaries, constraints and an acceptance process.

About this site: https://gruenderkurse.de/en/about/