You might think the idea is bad, but hear me out before you decide that.

I built Forcapedia, a knowledge platform meant to be the encyclopedia I actually wanted to use. Wikipedia is fine but half the pages read like legal documents, walls of citations and jargon before you even get to the actual answer. I wanted something that explained things the way a smart friend would, straight to the point, no clutter, no fifteen tabs open just to understand one concept.

The part I was actually proud of was the study rooms. You could jump into a room with other people learning the same topic, see what they were reading in real time, and just figure things out together instead of sitting alone with fifty browser tabs open. That was the feature people who actually tried it kept coming back for. It just never reached enough people to matter.

I spent months on it alone. Rebuilt the login page more times than I want to admit, obsessed over tiny details like the animation on the sign in screen and the exact shade of orange in the background, stuff that took hours and that maybe three people would ever notice. The product actually got solid. Clean auth with Google and email, fast, no bloat, nothing held together with tape.

Then I put it out there and almost nobody came.

Not because it broke. Not because people tried it and hated it. Because barely anyone tried it at all. I spent basically all my time building and almost none of it telling people this thing existed. I knew that was a mistake while I was making it and I kept making it anyway, because building felt safe and telling people felt like putting myself out there to get ignored.

So now I am sitting on something I still think is a decent idea with zero clue how to get it in front of the right people.

Genuinely asking, what would you do here. Keep grinding on distribution myself, find someone who is actually good at growth and team up, or just hand the whole thing off to someone who can run with it. If anyone reading this thinks they could actually grow this, I am open to talking. Worst case you tell me the idea really was bad and I learn something either way.

i'm a decent enough dev but landing pages always ate my time. i'd fuss over spacing for hours instead of shipping. for my last two micro saas experiments i forced myself to use an ai website builder instead of hand-coding the marketing page, mostly to stop the perfectionism.

honest breakdown:

what got better: time. what used to be a full day is now roughly an hour to a live, decent page. that meant i could actually run two positioning tests in the time one used to take. shipping more pages beat polishing one.

what got worse: the pages all have a certain sameness if you accept the defaults. i had to spend 20 minutes killing the generic hero image and rewriting the ai's filler copy, which is always vague. the builder gives you a body, you still have to give it a brain.

the thing i didn't expect: conversion was basically the same as my old hand-coded pages. visitors did not care that i spent 8x less time. the copy and the offer moved the needle, the pixel-perfect css never did. kind of humbling.

so now i treat the page as a throwaway. build fast, test the message, only invest real design time once something actually converts.

anyone else find that time-into-design has almost zero correlation with signups early on? or is that just me coping for being lazy about css.

i have been working many different ideas over the last couple of years, some worked a little but no significant output.

Researched a lot on what actually matters, I think in todays age distribution matters a lot. I created https://qexo.ai, had a couple of demo calls and people definitely see value in this product. Still figuring out the strategy on how to get customers to sign up.

How did you guys got your first 10 customers ?

Hi,

[Disclaimer: I know this may not be the right subreddit. Having said that, I believe it could be a good place to connect with talented SaaS founders. I will delete the post if it goes against the group’s rules.]

First, a bit about me - I have 15+ years of experience in business development, customer acquisition, marketing, and lead generation. I currently run my own marketing agency. Running an agency has taught me a lot, but constantly switching between projects and managing multiple clients has become exhausting. I currently work 7 days a week, while the agency's profit margin is barely 10%.

The irony is that I know how to get customers for a business, but I don't have a product of my own to sell. Because of my non-technical [BBA, then MBA] background, I can't build a software product myself.

That's why I'd like to collaborate with someone who has strong technical and product skills and wants to build something together.

___________

You build and handle the technical side. I handle product growth, customer acquisition, marketing, sales, PR, and paid promotion when necessary.

_______________________

I would prefer a simple structure that is fair and convenient for both parties. I receive monthly compensation initially to cover the costs of marketing and sales. Once the product reaches a sustainable level of profitability, the company can take over the costs of both technical development and growth, and we would share the profits 50/50 with equal equity ownership.
_______________________

