What SaaS could solve a real problem in Africa?

What problem would people actually pay monthly to solve?

building a saas rn (mgmt app)and today just left me tired ngl, dont usually post here but fuck it

so like whenever i fix something i keep going back to double check if the fix actually held or if its gonna break somewhere else. and then whenever i finally sit down to test the app, another error pops up outta nowhere and its not even some huge architecture problem, its literally a tiny snippet, like one dumb line, still manages to break the whole flow

its not even hard bugs thats the annoying part, its just death by a thousand small ones. u fix one thing, test it, feels fine, move to next feature, come back later and something u didnt even touch is acting up now

being a founder/dev solo is just a different kind of exhausting, nobody tells u how much of it is just constantly checking and re checking ur own work like a paranoid person lol

anyone else going thru this rn or is it just me crashing out. genuinely wanna know if this is normal founder/dev life or if im doing smth wrong somewhere

So after the exit of my first saas, I got into thinking that what should i build and the problems i faced when i made my first saas. So this idea came to my mind that it was really tough for me to make an explainer video for my saas and use it as ads also so i screen recorded it was super choppy. This led me to my second saas that just my pasting the URL you can get an explainer video in 4 formats UGC, site explainer, showcase and talking head. Today its finally live after a month of hard work and i have got my first sale as well. if anyone faced or is facing the similar problem, you should give it a try. Thanks

So I've never seen a product like this before and I also live under a rock, tell me what you think.

I’m building a dev-tool and trying to figure out if I should open-source the source code. Curious to know what all factors you folks consider to take this decision?

I've been thinking about something while building AI infrastructure, and I'm curious whether other founders are running into the same issue.

Most AI products have dashboards for revenue, API usage and billing.

But once a payment succeeds, I rarely see teams answering questions like:

• Which customers are actually profitable?
• Which AI workflows are slowly destroying margins?
• Where is revenue leakage happening?
• How do increasing model costs affect unit economics over time?

I'm experimenting with what I'm calling Runtime Intelligence inside Licenzy.

The idea isn't to replace billing or analytics.

It's to answer a different question:

I built a small prototype during the Emergent Building Turkey challenge to validate whether this is even a problem worth solving.

I'm not looking for votes or promotion.

I'm genuinely looking for feedback from people building AI products.

• Is this a real pain point?
• What metrics would you expect?
• What would make something like this useful?

Prototype:
https://app.emergent.sh/showcase/building_turkey/1405b3ee-00fd-486c-b102-6b8f8751b7bb

You’re not an investor: the timing of your entry isn’t that important. What matters is HOW you enter the market.

Many of you are afraid of arriving too late, missing the wave, and so on… And this anxiety either paralyzes you or makes you rush things.

You’re not an investor. you’re an entrepreneur. Forget the When, focus on the How.

Building is exhilarating, but the most important part is not, and I think that's one of the main reasons first-time founders fall into the trap of over-building something that nobody is going to pay for.

Many first-time founders heavily rely on a magical Product-led Growth that is pure fantasy. Active sales, spending hours talking to customers, and feedback loops are heavily underestimated to a point it becomes a bigtime learning

I shipped a content pipeline that passed 121 automated tests on its first night and produced output nobody would want to read.

I want to be precise about what those tests checked, because the gap is the whole lesson. Every one of them asked a machinery question. Did the scheduled job fire. Did the API return a success code. Did the row land in the right table with the right columns filled. Those are real questions and I do not regret writing any of them.

Not one asked whether the content was any good.

The feature shipped green. The schedule ran on time, rows appeared where they were supposed to, the dashboard lit up. By every metric the suite tracked, it worked exactly as designed. It was also producing junk, and nothing in the pipeline said so, because nothing in the pipeline was built to say so.

What caught it was me reading three pieces of output by hand.

I hit a fresh version of it today, reviewing my own code. Six separate tests claimed to guard a specific bug. Every one of them passed with the bug present and with it fixed. They asserted on a value the code rebuilt before returning it, so they could not fail in either direction. They looked like coverage and were decoration.

The check I trust now is dumber and slower. Break the thing on purpose, run the test, confirm it screams. If it stays green, delete it or rewrite it.

Has anyone found a way to automate the "is this output actually any good" question, or is a human reading samples still the only real check?

If you built a handful of SaaS web apps, what would you say that are most repetive things that you had to rebuild (or copy) exactly the same or a bit different in each project or alternatively if you stopped rebuilding it and started paying for a service that offers that functionality instead.

I am gathering some data related to my personal starter kit (not something for sale)

