--- title: "Lovable MVP to Production Exercise" description: "Build a sales pipeline tracker in Lovable from a structured prompt to a production decision, with a CEO asking for logins in week two. A 75 minute exercise." canonical_url: "https://builderscamp.com/guides/challenges/building-with-lovable-mvp-to-production" date_published: "2026-09-16" date_modified: "2026-09-16" author: "Andre Albuquerque, Ricardo Luiz" publisher: "Builders Camp" guide_class: "challenges" --- # Lovable MVP to production practice exercise **TL;DR:** This exercise has you take a non-technical PM's sales pipeline tracker from a structured Lovable prompt through a working MVP, then handle the moment her CEO asks for per-rep logins and a customer demo with only six days left, forcing a real production trade-off under a hard deadline. ## The scenario A product manager at a five person B2B SaaS startup gets a Post-it note from her CEO on a Monday morning: build a sales pipeline tracker, internal tool, use Lovable, two weeks. She has never shipped code and has no developer assigned. What she does have is a browser, Lovable, and a methodology: define, design, structure, execute, iterate, publish. Skip any one of those steps and the build tends to collapse into a loop of broken prompts and random fixes rather than a working product. Getting an MVP working is only the first half of the story. By the second week, the CEO comes back with two more requests: can each sales rep log in and see only their own deals, and can the tool be shown to three paying customers next week. That single moment is where the exercise stops being about prompting and starts being about production readiness, because introducing real users and a real customer demo pulls in identity, security, and monetization decisions that a purely internal MVP never had to answer. ## What you are asked to do The exercise has six connected parts: - Write the complete structured product prompt for the pipeline tracker, covering the operational problem, the users and how often they use it, the core workflows, and the measurable success criteria, following the course's four part framework. - Evaluate three possible starting points, a pre-built template, a public community clone, and a blank project, against time to first working build, risk of architectural drift, and fit with the actual workflow, then pick one and justify it in one sentence. - Draft the complete masterplan.md file that will be pasted at the start of every Lovable session, tight enough to fit in a single prompt. - Write the recurring daily prompt that reads the task list, executes the next bounded task, marks it complete, explains the result, and proposes what comes next. - Choose 2 of 4 recommended governance files to maintain for a two week build, and justify the choice, including what is being sacrificed by dropping the other two, in 100 words or fewer. - When the CEO asks for per-rep logins and a customer-ready demo with six days left, choose 2 of 4 possible production upgrades to implement, and write the actual Lovable prompt for each one. ## What a strong answer covers The exercise's own objectives are what a strong submission has to satisfy: - Does the structured prompt describe workflows and operational realities rather than a list of UI features, matching the course's own stated distinction? - Is the starting point choice actually justified against the three stated criteria, rather than picked by default? - Is the masterplan.md tight enough to serve as a genuine persistent reference, rather than a long document nobody would actually paste into every session? - Does the governance trade-off name specifically what is being given up by dropping two of the four files, within the 100 word limit, rather than a vague statement that trade-offs exist? - Do the two chosen production upgrades reflect an honest read of what actually matters most before a paying customer sees the tool, with prompts specific enough to execute, rather than a restated wish list? ## Skills this exercise practises Writing a product prompt that describes a real workflow instead of a feature wish list. Choosing a starting point deliberately instead of defaulting to a blank project. Managing scope and process overhead on a real deadline, including deciding what documentation to skip. Recognizing the exact moment a prototype needs to become something closer to a real product, and prioritizing under a hard time constraint when it does. These map onto the bootcamp's own curriculum on the PM prompting framework, Supabase integration, and feature adoption metrics. For the underlying prompting and masterplan technique, see [how to build a prototype with Lovable](https://builderscamp.com/guides/tools/build-a-prototype-with-lovable), and for the broader case of shipping without a technical cofounder, [how to build an MVP as a solo founder](https://builderscamp.com/guides/other/mvp-as-a-solo-founder). If you want the equivalent exercise in a code-based AI tool instead of a no-code builder, the [Ask, Plan, Agent workflow exercise](https://builderscamp.com/guides/challenges/building-with-cursor-ask-plan-agent-workflow) from Building with Cursor covers a comparable structured build discipline. ## Which bootcamp this comes from This exercise is the practical challenge from [Building with Lovable](https://builderscamp.com/bootcamps/building-with-lovable), a two week bootcamp on Builders Camp with three live sessions covering the PM prompting framework, visual editing, Supabase integration, debugging and rollback, and deployment, taught by Ricardo Luiz. Completing the practical challenge counts toward the bootcamp's completion requirement and its certificate, alongside the certification quiz. Builders Camp runs this bootcamp both live and self-paced, included with the Builders Camp Membership alongside every other bootcamp, track, and masterclass. ## Frequently asked questions ### What is the setup for this Building with Lovable exercise? You play a PM with no developer and no coding background who has two weeks to ship an internal sales pipeline tracker in Lovable after her CEO watched the bootcamp over a weekend. The exercise follows the course's Define, Design, Structure, Execute, Iterate, Publish framework end to end. ### Do I need to already know Lovable to attempt this exercise? It helps to have gone through the bootcamp's earlier sessions, since the exercise assumes you know what a masterplan.md file and the magic prompt loop are. It is the practical challenge for the bootcamp, not a standalone introduction to the tool. ### Why does the exercise force you to pick only 2 of 4 governance files? Because a two week internal tool with no spare time cannot support all four governance files without the process becoming a burden bigger than the build itself. Picking two and justifying the trade-off in 100 words is the actual skill being tested, not memorizing all four. ### What changes in week two of the exercise? The CEO asks for per-rep logins and the ability to demo the tool to paying customers. That single request moves the project from an internal MVP into territory that needs real identity, security, and billing decisions, and you only have time to implement 2 of 4 possible upgrades before the deadline. ### How long does the exercise take? About 75 minutes, rated beginner difficulty, inside a two week bootcamp with three live sessions. ### Does completing it count toward a certificate? Yes. Finishing the practical challenge counts toward completing the Building with Lovable bootcamp on Builders Camp, alongside the certification quiz, and the bootcamp issues a certificate on completion. ## Sources - [Builders Camp: Building with Lovable bootcamp page](https://builderscamp.com/bootcamps/building-with-lovable) ## How this guide was made Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.