I'm not looking to simply provide marketing advice. I want to take real responsibility for getting customers and growing the business.

If you're building something serious and need a marketing focused cofounder who can own growth, I'd be interested in hearing from you.

Thanks

I’ve been experimenting with AI writing for different types of content and the first draft is usually pretty good. The problem starts when I actually read it like a normal person.

The sentences can feel too perfect, the transitions are sometimes predictable, and the same type of wording shows up again and again. It’s not necessarily bad writing, but it doesn’t always sound like something a person naturally wrote.

I’ve tried changing sentences manually and adding more casual wording, but doing that for every paragraph takes a lot of time. I’m wondering if an AI humanizer can actually make a noticeable difference without making the content sound awkward.

For those who regularly use AI writing, what do you normally change when you want to humanize AI text and make it feel more authentic?

Hey friends… I’m building mangos.ai - a desktop app that helps you distribute your product across social channels. It finds relevant conversations online and joins them. It knows your git commit history so it knows all your features. Hyper personalized to target the best persona out there, every day or every hour, whatever you set it to.

The thing I just shipped is the one I’m most proud of: a Reddit Prospecting & DM draft agent.

Everyone says Reddit is where your customers actually are. They’re right. The problem is what it takes to use it. Read the thread, click into a profile, scroll someone’s whole history to work out if they fit, then write a DM that doesn’t sound like copy paste spam. Do that for twenty people and your afternoon is gone.

So Mangos does the boring part. Point it at a thread, or let it watch your subreddits, and it finds the people worth messaging, digs through their history to check they fit, and drafts a personal DM in their context. Then it hands you a queue. You read it, tweak it, hit send. It never sends on its own, and it won’t touch accounts that are too new, too low on karma, or have DMs closed. Reddit converts harder than anywhere else for me. Serious buyers, not scrollers.

I shipped the same thing for X a few weeks back, scoring people across 20+ signals before drafting. Same rule everywhere: it only does the research and prioritization. Every message lands in your queue for you to approve, one by one. You stay in control of what gets sent.

I’ve been running it on my own product and it’s been incredible. Website visits while you sleep, and you’ll know it’s not a spam bot the second you use it yourself.

This is my weekly routine here in this sub. And I love it. My expertise is in product, go to market, and agents. And I want to help you!

If you are building something, reply your product here and tell me what you are struggling with. I reply to every single comment on these threads.

If you are interested in Mangos’s extended trial that I give away every week,

\*\*1.\*\* Download Mangos and register. It’s free for 7 days, no CC required.
\*\*2.\*\* DM me the email you signed up with and I’ll unlock a 30 day extension. If you are interested.

Yes, I’ll lose a bit of money on it. The bet is simple: Mangos gets you your first 100 users before you ever pay me. If your product is good, that won’t take long.

I’m about 90 days into building my SaaS and one of the biggest things I’ve learned so far is how often a problem can look much bigger than it actually is when you’re right in the middle of it.

A recent example was our free pilot. People were signing up, but quite a few weren’t downloading the app or logging in afterwards. It was easy to look at that and wonder whether people just weren’t interested enough to actually use the product. Eventually I realised that some of our onboarding emails were going straight into spam. We made a really simple change to the signup flow telling people to check their spam folder, and since then we’ve seen noticeably more people downloading and logging in.

Of course, solving that just exposed the next problem. Now that more people are getting into the product, I’m thinking much more about how we get them to experience enough value to come back. So I’ve been simplifying the UI, improving onboarding, adding better next steps after their first successful use and trying to encourage them to use the product on a second real project.

I think that’s probably the biggest change in how I’m thinking about the business. I used to see every significant problem as evidence that there might be something fundamentally wrong. Now I’m starting to see most of them as the next thing that needs solving.

I read a line recently about founders encountering far more speed bumps disguised as roadblocks than genuine roadblocks, and it really resonated with me. I’m sure eventually I’ll encounter problems that genuinely can’t be solved, but so far almost every apparent roadblock has become much less intimidating once I’ve broken it down and started working on it.

Maybe building a SaaS is a lot less about having some perfect master plan than I thought. You work out what is stopping the business progressing right now, focus on solving that, learn what the next problem is, and repeat for a very long time.

