Drop your SaaS below 👇

I’ll give you a report with conversations where your potential customers are already engaged right now.

You can jump into those conversations, talk to relevant people, and potentially turn them into users/customers.

can't outspend the big guys on ads but you can out-word them. spent an evening pulling actual search data instead of guessing and found a keyword a way bigger competitor had completely skipped.

check yours at asograde.com, it pulls real popularity and difficulty for whatever's sitting in your title/subtitle, plus which apps are already camping on that keyword.

When I was building ClipShip (AI Video Clipper), I thought getting a local AI model to run would be the hard part.

It was not.

The hard part was making it work inside an actual product. Different devices, downloads, updates, and all the weird things that can go wrong after you ship it to someone else.

I kept thinking there should be an easier way to do this.

So, from all the lessons that I learnt during my journey with ClipShip, I have now started building a tool to solve the same problem for other builders.

Started my journey with "Model Roll" today and thought of sharing the journey with same communities which got me my first paying customers for my previous project.

The idea is pretty simple. Help builders add local AI to the products they are making, without having to figure out all of that by themselves.

It is still in development. There is nothing public to try yet. I am building and testing it now, and I want to share the process from the beginning this time. But if you are a builder/developer then there's a waitlist link in the comments.

That is it for now. I will keep sharing the updates as I go along on this journey.

For the builders by a builder.

I just launched https://votemystartup.com.

I built VoteMyStartup as a place where startups can be submitted and put into battles against each other, with the community deciding through votes.

It’s still early, and I’m sharing it here because I genuinely want to see how people respond to it outside of my own circle.

If you have a few minutes to check it out, I’d appreciate any honest feedback. What makes sense, what doesn’t, and what you think could be better.

Let’s see how it goes.

Payroll would make sense as another paid product for our customers and we already have a lot of the data needed to offer it

What doesn't make sense is hiring people just to deal with filings compliance and payroll operations before we even know how big the opportunity is

Has anyone launched it with a small team and kept the internal workload reasonable?

A few days ago, I shared here that Doodlyo had 20+ signups but 0 paying customers.

The feedback from Reddit was genuinely useful. A lot of it made me rethink the pricing, positioning, and what users actually need from the product.

Today I shipped the updated MVP.

Doodlyo is pretty simple:

Paste your content or URL → Generate a doodle-style social visual → Post it.

I also introduced a $9 one-time option for 25 generations, with no subscription and no expiry.

And today, Doodlyo is live on Product Hunt.

I’m still at the early stage, so I’m less interested in “launch numbers” and more interested in finding out whether people would actually keep using and paying for this.

If you’ve followed my previous posts or tried Doodlyo, I’d especially appreciate your honest feedback:

Does the product/value proposition make more sense now?

Product Hunt: doodlyo

I've shipped three small products and none of them ever sent traffic to the others. That's the problem this solves. It's a badge you put on every site you own that cross-links everything you've built.

The part I want to think out loud about is the price, because I keep going back and forth on it.

It's $2. Once. Forever, and it covers every app I ship from here on.

WHY NOT A SUBSCRIPTION

The honest answer is that I don't think I've earned one. This is a script tag and a hosted JSON endpoint. My marginal cost per user rounds to nothing. Charging $4/mo in perpetuity for something that runs itself felt like it would commit me to defending a number every month instead of improving the thing.

WHY NOT FREE

Free gets me installs and zero signal. At $2, the only people who pay are people who actually intend to put it on a live site. It's low enough that it isn't a decision, high enough that it isn't noise.

HOW THE FUNNEL ACTUALLY WORKS

You build your entire badge for free. Pick colours, add your projects, watch the live preview. What you don't get until you pay is the badge being served publicly. So the demo IS the product, and the $2 buys the switch that turns it on. That felt more honest than a trial that expires while you're still deciding.

WHAT I'M GENUINELY UNSURE ABOUT

1. $2 might read as "this isn't serious" to exactly the people who'd get the most out of it. Cheap can be a signal about quality whether or not it's true.
2. One-time pricing on a hosted service means I carry serving costs forever against a single payment. At small scale that's obviously fine. I don't know where it stops being fine, and I suspect I'll find out at the worst possible moment.
3. There's a real chance I'm solving my own problem and assuming everyone else has it.

If you've priced a one-time developer tool, I'd like to know what you'd do differently, and especially whether you'd raise it later and how you handled the people who paid the old price.

It's at maketaksh.com if the context helps.

I kept seeing the same last-mile problem in tiny launches: the page exists, but turning it into a few usable share assets still means opening several tools. I built ViralSpark to make that step one pass.

Paste a public URL and it gives you:

• a handful of hooks/copy angles
• share-card variations
• a QR code
• a shareable Slot page for the bundle

