I'm the Marketing Head at Deliveryman AI, and today has been one of the busiest days I've had in a while.

We've spent months building the product, but launch day made me realize something:

Building the product and getting people to discover it are two completely different challenges.

Over the last few hours, I've been reaching out to communities, replying to every comment, talking to users, and trying to get honest feedback. It's been a great reminder that distribution is just as important as product.

For anyone curious, Deliveryman AI was built to simplify cold outreach by bringing together domains, inbox setup, warmup, verification, campaigns, and inbox management into one platform instead of juggling multiple tools.

We're currently in a close race for Product of the Day on PeerPush, with less than 3 hours left.

If you're into SaaS, outbound, or just enjoy supporting products built by small teams, I'd appreciate you taking a look. If you think we've built something worthwhile, an upvote or comment would genuinely help.

More importantly, I'd love to hear from other founders and marketers:

What's been harder for you: building the product or getting people to discover it?

Link: https://peerpush.com/p/deliveryman-ai

No pressure, just excited (and a little nervous 😅).

Happy to answer any questions.

I have been working on a bunch of different SAAS ideas at this point, some of them are just parked right now as I have decided to market others or have lost passion for the project.

Its hard to check logs in a unified fashion for a bunch of different sites, I have backend's on Fly io, Heroku, Vercel, Hetzner and AWS (for varying reasons, some consulting, some work etc). just wanted like text message updates for things with a summary, like "3 new users on ```something.com```, 300MRR created etc, usual latency across all sites".

I made canaryhub.ai, so you can just throw in your site and then have pings for health and then can upstream certain events and get summaries and notifications via Telegram Discord sms etc. I love getting a text saying "hey a user just signed up" even if they aren't a conversion.

Its free for your first project with three monitors so if you have your frontend on Next, webapp on Remix and then maybe another api etc.

Just launched it so feel free to comment with any feedback and improvements.

