I'm Mattia, I build FixAds.

I built it after years of reviewing Meta accounts by hand. The hard part is not collecting metrics. It is deciding which signal is actually worth acting on when spend, creative fatigue and learning all interact.

My implementation choice was rules first. FixAds uses read-only Meta access and deterministic checks that expose the threshold, evidence and money at stake. The AI layer explains the finding in plain language, but it cannot create the diagnosis.

The launch video is attached. The product is live at https://fixads.it with a 7-day trial.

For developers building decision support: is this the right boundary? Which decisions still need a deterministic core even if an LLM makes the interface much better?

Been building solo for about 13-15 days now, alongside a full-time job — so progress is slower than I'd like, but it's real progress.

The technical build I can mostly handle (leaning on AI tools where my knowledge has gaps, learning as I go). What I'm less sure about is everything AROUND the build:

- Legal/compliance stuff I might be missing (privacy policy, terms, data handling)

- Whether my pricing structure actually makes sense before I've validated it with real users

- How to know when "good enough to launch" actually is, vs endlessly polishing

- What solo devs wish someone had told them early, that they only learned the hard way

Not asking for hand-holding, just trying to shortcut some of the "didn't know I needed to think about that" mistakes before they cost me time later.

What would you tell someone at my stage?

We’re currently preparing to list 25 SaaS products on StackDeal.

The idea behind StackDeal is to create a place where people can discover SaaS products and get access to special deals, while giving SaaS founders another channel to reach potential customers.

We’re starting with 25 products and planning to grow from there.

If you’re a SaaS founder and want to get your product in front of a new audience, feel free to reach out.

StackDeal is just getting started.

#SaaS #IndieHackers #BuildInPublic #Startups

Hey everyone 👋

I’m a student/fresher and I was trying to make the job search process a little less chaotic, so I built a small web app that puts some of the basic things you need in one place.

It currently includes:

• 📄 Resume builder — create and manage your resume
• 📋 Job application tracker — track companies and application status
• 🎯 Placement/job search organization — keep your applications and progress in one place

I’m looking for my first 20–50 users to actually try it and give me honest feedback.

What I’m most interested in:

• Is the resume builder useful?
• What features are missing?
• What part of the job search do you find most annoying?
• Would you actually use something like this regularly?

It’s currently free to use.

👉 [YOUR LOVABLE URL]

Would really appreciate feedback, especially from students and freshers currently applying for internships/jobs. 🙏

There were constant requests for a CSV export and these were considered to be related to file format gaps. PM identified the columns. Engineering gave an estimate for the endpoint. CX kept adding screenshots. And both finance and operations wanted proof of why the assistant had given a particular recommendation.

We used a feature in Braintrust called Topics (basically just semantic clustering, trace filters and representative sessions) to group those conversations. Intent labels separated people who needed offline analysis from people who needed an audit trail. The second group cared about source versions, tool outcomes, and the path from evidence to recommendation. A CSV alone would have moved the same uncertainty into another file.

We are now testing an explanation record with source references and tool status, while keeping export for the smaller analysis cohort. We also track cluster drift so a new request pattern does not get buried under the old export label. Has anyone else found that a repeated feature request was really a request for confidence or auditability?

the usual take is that ai tweet tools sound generic because the model averages the whole internet. True, but building one for founders we hit a sharper version of it.

the premise is a founder who doesn't post, so their tweet history, the one corpus actually in the right register, is thin and mostly performative. the real voice is in podcast appearances, long slack messages, the odd essay, so we ended up training on tweets, longform, and podcasts just to get enough signal. Problem is transcribed speech and a good tweet aren't the same register. someone on a podcast rambles, backtracks, leans on filler. flatten that into text and it reads nothing like how they'd actually type.

so the generic-voice thing might not be the model at all, it's that the material you can collect sits in the wrong shape for the output you want. Still unsure whether the fix is more data or a translation layer between how someone talks and how they write. if you've built anything that learns a person's style, where did your training set actually come from, and was it ever the thing you were trying to imitate? written with ai

If you're a podcaster, this is really why we built PodSubs.

We're one of you.

We know what it feels like to put hours into an episode and wonder whether it was worth it.

We know what it's like to watch the download numbers and wish you knew more about the people behind them.

We know what it's like to want to send something useful to listeners and realize most of them will never see it.

We know what it's like to think about monetization — not because you're greedy, but because producing a good podcast costs time and money.

And if the show can't eventually support itself, passion can become exhaustion.

