r/saasinvestors

Hey everyone, I’m Bailey, co-founder and CEO of Cal.com. I started building Cal.com at 17.

Since then, Cal.com has grown to more than 1M users, raised over $32M, and reached a valuation above $200M.

I’ve spent the last few years building, hiring, fundraising, and scaling in a competitive SaaS market. Ask me anything about fundraising, working with investors, growth, or the decisions and mistakes behind the journey.

If you’re building something, navigating your career, or curious about how companies get built, leave your question below.

Jacob Solano, Head of Partnerships & Community at Fibe, and I will use this thread to help prioritize what we cover during our live AMA on X on August 26 at 11:00 AM ET.

RSVP to join the live: https://cal.com/bailey-and-jacob-ama

Hi all,

As i'm working on growing launchpact.io i'm seeing a lot of unprepped launches and as the day unfold they don't get much visibility and end up with a failed launch.

This is one of the reasons i build launchpact.io, if you have an upcoming launch do check it out and prep ahead of time, i also added this checklist that can give some hints too, have a read.

Good luck everyone!

I built Walnut Markets because most stock research still feels way too fragmented.

You can find Congress trades, insider filings, institutional data, technicals, fundamentals, contracts, and news — but usually not in one place, and rarely with a clear read on what the data is saying.

Walnut is my attempt to fix that.

It tracks:

- Congress disclosures

- Insider activity

- Government contracts

- Institutional filings

- Technicals / price-volume

- Fundamentals

- Watchlists and screeners

- Bullish and bearish monitors

- A proprietary confirmation score

The goal is not stock picks.

The goal is better research.

If $MU is moving, I want to know whether the data actually supports the move: revenue, EPS, margins, price action, institutional activity, insider/Congress disclosures, and what to watch next.

Free tools are great for alerts. I’m trying to build something more useful for actual research.

Would appreciate any feedback, especially from people who track filings, insiders, Congress trades, or earnings closely.

https://walnutmarkets.com

Research only. Not investment advice.

Around 2-3 weeks ago I launched my SaaS, SeoLoupe.

It is a lightweight SEO tool that helps you find and fix SEO issues holding your website back, currently I am at 432 users and 5 paying users.

Essentianly the main purpose is to help your website rank higher on Google search and LLMs.

Since I am always trying my best to improve the product, I am happy to answer any questions or any feedback in the comments.

(here is the product if you want to check it out)

TaskLoco is a sticky-note storyboard workspace for tasks, events, notes, projects, files, reminders, and anything you can stick in or attach to a digital sticky note.

Freemium version now includes 100 taggable sticky notes no strings attached

Website: https://www.taskloco.com

Unlike other productivity apps TaskLoco goes with your flow.

It’s visual and spatial so you can actually focus because you can literally see what you’re doing

TaskLoco is visual sticky-note storyboard for tasks, events, docs, notes, media & files.

Anyone can TRY IT FREE @ (https://www.taskloco.com)

My SaaS apps auto-deploy off main. Updates pile up (security, features), but merging at 14:00 is a deploy at 14:00 and knocks people off the app.

GitHub auto-merge and Azure DevOps auto-complete fire when checks pass. Neither will wait until Friday 18:00. Neither will refuse a Saturday merge.

Scheduled-PR is a GitHub App and an Azure DevOps extension. Comment /schedule friday 18:00 Europe/Berlin (or a label, or the dashboard). At that instant it re-reads the PR: still open, no conflicts, checks green, outside your blackout windows. Then it merges, or it says why not.

One bot comment per PR, edited in place. Policy lives in .scheduled-pr.yml in the repo.

https://scheduled-pr.dev

6 security checks you can run on your own SaaS in 15 minutes :

I am a cybersecurity enthusiast and the same handful of mistakes shows up in almost every app built fast. None of these need a tool.

1. Row-level security is off Your Supabase anon key is public by design. RLS is the only thing stopping anyone from reading every row. Check: Table Editor, look for the "RLS disabled" badge. Any table with user data and that badge is a public database.
2. RLS is on but the policy allows everything using (true) is the same as no policy. Check: Authentication > Policies. If a policy never references auth.uid(), it is not restricting anything.
3. Secrets in NEXT_PUBLIC_ or VITE_ variables Those get compiled into the JS bundle and shipped to every visitor. Service role keys land here constantly because the AI put them there to clear an error. Check: grep -rn "NEXT_PUBLIC_\|VITE_" .env*. Would you print each value on your homepage? If not, move it.
4. Auth that only runs in the browser A redirect in a React component is a suggestion, not authentication. Check: curl your most sensitive API route with no session cookie. If it returns data, your auth is in the wrong place.
5. .env in git history Deleting the file does not remove it. If the repo was ever public, assume the keys are gone. Check: git log --all --full-history -- .env. Any output means rotate today.
6. Webhook with no signature check Anyone who finds the URL can POST a fake "payment succeeded" and upgrade themselves free. Check: your Stripe or Paddle handler. If it reads the body before verifying a signature, it is an open door.

1 and 4 cause most of the breaches you read about. Moltbook leaked 1.5M API tokens in February from exactly that combination: publishable key in client JS, RLS off

Disclosure: I have build Sentrint (https://sentrint.com/?utm\_source=reddit), which automates these. Feel free to ask me any questions.

Which of these did you find on your own app?

Hey everyone,

Over the past year, I’ve been working on a personal project — designing a wireless phone/headphone charger made out of wood and leather. To bring the project to life, I bought a CNC machine about 6 months ago.

That immediately launched me into a black hole of prep work: building a soundproof enclosure, ordering end mills, sourcing stock materials, and buying endless small parts.

Very quickly, I hit a wall. Managing inventory, material costs, and project estimates in Google Sheets was a massive pain — especially when I just wanted to be at my workbench, not booting up a PC to update a cell.

Since I’m a developer, I decided to build a simple tool to solve my own headache. Fast forward 5 months, and I just released the first version of Trace on the App Store.

What Trace does:

Workshop Inventory: Track stock (wood, acrylic, hardware, tools) straight from your phone.

Project Costing: Calculate the real cost of every build (materials + labor) on the fly.

Invoices: Instantly generate clean PDF receipts/invoices for clients or sales.

Since I built this out of a genuine need from my own maker journey, I would love to get your honest feedback, critique, or feature ideas so I can keep improving it for the community.

You can check it out on the App Store: https://apps.apple.com/lv/app/trace-workshop-manager/id6789042632

Thanks for reading, and happy making!

Building a SaaS is one thing. Getting people to notice, visit, and actually engage with it is another.

Drop your SaaS below with:

1. What it does
2. Who it’s for
3. What’s currently holding back your growth

I’ll check out as many as possible and share honest feedback.

I’m building Shipflash, a production-ready SaaS foundation that helps founders skip repetitive setup and focus more on building, launching, and growing the actual product.

https://shipflash.dev

Drop yours 👇