This started as a personal itch. I kept bouncing between a dozen single-purpose text sites (case converter here, dedupe there, a sketchy regex one I didn't trust), all buried in ads and cookie banners. So I built my own. It's called TextArray.com, now 300+ text tools in one place plus a builder to chain them together.

I'll skip the pitch and share the stuff that was actually useful to learn, since that's what I'd want to read here.

Tech stack:

• Astro for the frontend. This turned out to be the single best decision. Astro ships zero JavaScript by default and only hydrates the interactive island (the actual tool), so every page is basically static HTML with one small interactive component. Pages load instantly, which helps both the user and the rankings.
• Chrome, Edge, and Firefox extensions from mostly one codebase using the WebExtensions API. Cross-browser was less painful than I expected, though Firefox and Chromium disagree on enough manifest details to be annoying.
• The builder logic is the core. Every tool is a pure function, string in, string out. The builder just pipes the output of one into the input of the next. Once I settled on that model, no tool needs to know about any other tool, and adding a new one is almost trivial. That's honestly why I'm at 300 and can't stop.

The SEO lesson (the actual point of this post):
I didn't plan this. Because each tool is its own statically generated page, I ended up with 300+ pages (and counting up), each targeting one specific long-tail query. People don't search "text tool," they search "remove duplicate lines" or "convert csv to json." Each of those has a dedicated page that loads fast and does exactly the one thing. That's a much better SEO surface than one big app behind a login.

A few things that mattered:

• Auto-generated sitemap so all 300 pages actually get crawled.
• Per-page meta and descriptions rather than one generic template, so pages don't cannibalize each other.
• Internal links between related tools, which also happens to be good UX.
• Keeping the pages genuinely static, so Core Web Vitals stay clean without me fighting them.

Revenue: none. It's free, no ads, no signup, and I want to keep it that way, because ad-riddled tool sites are the reason I built it. I might add a Buy Me a Coffee at some point, and that's the entire monetization plan.

TextArray.com if you want to see it.

If you've done programmatic or many-page SEO for a utility product, I'd love to hear what worked. And if the builder is confusing the first time you see it, tell me, that's the part I most want to get right.

Tiny product, one person, a few hundred paying users. Late last year every thread I read was some version of "your exact tool but as a prompt," and I spiraled. If an AI writing tool can spit out what my product does in a chat window, why would anyone keep paying me a monthly fee. I lost most of a season to that fear.

What pulled me out was not a pep talk. It was actually asking my users, one at a time, why they were still around.

Almost none of them mentioned the feature I was panicking about. What came up over and over was boring stuff. It always works. It does not change on them every week. When something breaks, a real person answers and fixes it. A couple of people literally said they had tried the do it yourself AI route and came back because they did not want to babysit a prompt to run a part of their business.

That reframed the whole threat for me. The thing a general AI tool is worst at is exactly what a small paid product can be best at: being boring, stable, and accountable. It does not wander off. It does not hallucinate their data. There is a name attached to it who will pick up.

So I stopped racing to out feature the panic and put that energy into reliability and uptime instead. Fewer new features this year, more of the product just quietly working. Retention went the right direction.

For other one person founders: when the "AI will kill your product" wave hit, what did you find people were actually paying you for underneath the features?

I built an app nobody found, so I built the thing that posts for me

Roamly - Trip Planner was my last project. App for couples who travel together. 56 users. That's it.

Not because the app is bad. I'd spend a lot of time shipping features and then have nothing to post. Marketing was always tomorrow's problem.

So I built the thing I actually needed.

Klipsy makes the post, publishes it, and tells me if it worked:

• short videos, image posts, text posts — faceless, no camera
• posts straight to TikTok, YouTube, Instagram and X (official APIs)
• runs on a schedule, or asks me first if I want
• one dashboard for views, likes, comments, shares
• ranks my templates so I know what to make next
• mcp connection to analyze your data

It's posting for me while I code. That's the whole pitch.

Not open yet, letting people to join waitlist first: Klipsy Waitlist

If you've got the same problem good product, dead socials tell me what would actually make you use this?

actually I made this site for myself to find best UI's for my apps and websites but i guessed people needed a site like this.
This is the public repo, https://github.com/en970/ui-vault.git
And this is the site;https://en970.github.io/ui-vault/

It helped me a lot hope it helps you for your ideas too!
Don't forget the star<33

Hey everyone,

I’m a developer who’s researching to help with some frustrations for Mindbody users . I noticed that the export process, data lock-in, and “export fees” when switching platforms have come up a significant amount. A lot of you also seem to waste hours manually moving sales/invoices/client data into QuickBooks or spreadsheets for bookkeeping.

So here are some quick questions for you guys:

• How much time/money does manual exporting or reconciliation cost you per month?
• Have you ever paid (or considered paying) their export fee when switching software?
• Would an automated daily sync/backup tool (Mindbody → clean QuickBooks import, CSV, or Sheets) be something you’d actually pay for? (for example ~$29–49/mo)

I’m thinking about building a simple, reliable tool specifically for this pain point — nothing fancy, just something that works consistently, and then see where it goes from there.

If this sounds useful, a reply would be incredibly useful. I’m looking for a few early beta testers who’d be willing to try it (heavily discounted or free at first) and give honest feedback on what’s missing.

Appreciate any input — especially horror stories or “this would save me X hours a week”, but also "this isn't too useful at all" comments. Anything that's honest helps me.
Thanks!

I’m in the US, my family isn’t — so every call started with “wait, is he even awake?”

Built a tiny tool for it: set your hours once, share one link, and whoever opens it sees (in their time and yours) if it’s a good moment to call. Green = go. Shows if you’re asleep or on another call. No accounts, no booking, no app.

Not trying to be Calendly — no scheduling, just “are they free right now.”

You can try to make yours as well.

Sample my good to call link: https://good-to-call.vercel.app/?id=6gl75nhi

The idea: local business owners (restaurants, salons, contractors) almost never respond to their Google and Yelp reviews. Either no time, don’t know what to say, or they type something they regret.
A single unanswered 1-star review sits at the top of your profile for months doing damage. A good response takes 3 minutes and changes how every future customer reads that review.
So I built ReviewReplier. Paste review → business type → tone → done. Runs on Claude AI, keeps the response human.
What I’m actually looking for:
— Does the copy on the page make sense?
— Would you pay $19/month if you owned a local business?
— What’s missing from the MVP?
Any feedback appreciated, even if it’s “this already exists, here’s why it’ll fail.”

As the title says, I want to guest post or publish on "write for us" , in my industry. I see guest posts you can buy but they are too broad and anyone with money publishes random topics and has no moderation. So I thought to ask this community if anyone knows anywhere I can write content for, mainly in career, LinkedIn, or jobs kind of fields.

Thank you. Any help is appreciated.

Hello dear community

i have just created myjibi.com which a website for now, makes you track money, like how much you spent this month, tracking your goal, debts with friends and splitting your month budget

i know this idea is already has many apps, but i have added some features and willing to

you can test it, create your account there, test and i am open to any advice, criticism and anything ))