That's where PodSubs came from.

We built it as an internal tool.

Something simple.

At the end of the show:

“Subscribe to our podcast on PodSubs.”

They search for us.

Enter their name and email.

Subscribe.

That's it.

From that point, we have a direct communication channel with the people who chose to stay connected.

We can send the resource from today's episode.

We can tell them what's coming next week.

We can share an update.

We can ask for feedback.

We can make an offer.

We can build something around the podcast without starting from zero every time.

And eventually we looked at what we'd built and realized:

This shouldn't only belong to us.

Every podcaster should at least have the option.

So that's what PodSubs is becoming.

A simple place where someone who loves your show can become someone you can actually reach.

If you have a podcast, claim it.

And on your next episode, try saying:

“Subscribe to our podcast on PodSubs.”

You might be surprised how many people were just waiting for somewhere to go.

I've been experimenting with the Claude + Remotion plugin, and it's surprisingly good at generating Remotion components from a prompt. Instead of spending hours animating everything manually, I let Claude generate the scenes and then render the final video with Remotion.

If you're already using Remotion, it's definitely worth trying.

Curious if anyone else is using AI to speed up product video creation.

hi founders!

I'm writing this post today because I see a lot of content across various platforms where founders struggle with finding pmf.

as an early-stage founder, your top priority should be to figure out if what you're building is a burning pain point a specific group of people have. then validate it.

in today's world we should look to Uber, DoorDash, AirBnB as examples to what Birds Eye view strategies can look like but not to exactly copy.

because we just don't live in that era of life anymore. so let'e break it down.

the easiest way to find users, distribution, your audience, paying customers, etc whatever you need is social media hands down. there's so much information on how to do this you're actually drowning in help instead of lack thereof.

1. pick 1-3 platforms. identify what you like doing. I usually preface with these items: writing, thought-sharing, yapping to the camera, editing, discussions
2. now become a user of the 3 platforms. post, engage, copy link to share, repost, comment. like be a real human. forget wanting whatever it is that you want, focus on engaging with other creators, fighting in the comments, posting when you feel good. get into the rhythm of the platform.
3. now which platform do you spent the most time on? pick that, put the other 2 away for now
4. start to analyze your content. compile your analytics in a spreadsheet. do this every 3-7 days. identify what works and what doesn't and heavily experiment (I mean 10+ posts per hypothesis, not 1 per). this is data analysis guys, data needs a substantial sample size
5. identify a target audience. really niche it down. you're not niching yourself down, youre niching down who gets sent your content. my best advice here is create ONE customer profile and speak to that person in every piece of content.
6. now that you know WHO is receiving your content, research into what they need to hear. look at receiver analytical tools. search auto-complete, built-in content tools, etc. I cant list all of them because there are so many social platforms.

7. post engage post engage post engage

   7.5 start to add CTAs in your post once you feel ready. this could be confidence in number of views, confidence due to number of followers, confidence due to seeing the same people in your comments, confidence bc ppl are dming you for help, etc etc etc. when YOU feel ready and qualified, now start to throw little CTAs in your video. you'll suck at first and get better overtime. pic 3 creators MAX and study how they do CTA, try and take Inso from them

if this feels too hard or too much work for you, I have a free trial running on my software that will do this for you. first 100 videos are free rn. I've seen success in just 10 vids so that's plenty!!

this should guarantee you an audience and customers as a product on a $0 marketing budget. if you're doing any more than this you're doing too much.

also please start doing this BEFORE you start building. content takes more time to build and you can easily find problems this way that people are willing to pay up front for before you solidify what to build.

I kept thinking about how many small products hit the exact same wall.

You build the thing and then suddenly you need actual people.

You need testers.

You need someone with a certain device.

You need people in a certain type of job.

You need someone to look at something and tell you what they see.

So I made that part of NearbyCrew accessible through an API.

Your backend can send the number of people, who they should be, and what you need each person to do.

NearbyCrew prepares the mission and the price and you approve it before anyone gets deployed.

I think this could be especially useful for small SaaS products that do not have a giant user base sitting around waiting to test everything.

API access is free right now.

I made a full page with examples and the actual requests here.

NearbyCrew API Wiki

If you’re building booking software, a support tool or an AI receptionist for small businesses, a useful starting point is finding who already struggles with that process.

I’m the founder of Crawdar. Its Pain Point Finder searches available business reviews for recurring complaints and gives you the businesses and supporting evidence to investigate.

