From Idea to First Customers
Build a micro-SaaS with bolt.new & launch outbound with Instantly.ai
A complete, open-source, step-by-step guide covering ideation, AI-powered app building, payments, ICP definition, and cold email campaigns. Everything you need to go from zero to your first paying customers.

The Full Pipeline
This guide walks you through the entire journey from a raw idea to your first paying customers. Five phases, one day, zero hand-waving. Every prompt, template, and decision is documented so you can replicate it with your own idea.
Who is this for?
The AI Workflow Model
This guide uses a deliberate AI workflow — different models for different jobs:
Claude Opus
Planning, strategy, debugging blockers. The heavy-thinking model.
Claude Sonnet
Executing on the plan, writing iterations, filling in content.
bolt.new
AI app builder that generates your actual application code.
Ideation: Pick the Right Idea
Not every idea works for this pipeline. You need an idea that's buildable in bolt.new, targetable with cold email, and monetizable from day one. The guide includes a 5-Filter Framework to validate any micro-SaaS idea before you write a single prompt.
The 5-Filter Framework
Every idea must pass these five filters. If it fails any one, rethink the idea before building.
Filter 1: Can you explain the problem in one sentence?
Say it to a non-technical person. If they nod, you've got something.
Filter 2: Can you build it in bolt.new with 1-2 core features?
V1 should do one thing exceptionally well.
Filter 3: Can you find your ideal customer on the internet?
Run a test search. Are there 1,000+ matching contacts?
Filter 4: Does the cold email hook write itself?
If the opening line feels natural and specific, you're golden.
Filter 5: Is the price worth it for the value?
Would the buyer see this as an obvious win at your price point?
The Underserved Market Sweet Spot
The best micro-SaaS ideas sit at the intersection of three things:
Industry behind on tech
Restaurants, dental, trades, real estate, pet services
Painful & frequent problem
Unanswered reviews, no testimonials, manual invoicing
No affordable tool exists
Competitors charge $300+/mo for what you build at $29/mo
Quick Validation Checklist
If 5+ of these are checked, proceed to building. The full starter kit includes detailed worksheets and 6 pre-researched app ideas with scoring matrices.
Common mistakes to avoid:
- • Building for developers (they build their own tools)
- • Making V1 too complex (it should do ONE thing well)
- • Choosing a broad market ("Small businesses" is not an ICP)
- • Ignoring the cold email step during ideation
- • Over-engineering the demo
Build: Vibe-Code Your App
bolt.new is an AI app builder that generates full-stack web apps from natural language prompts. The key is knowing how to prompt it effectively. The starter kit includes copy-paste ready prompts for every stage of the build, plus the complete TopReply.ai build as a worked example.
The Build Sequence
Follow this sequence — one concern per prompt, in this order. Mixing concerns (like adding features and design changes in the same prompt) is the number one cause of bolt.new generating broken code.
| # | Prompt | Focus | Time |
|---|---|---|---|
| 01 | Scaffold | Landing page + dashboard + core app shell | ~8 min |
| 02 | Core Features | Build the real functionality that delivers value | ~5 min |
| 03 | UI Polish | Animations, loading states, micro-interactions | ~5 min |
| 04 | Payments | Stripe integration (Payment Links recommended) | ~10 min |
| 05 | Auth | Supabase authentication + database persistence | ~10 min |
| 06 | Deploy | Vercel/Netlify deploy + env vars + DNS | ~5 min |
The Scaffold Prompt (Most Important)
Your first prompt determines 80% of the app. Give bolt.new five things upfront: what you're building, who it's for, core features (3-5 max), tech preferences, and brand direction. Do NOT include authentication, payments, or analytics in this first prompt.
Build me a [type of app] called "[App Name]" for [target user].
The core problem: [one sentence problem statement].
The app should:
1. [Core feature #1 — the main value proposition]
2. [Core feature #2 — supporting functionality]
3. [Core feature #3 — nice-to-have for V1]
Design direction:
- Clean, modern, minimal UI
- [Color palette or brand vibe]
- Mobile-responsive
- Professional enough that a business owner would trust it
Tech notes:
- Use React with Tailwind CSS
- Use a clean component structure
- No authentication needed for V15 Golden Rules for bolt.new Prompts
Front-load context in your first prompt
Don't drip-feed information. Give bolt.new everything it needs upfront — product, user, features, style.
One concern per prompt
Don't mix features with design changes. Prompt 1 = features. Prompt 2 = polish. Never both.
Be specific about what NOT to change
Say "do NOT change any functionality or page structure — only add visual polish." This prevents bolt.new from breaking working code.
Describe the user journey, not the code
"User clicks Generate, sees a typing animation, then a copy button appears" is better than "add an animation to the output div."
If something breaks, describe the symptom
"When I click Generate, nothing happens and I see a console error" works better than "fix the bug."
The UI Polish Checklist
After your core features work, run through this checklist for your polish prompt. Each item makes your app feel production-quality instead of a prototype:
Key lesson: Use Stripe Payment Links
During the TopReply build, bolt.new generated deprecated Stripe API code. Instead of debugging, we switched to Stripe Payment Links — a simpler approach that requires zero backend code and zero SDK. Your "Upgrade to Pro" button simply links to a hosted Stripe checkout URL.
This pattern — choosing a simpler architecture when the AI generates something broken — is a core skill of vibe coding. Don't fight the tool. Find a simpler path.
Launch: Deploy & Accept Payments
bolt.new has built-in deployment to Netlify (one click). You can also deploy to Vercel with GitHub integration for better control. The key is: don't overthink it. Ship the thing and start getting it in front of people.
Post-Deployment Checklist
Landing page loads correctly
Check on desktop and mobile
Navigation works on all pages
Click every link
Core functionality works end-to-end
Input → Process → Output
Stripe payments redirect correctly
Use test card: 4242 4242 4242 4242
Mobile layout looks professional
No horizontal overflow or broken elements
Page load time < 3 seconds
Check with Chrome DevTools
Recommended Tech Stack
| Tool | Purpose | Why |
|---|---|---|
| bolt.new | Build the app | AI app builder — full-stack from prompts |
| Supabase | Database + Auth | Free tier, Postgres, built-in auth |
| Stripe | Payments | Payment Links = zero backend code |
| Vercel | Hosting | GitHub deploys, free tier, fast CDN |
| Instantly.ai | Outbound | 450M+ contacts, campaign engine, warmup |
| Claude | AI assistant | Plan with Opus, execute with Sonnet |
Find: Define Your ICP & Build a Lead List
Your app is live. Now you need to find the people who need it. This is where most builders get stuck — they built something great but have no idea how to reach potential customers. The answer is an Ideal Customer Profile (ICP) and a lead database.
What is an ICP?
Your ICP (Ideal Customer Profile) is the specific type of person or business that:
Has the problem your app solves
They feel the pain today and would recognize it immediately
Can afford your solution
Your price point is a rounding error for their business
Is reachable via cold email
Has a business email, findable in lead databases
Can act quickly
No 6-month procurement process — they can buy today
ICP Worksheet
Fill in these three sections to define your ICP. The TopReply example is included in the starter kit as a worked reference.
Section 1: Who has this problem?
Section 2: Why would they care?
Section 3: Can you reach them?
Finding Leads with Instantly SuperSearch
Instantly SuperSearch is a B2B lead database with 450M+ verified contacts. Think of it as LinkedIn Sales Navigator meets a verified email database, built directly into the campaign platform. Here's how to set up your first search:
Job Titles: Owner, General Manager, Marketing Director
Industry: Restaurants & Food Service
Company Size: 1-50 employees
Location: Austin, TX (start local, expand later)
Has Email: Yes
// Or use natural language:
"Find restaurant owners in Austin, Texas with fewer
than 50 employees who have a Google Business Profile"The ICP Hierarchy: Start Narrow, Expand
Don't blast 50,000 contacts on day one. Start narrow, validate your messaging, then expand:
Restaurant owners in Austin, TX
Test messaging
Restaurant owners in Texas
Validate at scale
Restaurant owners in the US
Scale what works
All local business owners
Expand verticals
Sell: Launch Your Outbound Campaign
You've built the app, found the leads, and now it's time to reach out. Cold email is the most scalable, cost-effective way to get your first customers for a micro-SaaS. The key is being helpful, not salesy.
Anatomy of a Cold Email That Gets Replies
The golden rule: Under 100 words, no HTML or images in Email 1, one CTA per email, write like a human.
The 4-Email Sequence
Each email has a different purpose. Don't repeat the same pitch four times — each touchpoint adds a new angle or piece of value.
Reference observable data about their business (review count, website detail, location). Make it obvious this isn't mass-blasted.
Show the product in action. Include an example output (like a sample AI-generated review response for their business). Quantify the value.
Approach the same problem from a new direction. If Email 1 was about responding to reviews, Email 3 could be about recovering from negative reviews.
Respectful close. Acknowledge you don't want to be annoying. Drop your URL casually. Leave a positive impression even if they don't convert.
Example: Email 1 Template
Here's the actual Email 1 template from the TopReply campaign in the starter kit. Notice how every variable ({{companyName}}, {{firstName}}) maps directly to data from Instantly SuperSearch:
Subject: {{companyName}}'s google reviews
Hi {{firstName}},
I was looking at {{companyName}}'s Google reviews — you've
got {{reviewCount}} reviews, which is great. But I noticed
most of them don't have a response from your team.
Responding to reviews actually boosts your local SEO ranking
and makes new customers 16% more likely to visit.
I built a tool that generates professional review responses
in seconds using AI. Would it be helpful if I showed you
how it works with your actual reviews?
— BrandonSubject Line Formulas
{{companyName}}'s [topic]quick question about [thing]idea for {{companyName}}[mutual connection / context]Rules: lowercase, under 6 words, no emojis, no exclamation marks, no spam trigger words (free, guaranteed, limited time).
Campaign Launch Settings
These are the recommended settings when you launch your first Instantly campaign:
What to Watch (First 48 Hours)
| Metric | Healthy Range | If Low |
|---|---|---|
| Open Rate | 50-70% | Test new subject lines |
| Reply Rate | 5-15% | Revise your hook or CTA |
| Bounce Rate | < 3% | Check email verification |
| Unsubscribe Rate | < 1% | Refine ICP targeting |
| Spam Reports | < 0.1% | Stop immediately, rework approach |
Pre-Launch Checklist
Email Infrastructure
- • Sending accounts warmed up (2+ weeks)
- • Domain reputation clean
- • SPF, DKIM, DMARC records set
Campaign Content
- • Email sequence written and tested
- • Subject line A/B variants ready
- • No broken variables
Lead List
- • Leads loaded from SuperSearch
- • Duplicates and competitors removed
- • Reasonable size (200-500 for test)
Tools & Resources
Everything referenced in this guide, plus alternatives and learning resources. All tools listed have free tiers or free trials — you can build and launch without spending money on tools.
Core Tools
AI Builder Alternatives
Recommended Reading
Communities
Key Takeaways
Mock-First Development
Build the entire UI with fake data and mock AI responses. Connect real APIs later. This lets you iterate on the experience without burning API credits.
The "Don't Change" Guardrail
Always tell bolt.new what NOT to modify when adding features. "Do NOT change any existing functionality" prevents it from breaking working code.
Simple > Clever
When bolt.new generates something broken (like deprecated Stripe APIs), don't debug it — find a simpler architecture. Stripe Payment Links beat Stripe SDK every time for V1.
Start Narrow, Expand Later
Your first campaign should be 500 leads in one city. Validate messaging before scaling. A 10% reply rate on 500 leads = 50 conversations. That's enough to validate.
Expect Follow-Up Prompts
5 out of 8 prompts worked on the first try. Needing 2-3 fix prompts is normal, not a failure. Authentication is always the trickiest part.
The Full Pipeline is ~1 Day
Idea (morning) → Build (afternoon) → Deploy (evening) → Find leads (next morning) → Launch campaign (next afternoon). Ship fast, iterate faster.
Want help building your outbound engine?
We help companies design and launch outbound campaigns, build growth marketing systems, and implement the same strategies covered in this guide.
Whether you need the full pipeline built for you or just want a second pair of eyes on your campaign strategy, we're happy to chat.
No pitch — just a conversation about what you're building