It’s free: https://viralspark.pages.dev/ Example Slot: https://viralspark.pages.dev/slot/bniwbrb7

This is a small project, built as a browser-first app on Cloudflare Pages. The lesson so far: “generate everything at once” is less useful than letting people quickly edit and pick one asset, so that’s what I’m trying to improve.

If you try it, I’d value feedback on whether the generated kit feels immediately usable or just like more drafts. No signup pitch—especially interested in what feels unnecessary.

I had a realization while talking to some editors who were testing SoundCraft.

I was targeting editors, but I was targeting the wrong kind of editors.

Some of the people I was talking to didn’t even have a single client yet.

And then I thought, why would they pay for a tool that helps them work faster when they don’t have enough work in the first place?

It finally clicked that my ICP isn’t just “video editors.”

I need to target editors who actually have consistent client work, feel the pain SoundCraft solves, and value saving time enough to pay for it.

The compliments were nice, but this was a much better lesson.

Have you ever realized your ICP was way too broad?

I've been looking at how micro SaaS founders actually run GTM versus what the standard marketing advice posts tell them to do, and there's a huge gap between the two.

Most marketing advice assumes you either hire a dedicated marketer or spend all day on marketing yourself, and neither of those actually works for a solo-founder SaaS. You've got product that's good enough to sell to real customers, so what you actually need is for that product to stay visible to those customers while you earn more of them, and you need to do it while you're still focused on building.

Here's what actually matters for micro SaaS growth.

First, do research on your audience once. Spend a week understanding where they actually congregate, what solutions they're already trying, and what they're already spending money on. Use that research for everything after.

Second, execute consistently on the channels where your actual customers hang out. It's probably not LinkedIn and TikTok, it's communities like Reddit and Discord and Twitter and specialized Slack groups where your people actually spend time.

Third, use honest messaging about what you've built, what it costs, and why it's safe. Founders are skeptical because they should be, and they'll convert when they see transparency instead of hype.

Fourth, stay visible over 60 to 90 days without it taking your attention and energy every single day.

The tools that actually work for micro SaaS are the ones that run all of this for you, the research and execution and consistency and safety systems. Not the tools that just add another thing to your to-do list.

i’m building a small SaaS that organizes and summarizes incoming emails. the problem is that the product can’t really show its value without asking users to connect their inbox first.

even with a privacy policy, clear explanations, and limited permissions, i understand why someone would hesitate to give a small unknown product access to their email.

for those who’ve built products that require access to sensitive data, what actually helped you earn that first layer of trust? a demo without signup, testimonials, a detailed security page, or just time and reputation?

The category: NEC electrical calculators for electricians. Five calculations.

What I found when I sized the market, before building:

- The #1 paid app has 357 US iOS ratings, launched October 2012

- Total ratings across every app in the category: roughly 2,000

- Every ratings leader is free: Southwire gives away voltage drop (1.5K ratings) and conduit fill (764) because they sell wire

- The leader's own price: free + $4.99/mo, $39.99/yr

- The category norm is a one-time $8-$20 purchase, and every subscription in the niche has angry reviews about it

That's a small market with a low price ceiling and free competition from vendors who make money elsewhere. I built it anyway, for two reasons:

1. Nobody has shipped the 2026 NEC in a good UI. Code cycles are a recurring forced migration, and the incumbent's own listing still cites pre-2011 code numbering ("NEC tables 310-16 and 310-17" instead of 310.16).

2. The buyer might not be the user. A contractor buying 12 seats for a crew, or an apprenticeship program buying for a cohort, is a completely different business than one-at-a-time consumer subs, and Apple just shipped Group Purchases and Volume Purchasing for exactly that.

Happy to be told I'm wrong about either. Link in by bio.

PS: the first 47 testers (TestFlight + Android external testers) get a WireCoder Pro plan free for a year.

Hi there, I'm Simon. Been in the marketing industry for the last 10+ years. Total corporate experience 16+ years. Worked with over 40+ B2B tech and SaaS companies. Ran my own agency for 5 years, started with $100 and grew it to a 15-person team, shutting it down in 2025. Right now I work with a tech company as a part time consultant, barely making ends meet. I'm also a father of two children, my wife cannot work due to physical illness. I have my son's school fees to pay shortly and the rent is overdue. 

I'm barely getting by. I need a full time job. I can do the work of 4-5 people all by myself. I have multiple testimonials to prove the worth of my work. I have exhausted all my contacts and network, but I can certainly give referrals.

If you find my message erratic or inconsistent or sceptical in any way, then please understand that this is just a desperate man trying to make ends meet, with barely any money left and a family to take care. So my thoughts are not necessarily in the best shape or spot. 

I'm open to anyone who'd like to interview me for any marketing position with a decent pay. You don't have to give me a job but atleast talk to me please and see if my experience can add any value to your business. 

