{"skill":{"slug":"microsaas-launcher","displayName":"MicroSaaS Launcher","summary":"Autonomously builds, deploys, and launches a micro-SaaS from niche idea to monetization, including market research, coding, deployment, payment setup, and ma...","description":"# MicroSaaS-Launcher Skill\n\n**Name:** MicroSaaS Launcher\n**Description:** Autonomous end-to-end micro-SaaS builder. When the user provides a niche idea and a budget (minimum $300), this skill researches competition, chooses a tech stack (Next.js + Supabase/Stripe by default), writes all necessary code, deploys to Vercel, sets up domain and Stripe payments, creates a landing page with a waitlist, launches on platforms like Product Hunt, Twitter, and Reddit, handles customer support via email/chat, tracks daily revenue, and iterates on features based on usage analytics.\n\n---\n\n## Core Workflow (Step-by-Step Runbook)\n\nThis runbook outlines the process for launching a micro-SaaS. Each step must be explicitly completed and documented.\n\n### Phase 1: Idea Validation & Research\n\n1.  **Understand Niche Idea:**\n    *   **Action:** Clarify the user's micro-SaaS idea. Ask clarifying questions if the niche or problem is unclear.\n    *   **Tooling:** `message` (to user)\n    *   **Logging:** Record the initial idea and any clarifications in `LAUNCH-LOG.md`.\n\n2.  **Market Research & Competition Analysis:**\n    *   **Action:** Use web search to identify existing competitors, analyze their features, pricing, and marketing strategies. Look for gaps or \"winning features\" that can be integrated or improved upon.\n    *   **Tooling:** `web_search` (for competitor analysis, market trends, user pain points)\n    *   **Output:** Summarize competitive landscape and potential differentiators.\n    *   **Logging:** Record research findings, competitor URLs, and feature insights in `LAUNCH-LOG.md`.\n\n3.  **Validate Idea & Feature Set:**\n    *   **Action:** Based on research, propose a lean MVP (Minimum Viable Product) feature set. Highlight unique selling propositions (USPs).\n    *   **Tooling:** `message` (to user for validation and confirmation of MVP features)\n    *   **Logging:** Document the proposed MVP features and user confirmation in `LAUNCH-LOG.md`.\n\n### Phase 2: Technical Setup & Development\n\n4.  **Budget Confirmation:**\n    *   **Action:** Get explicit confirmation from the user on the allocated budget (minimum $300).\n    *   **Tooling:** `message` (to user)\n    *   **Safety Check:** **Mandatory confirmation before proceeding.**\n    *   **Logging:** Record confirmed budget in `LAUNCH-LOG.md`.\n\n5.  **GitHub Repository Creation:**\n    *   **Action:** Create a new private GitHub repository for the project. If user provides GitHub credentials, use them; otherwise, ask user to create and invite the agent.\n    *   **Tooling:** `exec` (for `git` commands, or `web_browser` for GitHub UI if `exec` is not sufficient for repo creation/management).\n    *   **Output:** Repository URL.\n    *   **Logging:** Record GitHub repo URL in `LAUNCH-LOG.md`.\n\n6.  **Tech Stack Selection (Default: Next.js + Supabase/Stripe):**\n    *   **Action:** Confirm the default tech stack or adjust if user has specific requirements and it aligns with budget/complexity.\n    *   **Tooling:** `message` (to user for confirmation)\n    *   **Logging:** Record final tech stack in `LAUNCH-LOG.md`.\n\n7.  **Code Generation & Implementation:**\n    *   **Action:** Based on the validated MVP features, write the entire codebase. This includes:\n        *   Next.js frontend (UI/UX, pages, components)\n        *   Supabase integration (database schema, authentication, API endpoints)\n        *   Stripe integration (checkout, webhooks, subscription management)\n        *   Unit/Integration tests.\n    *   **Tooling:** `write`, `edit` (for creating/modifying code files), `exec` (for `npx create-next-app`, `supabase cli`, `git add/commit`).\n    *   **Output:** All project code files committed to the GitHub repository.\n    *   **Logging:** Record code generation progress, major components, and commit hashes in `LAUNCH-LOG.md`.\n\n### Phase 3: Deployment & Monetization\n\n8.  **Vercel Deployment:**\n    *   **Action:** Deploy the Next.js application to Vercel. Obtain Vercel API token or guide user to connect GitHub repo to Vercel.\n    *   **Tooling:** `exec` (for `vercel deploy` CLI, or `web_browser` for Vercel UI).\n    *   **Output:** Live Vercel deployment URL.\n    *   **Logging:** Record Vercel deployment URL and status in `LAUNCH-LOG.md`.\n\n9.  **Custom Domain Setup:**\n    *   **Action:** If provided by the user, set up the custom domain in Vercel. Guide user through DNS configuration if needed.\n    *   **Tooling:** `exec` (for Vercel CLI), `message` (for DNS instructions).\n    *   **Logging:** Record custom domain setup details in `LAUNCH-LOG.md`.\n\n10. **Stripe Integration & Pricing Tiers:**\n    *   **Action:** Configure Stripe API keys, create product and pricing tiers (e.g., Free, Pro, Premium) as per validated features. Ensure webhooks are set up for Supabase.\n    *   **Tooling:** `web_browser` (for Stripe dashboard configuration), `write`, `edit` (for updating code with Stripe keys/IDs).\n    *   **Output:** Confirmed Stripe integration and pricing plans.\n    *   **Logging:** Record Stripe setup details, product IDs, and pricing in `LAUNCH-LOG.md`.\n    *   **Safety Check:** **Mandatory confirmation before enabling live Stripe payments.**\n\n### Phase 4: Marketing & Launch\n\n11. **Landing Page & Waitlist Creation:**\n    *   **Action:** Develop a compelling landing page within the Next.js app. Integrate a waitlist functionality (e.g., using Supabase email list or a third-party service).\n    *   **Tooling:** `write`, `edit` (for landing page code), `web_browser` (for third-party waitlist setup).\n    *   **Output:** Live landing page with functional waitlist.\n    *   **Logging:** Record landing page URL and waitlist setup in `LAUNCH-LOG.md`.\n\n12. **Launch Copy & Assets:**\n    *   **Action:** Write engaging launch copy for Product Hunt, Twitter threads, and Reddit posts. Create any necessary promotional assets (e.g., screenshots, short GIFs).\n    *   **Tooling:** `write` (for text content), `canvas` (for screenshots/simple graphics if needed, or `web_browser` to capture from live site).\n    *   **Output:** Drafted launch content for all platforms.\n    *   **Logging:** Record drafted launch content in `LAUNCH-LOG.md`.\n\n13. **Public Launch Strategy & Approval:**\n    *   **Action:** Present the complete launch plan (copy, assets, schedule) to the user for final approval.\n    *   **Tooling:** `message` (to user)\n    *   **Safety Check:** **Mandatory final user approval before any public posting.**\n    *   **Logging:** Record user approval for launch plan in `LAUNCH-LOG.md`.\n\n14. **Execute Public Launch:**\n    *   **Action:** Post the micro-SaaS on Product Hunt, Twitter, and relevant Reddit subreddits according to the approved schedule.\n    *   **Tooling:** `web_browser` (to interact with social media/PH platforms).\n    *   **Logging:** Record exact timestamps and links of all public posts in `LAUNCH-LOG.md`.\n    *   **State Change:** Switch to \"Maintenance Mode\" after launch.\n\n### Phase 5: Operations & Iteration (Maintenance Mode)\n\n15. **Customer Support Setup:**\n    *   **Action:** Set up basic automated customer support replies for common inquiries (e.g., via email or a simple chat widget integration).\n    *   **Tooling:** `write`, `edit` (for auto-reply scripts/configs), `web_browser` (for setting up third-party support tools).\n    *   **Logging:** Record customer support setup details in `LAUNCH-LOG.md`.\n\n16. **Daily Revenue Reporting (Cron Job):**\n    *   **Action:** Set up a daily cron job that fetches revenue data from Stripe and reports it to the user.\n    *   **Tooling:** `exec` (to schedule cron job), `web_browser` (to fetch Stripe data via API or UI), `message` (to send daily report).\n    *   **Logging:** Record daily revenue reports in `LAUNCH-LOG.md`.\n\n17. **Weekly Iteration Cycle:**\n    *   **Action:** Every week, review usage analytics (e.g., from Vercel, Supabase logs, Stripe data, customer feedback).\n    *   **Action:** Propose new features or improvements based on data and user feedback.\n    *   **Action:** Get user approval for next development sprint.\n    *   **Tooling:** `web_browser` (for analytics dashboards), `message` (to user for feedback/approvals), `web_search` (for new ideas/solutions).\n    *   **Logging:** Record iteration proposals, user decisions, and sprint outcomes in `LAUNCH-LOG.md`.\n\n---\n\n## Safety Rules\n\n*   **Never spend more than the approved budget without explicit user permission.** This includes recurring costs.\n*   **Never post publicly (Product Hunt, Twitter, Reddit, etc.) without final, explicit user approval.**\n*   **Prioritize free tiers first** for all services (Vercel, Supabase, etc.) whenever possible, only upgrading after user approval for budget.\n*   **Log every single action, decision, and significant output** in a dedicated file named `LAUNCH-LOG.md` within the `MicroSaaS-Launcher` directory. This log must be detailed enough to fully reconstruct the project's history.\n*   **After initial public launch, automatically switch to \"Maintenance Mode\"**, which primarily involves daily revenue reports and weekly iteration cycles based on analytics and feedback.\n\n---\n\n## Example Usage\n\n*   \"Launch a micro-SaaS for an AI prompt library with an $800 budget.\"\n*   \"Build a simple Notion-to-PDF converter tool. I have a $350 budget and a domain: `notion2pdf.com`.\"\n*   \"Use MicroSaaS-Launcher to deploy my idea for a simple project management tool, with a $500 budget.\"\n","tags":{"automation":"1.0.0","autonomous":"1.0.0","builder":"1.0.0","indiehackers":"1.0.0","latest":"1.0.0","saas":"1.0.0"},"stats":{"comments":0,"downloads":277,"installsAllTime":0,"installsCurrent":0,"stars":0,"versions":1},"createdAt":1771930762808,"updatedAt":1779077285372},"latestVersion":{"version":"1.0.0","createdAt":1771930762808,"changelog":"MicroSaaS-Launcher Skill v1.0.0\n\n- Initial release of an autonomous micro-SaaS builder skill.\n- Supports end-to-end SaaS launch: niche validation, competitor research, MVP development, Vercel deployment, Stripe integration, and launch on popular platforms.\n- Includes structured runbook for each project phase, with required safety/confirmation steps at key milestones.\n- Handles post-launch operations: customer support setup, revenue reporting, and weekly feature iteration.\n- All actions and progress are logged to `LAUNCH-LOG.md` for transparency.","license":null},"metadata":null,"owner":{"handle":"vibhansh19","userId":"s17dagvv7c7mhw6x1tk99qq2ds884m71","displayName":"vibhansh19","image":"https://avatars.githubusercontent.com/u/79039062?v=4"},"moderation":{"isSuspicious":false,"isMalwareBlocked":false,"verdict":"clean","reasonCodes":["review.llm_review"],"summary":"Review: review.llm_review","engineVersion":"v2.4.24","updatedAt":1779956064270}}