u/IndieSaaSMaker

https://www.validateit.app

Most devs show you a GitHub repo.

I'll show you validateit.app — a full SaaS I built completely solo. Auth, payments, community features, market intelligence. Live. Real users.

That's my portfolio.

Stack: Next.js • React • Supabase • Tailwind • Vercel

I understand the product side not just the code side — because I'm a founder who builds.

Rates: Flexible based on project scope. DM me your idea and I'll give you an honest quote.

Got a SaaS idea sitting in your notes? Drop it below or DM me 👇

One feature I built on ValidateIt that founders love:

The peer validation radar chart.

Here's how it works:

- You score your own idea on 5 dimensions

- Other founders score the same idea

- Both scores show on a radar chart side by side

The gap between the two scores = the most honest feedback you'll ever get.

Overconfident founders see it immediately.

Underrated ideas get discovered here.

Free to try → validateit.app

Would love feedback on this approach!

Built a feature on ValidateIt that shows this gap visually.

Founders score their own idea. Community scores it too. Both shown on a radar chart.

Most founders are overconfident on market size and underconfident on competition.

What's been your experience validating ideas before building?

validateit.app if curious!

Hey everyone,

Transitioning from non-AI SaaS to my first AI product and stuck on the economics.

Do you absorb API costs and bake it into pricing? Make users BYOK? Or run a credit system?

Also how do you even validate the idea without burning money on tokens before knowing if anyone wants it?

Using something like Claude Sonnet isn't cheap at scale so figuring this out before building feels critical.

What worked for you especially early stage?

Hey everyone,

Transitioning from non-AI SaaS to my first AI product and stuck on the economics.

Do you absorb API costs and bake it into pricing? Make users BYOK? Or run a credit system?

Also how do you even validate the idea without burning money on tokens before knowing if anyone wants it?

Using something like Claude Sonnet isn't cheap at scale so figuring this out before building feels critical.

What worked for you especially early stage?

Hey everyone,

Transitioning from non-AI SaaS to my first AI product and stuck on the economics.

Do you absorb API costs and bake it into pricing? Make users BYOK? Or run a credit system?

Also how do you even validate the idea without burning money on tokens before knowing if anyone wants it?

Using something like Claude Sonnet isn't cheap at scale so figuring this out before building feels critical.

What worked for you especially early stage?

Hey everyone,

Transitioning from non-AI SaaS to my first AI product and stuck on the economics.

Do you absorb API costs and bake it into pricing? Make users BYOK? Or run a credit system?

Also how do you even validate the idea without burning money on tokens before knowing if anyone wants it?

Using something like Claude Sonnet isn't cheap at scale so figuring this out before building feels critical.

What worked for you especially early stage?

Hey everyone,

Transitioning from non-AI SaaS to my first AI product and stuck on the economics.

Do you absorb API costs and bake it into pricing? Make users BYOK? Or run a credit system?

Also how do you even validate the idea without burning money on tokens before knowing if anyone wants it?

Using something like Claude Sonnet isn't cheap at scale so figuring this out before building feels critical.

What worked for you especially early stage?

Hey everyone,

Transitioning from non-AI SaaS to my first AI product and stuck on the economics.

Do you absorb API costs and bake it into pricing? Make users BYOK? Or run a credit system?

Also how do you even validate the idea without burning money on tokens before knowing if anyone wants it?

Using something like Claude Sonnet isn't cheap at scale so figuring this out before building feels critical.

What worked for you especially early stage?

Hey everyone,

Transitioning from non-AI SaaS to my first AI product and stuck on the economics.

Do you absorb API costs and bake it into pricing? Make users BYOK? Or run a credit system?

Also how do you even validate the idea without burning money on tokens before knowing if anyone wants it?

Using something like Claude Sonnet isn't cheap at scale so figuring this out before building feels critical.

What worked for you especially early stage?

Hey everyone,

Transitioning from non-AI SaaS to my first AI product and stuck on the economics.

Do you absorb API costs and bake it into pricing? Make users BYOK? Or run a credit system?

Also how do you even validate the idea without burning money on tokens before knowing if anyone wants it?

Using something like Claude Sonnet isn't cheap at scale so figuring this out before building feels critical.

What worked for you especially early stage?

I’m currently building my first SaaS product and honestly, pricing feels harder than building 😅

I don’t want to:

- overprice and lose early users

- underprice and make it unsustainable

Right now I’m thinking about how to set pricing in a way where users feel comfortable paying without hesitation or regret.

For those who’ve already launched:

- How did you decide your initial pricing?

- Did you start cheap and increase later?

- Subscription vs one-time — what worked better for you early on?

- How do you make users feel like it’s “worth it” without overthinking pricing?

Still figuring this out, so would love to hear real experiences.

I’ve been noticing that a lot of things in SaaS look simple from the outside, but are way more difficult once you actually start building or trying to get users.

Curious what caught you off guard the most.

I’ve been noticing this a lot lately…

whenever I want to stay updated on something (like SaaS ideas, trends, etc), I end up checking the same places again and again — Reddit, Twitter, YouTube, blogs

most of it is just noise, and only a small part is actually useful

it feels like more time is spent filtering than actually learning anything

I’m thinking about building something that just surfaces the useful insights instead of making you search repeatedly

but before doing that, I want to understand —

is this actually a real pain for you too?

or do you already have a way to deal with it?

What’s a small but annoying problem in your work that you wish had a simple tool?

Not looking for big startup ideas…

More like:

- something repetitive

- something you do manually

- something that just wastes time or feels inefficient

I’m exploring ideas for a small tool (micro SaaS) and wanted to hear real problems people are dealing with.

Would love to know what’s bothering you in your daily workflow.

I’m exploring a tool for WooCommerce stores to identify repeat returners and refund loss patterns.

The problem seems real — a small group of customers often causes most returns.

Now I’m trying to figure out the right direction:

• Keep it as a simple plugin (easy adoption, local use)

• Or evolve it into a SaaS (central dashboard, insights, alerts)

My concern is not overbuilding too early, but also not limiting the potential.

How would you approach this?

Would you validate as a plugin first, or start building SaaS features early?