the mobile app will be released soon, the website is just a simple test for now

Thank youuu

I'm building a service where the main feature calls an LLM API, so each free use has a real variable cost.

A free tier would let people see whether the product is useful before they pay. My concern is that it could mostly bring in people who never planned to pay, plus abuse and extra support work.

I'm considering a few setups:

- a small number of free calls each month

- one-time trial credits

- a cheaper model for free users

- no free tier, with a clear demo instead

For anyone running an AI product with usage-based costs, did free access improve paid conversion enough to justify the API bill? Which limit worked best without making the trial feel useless?

I spent the last few months building an AI security auditor called Aedis, and building it changed what I think actually matters when you're about to ship, sell, or inherit a codebase.

The stuff that actually scares me isn't the one-liners a linter catches. It's the bug that spans three files, where input gets trusted in one place, passed through another, and only becomes a hole in a fourth, because no quick scan connects those dots. And worse: whether whoever built it left something in on purpose. A hardcoded admin bypass, a hidden endpoint, a "debug" route that's really a way back into the app.

What makes it different from a single-model scan: Aedis runs several flagship AI models over your code independently, then cross-checks their findings against each other. One model flags something, another has to confirm it before it makes the report, which kills the false positives that make most AI scanners useless and catches things any single model misses on its own. It reasons across the whole codebase instead of file-by-file, so it catches the multi-file stuff and the deliberate-backdoor stuff, plus the usual broken-access-control and known-vulnerable dependencies.

Straight up about the limits: it reviews the code, it doesn't run or exploit your app or touch your infra, so it's not a full manual pen-test, but it catches the expensive, deal-killing stuff. And it writes findings as "does this kill a deal / cost you a week of engineering," not useless "CVSS 7.8" scores.

I want real micro-SaaS codebases in front of it instead of my own test cases. First 3 people to comment below, I'll reply with a coupon for a completely free full audit. All I ask is you tell me honestly what it nailed and what it missed, and if it turns out genuinely useful, a writeup would help me a ton, but zero pressure.

Hi everyone,

I’ve been doing some market research looking for a reliable netlist-to-schematic converter that outputs clean, human-readable diagrams (especially given how often LLMs and scripts spit out raw netlists or ugly grid stubs). Aside from basic layout engines or specialized SPICE tools, I haven't found a robust, modern solution.

Because of this gap, I'm considering building one myself.

Before diving too deep into development, I wanted to run a few questions by this community:

• Target Formats: Which schematic tool outputs/formats are most commonly used in your workflows today? (e.g., KiCad .sch/.kicad_sch, Altium, LTspice .asc, etc.)
• Product Model: Assuming a tool like this existed as a cloud/SaaS product, would you or your team be interested in using it as a paid service?
• Must-Have Features: If you were paying for a tool like this, what features would be non-negotiable? (e.g., round-trip connectivity verification, custom symbol mapping, hierarchical block structuring, automated layout arrangement)

I'd love to hear your thoughts, whether you'd find this useful, or what hidden gotchas I should watch out for when trying to map topology back into a readable diagram.

solo founder, launched about 5 weeks ago. the product is crawlmouse.com, it crawls your site and grades your internal linking A to F, finds orphan pages, stuff buried too deep, weak hubs. paste a url, get the grade, no signup. i built it because the desktop crawlers are overkill when you just want one question answered.

the numbers so far, since this sub likes receipts: 20 free users, 1 paying. google organic clicks after 5 weeks of doing SEO properly for my own site: zero. literally zero, DR 0 domain, everything ranks page 4 to 9. every single user came from reddit, mostly from comments where i answered someone's question and the tool happened to fit. two posts brought 9 site audits within 4 hours. my only google clicks are people searching "crawlmouse" by name after seeing it here. so reddit feeds google for me, not the other way around. if you're pre-traction and grinding blog posts, that's your cautionary data point.

the accidental marketing lesson: the thing people keep reacting to isn't a feature, it's the pricing structure. free tier is actually free forever, no credits, no trial countdown, no "you've used your 3 audits this month." i did that originally because i just wanted people to use the thing, but it turns out the entire SEO tool market has spent two years making people miserable with credit systems, ahrefs is sitting at a 1.8 on trustpilot mostly over credits, and people burn a month of credits in an hour. so "no credits" has become the line that gets quoted back to me. i didn't plan that. sometimes your positioning is just the wound the incumbents left open.