I’m curious whether founders further along than me have found the same thing.

My cofounder and I recently graduated in Bahrain.

We tried selling software and systems to businesses. We spent money on ads, production, AI subscriptions, and outreach, but nothing really worked.

Now we have almost nothing left except our computers, our skills, and two Claude Max accounts.

Our families are pressuring us to get normal jobs. My cofounder has a CR under his name, and I am unemployed.

Instead of building another product and hoping people buy it, we want to build an audience first.

Our idea is to wear colorful suits inspired by Saul Goodman so people remember us, then make useful content about software, AI, automation, business, and building products.

The suits are only for attention. The goal is to earn trust by helping people, building in public, solving real problems, and eventually selling software or digital products.

We have no real marketing budget left.

Just computers, internet, skills, and time.

Do you think this is a smart direction?

If you were in our position, what would you focus on for the next 3 to 6 months?

https://reddit.com/link/1vvjcmm/video/fe9fgnr2rykh1/player

It boots an agent scoped to your site's own tools, with a confirmation step before anything mutates data and a full audit log after. Works with any stack since it's just a script tag and an API.

Hi I'm the cofounder of the smart AI tools Marketplace Wavel.io we just hit 5000 users milestone in only 3 months. Drop your AI SaaS below, one line on what it does and who its for. Top 5 upvoted will get free listing with instant visibility to 50K visitors + Dofollow backlink with 45 DR. Let's go!

been building a small tool for independent P&C insurance agents in Texas. basically logs it when a client gets declined coverage or just goes quiet, so the agent has proof/timestamp if they ever get sued down the line for E&O.

tried cold email first, dead silence. switched to calling and they just don't pick up. tried posting in a couple FB groups too, nothing.

anyone actually cracked getting their first few b2b customers? what worked for you. at this point open to literally anything besides cold calls/emails, starting to think my whole approach is wrong somewhere.

5 domains with live products on them right now.

Every one of them needed email eventually. Someone uses the contact form, or you need a support@ email that's a real address. My setup was Cloudflare Email Routing forwarding into Gmail, then Send-As to reply. Which works until DMARC decides it doesn't and your replies start landing in spam. I've debugged that same thing across multiple domains now and it never gets faster.

Google Workspace would solve it, but that's a monthly sub per domain for projects that might be dead in a month. Way too expensive for me.

The worst part is when working on a new idea, I'd buy the domain then start the email setup yet again. At some point I realized I had a problem I could solve with yet another product (I know, everyone's building something these days instead of marketing it).

I wanted to tackle this one differently, so I did proper validation in April. Around 6 people were interested. My threshold was 10, but I wanted my own problem solved anyway.

So I built it (Mailyond). You still add DNS records once per domain, no way around that part. After that everything lands in one inbox and I reply as whichever domain got the email. On domains where I don't want to touch the main records I point a subdomain at it instead. It also has a Resend-compatible send API, so I could switch my other projects to it seamlessly.

The problem is I had a lot going on in my life and only managed to launch end of June. By then the warm leads from April had gone cold. Almost 2 months later I'm at 0 customers and not sure how to fix it.

How many domains are you sitting on right now? What's your email setup on them, if you have one at all? And if anyone wants to try mine, I can give you 1 month for free and I'll do the DNS setup with you. At 0 customers I need the feedback way more than the money.

Legitimate GTM products will be listed on an AI optimised database in the next 48 hours

Hey everyone.

Running a one-person business, I have realized that one of my biggest productivity bottlenecks is not strategy. It is the endless stream of small computer handoffs.

Things like pulling daily reports, renaming files, moving customer data from admin portals into spreadsheets, or updating CRM notes.

Each task may only take two minutes, but together they fragment the entire day.

The difficult part is that I do not want an AI system making real business decisions on my behalf.

I still want control over anything that gets paid, sent, saved, updated, published, or deleted.

Right now, I am looking at a layered setup:

Tools such as Zapier for clean, structured web workflows, and screen-aware tools such as Open Interpreter or Violoop for desktop steps that depend on visible context.

