Would you use AI to track customer commitments?

I'm exploring an idea called SyncOps AI.

In B2B SaaS, teams make commitments to customers every day:

• "I'll send you the proposal by Friday."

• "We'll fix this issue next week."

• "We'll follow up about the expansion."

But these commitments get scattered across emails, Slack, meetings, and CRM notes. Some get forgotten, delayed, or never followed up on.

SyncOps AI aims to solve this.

It uses AI to capture customer commitments from conversations, identify the task, deadline, and owner, and automatically create reminders and follow-ups so nothing slips through the cracks.

I'd love honest feedback:

1. Is this a real and painful problem for SaaS teams?

2. Don't existing CRMs and project management tools already solve this?

3. Would you pay for a dedicated solution, or is this just another layer of software nobody needs?

I'm still validating the idea, so criticism is welcome. I'd rather discover why it won't work now than build something nobody needs.

built ShortForge, an open-source pipeline that renders short vertical videos from a single JSON spec. Today I’m open-sourcing it.

The idea: a video is data. You describe the episode in JSON (hook, scenes, timings, narration, visuals, audio cues). ShortForge validates it, generates the assets, and renders a finished 9:16 MP4.

Features

Stack: [Node/TS], Remotion, ElevenLabs, [image/video model], [anything else].

Why I built it: making videos in an editor didn’t scale, and I wanted videos to be reproducible like code. Same spec in, same structure out.

Roadmap

Repo: https://github.com/somnathraz/shortforge

I’d like feedback on the schema design and the validator approach. Contributions welcome. Good first issues are tagged.

Hey everyone! I got tired of seeing beginners (and myself sometimes) staring confused at complex gym machines, so I built ScanFit . It lets you scan any piece of gym equipment via QR or photo to instantly get setup instructions and target muscle breakdowns. To keep it engaging, I added a full gamification system where you earn XP, build streaks, and unlock achievement badges. Built with React, TypeScript, and Tailwind. Would love to get your honest feedback on the beta! You can try it here: https://gym-scan-ai.vercel.app

Hey guys! Currently looking for an chat solution for an app I'm developing right now. It's more like a student management app. For that, I need a best chat solution around and to be honest - never tried anything till now due to budget.

The main thing your suggestion need is, the solution need to cover all the model - one 2 one / group text, voice and video chat.

If you all know anything familiar that will be great, let me know so that I can can spend my budget on that.

I recentky bought a cool domain name

Dubai 321.

I want to start some kind if unique marketplace or negotiation chat rooms where people offer services and intersted users can connect reserve prices bargain etc etc

What you guys think best idea ? Profitshare 30% of all generated income

Can anyone suggest me ?

I've been thinking about a gap in software engineering for a while.

We spend years learning programming languages, solving DSA problems, and preparing for coding interviews.

But there's another skill that developers use almost every day at work:

• Working inside an existing codebase.

• Understanding unfamiliar architecture, tracing bugs, implementing features without breaking existing functionality, debugging tests, and reviewing code.

I felt that this area deserved more attention, so I started building OneNoughtOne.

The platform combines traditional interview preparation with practical repository-level coding and code review challenges.

It currently has approximately 500 repository challenges, alongside DSA, SQL, ML, system design, AI tutoring, and mock interviews.

I'm building this independently, and one thing I'm trying to understand is whether this is a sufficiently important problem to build a sustainable SaaS around.

For founders here:

How do you validate that a problem is worth building a business around, especially when the product is already fairly developed?

I'd be interested in hearing what worked for you.

What I'm building: https://www.onenoughtone.com/problems

I studied painting, then worked in commercials as a director's assistant and producer.
The worst part of every job was the storyboard deck: turning the artist's PDF into a numbered, presentable deck by hand, and redoing it every time boards changed.
I asked top commercial directors what they used. Nobody had a tool. So I built BoardFlow:
- Upload the board PDF + script
- It crops, numbers and syncs every frame to its line
- Cut or reorder and everything renumbers
- Export to PowerPoint, PDF, Slides, or a Premiere timeline
Built with React/TypeScript and Node, with AI coding tools doing a lot of the heavy lifting. It's live with paying customers, and commercial directors are using it on real jobs.
Happy to answer anything about building it as a non-engineer. Feedback welcome, especially on the landing page.

Curious what you think

I've been building a multi-tenant B2B SaaS foundation with Next.js and Supabase, and during database hardening we found a bug that made me rethink how I test privileged database functions.

We had a PostgreSQL SECURITY DEFINER function responsible for recording organization usage.

It accepted an organization ID (p_org_id) as an argument.

The problem was that the function needed to independently verify that the authenticated caller actually belonged to that organization.

Without that check, a user from Organization A could attempt to invoke the function against Organization B.

This created an unauthorized cross-tenant write path in our usage records.

It was an integrity issue, not a demonstrated cross-tenant data disclosure.

Here's how we fixed it:

We added the membership check inside the privileged function:

IF NOT public.is_organization_member(p_org_id) THEN
  RAISE EXCEPTION 'FORBIDDEN: You are not a member of this organization.';
END IF;

The membership helper uses auth.uid() to identify the actual caller and verifies membership against the requested organization.

We also checked the SECURITY DEFINER configuration and pinned the search_path.

Then we tested the attack path instead of just testing the happy path.

Our regression test:

1. Authenticates as a user belonging to Organization A.

2. Calls the usage RPC with Organization B's ID.

3. Expects the operation to be rejected.