honest downsides so nobody thinks this is a victory lap: 1 paying customer is not a business, my email capture is basically zero so i can't even follow up with the users i do get, and reddit found two real bugs in my grading logic within hours of my first post, which was humbling and also weirdly the most useful QA i've ever gotten. one guy's site is navigated entirely through a search box and my tool gave him an F, we ended up debugging his site architecture together in the comments and he went F to C in a day. that thread converted better than anything i've written.

the thing i'm building now, and honestly the most fun part: an AI readiness score. the tool already reads the raw html your server returns, which happens to be exactly what GPTBot and claude and perplexity's crawlers see, because none of them run javascript. so a site can look perfect to you and be half empty to an AI crawler. i keep running audits where the human version of a site and the bot version are basically two different websites, and the owner has no idea. so i'm turning that into its own score next to the linking grade, how much of your site an AI crawler can actually access and read. it's not a "you'll rank in chatgpt" promise, nobody can honestly promise that, it's just showing you what the machines actually see, which right now almost nobody checks.

so my ask from this sub: run your side project through and tell me if the grade feels fair, the edge case reports are how i'm improving it. and i'm curious what founders here actually want to know about their AI visibility. like if you could see one thing about how chatgpt or claude sees your site, what would it be? genuinely shapes what i build next

My neighbor runs a small moving company. Good guy, works hard. He kept losing jobs because by the time he emailed a quote, the customer had already booked someone else.

He'd spend 20-30 minutes writing each estimate — pricing research, word it professionally, format it, send it. By the time it went out, it was too late.

So I built QuickQuote AI. You put in the job details and GPT-4o generates a complete estimate with line items and price range in about 60 seconds. Download the PDF or email it straight to the customer.

The core insight: for service contractors (movers, painters, landscapers, HVAC, etc.), speed of follow-up matters more than price. The quote that arrives first usually wins.

Live at quickquote-ai-woad.vercel.app — free plan has 5 quotes/month. Still early but curious what folks here think about the niche. Anyone else building for the trades?

I spent way too long on the wrong artifact. Sharing the small numbers because the lesson cost me weeks.

Early on I was convinced I was losing deals because my materials looked amateur, so I built a proper sales deck template and reused it everywhere. Deals kept stalling anyway. 12 paying customers later, here is what actually moved the needle, and it wasn't the deck.

**1. The pricing page did more selling than any call.** Half my customers told me they had basically decided from the pricing page before we ever spoke. When it was vague, people ghosted. When it named who each tier was for in plain words, they showed up to the call already sold.

**2. Three tiers beat one number.** A single price is a yes/no question, and "no" is free. Most people picked the middle tier once there was a middle to pick.

**3. Anchoring the value before the price.** One honest line about what the alternative costs them (their time, a tool they already overpay for) did more than any feature list.

**4. Removing choices, not adding them.** Every extra option on the page lowered conversion. The version that converted best was almost aggressively simple.

The deck? It closed exactly nobody on its own. It was fine as a leave-behind, but the buying decision was happening on a page I had barely touched.

For those further along: what is the one asset you underinvested in that turned out to be doing most of the selling?

One-man web design and maintenance shop for local service businesses. Two years in, about $6k a month, and for most of that I was stuck on the treadmill every freelancer knows: finish a site, get paid once, go find the next one. I wanted recurring revenue. Here's the specific thing that finally created it, in case it helps another solo services person.

The problem wasn't that clients didn't want maintenance. It's that maintenance is invisible. I'd spend a few hours a month on updates, backups, security, small fixes, and to the client it looked like I did nothing, so the retainer felt like a tax. They'd cancel the second money got tight.

The fix was making the invisible work visible. I set up an automated monthly report for each client, built with an ai report generator hooked into my tools, that shows in plain English what happened that month: uptime, updates applied, spam blocked, load time, the broken thing I quietly fixed before they noticed. Branded, one page, in their inbox on the 1st.

Nothing about the actual maintenance changed. The perceived value did. Churn on retainers dropped hard, a couple of one-off clients asked to move onto a monthly plan after seeing a friend's report, and recurring is now most of my income instead of a rounding error.

The lesson for solo services folks chasing MRR: people don't pay to keep paying for work they can't see. Show them the work, every month, without them asking. What's been your best move for turning project clients into recurring ones

