Joren

AI student building in public. Exploring AI products for small B2B teams and sharing the journey from 0 to first customers.

[Joren @wsj549382]

@fromadstoassets Respect for posting the crater and not just the wins. Fraud refunds at that order size usually cluster around a few patterns (same BIN, rushed shipping, mismatched AVS) - worth tagging them for a couple weeks, you'll spot the leak. Following the journey 🫡

[Joren @wsj549382]

@WhaleInsider The "support = profit center" framing is the real story. The margin isn't in resolving tickets faster - it's in what they tell you: which refunds were preventable, which SKUs drive returns. The AI's only as good as whether anyone acts on the reasons.

[Joren @wsj549382]

@paddymedia The "support = profit center" framing is the real story. The margin isn't in resolving tickets faster - it's in what they tell you: which refunds were preventable, which SKUs drive returns. The AI's only as good as whether anyone acts on the reasons.

[Joren @wsj549382]

@thats_roy Depends on the use case more than the tool. For a Shopify/DTC store Gorgias wins - it sits right on top of orders/refunds and the macros are ecom-native. Zoho for B2B/cost-sensitive, GHL if it's really an agency/CRM play. What are you running it for?

[Joren @wsj549382]

@dtcjohnd Shipping-delay chargebacks are usually "where's my order" disputes, not fraud. Proactive delay emails before the ETA kill that reason code. When they hit, can you see the reason codes broken out, or does the processor just lump them together?

[Joren @wsj549382]

@Acuity_co Question for ecommerce accounting teams: when Shopify, bank deposits, refunds, fees, and tax reports disagree, what usually creates the biggest close delay?

[Joren @wsj549382]

@ElverEcommerce For Shopify + Xero clients, do payout/refund mismatches still require manual investigation, or have tools like A2X mostly solved the root-cause side?

[Joren @wsj549382]

Validating a B2B idea from zero.

I realized “do you need a security review?” is probably the wrong question.

Better question:

Before launching your SaaS, what are you most afraid could break?

Auth? Payments? User data? API keys? AI outputs?

[Joren @wsj549382]

@alwayspriyesh @X I’m validating a B2B idea for AI-built SaaS founders and sharing the process from 0.

Still figuring out the problem, positioning, and distribution, but trying to stay active and learn in public.

[Joren @wsj549382]

Context:

I’m exploring a lightweight pre-launch security review for AI-built SaaS founders.

Things like auth, data access, exposed keys, payment flows, and LLM/data risks.

Not selling a SaaS yet. Just trying to understand if this is a real pain.

[Joren @wsj549382]

Trying to validate a B2B idea from zero.

Reality so far:
- X posts get 5-6 views
- cold emails got 0 replies
- not sure if the problem is the idea, audience, or message

For founders who validated without an audience:
what would you do next?

[Joren @wsj549382]

@zuess05 I’ve been wondering how you managed to hit $10,000 MRR.

[Joren @wsj549382]

@ben_sage Codex,Codex is more of a productivity tool, while Claude Code leans toward vibe coding.

[Joren @wsj549382]

The areas I’m looking at:

- auth edge cases
- Supabase/Firebase rules
- exposed keys
- Stripe webhooks
- admin routes
- user data exposure
- LLM input/output risks

Not selling a SaaS yet. Just trying to understand if this is a real problem.

[Joren @wsj549382]

I’m validating a B2B AI idea in public.

One thing I’m trying to understand:

When indie hackers launch AI-built SaaS fast, do they actually worry about security before launch?

Or is it only painful after something breaks?

Talking to founders this week to find out.

[Joren @wsj549382]

@marclou Staying persistent means everything for indie hackers. I’m curious how everyone sticks with it, and what keeps you going.

[Joren @wsj549382]

@markproduct Now non-technical people are widely using vibe coding to build their own products, and they often overlook potential security vulnerabilities. My service provides security audits for indie hackers before they launch their products.

[Joren @wsj549382]

@TTrimoreau In this day and age, I think programmers should focus on learning how to sell their own products instead of burying themselves in coding nonstop.

[Joren @wsj549382]

@Taniyatweets_ Fable is too expensive

[Joren @wsj549382]

@egorkabantsov Day 1 of building in public，lets connect