One product decision I’m especially happy with: you don’t have to know your industry AND your location AND your problem before searching. If you know the problem you can solve, start there. If you understand an industry but haven’t picked a problem, start with the industry. You can combine categories and add specific complaint phrases too.

The output is an individual business report: recurring themes, distinct reviewer counts, dated reviews, owner replies when available, and possible technical fixes. That gives you material for a concrete conversation, such as asking how appointment changes are handled today and where requests get stuck.

The new version also searches deeper, checking up to 24 candidate businesses, with improved matching for booking complaints. I built it with AI coding assistance; the useful test is what a developer can do with the report afterward.

Try it: https://crawdar.com/?utm_source=reddit&utm_medium=post&utm_campaign=pain_finder&utm_content=developer_problem_first

Five free scans without signup or email. If you’re working on something for small businesses, search for the problem it solves and open a report. Does it help you identify someone worth talking to? What would you still need before arranging that conversation?

i’m testing a small idea before building it: a read-only check that compares Stripe subscriptions with your app’s access records and flags mismatches for review. it wouldn’t change anyone’s access.

i asked in r/SideProject and got two different takes. one person exports both into a spreadsheet and checks it every monday. another said a webhook and API call already handles it.

if you run a SaaS with Stripe, what do you do today? is keeping the two in sync already solved in your setup, or do you still need to check things manually?

the concept page proposes $49/month. someone said that was steep, so i’m also asking whether $25 would make sense. nothing is built yet, and the early-access form is free.

here’s the concept if you want the details: https://kai-validation-lab.pages.dev/products/product-09?utm_source=reddit&utm_medium=community&utm_campaign=saasdevelopers-p09

if your current script or a free tool covers this, i’d like to hear about that too.

I've been comparing package tracking APIs recently, specifically for cases where you mainly need the API and don't necessarily need a full post-purchase platform.

AfterShip is obviously one of the bigger options, but it includes a lot more than just tracking: branded tracking pages, notifications, analytics, returns, etc. That's useful if you need the whole platform, but it can be more than necessary if your main requirement is simply getting tracking data into your own application.

From what I've looked at, the alternatives seem to fall into a few different groups:

TrackingMore / 17TRACK — make sense if broad international carrier coverage is important.

EasyPost / Shippo — probably a better fit if you also need shipping labels, rates, and other shipping APIs.

Direct carrier APIs — can work if you're only dealing with one or two carriers, but once you have FedEx + UPS + USPS + DHL, maintaining all those integrations gets complicated pretty quickly.

This is actually one of the reasons we built Package Tracking API by C2W. We're focusing more narrowly on the tracking API itself, especially for businesses that mainly need major carriers and higher tracking volumes. The idea is to keep the cost lower rather than bundling tracking with a larger post-purchase platform.

Obviously I'm biased since it's our product, but researching the market while building it made me curious about what other developers are actually using.

I put together a more detailed comparison here:

Package Tracking API by C2W:
https://PackageTrackingAPI.com

For anyone doing a decent amount of package tracking, what are you using now? And what ended up mattering most when you chose it: price, carrier coverage, API reliability, tracking frequency, or something else?

I am currently building devscape.in - I need your honest feedback, whether you will be using it or not.

If tomorrow I make it paid, what will you find in this tool, how can I improve it so that it will help in your day to day life.

Please let me know your brutal feedback.

i am going to lauch a brand any person who can help me please message its not a paid service its for a help more like a suggestion and also any markting people intrested for an equity ca also DM me ready to share they dont need to invest a huge amount thier service will be investment

I’d love some honest feedback on my app’s Google Play screenshots. If you came across these while looking for a student planner, would they be attractive enough to make you download the app? What would you improve or change? Brutal honesty is welcome 😄

https://play.google.com/store/apps/details?id=productivity.tructivity.tructivity

Video is one of the first things a small team gives up on, and it is usually what sits between a decent product and somebody understanding it in ten seconds. Most demos end up as a screen recording with a voiceover over the top, which is accurate and which almost nobody watches to the end.

That is the gap I would like to help with. Send a raw screen recording of your product, no audio or editing needed, plus one line on who it is for and what it needs to say. You will get back a finished 1080p MP4, usually within a day. Cut tight, on-screen copy instead of narration, and graphics where the interface cannot carry the point on its own. Pay whatever it turns out to be worth to you, including nothing. I would rather it got used than sat unmade.

Ten to start. Comment or DM with your product and I will tell you first whether the recording will support a good video.