Non-technical solo founder here. I built a dog-health app, the "is this a vet trip or am I overreacting at 2am" thing. Early on I had to decide what's free and what's paid, and I went with something that felt backwards.

The free-forever layer is the scariest-moment stuff: an offline toxic-food and plant checker, and an emergency warning-signs guide. No account, works with no signal. The paid part (3-day trial then subscription) is the AI photo and chat triage, the "help me think through what I'm actually seeing" layer.

My gut said paywall the emergency features, since that's peak urgency and peak willingness to pay. I couldn't do it. Putting "is this food about to hurt my dog" behind a card form felt genuinely wrong.

Two weeks in, the surprise: that free safety layer is basically the entire marketing engine. It's the thing people install "just in case" and screenshot to other dog owners, and it's what earns enough trust that they'll even consider paying for the AI later. Revenue is tiny so far (honest: a handful of trials), but the installs and word-of-mouth are all coming through the free tool, not the paid pitch.

Genuine question for anyone doing freemium: where do you draw the free/paid line when your highest-stakes feature is also your best trust-builder? Do you give away the emotional peak, or is that just leaving money on the table?

(It's Pawsy on iOS if the context helps: https://apps.apple.com/us/app/pawsy-ai-dog-health-vet/id6782015126 — but I'm really after the pricing-philosophy discussion, not upvotes.)

I’ve spent a long time building side projects that never got launched.

This week I finally pushed one live: TechTools Notepad → https://notepad.techtoolsweb.com/

What it does:

• Edit HTML, CSS, JavaScript, Markdown, JSON, SQL, and plain text
• Live browser preview for markdown and html content
• Multiple tabs
• Cloud save
• Password protected tabs
• Export and formatting tools

The idea came from my own workflow: I often need a quick scratchpad for code snippets, landing page experiments, API responses, and technical notes, and I wanted something that felt closer to a real editor than a simple online notepad.

I’m currently validating whether developers and technical writers would actually pay for features like cloud sync, version history, snippets, and AI tools.

If anyone here has launched a developer-focused SaaS before, I’d love advice on:

• Pricing for Indian vs international users
• The best channels for getting the first 100 users
• Whether the product feels more like a "notepad"

Any brutally honest feedback is welcome.

sometime ago i was tasked with building a chatbot i built it then reality hit api costs were sky high thats why i built a platform to reduce it ornymo a async first pipeline that caches meaning on intent and verify it

About two months ago I put my mind to researching SaaS ideas, I'm sure most people automatically come across ideas from social media. These ideas mostly involve either high competition SaaS or more interesting tools to develop (e.g AI automation, Travel Planner etc).

After doing research, I realised the best place to be is to be in a boring sector which actually solves a problem that has little solutions available. If you can beat the low competition with lower prices, more features & more accessible, you will dominate that sector. Even if you capture 1-2% of that market which could be relatively small, say that sector of SaaS generates 1M /MRR then you claim $10,000 - $20,000 of that.

They are also notoriously easy to market, if you try to promote a product in a large audience you will get ignored and word of mouth won't spread easily. However if you target a small audience, your product can become very popular and well recognised without being disregarded.

I'm hoping to release soon after around a month of building and will document if it succeeds. If you disagree with any of these takes then I'm happy to take any comments.

I'm an ex strategy consultant who built a small tool for my own client work and started selling it on the side. I don't post much, but this lesson was worth writing down because it cost me months to learn.

For a long time I described the product by what it did. Structured workspace, report builder, that kind of thing. Accurate, and nobody cared. Signups trickled.

On a whim I changed the positioning to a "notion alternative for consultants." Didn't touch a line of code. Just rewrote the landing page and how I talk about it in comments and DMs. Signups roughly tripled over the next several weeks off basically the same traffic.

Why it worked, best as I can tell: "notion alternative" is a search people actually type and a mental slot they already have. Consultants know they're overpaying in time wrangling Notion or Google Docs into deliverables. When I named the thing they were already frustrated by and stood next to a tool they know, I stopped having to explain the category from scratch. I borrowed a category and narrowed it to my niche.

The lesson I'd pass to other micro founders: your positioning is doing more of your selling than your features are. "A tool that does X" makes people work to place you. "The [known thing] alternative for [specific person]" hands them the frame for free. You can test it in an afternoon.

Anyone else seen a positioning change move revenue harder than a feature ever did? Curious how far this goes before it stops working.