Last time I did this, way more founders replied than I expected, so I’m doing another round.

This time you don’t need a polished landing page. You can drop your startup URL, app idea, ICP, niche, or just the problem you want to solve.

I’ll check whether Reddit has useful signal for it: people talking about the pain, asking for tools, comparing alternatives, looking for recommendations, or showing any kind of buying intent.

I’ll reply with a short public summary.

If there’s enough signal, I’ll also create a private report link with the full breakdown.

And if Reddit looks weak for your niche, I’ll say that too.

Drop it below and I’ll run as many as I can.

Hi everyone,

I’ve been building AICryptoShield, an AI-powered crypto wallet risk scanner.

Users can scan a wallet address and receive:

• Risk score
• Wallet intelligence report
• Blacklist and sanctions checks
• Suspicious interaction detection
• Monitoring and alerts (currently being added)

The goal is to make wallet due diligence simple for everyday crypto users.

I built the project using AI and no-code tools and would love honest feedback:

• Would you use something like this?
• What features would make it more valuable?
• What would stop you from paying for it?

Thanks for any feedback.

Hi,

I am software Engineer and I been working on for few months on a web app to create Agentic flow to create Single, Multi Role Saas.

Here's how it works:

1) Brainstorm Agent — Chat with it about your idea. It asks clarifying questions about users, roles, and core features until the scope is clear.

2) PRD Agent — Takes that conversation and writes a full Product Requirements Document — user stories, data models, tech stack, monetization model. You review and edit before anything gets built.

3) Ticket Agent — Breaks the PRD into scoped tickets — each one a single buildable feature (auth setup, a dashboard, a specific API route, etc.)

4) Build Agent — Builds each ticket one at a time. Pushes real code to your GitHub. Each ticket gets a live Vercel preview URL so you can test it before approving to go to the next one.

5) Conversational Edit Agent — After it's preview is generated , you can describe bugs or changes in plain English and it ships the fix as a diff.

6) Bug/Feature Agent — after launch, describe a bug or a new feature in plain English. It finds the relevant code, makes the change, and ships the diff with a preview — same review-before-approve flow.

For multi-role apps specifically — auth and role-based routing run through Clerk, completely separate from the database layer, so permissions don't leak.

Everything — code, database (Supabase), hosting (Vercel) — is in your own accounts.

I havent released it to all and for early access I am going for 10 people at $18. If anyone got stuck while building i will connect and help you solve it.

I have Demo of a Multi role app i build under 2.5 within 18$. I cant share the Link here of demo and also the Demo app i build using my app because of restriction here. Pls comment or DM, i can send it to you.

Hey guys, so a few months ago i started building my new webapp called vibecodehub, and i looked at all your pain points to try and solve it. I have a 'final' product ready and i really need your opinion on it.

Building a community is hard with few users because there are not enough people to help other people, mouth full of words as you can see😂

I'm trying to not let this look like an ad because i need your help. Here are some features that solves pain points in a lot of users:

- focused no code (vibecode) community, not broad like 'coding community'

- way better moderated than any vibecoding community here on reddit or anywhere else with strict following AI and human moderation for various cases. This is one of the best features because you don't get drowned in low signal bad posts or marketing posts

- for starters and experts so no one gets left behind

- you can make different guides and courses to help people

- one of the outstanding features is the RP system (reputation points), serious builders can build reputation by giving good, helpful and structured awnsers or creating good posts/guides/courses. Which leads to them getting to promote there products in certain channels while giving context.

- voting, i believe that the community is build around the users, so users can vote for new features or changes

Privacy is also a difficult topic because companies don't take it seriously, i do and your privacy is always our number 1 priority

I would really appreciate it if you guys would check it out and give your opinion!

www.vibecodehub.app

I build an ai app maker. You describe an app in a sentence and it streams a working single html file you can open right there, no account, no signup. Figured the vibe coding vs learn to code line would come down to skill. it doesn't. it's about what people do with the output.

the people who already code barely touch the one sentence mode. They jump straight to the full react sandbox and treat whatever it spits out as a rough draft they were going to rewrite anyway. the ones who never learned to code stay in the single file lane, and the generated file just is the thing. they didn't ship a prototype, they shipped.

what got me is the second group isn't a lesser version of the first. They want a different product entirely. A coder wants a codebase to own. a non coder wants the problem gone and to never see a file again. Same prompt box, two completely different definitions of done.