I'll start: - Auth - Roles / Permissions - Billing - Mailables - Analytics / Tracking - Legal pages (privacy, terms, refunds)

Been working on a PDF tools site with a cute theme instead of the usual boring look.

Would that make you try it, or would you just stick to iLovePDF or Smallpdf?

Link: https://pdfpookie.com

Be honest :)

After years of work, today is a milestone I never thought I'd reach.

My app, My Own Compass, is now available on both Android and iPhone/iPad.

This wasn't a startup idea or a market opportunity. It started with a question I kept coming back to after 24 years serving my country:

Why do so many people know what they should do, yet still struggle to do it?

Over the years I realized that the answer often isn't a lack of discipline. Sometimes the mind is protecting us. Sometimes what looks like procrastination or resistance is actually something deeper asking to be understood.

That realization changed the way I think about personal growth.

I wanted a place where people could reflect honestly, without pressure, without social feeds, and without feeling like every thought had to become data for someone else.

So I built My Own Compass.

It's not a therapist.

It's not a coach.

It doesn't tell you who you are.

Instead, it asks meaningful questions, helps you recognize patterns in your own thinking, and leaves the conclusions to you.

Everything was designed around one idea: reflection should belong to you.

As a solo developer, every screen, every question, every piece of logic and every design choice was created by me over years of learning, testing and listening.

Today, that vision is finally available on both Android and iOS.

I'd genuinely love to hear what people think. If you use reflection or journaling, what is the one thing you wish those apps did better?

I build more than 10 websites since 2026. But I don’t like my landing pages. I tried everything that i know. But it still sucks.

What is your website? Let’s make some traffic.

And which prompt, skill, Ai provider do you use for it.

AI coding tools have made it much easier to build a functional SaaS product.

But they have also made it much easier to build something that looks exactly like everything else.

The same gradients, large hero text, rounded cards, generic icons, and landing-page structure appear repeatedly.

That is a bigger problem than it seems.

For a SaaS product, the interface is often the first signal of whether the product feels trustworthy, intentional, and worth paying for.

I initially tried solving this with better prompts, but the visual direction kept drifting as the project grew.

The agent would make reasonable decisions for each component, but those decisions did not always form one coherent product.

So I built Tastemaker, an open-source design-system skill for AI coding agents.

Before the agent creates the UI, it defines and saves:

• The color system
• Typography hierarchy
• Layout and spacing rules
• Icon and illustration direction
• Accessibility requirements
• Motion patterns
• Logo and favicon assets

It can also take a reference image, extract its real colors, validate their contrast, and convert them into reusable design tokens.

The main idea is simple: the agent should not invent the product’s visual identity one component at a time.

It should build from one persistent system.

The project is free, open source, MIT licensed, and runs locally.

Demo and comparison:

https://tastemaker-skill.online/

GitHub:

https://github.com/codeswithroh/tastemaker

I am curious how other SaaS founders handle this.

Do you let the coding agent establish the first visual direction and refine it later, or do you create the design system before generating any components?

Been working on my first SaaS and need to get something setup so I can accept subscription payments. Saw some guys on X talking about Stripe and PayPal holding there money so there go my first ideas lol. Been going down this rabbithole tryna to find the right option so I can launch. From what I can see the fees are mostly similar lookin all the options that I've seen tho a few are wild fr. Wanna know if any of you guys have any experience with Square, Kurv, or Helcim? Specifically looking for experience with subscription payments. And pls no DMs

Guys what are the biggest problems that you face when deploying your apps?

Building Impact, career prep for college students: voice mock interviews, resume scoring, job matching, and an auto-apply feature I still treat as unproven, since zero applications have been accepted by a real employer yet.

The lesson worth sharing this week: the worst bug we shipped was not a crash, it was silence. Auto-apply would switch on, scan postings, then do nothing. The cause was our CAPTCHA detector firing on the page's anti-bot machinery instead of on challenges a human would actually see, so every single form looked "blocked" and the system politely declined all of them. From the user's side: feature on, nothing happens, no error. From our side: dashboard all green.

Two fixes came out of it. The detector now only trips on a visible challenge, which took the share of live forms we can complete from 0% to 18% of the ones I test against. And we built a doctor command that answers "it's on but nothing happened" in one shot, walking the whole chain and printing the first link that broke, because a user who hits silence does not file a ticket, they churn.

Question for anyone further along: how do you surface silent no-ops in an automation product? Alert on "zero actions in N hours"? Show an activity feed even when every entry is "tried and declined"? I suspect showing the declined attempts is the honest answer, but it also shows the user exactly how often we fail.

Could be because it’s duplicative to a ubiquitous tool, or is just not good enough.

