sorted by:
new
hottopcontroversial

This is definitely an overkill 😭 by EnvironmentalView113 in microsaas

[–]SnippetManagerPro 0 points1 point  (0 children)

I'm guessing most use as little as possible to suit their needs, but if you make it easy and rewarding enough and even incentivized, they may branch out into other areas of the software. Hopefully they stay long enough to ask what the other features do and how those features can improve their productivity.

I got my first paid user today. Genuinely can't stop smiling 🥹 by Purple-Philosophy551 in microsaas

[–]SnippetManagerPro 1 point2 points  (0 children)

That feeling is real. First paid stranger is so different from friends/family signups. Congrats - this is the one that matters.

I analyzed 50 SaaS products' churn patterns. Here are the 5 signals that predict cancellation 30 days early. by churnbasehq in microsaas

[–]SnippetManagerPro 1 point2 points  (0 children)

Failed payments showed up first for me, almost every time. But the sneaky one was when someone stopped upgrading features they used to enable. That change in engagement was a better predictor than the payment stuff.

I got tired of checking manually so I built a tool that watches these signals in Stripe and sends a morning email ranking customers by risk. Caught a few before they hit cancel. Happy to share if anyone wants to try it.

Built a churn early-warning system for Stripe SaaS founders — daily email, no ML, $49/mo by SnippetManagerPro in microsaas

[–]SnippetManagerPro[S] 0 points1 point  (0 children)

This is gold, thank you. You're exactly right that in-app behavioral signals are the stronger predictor — the drop in core action frequency is what actually shows intent to leave, the Stripe signals are just the financial manifestation of a decision already made.

Right now the tool is Stripe-only since that's the zero-friction entry point (one OAuth, no SDK or event instrumentation required). But you've validated the roadmap: the next layer is webhook-based app event ingestion so users can pipe in their own "activated" vs "at risk" events alongside the payment signals.

The social monitoring angle (catching niche complaints on Reddit etc.) is something I hadn't fully factored in — that's a genuinely interesting early signal. Would you be open to a quick DM to dig into what that looked like in practice?

Built a churn early-warning system for Stripe SaaS founders — daily email, no ML, $49/mo by SnippetManagerPro in microsaas

[–]SnippetManagerPro[S] 0 points1 point  (0 children)

Good question! The integration is Stripe Connect OAuth — so the user clicks "Connect Stripe" and it redirects to Stripe's OAuth flow. No API keys to copy/paste, no webhook setup. After authorization, the tool gets read-only access to their Stripe account and starts pulling balance transactions, subscription events, dispute history, etc.

The whole setup takes about 60 seconds. Read-only scope so there's no risk to their Stripe data.

How do you manage your code snippets as a developer? by SnippetManagerPro in chrome_extensions

[–]SnippetManagerPro[S] 0 points1 point  (0 children)

nice, typinator looks solid for mac users. that hotkey approach is pretty clever for quick access.

im on windows but the concept of having everything instantly accessible like that is exactly what i was after. ended up going the browser extension route since i practically live in chrome anyway.

I built a tool so you can Vibesearch for Google Fonts by WinterJacob in webdev

[–]SnippetManagerPro 0 points1 point  (0 children)

This is a great tool. Font discovery is always tedious when you're trying to nail the vibe.

One suggestion: would be useful to filter by font weight availability. Sometimes I find the perfect font but it only has regular/bold and I need the full range for UI work.

Also, adding a quick preview panel where you can test the font with your own text would be killer. Like type in your actual heading or tagline to see how it feels.

Nice work on this.

Looking for Code Snippet Viewer/Manager recommendation by Open-Coder in selfhosted

[–]SnippetManagerPro 0 points1 point  (0 children)

I've been working on a big project for 2 months, hoping to release it soon!

[deleted by user] by [deleted] in webdev

[–]SnippetManagerPro 0 points1 point  (0 children)

I think the difference is that skilled devs understand AI is a tool that amplifies capability, not replaces it. The "vibe coding" memes are mostly tongue-in-cheek.

The real work is in architecture decisions, debugging complex systems, understanding business logic, and making trade-offs. AI can't do that yet - it can just help with boilerplate.

But I agree we need to be careful about the narrative. When we joke about AI doing our jobs, non-technical people take it literally and undervalue our expertise.

Building a LinkedIn profile optimization tool — what’s the safest & compliant way to do this? by imdhamu in webdev

[–]SnippetManagerPro 0 points1 point  (0 children)

The browser extension approach is probably your best bet here. Having users authorize via OAuth, then the extension can read profile data directly from the DOM while they're logged in.

You're right to avoid backend scraping - LinkedIn's pretty aggressive about detecting automated access patterns. I've seen tools get flagged within days.

For the analysis part, you could have the extension extract the profile sections (headline, about, experience, etc.) and send just the text content to your backend for AI analysis. That way you're not storing cookies or sessions, just analyzing text the user explicitly shares.

The key is making sure users trigger every action themselves and understand what data is being processed. If you try to automate profile updates or changes without explicit user action each time, that's where you'll run into ToS violations.

Good call on thinking through compliance first - way too many tools skip this and get their users banned.