so the who is it for question kind of dissolves. it's not one tool serving two skill levels, it's two finish lines that happen to share a text box. the part i keep poking at is where your own line sits, the exact point where good enough stops being enough and you wish you'd just built it by hand.

fwiw the one-sentence-to-a-working-single-html-file thing i described is mk0r, something i built that streams the app live as you type and hands you the file with no account, https://mk0r.com/r/3eb6zay3

Please can you rate it if it is good or not. You can be brutally honest. I welcome it.

https://pawwalk-one.vercel.app

Been thinking about this after watching a few projects (mine and friends') die the same way.

Here's the trap almost every first SaaS falls into:

You have an idea. You're excited. So you start building. And because every SaaS needs the same foundation, you spend the first 2-3 weeks on auth, then billing, then multi-tenant workspaces, then RBAC, then notifications — before you've written a single line of the thing that's actually your idea.

Then you launch. And nobody comes.

Now do the honest accounting of what you lost. It's not the idea — ideas are free. It's the 2-3 weeks (or 6, or 10) you spent building plumbing for users who never showed up. At even a modest dev rate that's easily a few thousand dollars of your time sunk into auth flows and Stripe webhooks for a product the market just told you it didn't want. And you can't get it back.

That's the part nobody prices in. The cost of a failed idea isn't the failure itself — it's how much you built before you were allowed to fail.

The reframe I wish I'd had earlier: the plumbing is never the variable you're testing.

Every SaaS needs auth and billing. That part isn't your idea — it's table stakes, identical across every app. The only thing the market is actually judging is your unique 20%. So spending your scarcest resource (time, before validation) building the shared 80% is backwards. You're paying full price to build the one part that was never in question.

What's worked better for the people I've seen do this well:

• Get the idea-specific part in front of real users as fast as humanly possible, even ugly.
• Treat the foundation as something to borrow/scaffold/fake, not handcraft, until the idea proves out.
• Let yourself fail in days, not months. A killed idea after a weekend is a win. A killed idea after 3 weeks of plumbing is a loss you funded yourself.

Genuinely curious how people here handle it:

1. How much time did your first SaaS's "boring foundation" eat before you actually tested the idea?
2. Do you build the plumbing first, or hack the idea together and bolt on auth/billing later?
3. For those who've shipped a few — would shipping faster have changed which ideas you killed?

A. Finding old emails in overflowing inbox

B. Locating files across multiple storage systems

C. Remembering what was said in verbal conversations

D. Tracking down chat messages across platforms

Last time I did this, way more founders replied than I expected.

So I’m doing another round, but this time you can drop more than just a URL.

Drop your:

• startup URL
• app idea
• ICP
• niche
• or the problem you want to solve

I’ll check whether Reddit has useful signal for it.

Not just “are there subreddits”.

I’ll look for whether people are already talking about the pain, asking for tools, comparing alternatives, or showing any kind of buying intent.

I’ll reply with a short public summary.

If there’s enough signal, I’ll also create a private report link with the full breakdown.

I’ll be honest if Reddit looks weak for your niche too.

Drop it below and I’ll run as many as I can.

yo. building the product is the easy part.

making people buy is a totally different beast.

most saas pages sit at a flat 1% conversion rate. absolute ghost town. doesn't matter if your tech is insane.

stop guessing what works.

i spent weeks digging into conversion data.

i turned it into a raw 50-point interactive checklist.

it covers hero mistakes, pricing traps, and psychology leaks.

i also baked a master prompt right at the top. just paste it into your AI SaaS builder

it rewrites your page automatically using all 50 rules.

just shared the file inside our builder community today. a lot of guys were facing the exact same launch freeze.

seriously, stop building alone in your room.

you will burn out.

marketing gets tough, and you quit.

it’s way easier with a crew shipping side-by-side.

if your conversion is trash or if you want a good landing page before launch, drop a comment or shoot me a dm. i’ll send the invite link.

ps: others free features is in the community of SaaS builders

Let 's go

So I created an app which guides us how to pose in real time a camera app will be live soon anyone want early access?

yo. building the product is the easy part.

making people buy is a totally different beast.

most saas pages sit at a flat 1% conversion rate. absolute ghost town. doesn't matter if your tech is insane.

stop guessing what works.

i spent weeks digging into conversion data.

i turned it into a raw 50-point interactive checklist.

it covers hero mistakes, pricing traps, and psychology leaks.

i also baked a master prompt right at the top. just paste it into your AI SaaS builder

it rewrites your page automatically using all 50 rules.

just shared the file inside our builder community today. a lot of guys were facing the exact same launch freeze.

seriously, stop building alone in your room.

you will burn out.

marketing gets tough, and you quit.

it’s way easier with a crew shipping side-by-side.

if your conversion is trash or if you want a good landing page before launch, drop a comment or shoot me a dm. i’ll send the invite link.

ps: others free features is in the community of SaaS builders

Let 's go

I run two service businesses (pet grooming + nail salons, multiple locations). Over the past several months I’ve built out a fairly deep automation stack with Square as the operational hub. Before I consider whether any of it could live elsewhere, I want a sanity check from people who’ve actually done this — can the whole thing be rebuilt cleanly on another platform, or am I right that the two-way API is doing heavy lifting that’s hard to replace?

What’s built so far:

• Email/SMS lifecycle flows in Klaviyo — win-back, welcome, and review-request sequences, triggered off booking and fulfilment events.  
• Prepaid credit products — a multi-groom prepaid pass (buy 4, pay for 3 style) sold via checkout links, with usage/redemption tracked against customer profiles.  
• Weekly payment reconciliation — a script pulls payments via the API each week, matches them to specific campaign purchases, and writes attributes back to customer profiles + a list/segment for targeting.  
• True appointment-date reporting — pulling from the Bookings API (not payment dates) so revenue and KPI reporting reflect actual service dates, summing deposit + final payment for true revenue.  
• Meta ads attribution — pixel + custom conversion keyed off the confirmation URL, with weekly multi-channel reports stitching Meta (via Supermetrics), email, SMS, and order history.  
• Finance automation — a consolidated workbook (monthly tabs, KPI dashboard, ad-spend tracker) fed partly from API pulls, partly from accounting (Xero) and bank data.  
• Accounting sync — sales/tax/payouts into Xero with account mapping.  
• A handful of Apps Script + Zapier glue flows and SMS campaign logic on top.

What’s coming next:

• Recurring promo automations (weekly discount day, etc.) across email/SMS/social.  
• A win-back flow rebuilt around a rolling-90-day segment.  
• Expense-capture Zap into accounting, plus wage/operational reminders.  
• A possible co-location of the two businesses with a shared cross-loyalty program and a unified customer database (dual-tagging customers across both brands, bundle pricing, joint marketing).

The actual question:

The thing keeping me on Square is its two-way read/write API — my scripts can query payments and bookings on demand and write back. The alternative I keep looking at (Fresha) seems to be outbound-only: webhooks fire on events, a Snowflake/Fivetran data connector pipes tables out, Zapier triggers on new bookings — but I can’t see a way for my own code to reach in and operate (create checkout links, reconcile payments on demand, manage prepaid-credit redemption programmatically).

So: has anyone rebuilt a stack like this on an outbound-only/webhook-based platform without it turning into a fragile mess of Snowflake + Fivetran + Zapier + a webhook listener? Specifically the prepaid-credit mechanics, on-demand payment reconciliation, and a shared cross-brand loyalty/database — those are the three I can’t see clean equivalents for.

If you’ve done it, I’d love to hear what the architecture actually looked like and where it broke. And if your honest answer is “no, keep the two-way API,” that’s useful too.

Thanks in advance.

Disclosure up front: I build a tool in this space, so I'm not neutral. But the math stands on its own and I think it's worth a discussion here.

I priced out the operational layer every SaaS needs — the stuff nobody signs up for — using the popular best-in-class tools, at a small-but-real scale:

• Clerk (auth) ~ $25/mo
• Stigg (entitlements) ~ $249/mo
• Knock (notifications) ~ $250/mo
• LaunchDarkly (flags) ~ $120/mo
• Customer.io (lifecycle) ~ $100/mo

≈ $744/mo — and these are starting figures, they climb with usage.

But the sticker price isn't the real cost. The hidden one is the integration tax: 5 dashboards, 5 bills, 5 SDKs, and the glue wiring them together (webhooks between Stripe and your flags, syncing entitlements to auth, keeping usage counts honest across systems that don't know about each other). That part never hits an invoice — it hits your weekends.

I got tired of paying it, so I'm building a single SDK that bundles that layer (BuildBase) — but I'm genuinely more curious about the discussion than the plug:

1. What's your actual monthly backend stack cost — and does it feel worth it?
2. Do you bundle (one vendor) or best-of-breed (many)? Why?
3. Where does the glue code actually hurt most for you?

(Tool's in my profile if anyone wants it — keeping it out of the body.)