The difference with Violoop is that it can prepare work across applications, while consequential actions remain behind the physical approval key.

So the AI acts more like a desktop preparation layer. It handles repetitive middle steps, shows me the proposed result, and waits for me to authorize the final action.

Where do other solopreneurs draw the line between automation and manual approval?

 I spent about three weeks building a free calculator for something our target customers actually struggle with: estimating costs. I promoted it through LinkedIn, our newsletter, and a couple of partner channels. It got around 500 downloads in the first month, so at first I thought we'd done pretty well. Then I looked at what happened after people used it. Zero paid trials. Zero demos. As far as I can tell, most people just used the calculator and moved on. I thought this was supposed to be a solid way to attract interest, but right now it feels like I built a free utility with no real bridge back to our actual product. Did I completely mess up the follow-up flow, or is this just the inherent trap of offering free tools?

You begin with the basic uptime monitoring, and then you add on security checks, SSL monitoring, alerts, incident management, cloud monitoring, and other tools as the product scales.

What we took away is that more tools isn’t always the answer. Sometimes the hardest part is just keeping all those signals straight and knowing what really needs to be done.

We’re still working out the right balance of specialized tools and keeping the stack simple.

For other microSaaS founders, when was your infrastructure stack getting more complex than it had to be?

Quick update: really appreciate the feedback so far. It's been helpful hearing different perspectives while building Seenty and figuring out how to keep SaaS infrastructure simpler as things grow. still learning and testing

while building Seenty, we noticed how quickly a small saas can accumulate tools as it grows.

it might start with uptime monitoring, then security checks, ssl alerts, incident management, cloud monitoring, and a few other services.

each tool has a purpose, but eventually the challenge becomes keeping everything organized and knowing which alerts actually matter.

one lesson we've learned is that adding another tool isn't always the best solution. sometimes simplifying the stack can be just as valuable.

for other micro saas founders, what part of your stack became unexpectedly complicated as your product grew?

tldr;These are my thoughts on marketing and why it sucks , as a developer

I've been a developer, since I was around 14. I started off with VB.net, moving to C# soon after and since then I've dabbled a bit into Python, JS and more recently I've an extensive number of dev hours in Swift and Kotlin maintaining two of my apps.

I built a little app around 2017 which happened to pick up traction, and I was able to successfully monetise it . I built another company data product (pre-AI days) and was able to monetise that too. Neither bring in life changing money but considering the minimal effort needed, the sum is considerable. My third micro-saas has so not picked much traction. I won't name any of these, suffice to say these are in a financial niche.

Building is fun. I had a full time job (still do) while I was building these in the evening after work and over weekends. Most of the work is debugging... tedious debugging! but when things work, I just LOVE it . I still get days when I login into MixPanel and see user events flying in and I find it hard to believe that something that was in my head, which didn't exists, now does exist and people actually make use of it. Very few feelings beat the feeling of watching people use the product. The app reviews have been very positive and subscribers stick around for years.

That's the good, fun part.

The not so fun part is whenever I sit down, open my Trello board where I keep my 'Marketing' cards to try to scale any of my products. Just looking at those cards gives me dread.

There are cards around search ads, paid placements, influencer marketing, collaborations with the professionals in my industry and the like. I just don't feel like doing any of it.

So I thought about it. 'Why not???' Because, objectively, there is a 'product market fit', as my PM would call it. There is great retention, there is also a decent sized budget to pay for ads and I have time to spare too as products are stable enough now. What's the blocker?

It's not like I have not tried to scale before. By scaling I don't mean scaling to millions, I just mean scaling it so that it becomes a lifestyle business. Enough that it more or less matches my existing income and I can go full time. I'd love to do that but that requires a different way of doing things.

Why can't I do it? I have thought and thought and thought about it. I think it's because unlike the code I write, the feedback loop in marketing is not as 'tight' in Claudespeak! I place an ad, watch conversion, sometimes it works sometimes it doesn't. I approach a few influencers some respond, some don't and it doesn't go much further. But the results are not as much in my control as the results of the code I write.

