u/AdubsOK

I'm building a niche B2B SaaS tool and trying to be disciplined about not over-building before I've validated demand. I'm sure this approach makes sense to people who've done this before, but I would love to get some feedback and understand more specifics...

The short version: I identified a pain point I personally experience in my own work (silent failures in automation workflows), built a landing page, and I'm collecting founding member signups at a discounted lifetime rate before writing a single line of product code. The idea is to hit 50 signups as a signal that there's real demand before I commit to building the full thing.

A few things I'm genuinely unsure about:

1. Is 50 signups a reasonable validation threshold for a $49/mo B2B tool, or is that too low to mean anything? I've seen people say 10 is enough and others say you need 100+ paying customers before it counts (For now, I'm not taking payment, just creating a list).
2. I'm doing organic marketing only right now (Reddit, niche communities, LinkedIn). No paid ads until I have something to show. Does that make sense at this stage or am I leaving early adopters on the table?
3. The founding member pricing is locked for life. Good hook or bad precedent? I've heard arguments both ways.

Happy to share more context on the product if it helps. Mostly just want a gut check from people who've been through this before. I could use feedback on the landing page itself from a design perspective, but I'm not sure if this is the right place to ask for that. If anyone wants to lend an eye, that'd be great, just let me know.

In the meantime, what am I missing? Any tips, tricks, or effective methods for validation and initial awareness are appreciated!

I'm building a niche B2B SaaS tool and trying to be disciplined about not over-building before I've validated demand. I'm sure this approach makes sense to people who've done this before, but I would love to get some feedback and understand more specifics...

The short version: I identified a pain point I personally experience in my own work (silent failures in automation workflows), built a landing page, and I'm collecting founding member signups at a discounted lifetime rate before writing a single line of product code. The idea is to hit 50 signups as a signal that there's real demand before I commit to building the full thing.

A few things I'm genuinely unsure about:

1. Is 50 signups a reasonable validation threshold for a $49/mo B2B tool, or is that too low to mean anything? I've seen people say 10 is enough and others say you need 100+ paying customers before it counts (For now, I'm not taking payment, just creating a list).
2. I'm doing organic marketing only right now (Reddit, niche communities, LinkedIn). No paid ads until I have something to show. Does that make sense at this stage or am I leaving early adopters on the table?
3. The founding member pricing is locked for life. Good hook or bad precedent? I've heard arguments both ways.

Happy to share more context on the product if it helps. Mostly just want a gut check from people who've been through this before. I could use feedback on the landing page itself from a design perspective, but I'm not sure if this is the right place to ask for that. If anyone wants to lend an eye, that'd be great, just let me know.

In the meantime, what am I missing? Any tips, tricks, or effective methods for validation and initial awareness are appreciated!

I'm building a tool that monitors Make and n8n workflow execution patterns and flags when something looks off. Not just "did it crash," but more like "it's running, just differently than it normally does."

Right now I'm using a rolling Z-score on execution frequency (runs per hour, basically). It works reasonably well for catching sudden drops or spikes, but I'm already seeing its limits... mostly around workflows that have natural weekly patterns. Ex: a workflow that legitimately runs 10x on weekdays and near-zero on weekends would look like a crisis every Saturday.

I'm planning to add seasonal decomposition down the road to handle that, but curious what else people have found useful for this kind of problem.

Specifically wondering about:

• Whether CUSUM is worth the added complexity for catching slow drift
• If anyone's actually used Isolation Forest in a production monitoring context
• Whether output validation (checking if the workflow result makes sense, not just whether it ran) is worth pursuing early or if it's a rabbit hole

Anyone dealt with this kind of problem before? Open to being told I'm overcomplicating it too.

I've been building automations lately (mostly n8n, but some with Make just to get more familiar) and the thing that keeps catching me off guard isn't the crashes. It's the workflows that technically keep running but quietly drift out of sync with reality.

The trigger fires, the webhook succeeds, the logs look clean, but underneath, the context has shifted. Nothing looks broken until someone notices the outputs are just... off.

The more complex the automation stack gets, especially once you layer in AI responses, async triggers, multi-channel sequences, the harder it is to catch this stuff early.

I started building something to tackle it. The core idea is monitoring execution patterns over time rather than just pass/fail status. Right now I'm using a rolling Z-score to flag deviations from baseline behavior. Planning to add output validation with AI down the road.

Still early and honestly not sure if I've fully cracked it yet. Curious if anyone else has run into this and what methods you've used to catch anomalies before they turn into bigger problems. Open to ideas!