Build an MVP in a weekend - for your own products or agency clients
This page was last updated on: 15th May 2025
Important: Before starting MVP development:
This guide applies to BOTH:
Quick Prototype with an AI Site Builder
With the insights and initial PRD from your Granola and Grok conversations (as detailed in the Idea Validation page), use them to quickly create and launch a live landing page. This allows you to start gathering user interest immediately. Adding a waitlist at this stage is optional, but can be useful for collecting emails if you anticipate a longer development cycle (but waitlists aren’t mandatory).
This step focuses on creating your initial public-facing landing page. For this, consider AI-powered no-code tools like:
The primary goal here is to get a functional public landing page deployed as fast as possible. You can iterate on its design later.
These tools can help you:
Once your landing page is live and you ‘think’ you’ve nailed the core value proposition, get further feedback by:
While you might explore several AI site builders, we recommend prioritizing getting one version live quickly. Our current favorite for this is Lovable due to its straightforward Clerk integration if you decide to set up a waitlist (see their Clerk Integration Guide). The exported files or the entire repository from this initial landing page (e.g., your Lovable project) should be saved. We will clone this prototype repository into a folder within your Titan project later to use as a direct reference. If you decide to publish the landing page immediately (with or without a waitlist), the social media feedback will directly inform the features and design of your subsequent documentation and full MVP.
Product-Specific Setup
Before diving into development, set up the product-specific infrastructure:
Domain & Email
Third-Party Services
For Agency owners, using your own accounts to setup and test the MVP is okay because the handover will be cleaner later when you transfer ownership of the services to the client.
See the Account Management Guide page for more details on how this works and how to transfer ownership of each service to the client, later.
Client Prerequisites (they must provide):
See the Account Management Guide page for more details on why you should use your own personal email address or have a company email address already setup in Parent Company Setup and don’t need the client to setup any of the 3rd-party services for the stack (like Supabase, Clerk, Stripe, etc.).
For agency work, clients should own all services and domains. This ensures clean handover and avoids billing/ownership complications.
Create a new Codebase
Spin up a new project quickly with Titan
Just run ‘Setup via CLI’ step in the Titan guide so that we simply create a new repository.
We will start building the actual product (MVP) in later steps, but there are a few things to do first, like generating the right documentation and embedding that in the codebase so that we have enough business and product context for the LLMs, and creating all the brand assets and landing page (especially if we want to start collecting emails and building a waitlist).
Requirements & Documentation
Import your Granola recording summary into Cursor and then use the below strategy to generate comprehensive documentation:
For best results, use either gemini-2.5-pro
(gemini-2.5-pro-preview-05-06
) or claude-4-sonnet-thinking
.
Example prompt:
You can use the @web tag in agent-mode to let Cursor search the web for inspiration and verify details (font names, colors, etc.)
Develop Full Brand Assets & Prepare Landing Page for Titan Integration
In Step 2 (“Quick Prototype with AI No-Code Tools”), you prototyped an initial landing page design and potentially gathered feedback if you chose to launch it. In Step 5 (“Requirements & Documentation”), you generated ‘Brand Identity Guidelines’. Now, let’s develop your full brand assets and prepare to integrate your validated landing page design into Titan.
Agency clients will and should provide their own brand assets.
docs/brand-identity-guidelines.md
) if you’re building for yourself.You can use this chrome extension to identify fonts on other websites: WhatFont
The goal is to have a polished brand identity and a clear plan for how your validated landing page design will live within your project.
Be sure to tag the docs
folder (especially brand-identity-guidelines.md
) when prompting with Composer or any AI tool for assistance with brand asset finalization.
Fonts should go in the public/fonts/ folder. Remove the default font in that folder (Sora.zip)
For Agency Work: Use the client’s provided brand assets and guidelines. If they don’t have any, help them develop these using the tools mentioned above before proceeding.
While launching a landing page with a waitlist in Step 2 was optional, having that early version (live or not) provides a solid design foundation for this stage.
Legal Pages
Every product needs legal documentation to protect both you and your users. Instead of expensive legal consultations for your MVP, use AI to generate these essential pages:
Use this prompt with Cursor agent mode to generate all required legal pages for your MVP and save them to your documentation folder:
Update any variables in the prompt below with the correct values.
For Agency Work: Generate these documents using the client’s company details and have them review and approve before implementation.
Setup Local Development Tools & Build MVP
Before building the MVP, set up essential development tools that will accelerate your workflow. Then continue to the Titan guide.
Set up these tools in your project to maximize development speed:
TaskMaster - AI-powered task management
CodeRabbit - AI-Powered Code Reviews
StageWise - Precise UI refinements
Cmd+Shift+P
→ search “StageWise” → “Auto Setup StageWise Toolbar”BrowserMCP - Browser automation for testing
Operative.sh MCP - Automated manual web app testing
See the Building Guide if you want detailed setup instructions and advanced usage of these tools.
With your documentation, brand assets, a clean landing page design (from Step 2 & 5), and development tools (TaskMaster, StageWise, BrowserMCP) set up, it’s time to build the core MVP features.
Leveraging Your AI-Built Public Landing Page/Prototype: The public landing page you prototyped with an AI tool (e.g., Lovable in Step 2) is a valuable asset for your project’s public face.
docs/prototype_references/live_landing_page_v1/
) open as a direct visual and functional reference for your public-facing pages in Titan.Once you’ve added the landing page to the codebase, we can now start building the MVP (the core feature/s that makes the product what it is).
Focus on implementing the 1-2 core features identified in your PRD. The goal is a functional, testable product. Tell agent-mode in Cursor to use TaskMaster for everything.
See Titan - Building the Product, for the technical build process.
For Agency Work:
Beta Testing
Once the core MVP is done (1 main feature that is tested and works end-to-end), spread the word (marketing) to get some initial feedback.
See our Marketing Guide for more lots of strategies to get initial feedback.
If you’re simply building a product to show proof you’re proactive (to recruiters and hiring managers), then simply posting to LinkedIn and any personal social media is good enough (to get users)
Aggressively fix bugs and improve the product based on the feedback (UserJot). Continue to market.
Record product demos to help with marketing - using Cursorful
If people see that you squash bugs at lightning speed and deliver features so fast they can’t keep up, they’re drastically more likely to pay for your product and not churn.
Thankfully, Cursor can help you do this. Keep referring to the Building page for lots of tips and tricks. Make those workflows second nature.
Official Launch & Decision Point
After 2-3 weeks of beta testing, you can continue to work on it or keep it on the backburner.
You have 2 options based on any ‘success’ so far:
If you have 20+ active users OR $100+ MRR:
Product Development
Growth
After successful launch:
Final Handover
Maintenance Plan
Build an MVP in a weekend - for your own products or agency clients
This page was last updated on: 15th May 2025
Important: Before starting MVP development:
This guide applies to BOTH:
Quick Prototype with an AI Site Builder
With the insights and initial PRD from your Granola and Grok conversations (as detailed in the Idea Validation page), use them to quickly create and launch a live landing page. This allows you to start gathering user interest immediately. Adding a waitlist at this stage is optional, but can be useful for collecting emails if you anticipate a longer development cycle (but waitlists aren’t mandatory).
This step focuses on creating your initial public-facing landing page. For this, consider AI-powered no-code tools like:
The primary goal here is to get a functional public landing page deployed as fast as possible. You can iterate on its design later.
These tools can help you:
Once your landing page is live and you ‘think’ you’ve nailed the core value proposition, get further feedback by:
While you might explore several AI site builders, we recommend prioritizing getting one version live quickly. Our current favorite for this is Lovable due to its straightforward Clerk integration if you decide to set up a waitlist (see their Clerk Integration Guide). The exported files or the entire repository from this initial landing page (e.g., your Lovable project) should be saved. We will clone this prototype repository into a folder within your Titan project later to use as a direct reference. If you decide to publish the landing page immediately (with or without a waitlist), the social media feedback will directly inform the features and design of your subsequent documentation and full MVP.
Product-Specific Setup
Before diving into development, set up the product-specific infrastructure:
Domain & Email
Third-Party Services
For Agency owners, using your own accounts to setup and test the MVP is okay because the handover will be cleaner later when you transfer ownership of the services to the client.
See the Account Management Guide page for more details on how this works and how to transfer ownership of each service to the client, later.
Client Prerequisites (they must provide):
See the Account Management Guide page for more details on why you should use your own personal email address or have a company email address already setup in Parent Company Setup and don’t need the client to setup any of the 3rd-party services for the stack (like Supabase, Clerk, Stripe, etc.).
For agency work, clients should own all services and domains. This ensures clean handover and avoids billing/ownership complications.
Create a new Codebase
Spin up a new project quickly with Titan
Just run ‘Setup via CLI’ step in the Titan guide so that we simply create a new repository.
We will start building the actual product (MVP) in later steps, but there are a few things to do first, like generating the right documentation and embedding that in the codebase so that we have enough business and product context for the LLMs, and creating all the brand assets and landing page (especially if we want to start collecting emails and building a waitlist).
Requirements & Documentation
Import your Granola recording summary into Cursor and then use the below strategy to generate comprehensive documentation:
For best results, use either gemini-2.5-pro
(gemini-2.5-pro-preview-05-06
) or claude-4-sonnet-thinking
.
Example prompt:
You can use the @web tag in agent-mode to let Cursor search the web for inspiration and verify details (font names, colors, etc.)
Develop Full Brand Assets & Prepare Landing Page for Titan Integration
In Step 2 (“Quick Prototype with AI No-Code Tools”), you prototyped an initial landing page design and potentially gathered feedback if you chose to launch it. In Step 5 (“Requirements & Documentation”), you generated ‘Brand Identity Guidelines’. Now, let’s develop your full brand assets and prepare to integrate your validated landing page design into Titan.
Agency clients will and should provide their own brand assets.
docs/brand-identity-guidelines.md
) if you’re building for yourself.You can use this chrome extension to identify fonts on other websites: WhatFont
The goal is to have a polished brand identity and a clear plan for how your validated landing page design will live within your project.
Be sure to tag the docs
folder (especially brand-identity-guidelines.md
) when prompting with Composer or any AI tool for assistance with brand asset finalization.
Fonts should go in the public/fonts/ folder. Remove the default font in that folder (Sora.zip)
For Agency Work: Use the client’s provided brand assets and guidelines. If they don’t have any, help them develop these using the tools mentioned above before proceeding.
While launching a landing page with a waitlist in Step 2 was optional, having that early version (live or not) provides a solid design foundation for this stage.
Legal Pages
Every product needs legal documentation to protect both you and your users. Instead of expensive legal consultations for your MVP, use AI to generate these essential pages:
Use this prompt with Cursor agent mode to generate all required legal pages for your MVP and save them to your documentation folder:
Update any variables in the prompt below with the correct values.
For Agency Work: Generate these documents using the client’s company details and have them review and approve before implementation.
Setup Local Development Tools & Build MVP
Before building the MVP, set up essential development tools that will accelerate your workflow. Then continue to the Titan guide.
Set up these tools in your project to maximize development speed:
TaskMaster - AI-powered task management
CodeRabbit - AI-Powered Code Reviews
StageWise - Precise UI refinements
Cmd+Shift+P
→ search “StageWise” → “Auto Setup StageWise Toolbar”BrowserMCP - Browser automation for testing
Operative.sh MCP - Automated manual web app testing
See the Building Guide if you want detailed setup instructions and advanced usage of these tools.
With your documentation, brand assets, a clean landing page design (from Step 2 & 5), and development tools (TaskMaster, StageWise, BrowserMCP) set up, it’s time to build the core MVP features.
Leveraging Your AI-Built Public Landing Page/Prototype: The public landing page you prototyped with an AI tool (e.g., Lovable in Step 2) is a valuable asset for your project’s public face.
docs/prototype_references/live_landing_page_v1/
) open as a direct visual and functional reference for your public-facing pages in Titan.Once you’ve added the landing page to the codebase, we can now start building the MVP (the core feature/s that makes the product what it is).
Focus on implementing the 1-2 core features identified in your PRD. The goal is a functional, testable product. Tell agent-mode in Cursor to use TaskMaster for everything.
See Titan - Building the Product, for the technical build process.
For Agency Work:
Beta Testing
Once the core MVP is done (1 main feature that is tested and works end-to-end), spread the word (marketing) to get some initial feedback.
See our Marketing Guide for more lots of strategies to get initial feedback.
If you’re simply building a product to show proof you’re proactive (to recruiters and hiring managers), then simply posting to LinkedIn and any personal social media is good enough (to get users)
Aggressively fix bugs and improve the product based on the feedback (UserJot). Continue to market.
Record product demos to help with marketing - using Cursorful
If people see that you squash bugs at lightning speed and deliver features so fast they can’t keep up, they’re drastically more likely to pay for your product and not churn.
Thankfully, Cursor can help you do this. Keep referring to the Building page for lots of tips and tricks. Make those workflows second nature.
Official Launch & Decision Point
After 2-3 weeks of beta testing, you can continue to work on it or keep it on the backburner.
You have 2 options based on any ‘success’ so far:
If you have 20+ active users OR $100+ MRR:
Product Development
Growth
After successful launch:
Final Handover
Maintenance Plan