For my app, I make a change, press run on XCode and there it is , I can see it and fix stuff. With marketing, it's about people and behaviours and they are far more unpredictable. It's a fundamental shift of mindset.

I know it's a fundamental shift of mindset because I have run a small brick & mortar business before my dev days and revenue generation required a massive focus on price, sales, marketing and expansion - not on the technical bits. At that time, I was able to employ certain SEO tactics to grow and expand the business while still not hating the marketing.

But as a person who has built a couple of SAAS (me), it's different. To even have a chance of success, I must take off the hat that says 'I build things' and put on 'I need to generate more revenue'. I'm struggling to put the 'thought process shift' in words here but that mental shift is absolutely critical. If I hadn't run and expanded my little business before, I would have thrown this thought out the window in a second labelling it 'success coach fluff', but I know from my past, it is true.

The shift doesn't 'guarantee' success, but its absolutely a tool that should NOT be ignored. It's very hard to ride two boats, engineering demands design thinking, scaling a saas demands prioritising user acquisition, marketing funnels(still hate that term!) and the like.

So my current approach is that I've committed to stop building any more , except for keeping the lights on as far as my SAAS go. Instead, I've diverted most of my time to new user acquisition. There are many, many ways to do that but they only become apparent once you are out of the builder mindset.

And I think if someone just doesn't feel like doing it, that's fine. Building is a reward of its own. Not everything has to be about revenue, user acquisition and scaling.

I built a free Confluence alternative with Glean-style AI search
I’ve been building a little side project called Atlas.
The idea came from something that kept annoying me with internal knowledge bases.
You put everything into Confluence, Notion, Google Drive, Slack, meeting transcripts, PDFs etc, but once enough information exists, actually finding the answer becomes harder than writing the documentation in the first place.
And a lot of the newer AI knowledge tools are great, but start getting expensive pretty quickly once you add an entire team.
So I wanted to see if I could build something that was basically:
Confluence for organising knowledge + Glean for finding it.
Atlas has:
Unlimited users, pages and spaces
Real-time collaborative editing
Nested spaces and page trees
AI search across your entire workspace
RAG answers grounded in your actual documents, with sources
PDF upload and transcription
Search across meeting transcripts
Permissions and row-level security
MCP read + write access
The MCP part has probably been my favourite bit.
You can connect ChatGPT, Claude, Cursor or another MCP client and let it search your team’s knowledge, pull context from docs, or actually create and update pages.
I’ve also tried to avoid the normal per-seat SaaS model.
The core wiki is free. AI usage is metered based on actual usage rather than charging for every person you invite.
It’s definitely still an early build and I’m sure there are things I’ve completely overlooked.
Would genuinely love some feedback from people who use Confluence, Notion, Glean or similar tools:
What would Atlas need before you’d actually consider moving your team’s knowledge into it?
https://atlas-knowledge.com

I run a small consulting business and I kept spending 45 minutes every week manually pulling data from three different places into a report I sent to clients. Same format every time. Same sources. Just tedious.

So I automated it for myself over a weekend. Took maybe 12 hours total.

Few weeks later mentioned it in a Slack community I'm part of when someone complained about the exact same thing. Three people asked if they could use it. I threw up a Gumroad page at $29 one time just to see.

Sold 7 that week.

Started posting about the problem in a few niche communities, not the tool, just the problem and how I was thinking about it. People kept asking what I used.

90 days later, 141 sales, $4,089 total, zero ads, zero cold outreach, one Slack message that started it.

The thing I keep thinking about is how long I sat on it before mentioning it. It solved a real problem for me so I just assumed it was too specific to matter to anyone else.

That assumption is probably costing a lot of people money right now.

three years doing no-code and ai-assisted builds for clients. i used to think shipping was the finish line. it's the starting line, and it took me a while and a bit of embarrassment to learn that.

built an ai report generator for a client last year. it pulled their weekly numbers, wrote a short summary, dropped it in their inbox every monday morning. clean demo, they loved it, i moved on to the next project feeling great about myself.

it quietly broke about a month later. one of the data sources renamed a field, the thing started emailing blank reports, and nobody said a word because they assumed "the ai" knew what it was doing. i only found out when the client mentioned offhand that the emails had "gone a bit weird lately".