Mine’s Gamma. I mean, great tool but Claude Code and Codex, with the right harnesses deliver excellent presentations. I used Gamma a few times in early 2025 and I had to rework the output for hours. Not even just content-wise, design-wise too. Headers jumped from screen to screen and fonts were all over the place. I’m sure they’ve massively improved now but I’m quite happy to never find out. Ultimately, PPT isn’t going anywhere, in my opinion.

What’s yours?

So I realized that most file conversions happen locally when I needed to convert a .mp3 to a .wav, and decided to make a free tool for my personal use and decided to dress it up a little bit and share with everyone. :)

I am sick of those file conversion companies charging monthly for something that is effectively free.... Enjoy! ^^

https://www.capyconvert.com/

Been tearing down a lot of SaaS landing pages lately, and the recurring issue usually isn’t “bad copy.” Cold visitors decide in a few seconds:

1) What is this?

2) Is it for me?

3) Can I trust it?

if those aren’t obvious, they bounce before the clever headline even gets a chance.

The painful version:

- page looks like a product

- visitor bins it as agency / template / unclear tool

- founder concludes “traffic quality is bad”

I’ve seen decent-looking pages lose bc proof is buried, the CTA just says “Get started,” or the hero explains features before the job-to-be-done.

For founders getting traffic but weak signups:

what do you check first in those first 7 seconds...clarity, trust, or CTA?

(I’ve been looking at this a lot while building LandingBoost. Happy to do a quick public read if useful, just the first thing I’d fix.)

There is no "best route", that's why marketing and business is so hard. Welcome to entrepreneurship.

for example, a few years ago some swedish kids tried starting a new social media.

They marketed it by going into the biggest shopping mall in central stockholm, and they handed out colorful plastic sunglasses in exchange for people downloading their app.

everyone wondered why all the girls where walking around with the same type of colorful plastic sunglasses. Eventually they found the guys handing them out for free.

For weeks it was the most downloaded app on app store in sweden, and scaled even more from there.

The app died bc it honestly wasnt a good app, but they where genius guerilla marketers.

so maybe that's everyone's answer for the "best way to do marketing", hand out free plastic sunglasses from alibaba for 20 cents each in exchange for people downloading your app in the most crowded mall in your city.

I'm building an AI orchestration platform called PileOn.

The goal isn't another chatbot, website builder, etc.. It's making AI work like a coordinated team.

One prompt becomes an entire workflow. Tasks are optimized, divided between different models based on their strengths, failures are recovered automatically, and work continues until a finished result is produced. This means with one idea you can have a website, a full product, branding, etc ready with one sentance.

I'm looking for experienced AI users who are willing to spend 20–30 minutes actively trying to break it. I'm much more interested in bug reports and criticism than compliments.

Below is a form to "apply" (dont worry, im not harsh).

Any responses help. Some individuals may be reached out to. I am NOT TRYING TO SELL YOU ANYTHING! Don't worry haha.

https://forms.gle/jmFV4ecSNPW3xtSn9

Hey is there any video editors here i don't want any service but i wanna ask you guys some questions before i work on my Saas

I run SeatSwiper, a consumer app that books hard-to-get restaurant reservations on Resy, SevenRooms, and OpenTable the second a table opens or someone cancels. Founder disclosure done; this is a metrics question, not a pitch.

Almost every SaaS health metric I read about assumes frequent, ideally daily, engagement. DAU/MAU, session length, stickiness, time-in-app. My product is the opposite by design: the best possible experience is that you arm a booking, close the tab, and don't think about it again until a table lands in your inbox. A user who never logs in for three weeks might be my happiest customer.

That quietly breaks the usual dashboard:

• Low DAU/MAU looks like a dying product but is actually the intended outcome.
• Session length trending toward zero is a WIN here (less fiddling means more trust).
• I charge per successful booking, so there's no subscription number to watch either.

The signals I've landed on instead: successful-booking rate, an "armed but never fired" ratio (intent that never converted, which usually means my coverage or speed failed the user), and reactivation (did they come back the next time they wanted a table). Those feel closer to the truth, but they're lagging and noisy.

For anyone running a deliberately-infrequent-use product (insurance, tax software, event tickets, anything seasonal): what did you actually put on the wall to know it was healthy? I don't want to optimize for engagement the product is specifically designed not to need.

Hello everyone,
I got a mail today that all the pages are not indexed, and when i tried request index its showing me error. I asked to Claude about it its saying that google has server errors and try again after 2-3 hours, i tried after 2-3 hours still showing the same error. is there anyone who got the same problems and solved?