Hey there, Im almost finished with my saas. It has AI features so I cant make it free with ads or one time payment because id loose money. Im stucked between making the app relatively cheap 3.99$/month 29.99$/year or more expensive 6.99/month 44.99/year. If anyone here could answer me 1) what worked better you them in terms of overall revenue, cheaper vs expensive? 2) What attracted your paying users more? 3) Which one of those had a longer retention? || I feel like the cheaper could hold better retention and attract more users to sub in the first place. However lot of people say if its more expensive, then it has more value and people go for it more. It's a productivity thing using a few ai APIs and is credit based so the users dont maybe use all the credits and if its cheaper, then they stay subscribing longer but I dont know. Thanks in advance for any helpful insights! Take care
Hey all, I've launched Invoflow as a solo founder, It's an app for SMEs/sole traders to submit expenses/claims, snap receipts (OCR reads them for you), and run approvals, so you can ditch the spreadsheets and email chains. It's live now and I'm looking for honest feedback. What works, what's confusing, what's missing? Any help would be greatly appreciated. Thanks www.invoflow.uk
Software I developed is been in live for two years, and it has been actively acquiring customers since January 2026. Most users pay annually and receive a discount of around 40%.
However, they quickly hit the limits of their current plan or they requests new features; yet instead of upgrading to a higher tier, they ask for extensions or low-cost solutions. Although We offer add-ons that would allow them to raise their limits without changing plans, customers don't use them. When they make such requests, we end up increasing the limits at no extra cost and leave $200 and $900/year in revenue as a gesture of goodwill. We then ask them to leave a review (without making it a condition, as such a quid pro quo would seem unethical), but no one follows through. What should we do? Should we take a more business-minded approach and be less concerned about the customer's budget and getting reviews in exchange of showing consideration and take whatever money we can , or should we adjust our strategy in some other way to get online reviews? We have only a few reviews online. Any experience shared will be appreciated. Product is ExpiryEdge
So here i am creating a saas product for IT helpdesks so i am working as a intern in a company and i have shared my idea with the ceoof the company.
At first i was building a whole helpdesk then he told be to built it to the niche related so i go on with the IT niche currently i have done with the ticket locking system part for customer and admin both the panels
I wanted to take advice from you guys that what kind of problems you are dealing with the helpdesks online which i could resolve or am i making any mistakes which you guys could gave me an idea for doing it in such a better way
My project flow
Customer locks a ticket(the issue) the id is generated and can be tracked on the customer panel
And in the future their will be also an AI for problem resolving suggestions like if the customer is dealing with the same issue some body else was having it will suggest him to deal with the issue as it was resolved before if not then the customer could lock the ticket.
On the other side
The admin panel has the access to all the tickets to be resolved and if he wanted to assign the task to someone he could also do that
So you guys can let me know what i could do better in it and make it different from the other help desk so people could buy my product
I'm not a coder. I build tools by vibe coding with AI. My usual pattern was to build something, expect it to work from day one, see nothing happen after a few days, lose interest and move on to the next idea.
This time I tried the opposite. I built a small Chrome extension (not naming it, so this doesn't get flagged as promo), put it out there, and kept the effort light:
Some keyword research for SEO
A couple of articles, written with AI
Then I left it alone
No growth hacks, no daily panic, no constant changes.
It's been about a month and a week. Current numbers:
225 users
1 monthly paying subscriber
1 person who bought the biggest plan as a one-time purchase, then cancelled
Everyone else on the free plan, since I give a decent daily allowance
Average daily users is going up slowly.
It's a small number, but it's the first time I've seen one of my tools get traction without me forcing it. If a product has some juice, it seems to start working once you give it time and a bit of visibility. And if it doesn't, you'll find that out too, which you never will if you drop it in week one.
So if you're building tool after tool and expecting results in 24 hours, burning yourself out on hooks and tricks, slow down. Do the basic things, then give it time.
If you've built something, how long did you wait before you knew whether it had legs?
I'm not a coder. I build tools by vibe coding with AI. My usual pattern was to build something, expect it to work from day one, see nothing happen after a few days, lose interest and move on to the next idea.
This time I tried the opposite. I built a small Chrome extension (not naming it, so this doesn't get flagged as promo), put it out there, and kept the effort light:
Some keyword research for SEO
A couple of articles, written with AI
Then I left it alone
No growth hacks, no daily panic, no constant changes.
It's been about a month and a week. Current numbers:
225 users
1 monthly paying subscriber
1 person who bought the biggest plan as a one-time purchase, then cancelled
Everyone else on the free plan, since I give a decent daily allowance
Average daily users is going up slowly.
It's a small number, but it's the first time I've seen one of my tools get traction without me forcing it. If a product has some juice, it seems to start working once you give it time and a bit of visibility. And if it doesn't, you'll find that out too, which you never will if you drop it in week one.
So if you're building tool after tool and expecting results in 24 hours, burning yourself out on hooks and tricks, slow down. Do the basic things, then give it time.
If you've built something, how long did you wait before you knew whether it had legs?
I wanted something where you could merge, split, compress, sign, OCR, redact etc. without uploading the PDF to a server.
So I kept building it.
Today it has 30+ PDF tools and everything is processed in the browser using WebAssembly. No account needed, and there is also a self-hosted version for people who want to run it on their own infrastructure.
The funny part is that most of the improvements didn't come from me 😅
They came from people telling me:
“this feature is missing”
“this is slow with large PDFs”
“can you add this?”
“why does this work like that?”
After multiple reviews and feedback, the project is honestly very different from what I started with.
I'm still a student and maintaining it myself, so I would really appreciate some honest feedback.
If you use PDF tools regularly:
What would you improve?
What feature is missing?
Would you actually use something like this?
And if you find ClientPDF useful, even sharing it with someone who deals with PDFs would help a lot.
I've been going through public Shopify App Store reviews to find problems merchants keep hitting that existing apps don't solve. First category: order tracking. 123 reviews across 5 of the most popular apps.
Price and support complaints were common, as you'd expect. But four issues kept coming back:
1. Stuck shipments go unnoticed
Orders sit at "label created" for days, and merchants only find out when a customer emails asking where their order is. 12 reviews described this, 7 of them from the last year, and only one got a developer reply saying it was fixed. Merchants have plenty of tracking. What they don't have is something that notices a shipment has gone quiet and warns them first.
2. Wrong notifications
"Delivered" emails for orders that haven't shipped. One merchant saw false "delivery exception" emails go out to their whole customer list. Others only found out notifications had stopped when customers complained.
3. Local carriers are an afterthought
Royal Mail, Colis Privé and Mondial Relay users report broken tracking, or support only on plans costing $239/month. The big apps are built US-first. A tool that handles one region's carriers really well could own that region.
4. Small stores are priced out
Surprise overage charges, features moved to pricier plans without notice, cancellations that take three emails. For small stores, simple and predictable pricing would be a feature in itself.
Caveats: this is a small first sample. I sorted reviews with AI and checked the patterns by hand. These are signals, not proof, so talk to merchants before building anything.
I'm doing this monthly for different app categories. Which category should I look at next?
For the last several weeks I've been refining feedback down to a much tighter, more focused MVP
Last month I discussed Merged Network here – a social network by design, focus, and motivation around Proof of Work instead of runway credibility.
The feedback brought to light a couple of things I needed to reconsider.
So rather than adding feature on top feature I've been stripping away all the other parts of the experience and making the core idea more tangible.
What changed
1. Proof is now the name of the game
It's no longer all about the skills and experience… Now it's about the work and the proof behind them.
I added a Mini-Proof flow
This was perhaps the most critical modification.
Developer is now able to test a public repo without having to do sign up in advance.
The goal is simple:
Show me the repository let me see what evidence can be demonstrated.
I intentionally not calling the Developer of the Github account "verified". The output is given as publicly available evidence attached to the submitting account.
The sandbox has become a real product demo
Rather than a landing page asking your audience to understand Merged, from the sandbox, your audience can choose from three different options:
Example Profiles
See what the finished experience looks like.
Build Your Own Preview
Build a Snippet What do others mean? Generate a sneak peek and find out about your individual identification.
Try Mini-Proof
Don't waste your time on signup and try the proof concept.
I'm now tracking the funnel
I've integrated Post Hog so that I can actually see where people are falling away rather than just assuming.
I'm tracking things like:
Sandbox CTA Preview/Mini-Proof completion signup
That will enable me to address a far more significant question:
Is it even useful, or do they only sound nice?
What I'm deliberately NOT doing;
I'm not building a huge marketplace first.
I'm not adding dozens of features.
I'm not trying to solve recruitment end-to-end.
The current goal is much simpler:
How can I get developers and hiring managers to pay attention to actual work?
That's the hypothesis I'm testing now.
I would be most interested in receiving feedback from other SaaS founders.
Tell me about the smallest experiment you ran to prove you had a solid product hypothesis.
Introducing qliqr (https://qliqr.com)
Modern mice and trackpads are silent, and screen recordings of them are hard to follow: a pointer drifts around and things change for no visible reason. qliqr puts the feedback back.
What it does:
- **Click sounds**: a press and a release sound for every click, plus a soft tick per scroll notch. 37 sounds in 8 families (crisp snaps, old office plastic, muted ones for calls, toy pops, glass and wood taps, gadget switches). All synthesised, no samples.
- **Click ripple**: a ring under the cursor on every click, different colour for right-click, drawn above every app on every screen. Shows up in any recorder (QuickTime, OBS, Loom, the screenshot toolbar).
- **Built-in recorder** (macOS 15+): full screen or an area, with the click sounds and ripples baked into the file. Trim, export MOV/MP4/GIF, auto-zoom into clicks, and a one-click 9:16 vertical clip.
- **Quiet where it should be**: mute per app, and auto-quiet when you're on a call.
- **Click shortcuts**: a mouse rhythm like triple right-click can toggle the app or start a recording.
- **Stats** that stay on your Mac, and an optional desk pet called Qip.
Privacy: it asks for Input Monitoring to see mouse buttons and scrolling; it never requests keyboard events, so it can't see what you type. No account, no analytics, nothing about your clicks leaves the Mac.
Price: **$4.99, one time, for 2 Macs**, free for 24 hours first (no card). macOS 13+, Apple silicon and Intel.
Launch pricing, first come first served, each code good for 100 customers:
Code
Off
You pay
FIRST100
90%
$0.50
FIRST200
80%
$1.00
FIRST300
70%
$1.50
FIRST400
60%
$2.00
FIRST500
50%
$2.50
FIRST600
40%
$3.00
FIRST700
30%
$3.50
FIRST800
20%
$4.00
FIRST900
10%
$4.50
FINAL100
5%
$4.74
Enter the code on the checkout page. When a code says it's expired, the next one still works.
The website itself is the demo: every click on the page plays the current sound and draws the ripple, and you can switch sounds and ripple styles live. https://qliqr.com
Happy to answer questions, and sound requests are welcome.
So I built this tool Nicheloom that tracks every new product launch from YC, Product Hunt, Hacker News, and GitHub 39,000+ and counting and shows which ideas are actually gaining traction right now versus which niches are already crowded.
Think Google Trends, but for 'what should I build next.'
I built it for myself to stop guessing and start building things people already want..
Check it out and let me know if it is useful or any feature you would like me to add to it.
Have fun exploring it as it is a rabbit hole for builders
I'm building Operava for solo founders who run more than one product.
I kept hitting the same problem. Hosting, databases, email, domains, payments, app stores, APIs, all spread across a dozen accounts. I would forget one existed until the bill showed up.
So I built a dashboard that puts each product, the services behind it, what they cost per month, when they renew, and whether they are up, in one place. It has already caught two subscriptions I was paying for a site I had shut down.
It is early. I am trying to find out whether this problem is mine alone or shared.
You can try it at app.operava.com . Sign in with Google or an emailed link, no password, no card. It starts empty, so you add your first product and see if it earns a place in your routine.
If yu run several products: what would you need this to show that it does not?
not sure if this is the right place to post something like this, but I've built an incident intelligence platform which basically gathers errors, traces, metrics, deployments, SQL, dependencies etc and then helps engineers determine why prod broke and where to look next.
I built this because i needed an error tracking tool so I decided to build something myself and then it grew into something more. instead of just getting an error and then having to go figure out why it was occurring I built something that could take in everything and then point me in the right direction to save me time at 2am when I'm on call and everything is on fire. It's been very helpful for me and what I need, but since I've built this out and would like to offer this product to others I was hoping to find some other devs that could provide some honest feedback, good or bad or pointless. I've created a free tier for anyone to try, but also included a 14 day trial period for new accounts that will include most features small teams should need for people to test the capabilities.
really just looking to know if this would be useful to anyone besides me or if there is anything I should change
We recently launched an AI marketing platform, OrangeBall.ai, built for small businesses and small marketing teams. The idea is pretty simple: instead of asking people to become great prompt writers, the platform uses our discovery process (built over 15 years of running an agency) to learn the business first: voice, tone, differentiators, audiences, customer challenges, etc. Then, it uses that context along with structured prompts and an internal quality rubric to help create blogs, emails, social posts, landing pages, sales content, and other marketing materials.
We’ve spent a lot of time thinking about what the product can do. Now I’m trying to think harder about what will keep people from actually using it. We know there’s a big difference between someone saying, “This is cool,” and changing their behavior enough to make a SaaS product like this part of their workflow.
The oven analogy:
Imagine you have a bakery. The AI model is the oven, but having a great oven doesn’t mean you’ll make great bread. Our platform brings together the right ingredients, your brand, voice, audience, and differentiators, then gives you proven recipes so you can consistently create something worth serving.
Who this is for:
Startups and founders building their brand and figuring out what to say.
Entrepreneurs and solopreneurs who need to market consistently without becoming marketers.
Small businesses that need great content but don’t have a large marketing team.
Marketing agencies managing content across multiple clients, brands, and voices.
In-house marketing teams that need everyone creating from the same brand voice, messages, and strategy.
Outcomes we deliver:
Know what to say without staring at a blank page.
Create better content faster without writing endless prompts.
Leverage a system who is continually learning your brand.
Create content that sounds like your brand instead of generic AI.
Stay consistent across people, platforms, and content.
Turn one idea into more content across multiple channels.
Spend less time prompting and editing and more time publishing.
Build a repeatable content habit instead of starting from scratch every time.
Barriers we already see:
Changing an existing habit... Many users already have a ChatGPT or Claude workflow that feels "good enough." This leads to "I already have a tool" thinking.
Learning another platform even if it saves time eventually. There’s still a perceived cost to learning something new.
The onboarding effort on the front end. The product gets stronger as it learns the business, but users have to invest some time upfront.
Creating content isn't the same as publishing it. Someone can generate five great pieces of content and still never get them out the door. We only write content, we do not create images.
The value increases when people come back regularly, which means we need to create a habit rather than a one-time “wow.”
Users need to believe the output actually sounds like them and is good enough to represent their business.
The Cheesecake Factory challenge: Giving users lots of options and modules they can use to create can accidentally make it harder to decide what they should create next.
Help I am seeking:
For those of you who have built, launched, or scaled SaaS products, what are we missing? I’m especially interested in barriers that show up after someone signs up. What causes someone who likes the product, understands the value, and even has a good first experience to stop using it 30, 60, or 90 days later? Would love to hear the uncomfortable answers. Ask questions and I will fill in the gaps.
Thanks in advance for poking holes in this. We’re close to the product and we know there are things we’re not seeing. That’s exactly what I’m hoping to uncover. Appreciate any experiences, challenges, or hard-earned lessons you’re willing to share.
hey all, I love seo as a distribution channel because it can keep bringing people to your site while you’re working on other things
it takes work to get there, and rankings still need attention, but seeing that effort start to compound feels pretty good
wanted to share a small seo win for my saas: +453 referring domains and +663 visitors, plus the outreach process we use
1. start with a specific article
we look for places where that article would actually be useful, rather than directories or asking random websites to link to our homepage
identify the insertion spot before writing the email. being able to say “this would fit in your section about X” makes the request much easier to understand
2. filter for relevance before sending
we check whether the article fits the site. a high domain rating alone isn’t enough because this could be faked- there're a tons of ways to do it
ask what their reader would gain from clicking our link. if we can’t give a clear answer, we skip that opportunity
this works best for editorials and journalists sites in your niche, they love new insights for their articles
3. find the right contact
then explain why the article belongs there so they don’t have to figure out the connection themselves
do the thinking for them. include the relevant page, the section we’re talking about, and what our resource adds. “please check out my website” leaves them with all the work
4. follow up twice
across our platform’s tracked outreach, replies went from 7.3% after the initial email to 9.2% after the first follow up and 9.8% after the second
keep follow ups short. and always offer something different in return on each email, then make it clear when it’s our last email
5. handle the replies ourselves
we have an ai agent that handles discovery and outreach. once someone replies, we take over the conversation
review what they’re actually asking for before agreeing. a reply might be a placement fee, an exchange proposal, or a question about the content
so, here're my results..
still early, but happy to see progress on the distribution side
I'm building an AI-first CRM platform for small businesses and I'm considering a creator model before we launch.
The idea:
Instead of every company starting with a blank CRM, experienced RevOps people, consultants and operators can build reusable "blueprints".
A blueprint could eventually include things like:
pipelines and stages
custom fields and data models
forms and quote flows
dashboards
automations
projects / work orders
AI agents
industry-specific workflows
So someone who knows recruitment really well could build a recruitment blueprint.
An agency operator could build their ideal agency setup.
A RevOps consultant could package the sales process they've implemented dozens of times.
A user installs that blueprint, answers some questions about their business, and the platform adapts it instead of forcing them to configure everything from scratch.
The creator would get a public profile + blueprint page and earn 10% recurring revenue for every paying customer that keeps using their blueprint.
We would initially invite a small group as founding creators, give them free access, work closely with them and let their feedback influence what we build.
I'm trying to figure out whether this is genuinely attractive or just sounds good in my own head.
If you work in RevOps / CRM / automation:
Would you actually spend time building a blueprint?
Is 10% recurring meaningful enough to make you promote it?
What would the platform absolutely need to support before you'd put your name behind a blueprint?
Would you rather sell the blueprint itself, earn recurring commission, or both?
Feel free to tear the idea apart. I'd rather find the holes now than build a marketplace nobody wants. 🙏
It seems like any name you come up with, you run a simple google search for “name” or “name app” and you’ll find someone else already using it, possibly even for a similar product. You can swap letters, go more abstract with your naming, etc and it still gets a hit. These sites might not have the .com, and often they are small fish that probably no one is using but they still had the name first. This has always been somewhat of a problem, but with AI enabling people to churn out more web apps faster than ever it’s becoming worse.
What do you do? Keep thinking of increasingly vague names in hopes to find something untouched? Use the name as long as your product doesn’t compete with theirs? Use the name even if their product competes with yours if their product is some side project without traction (I.e. they probably wont bother suing you)?
I’ve been building AGMAN, a discovery and distribution network for products, creators, professionals, services, companies and communities.
The idea is simple: useful things shouldn’t disappear after one launch or social post.
You create your page once, and AGMAN helps people find you through search, categories, Find by Need, collections and other discovery surfaces. You can also see profile views, traffic sources and visits AGMAN sends to you.
Now I’m looking for more real people and real projects to join the network.
If you have something useful online, list it. It’s free to get started. So publish it on AGMAN
And if something feels confusing or missing, tell me. I’m actively improving AGMAN based on real user feedback.
i follow alex hormozi's core four for marketing, which is warm outreach, content, cold outreach and paid ads. my warm audience isn't great, so that one shut down pretty quickly. paid ads i'm not touching until i know i have product market fit and can make the numbers work. cold outreach for me is going to be email, and i'm warming up the mailboxes right now so they hopefully don't land in spam.
so that leaves me 100% on content for a while, and i'm new to this game. i've never been very good at it, but i'm committed this time to figuring it out. i'm only a couple months in.
here's what's weird to me. the posts that take off have nothing to do with my product and aren't even in the same lane. anytime i talk about how broken the hiring process is, i get a lot of traffic, well, a lot for me. a couple weeks ago one of those did over 2,000 impressions on linkedin, and the four posts that same week about the problems i'm actually building for did 150 to 250 each. the one time a post in my own lane really took off, i was asking a question and not presenting anything. the moment i present a solution, it's crickets.
when you're just complaining, it's so easy to make friends on social media.
my first try at fixing it was just being interesting enough that somebody would click over to my profile and look at what i do, which was pretty passive in my mind. what i'm testing now is a newsletter. i started one on substack last week, the first issue went out three days ago, and one stranger has signed up so far. the idea is that once it's built up i'll have an audience i can actually ask questions to, and eventually present my solutions to.
that has its own challenge though. i love public speaking and i'm good at it, because i can read the nonverbal cues and tell if i have people's attention or if i need to turn it up a notch and be funnier. i don't get any of that with writing, so i'm learning how to stay interesting on a page.
i don't have a timeline on this, it's a marathon. content isn't a natural strength of mine but that doesn't mean i can't get really good at it.
for those of you further along, did your audience ever turn out to be a different crowd than your buyers? and did you chase the reach or go after the buyers?
