🚨 GIVEAWAY ALERT 🚨 $325 SaaS boilerplate for FREE Comment your SaaS idea below Repost this tweet If your idea excites us, you get full access to @ts_saas Auth, billing, email, multi-tenancy all production-ready WE'RE PICKING LIMITED FOUNDERS What are you building? 👇 #saaskit

#Marketing for #SaaS Don't just sell → Teach Write on X → Tutorials → Guides → Technical posts Help your users become better at their jobs #indiehacker

Hey @tannerlinsley, @AlemTuzlak , @schanuelmiller 👋 I'm stuck on a routing issue with TanStack Router and wondering if I'm modeling this incorrectly. I have: /{-$locale}/ → homepage (locale is optional because English is the default and should live at /) /{-$locale}/(extra)/$slug → SEO landing pages My goal is to support URLs like: / → English homepage /es → Spanish homepage /fr → French homepage /about-us → SEO page /es/about-us → Localized SEO page The problem is that when I visit /es, the router matches the slug route and I get: { slug: "es" } instead of: { locale: "es" } I also get this warning: Generated path "/fr" for route "/{-$locale}/" matched route "/{-$locale}/(extra)/$slug" instead. I tried treating locale codes as reserved values and redirecting snippet. but that just creates an infinite redirect loop because /es keeps matching the slug route again. Is this simply an inherently ambiguous route setup, or is there a recommended pattern for handling optional locale prefixes while keeping SEO pages at the root level? Would love to know how others are solving this. Thanks!

We sell #saasboilerplate and we put this at the bottom of our pricing page "Treat the purchase as a business investment, not a get rich quick scheme." TS-SAAS isn't for people who want shortcuts It's for founders who are serious about shipping and want to stop wasting weeks on infrastructure that's already been solved #saas #saaskit

Everything you need 24 hours before, during, and after your @ProductHunt launch to hit the Top 5. Night before ☐ Launch at exactly 12:01am PST ☐ Write your maker comment in advance ☐ Brief your hunter, don't assume they know the pitch ☐ Message your warm list personally, not via blast Launch day ☐ Reply to every comment within minutes ☐ Post live updates on Twitter every 2–3 hrs ☐ DM warm supporters, a personal ask ☐ Launch-day offer ready, give people a reason to act now After ☐ Thank commenters publicly ☐ Share the real numbers, good or bad ☐ Write the "what I learned" post Save this. Use it. #saas

How long did auth billing take on your last SaaS build? Be honest, no judgment – 1 week – 3 weeks – 2 months – till not done💀 #saas #saaskit #indiehacker #developer

the real question is whether the workflow survives the bill subsidies hide economics businesses eventually reveal them 🥲

Most #indiehackers underprice by 3–5x. Why → You price against your cost, not customer outcome → You're pricing for yourself, not your buyer Fix → What does it cost them NOT to use you? → Price against that number Your first instinct is almost always too low Double it. Then find out why people say no. #saas #saasboilerplate #TSSAAS

Most things that happen in a 1hr meeting could be a 3-paragraph message The best indie hackers I follow protect their focus the same way they protect their code

Hot take💀 The biggest tax on #indiehackers isn't App Store fees or Stripe's cut It's the 2-3 months you spend on auth, billing, and email before writing a single line of product code It's invisible Nobody talks about it But it's the reason most good ideas never ship #saasboilerplate #saaskit #TSSAAS

$325 sounds like a lot until you do the math 200 hours building auth, billing & multi-tenancy yourself. At even $20/hr of your time = $4,000. #TSSAAS Foundation is $325. One-time. We put a calculator on the pricing page so you can verify the numbers Drag it yourself ( link below ) #saasboilerplate #saaskit #saas

every single time💀 #meme #indiehacker #saas #saasboilerplate

Be honest when starting a new SaaS, how do you handle auth & billing? - Build from scratch - SaaS boilerplate 🔥 - Stitch libraries together pray - Outsource it

#ios27 support to these iphones #WWDC26

we are back with simpler sidebar in macos. #WWDC26 