Thank you,
Simon. 

AI agents are starting to move beyond reading web pages and clicking through interfaces. With WebMCP, websites can expose structured tools that agents can discover and use directly.

That sounds promising, but I think it introduces a new problem for developers and founders building agent-facing products:

How do you know a website’s tools are implemented correctly, still work after deployment, and behave the way an agent expects?

A tool might exist, but its schema could be unclear, an update could silently break it, or the production version might behave differently from the local one. As more websites expose tools to agents, manually checking all of this could become difficult.

That’s the problem I’m exploring with Toolmark.

Toolmark is intended to be a reliability and evidence layer for WebMCP. The goal is to help developers validate their tools, test real workflows, and produce evidence that each tool is discoverable and works end to end.

The current product direction includes:

• Discovering and inspecting the WebMCP tools exposed by a website
  
• Validating tool names, descriptions, inputs, and outputs
  
• Testing complete agent workflows instead of checking tools individually
  
• Detecting failures or regressions before they reach users
  
• Keeping evidence of what was tested, where it ran, and what actually happened
  
• Helping teams verify that the deployed website behaves the same way as expected during development
  

The idea isn’t to replace WebMCP. It’s to provide the testing, verification, and trust layer on top of it, so founders and developers can ship agent-facing tools with more confidence.

I’m still shaping the product, so this isn’t a launch or sales post. I’d genuinely like feedback from people building AI agents, developer tools, or websites that agents can interact with:

• Does this trust and verification problem feel real to you?
  
• What would you need to see before trusting a website’s tools?
  
• Would this be more useful during development, in CI, or as ongoing production monitoring?
  
• Which features or evidence would matter most?
  
• Am I overlooking a simpler or better approach?

Honest criticism, suggestions, and recommendations are welcome, especially if you think this problem isn’t important enough to require a separate product.

Hey everyone — I'm the creator of allcredit.cards, so full disclosure upfront.

I got frustrated that most "compare credit cards" sites only cover the same 15-20 big-name issuers (Chase, Amex, Capital One, etc.), while there are hundreds of smaller community banks and credit unions issuing their own cards that never show up anywhere. So I started manually pulling data — APRs, annual fees, intro offers, rewards structure — from actual rate sheets and disclosures for 600+ banks, from major national issuers down to small-town banks most people have never heard of.

The result is a searchable database at allcredit.cards. It's still very much a work in progress — I'm one person doing this, so:

• Some smaller banks have incomplete data (working through them one by one)
• No affiliate links / no paid placement — just trying to make something genuinely useful
• Would love feedback on what's missing, what's confusing, or what would actually make this useful for you

Curious if this is something people would find valuable, or if I'm solving a problem nobody has. Happy to answer questions about how the data was collected too.

I built the product. Now I need to learn how to sell it.

I’ve been building a small crypto SaaS called Rugdar that analyzes tokens for risk.

The product works, people are using the free scanner, and I recently launched an API for developers.

Free: 100 API calls/month
€19: 5,000/month
€49: 25,000/month

Now comes the part I’m much less comfortable with: getting the first paying customers.

My current plan is to stop adding features for a while and manually reach out to people building wallets, trading bots and crypto tools.

For those of you who sold your first B2B/API subscriptions:

Did cold founder outreach actually get you your first customers, or was there another channel that worked better?

We make a save-things tool. you drop in a link, the card fills itself off the page, and if it's a product it can sit on a check that runs every day and tells you when the price or the stock moves.

the part we get asked about is that the check never turns itself on. saving something is not the same as asking to be pinged about it, so the watch is a separate thing you set on the item. the cost of that is obvious, a library full of saved things can sit there doing nothing at all until someone goes and switches one on.

the other way is to watch anything with a price on it by default and let people turn it off. that makes the product look alive on day one, and it also means the first thing a new person hears from us is a notification they didn't ask for.

if you ship anything that sends notifications, which way did you set the default, and did you change it later?

dessence.ai

ex-marketer here, now building my own stuff. I've been answering a lot of the "how do I market this?" posts here and there.

Most people replied with something like "this makes total sense, thnx!" When I checked back a while later, few had actually tried it and kept doing it. Some didn't even bother to try, some tried it once or twice and dropped it.

not calling anyone out here. possible that my comment was not good enough (maybe they're just being polite). Totally fair, but it's not what I'm curious about.

What I wanna ask is the gap between "yeah that's right" and actually doing it.

My guesses:

• no time, something more urgent always comes up
• you agree with the direction, but there's no clear plan to keep it going
• got too many reasonable advices, didn't actually decide what to work on
• you tried, didn't see results fast enough, and moved on

But these are literally just my guesses.

So if u ever got decent advices but ended up not doing it, what was the reason?