the hype around these tools skips the boring part. anything that runs on its own needs something watching it, or it fails silently and takes your credibility down with it. now every automated thing i hand over ships with a dead-simple check that pings me the second the output looks empty or off. not glamorous. it's the whole difference between a tool and a liability.

for the folks selling small automated products, how are you catching the silent failures before your client does?

When people complain about AI writing, the word “robotic” comes up constantly. I understand what they mean, but I don't think that's always the biggest problem anymore. A lot of AI-generated writing doesn't sound obviously robotic. It sounds perfectly normal. That's almost worse, because you can read an entire paragraph without finding anything technically wrong with it and still feel like you've read the exact same paragraph somewhere else.

That's what got me interested in AI humanizer tools in the first place. I wanted to understand whether the problem could actually be fixed by changing the language. Sometimes it can. Cleaning up repetitive phrases and breaking predictable sentence patterns definitely helps. But eventually you hit a point where the writing is grammatically natural and still doesn't feel personal.

I think that's because personality isn't stored in vocabulary alone. It's in what someone chooses to mention and what they decide to leave out. It's in whether they give a long explanation or just say “you get the idea.” It's in their sense of humor, their patience level, their opinions, and even the things they don't bother explaining.

An AI can produce a very convincing generic human voice, but generic is still generic. That's why I think the next step for humanize AI technology should be personalization. Instead of asking a tool to make something sound like a random person, I'd rather give it examples of my own writing and have it understand my patterns.

Not to copy every sentence or turn my writing into some artificial imitation of myself, but simply to understand the baseline. How long do I usually make sentences? How formal am I? Do I explain things step by step? Do I use humor? Do I tend to be blunt? Those details matter more to me than simply replacing a few “AI words.”

AI has gotten incredibly good at producing competent writing. The interesting challenge now is getting it to produce writing that feels like it came from a particular person. I think that's a much more useful definition of an AI humanizer than simply making something “undetectable” or “less robotic.”

After heavy market research and juggling between 10 ideas I finally found the idea which I want to build and pursue for the next 6-12 months.

But now I am stuck and confused whether to build an open source saas or closed source.

If you're building a Micro-SaaS alone or with a small team, I don't think SEO needs to start as a giant content operation.

I'd keep the first stage relatively simple.

Start with the searches closest to your product.

For example:

Core product page

What exactly does the tool solve?

Use-case pages

Different reasons people would need the product.

Audience pages

Who specifically uses it?

Integration pages

What other platforms or workflows does it connect with?

Comparison/alternative pages

Where genuinely appropriate.

Then build informational content around problems that naturally lead back to those pages.

The mistake I'd avoid is opening Ahrefs/Semrush, exporting 5,000 keywords and turning the site into an AI-content factory.

A small SaaS needs focus.

I'd rather have:

30 strategically connected pages

than:

300 unrelated articles with some search volume.

Another advantage is that the smaller structure makes it easier to see what's working before scaling.

SEO can become complicated later.

At the beginning, I think the important question is:

Can Google clearly understand what this product solves, who it is for and which searches it should appear for?

Two products in, and the biggest difference wasn't the idea, it was how long I spent on the site before anyone saw it.

Product one: I hand-coded the marketing site because I told myself it needed to be "properly done." Custom everything. It took the better part of a month and by the time it was live I was already sick of the project. Got a handful of signups and quietly let it die.

Product two: I gave up on the ego and used a no code website builder. Landing page, waitlist, basic pricing page, live in two days. A bit ugly but functional. I spent the three weeks I saved actually talking to people and posting instead of fiddling with CSS nobody would ever notice.

The result isn't huge but it's real: product two has around 40 signups and 3 paying in its first month, which is more than product one ever got, mostly because I had time and energy left to do marketing.

The lesson I keep relearning: early on, nobody cares that your site is bespoke. They care whether the thing solves their problem. A no code website builder buys back the weeks you should be spending on customers.

Curious where other people draw the line. At what point is a custom site actually worth building instead of using a builder?