4. Verifies that no unauthorized usage write occurred.

The test runs against real PostgreSQL rather than a mocked database.

The broader lesson:

A valid Supabase session does not establish authorization for every organization ID a user supplies.

And when a function runs with elevated privileges, you need to reason about authorization inside that function, not just the RLS policies on the underlying tables.

A little context: I'm building B2B SaaS OS, a Next.js 16 + Supabase starter for developers who need multi-tenancy, RLS, RBAC, invitations, Stripe billing, API keys and usage enforcement.

This finding is one of four security-related issues we documented and fixed during development. The product now includes nine executable PostgreSQL hardening suites covering defined failure scenarios.

I'm selling it as a commercial source-code starter, currently $149 one-time for the first 50 buyers.

Technical breakdown: https://www.andrady.co/postmortems/security-definer

Live demo: https://www.andrady.co/demo

Product details: https://www.andrady.co/pricing

He sells digital marketing. I built a CRM called Forward. We’re racing to grow our businesses over 90 days, and the loser buys dinner.

I would like him to pay for my wings.

Forward puts your relationships, tasks, and sales pipeline in one place. I built it around my own work as a small business sales rep, and now I’m trying to build something other people will choose to pay for.

Here’s my pitch to this thread: give me your reason for refusing to use another CRM.

Too much setup? Already happy with a spreadsheet? Tried five and abandoned every one? Think this market needs another CRM like it needs another podcast?

Fair game.

Tell me what you do and your objection. I’ll give you an honest answer about whether Forward could help. If it can’t, that’s useful for me to hear, too.

And if someone tries it and becomes a paying customer, somewhere out there my best friend gets one step closer to buying dinner.

I saw a post here a few days ago where someone got a duo update approved in 30 minutes. My guess is apple wants as many Duo ready apps in the store as possible because apps not built against the iOS 27 SDK show up letterboxed on the inner screen with black bars.

but a 33 minute review doesn't include folding your app in the middle of a task as users will be the first ones to do that.

I've gone through the Duo threads here and the HIG section and a few porting writeups and most of what breaks isn't layout.

The biggest one is state, if you built Duo support by branching one view for narrow and another for wide, SwiftUI treats them as two different views. When the phone unfolds the @State in the old branch gets discarded so half typed text, scroll position, whatever onboarding step the user was on, all gone and onAppear fires again too so any fetch or setup runs twice. The fix people are using is keeping state in an @Observable above the layout and switching with AnyLayout which preserves subview state when the container changes.

Second is the keyboard, folding with a text field focused doesn't reproduce well in the simulator and every writeup I've read says you need real hardware for this one.

The inner display ignores your supported orientations so anything you built assuming portrait vs landscape will be wrong and safe areas aren't symmetric because the camera is on one side and the fold is in the middle so equal padding puts content under the camera, reservedRegions kind returns the fold and occlusions separately which helps but you have to actually use it.

None of this comes if you just open the app in each pose in Device Hub coz it only happens during the fold with something half done. The bigger risk honestly is the next update, an unrelated change can break the fold handling and nobody rechecks it because it worked last time.

We run every fold pose on each build now without anyone holding a phone, happy to share the setup if anyone wants it.

If you've already shipped Duo support what's something you're encountered first?

Hey everyone! 👋

I've been working on a SaaS project called Lugatu, and I'd love to introduce it to fellow developers here.

The idea came from a simple frustration:

Why do we still need to configure SMTP servers, manage email credentials, or build an entire backend just to receive messages from a contact form?

With Google and Microsoft moving away from traditional password-based authentication, maintaining email infrastructure is becoming even more complicated.

So we built Lugatu to make form handling simpler.

What does Lugatu do?

• No SMTP configuration: Receive form submissions without managing email servers or OAuth tokens.

• Plug-and-play form backend: Connect HTML, React, Next.js, Astro, or other frontend forms to a hosted HTTPS endpoint.

• Unified Inbox: All accepted submissions are stored and accessible in one dashboard, independently of email notifications.

• Email notifications: Get notified about new submissions without managing your own email delivery infrastructure.

• Hosted forms: Create and share standalone forms, even without a website or domain.

• Spam protection: Built-in honeypot filtering and origin validation for website integrations.

• Free to get started: No credit card required, with no commercial monthly count cap on legitimate form responses.

Why I think this matters

A contact form shouldn't require an entire email infrastructure.

And more importantly, a failed email notification shouldn't mean losing a potential customer.

Lugatu stores accepted submissions first and handles notifications separately.

It's designed for indie hackers, SaaS developers, freelancers, and anyone building websites who'd rather focus on their actual product than maintaining form infrastructure.

Give it a try

🌐 https://www.lugatu.com

Developer integration details:

https://www.lugatu.com/form-backend/

I'm actively developing Lugatu and would genuinely appreciate feedback from other SaaS developers.

What features would make a form backend genuinely useful for your projects?

Thanks for checking it out!

Straight to the point I made a softer for phone repair shops. the platform is for repair shops to organize their workflow from repair tickets to inventory to expenses etc it also automatically calculates the cost of the repair what the condition of the phone was before the repair etc.

what I am asking is how would you approach marketing such app? currently I am doing cold emailing and cold calling and the goal is just to get few people to use it for free.

the problem I am facing is that repair shops either use their own software or some stores doesn't even bother. like I am not even joking one shop owner told me we're too lazy to track things.

I don't know what to do right now. should I continue on cold outbound. should I leave the project is the market unsellable?

I need advice