Shipping Stories

What We Learned Shipping 5 Products with a $100 Budget

By BTW Team4 min read

What We Learned Shipping 5 Products with a $100 Budget

Shipping products on a shoestring budget isn’t just a necessity for indie hackers — it’s a rite of passage. In 2026, we took on the challenge of launching five products with a total budget of just $100. Spoiler alert: it wasn’t easy, but we learned a ton about resourcefulness and the tools that truly deliver value without breaking the bank.

The Challenge of Budget Constraints

When you're working with a limited budget, every penny counts. The pressure to make smart choices can lead to creative solutions, but it can also expose weaknesses in your product development process. We found ourselves questioning the necessity of certain tools and features, ultimately honing in on what really mattered for our launches.

Our Product Lineup: Quick Overview

Here’s a quick glance at the five products we launched and how we allocated our budget:

| Product | Budget Allocated | Launch Date | Revenue Generated | Key Learnings | |------------------|------------------|-------------|-------------------|------------------------------------| | Simple Survey Tool | $20 | Jan 2026 | $250 | Focus on user feedback early | | Budget Tracker | $30 | Mar 2026 | $150 | Minimal features can go a long way| | Habit Tracker | $25 | May 2026 | $100 | Marketing is as crucial as building | | Recipe Sharing App | $15 | Jul 2026 | $60 | Community building matters | | Daily Journal | $10 | Sep 2026 | $40 | Iteration is key |

Tools We Used: A Practical Breakdown

Launching five products required a lean stack of tools. Here’s what we used, how much they cost, and our honest assessments:

| Tool | What It Does | Pricing | Best For | Limitations | Our Take | |--------------------|--------------------------------------------|-----------------------|------------------------------|--------------------------------------|-----------------------------------| | Google Forms | Create surveys and collect feedback | Free | Quick surveys | Basic design options | We used this for our survey tool | | Notion | Project management and documentation | Free tier + $10/mo | Organizing projects | Can get complex with larger teams | Essential for tracking everything | | Airtable | Database management and collaboration | Free tier + $10/mo | Managing data | Limited features on free tier | We didn't use it for this budget | | Canva | Graphic design for marketing materials | Free tier + $12.95/mo | Social media graphics | Limited features on free tier | Great for quick visuals | | WordPress | Website creation and hosting | $4/mo (basic plan) | Building landing pages | Requires maintenance | Our go-to for all launches | | Zapier | Automate workflows across apps | Free tier + $19.99/mo | Automation | Limited features on free tier | Not used due to budget constraints | | Stripe | Payment processing | 2.9% + $0.30 per transaction | Accepting payments | Fees can add up | Essential for revenue collection |

What We Actually Use

For our launches, we primarily relied on Google Forms for feedback, Notion for project management, and WordPress for our websites. Each tool had its pros and cons, but they helped us stay within budget while still allowing us to execute effectively.

What Worked and What Didn’t

Successes:

  1. User Feedback: The survey tool helped us pivot our product features based on real user needs, leading to better engagement.
  2. Lean Marketing: We utilized social media for free marketing, which drove initial traffic and interest in our products.

Failures:

  1. Overcomplicated Features: Some products had features that users didn’t care about, which we learned through feedback loops.
  2. Underestimating Community Building: Our recipe sharing app struggled because we didn’t invest enough time in building a community around it.

Actionable Lessons Learned

  1. Prioritize User Feedback: Get feedback early and often. It can save you time and money in the long run.
  2. Keep It Simple: Don’t overload your product with features. Focus on solving one problem well.
  3. Leverage Free Tools: Use free versions of tools wherever possible. They can be surprisingly robust for indie projects.
  4. Community Matters: Investing time in building a community around your product can pay off significantly, even if it’s not a direct cost.

Conclusion: Start Here

If you’re an indie hacker with a limited budget, start by clearly defining your product’s core value. Use free tools to get feedback and iterate quickly. Keep your marketing lean, and don’t underestimate the power of community. Remember, you don’t need a big budget to ship great products — just a clear focus and the right tools.

Follow Our Building Journey

Weekly podcast episodes on tools we're testing, products we're shipping, and lessons from building in public.

Subscribe

Never miss an episode

Subscribe to Built This Week for weekly insights on AI tools, product building, and startup lessons from Ryz Labs.

Subscribe
Shipping Stories

Lessons from Shipping 12 Products in 12 Months: What Worked and What Didn’t

Lessons from Shipping 12 Products in 12 Months: What Worked and What Didn’t As indie hackers and solo founders, we often get caught up in the notion that shipping products is all a

Oct 16, 20265 min read
Shipping Stories

What We Learned from Shipping 7 Failed MVPs: A Cautionary Tale

What We Learned from Shipping 7 Failed MVPs: A Cautionary Tale Every indie hacker has a vision. You start with an idea, build a minimum viable product (MVP), and hope it resonates

Oct 14, 20264 min read
Shipping Stories

What We Learned from Shipping 5 MVPs in 5 Weeks: A Realistic Case Study

What We Learned from Shipping 5 MVPs in 5 Weeks: A Realistic Case Study In 2026, the pressure to ship quickly is more intense than ever for indie founders. We decided to take on th

Oct 14, 20264 min read
Shipping Stories

5 Unconventional Lessons from Shipping 5 Failing Products

5 Unconventional Lessons from Shipping 5 Failing Products As indie hackers and solo founders, we often hear about the success stories that make it to the spotlight. But what about

Oct 13, 20263 min read
Shipping Stories

5 Unexpected Lessons from Shipping a Failed SaaS in 30 Days

5 Unexpected Lessons from Shipping a Failed SaaS in 30 Days In early 2026, we decided to take on a challenge: ship a SaaS product in 30 days. The goal was to validate an idea quick

Oct 12, 20264 min read
Shipping Stories

5 Lessons Learned from Shipping Our First Product in 30 Days

5 Lessons Learned from Shipping Our First Product in 30 Days Shipping a product in 30 days sounds ambitious, right? Well, it is, and it’s also incredibly rewarding. In 2026, we dec

Oct 11, 20264 min read