Connect with the Product Hunt community

Genuine question for freelancers and small agencies.

For big projects, a contract is a no-brainer. But for a $300 logo tweak or a two-day dev fix, it can feel like overkill. Sending one can even make the client hesitate.

I ve gone both ways:

• No contract: fast start, but twice the scope crept and once the payment took 60 days.

• Contract every time: slower start, but no awkward that wasn t included conversations.

On 16 Sep I rewrote the title of one of my blog posts, a case study guide on AI in manufacturing. Google recrawled it on 18 Sep at 07:06, and the same day Search Console moved it from indexed to crawled, currently not indexed.

I posted about it that day as if the edit had cost me the page. In my next daily report, on 19 Sep, it was listed as newly indexed again. I had not touched it.

I shipped a small tool built with Claude Code thinking it was ready to go. The moment a second person opened the app and made a live update, it wiped out my recent edits because there was no conflict handling built in.

Since AI agents only build what you specifically tell them to I now ask one question in every prompt: what happens if two users do this exact action at the same time?

We ve been working with a developer in Germany for a while and would now like to bring them onto the team full-time.

The problem is that we don t have a German entity, and keeping them as a contractor doesn t really feel right once they re basically working as a regular employee.

Our accountant suggested looking at an employer of record, and G-P is one of the options we re considering so we wouldn t need to set up a company in Germany just for one person.

Has anyone here actually hired someone this way?

I m building a small clothing brand from USA and I m trying to grow without paid ads. So far I ve been testing Pinterest boards and SEO for traffic, but it s slow and I can t tell what s actually working.

For those of you who ve launched a physical product store:

1. What was your first channel that brought real customers, not just visitors?

2. How long did SEO or Pinterest take before you saw results?

3. Is there a metric you wish you d tracked from day one?

I d love to hear what worked and what was a waste of time. I ll share what I learn from this thread in a follow-up.

When I launched my design agency, I gave a 20% "early adopter" discount to almost every client who asked for one. I told myself it was necessary to build a portfolio. In reality, I was afraid of hearing the word "no."

Eventually, I was overbooked, underpaid, and burning out. I decided to enforce a strict no-discount policy across all services. I was expecting angry pushbacks and lost deals. Instead, most clients simply accepted the quote, and those who asked for discounts respected my polite refusal and signed anyway.

The lesson I learned: Clients negotiate discounts not because you are overpriced, but simply because they want to see if you'll yield. Discounting your core rate erodes trust and signals insecurity in your work. If a client truly has a lower budget, reduce the scope of work rather than cutting your price.

How do you handle clients who constantly ask for discounts? Do you hold your ground or offer scope adjustments?

I'm considering the possibility of small development teams spending less time on repetitive tasks and more time on solving actual problems.

For instance, a team could end up spending hours each week on manual testing, carrying out deployment checks, preparing bug reports, or keeping the project updates in order. However, it isn't always the case that everything should be automated since the costs involved in setting it up and in maintaining it can end up exceeding the time that is saved.

I would like to get some feedback from developers and startup teams who have dealt with this issue.

What is the basis on which you choose the first repetitive task to automate and was the outcome worth the trouble?

Last month we connected an autonomous agent to our support inbox to speed up reply times. The AI agent worked well at first cutting our backlog to zero within the first 48 hours. I was thrilled by the results.

The trouble started when a regular client asked a billing question that had a small edge case. The AI agent hallucinated a policy refund that we never offered and answered with politeness. We only caught the AI agent because our human quality audit flagged the outbound volume before sending. I felt uneasy when we discovered the mistake.

The issue was not the model capability. Our lack of guardrails around irreversible actions. We quickly updated the workflow so the AI agent drafts all responses but any account changes require approval. I think this new guardrail is essential.

Our current setup is simple. The AI agent handles the synthesis and drafting while humans own the click. I feel this balance keeps speed and safety aligned.

Offering monthly plans makes it way easier to get that initial yes from users but chasing churn every month is exhausting.

Annual upfront gives you cash right away but it definitely scares off people who aren't fully convinced yet.

Giving a huge discount to force annual signups feels like it cuts too far into profit.

Do you guys push annual pricing upfront or start everyone on monthly and upgrade them later?

We ran our B2B SaaS software at $19/month for almost two years without touching the price, despite adding dozens of new features. We were afraid that an increase would trigger a mass churn event, especially among our early supporters.

When we finally decided to raise the rate to $39/month for new signups and gave existing users a 6-month price lock guarantee, the retention rate blew us away. Churn didn't spike, and our MRR (Monthly Recurring Revenue) almost doubled over the next quarter.

The lesson I learned: Your most loyal users stay for the value your product provides, not just because it's cheap. Grandfathering existing customers into their old rate for a set period builds immense goodwill and gives them time to adjust. Communicating transparently why the price is changing (e.g., product improvements, support expansion) makes all the difference.

How do you handle price changes for SaaS or recurring subscription products without upsetting your core user base?

We made the classic mistake of building a heavy feature for five vocal customers. The extra settings completely ruined our main workflow and caused new users to drop off right after signing up.

Stripping that code out completely made the app feel fast and simple again. It was a huge reminder that adding features isn't always the answer to growing a product.

A user signs up on a Monday, forgets to cancel their sandbox project, and gets hit with a $49 charge on Sunday morning. They immediately dispute the charge with their bank instead of emailing support, costing us a processing fee and a potential advocate.

Nothing about our conversion funnel makes that cliff feel manageable. The fourteen-day trial label sets an expectation of breathing room, but the friction of entering payment info upfront turns the trial into a ticking clock rather than an exploration.

Card-required trials exist because they filter out low-intent signups and improve conversion rates to paid tiers, and that metric drives our growth charts. But optimizing for upfront conversion while ignoring day-one hostility creates a toxic cycle of chargebacks and angry churn.

What I would do differently: let users build and test fully in the free tier with strict functional limits, then prompt for payment only when they hit a hard wall that requires production scale. Harder to build separate feature gates, much healthier for long-term retention.

Before I would learn something first and then try to build with it

Now I often do both at the same time

I get an idea

Start building

Hi everyone!

I've noticed a problem with the way I discover and use digital tools. Whenever I find a useful website or app, I try it out, but after some time, I often forget its name or where I found it.

I've tried saving links in bookmarks, but eventually, they become difficult to organize, and I rarely go back to check them.

I'm wondering if this is something other people experience too. It feels like discovering a useful tool is only half the challenge; remembering it and actually using it later is another.

For a time our template directory pages were just a grid of images with titles and download buttons. We thought users just wanted to see the templates away so we kept the design as simple as possible.

The issue was that search engines had no text to read to figure out what the page was really about. We were appearing on the page for our main keywords and our organic traffic stayed the same for six months.

We stopped making templates for a week and went back to update our top twenty category pages. We added a three-sentence introduction at the top of each page that explained exactly what the templates were for and who should use them.

We also added a frequently asked questions section at the bottom to answer common technical questions. In than forty days those specific category pages had a forty-five percent rise in organic search visits.

Hey guys, hoping to get a bit of advice here. I formatted my old 10-year-old Acer laptop (Windows 10, HDD) and realized too late that I forgot to back up around 300GB of photos and videos.

I did a scan with Disk Drill just to check, and luckily all the files are still intact. But I can't afford the Pro version to actually recover them. I know people usually recommend PhotoRec, but is there anything a bit more user-friendly that is completely free for this much data? Thanks in advance!

As a developer looking at the current state of cloud gaming and digital distribution, I've been running into a major structural contradiction.

On one side, traditional cloud gaming forces users into a monthly subscription rental model where they never truly own local files or game data. On the other side, local gaming requires users to invest in increasingly expensive hardware. The industry treats "owning a game" and "executing a game" as a single bundled product.

I ve been exploring a hybrid concept and wanted to get thoughts from other makers here:

1. The Ownership Layer: A GOG-style approach where users buy and download actual local files for offline play, giving them absolute ownership with zero subscriptions.

2. The Convenience Layer: An optional edge/cloud-streaming network that acts as a runtime environment for those already-owned files when users are on weaker hardware or traveling, bridged via real-time save-state syncing.

For the year of our app we offered a free basic plan to attract as many users as possible. I expected this large group of users to eventually upgrade when they reach our usage limits.

The reality was entirely different from my expectations. Free users produced ninety percent of our support tickets. Asked for complex features they would never pay for. Meanwhile our actual paying customers got slower response times because we were busy managing the tier.

Three weeks ago we made a decision and disabled the free plan, for new signups. We replaced it with a fourteen-day trial that requires a credit card upfront. I honestly expected our daily registrations to drop to zero and our growth to stop completely.

Registrations dropped by eighty percent. Our actual paid conversions increased by forty percent in the first month. The people signing up now are buyers who test the product thoroughly instead of creating throwaway accounts.

Hey guys, I really need some help here. I recently formatted my 10-year-old Acer laptop (Windows 10, mechanical HDD) and lost around 300GB of irreplaceable photos and videos.

I scanned it with Disk Drill and the files are all there, but I just can't afford the Pro upgrade right now. I know my data is still safe on the drive, but I'm feeling a bit lost on what to use instead.
Could anyone recommend a genuinely free tool that can safely pull that much data off an old HDD? Thanks a lot!

Two years ago my hardware store struggled to attract search traffic for tools. We had hundreds of product pages. Most of them simply copied the manufacturer s short two sentence description.

Google treated those pages as content and placed larger competitors ahead of us. I stopped worrying about backlinks. Spent three months rewriting the top fifty product pages in my own words.

I added details about the materials the tool could cut its weight and common mistakes people make when using it. I answered the questions that our in store customers asked me every day.

Within sixty days organic traffic to those pages rose by more than forty percent. The pages began ranking for long tail search queries that I never even targeted on purpose.

Spent a whole month building a custom export tool because it was the #1 request on our feedback board.

Once it launched, barely 4% of the people who voted for it actually used it more than once. turns out they didn't really need the feature they just wanted to know the app had the option.

How do you test if users actually need a feature before wasting weeks building it?

Every week brings new launches, and I try a lot more tools than I keep. My filter is simple: does it replace something I already use, and do I still open it after two weeks?

For example, I tried three different note-taking apps this year. Two were beautiful but I stopped opening them after a few days. The one I kept looked plain, but it saved me time every single day.

It made me wonder if my filter is too strict, because the boring tool beat the flashy ones.

How do you decide what stays in your stack? Have you ever kept a tool that failed your usual test?

Coin collecting got me thinking about a product design challenge: how do you make a specialized hobby app useful to someone who doesn t yet know the terminology?

A beginner may have a coin they re curious about, but not know its country, year, or denomination. Asking them to fill out a detailed catalog entry could make the first step feel like homework.

My instinct is to start with a photo, let them save a basic record, and introduce more detail as they learn. But simplifying too much could also make the app less useful as their collection grows.

For makers building tools for specialized hobbies:

When you re building a startup, nothing is ever enough.

More users, a new feature, a bug. MRR, churn. It's hustling all the time. and pretty uncomfortable sometimes.

I tend to forget the day to day, and just think about tomorrow.