Reddit Signals

The honest part was this: "I want to actually understand how things work and be able to build something myself." That's the line most learning paths skip. The default advice is "take Andrew Ng's course" or "read Attention Is All You Need" and then people stall because they're consuming, not building.

What separates PMs who can actually ship AI features from PMs who can talk about them is a small, ugly first build. Not a polished demo. Just a notebook where you fine-tune a small model on your own data, or wire up an API and watch where it breaks on edge cases. The reading comes after the building, because the reading answers questions you only know to ask once you've tried.

The roadmap looks like this: one weekend with a basic tutorial, one weekend applying it to something in your own product, then read papers and docs with a real problem in your head. The order matters. Build first, study second.

AI literacy is a craft skill. Crafts are learned by doing. Source: r/ProductManagement, "PMs who are good at AI: how did you learn it?" (https://www.reddit.com/r/ProductManagement/comments/1vk2vjv/pms_who_are_good_at_ai_how_did_you_learn_it/)

He wrote: "We launched the product on product hunt ranked 6th and also spent a lot of time on all socials to push our product organically. All of this created a lot of buzz and we started getting signups."

The buzz worked. Signups came. What didn't work was the second step, turning those signups into paying customers who stayed. He and his CTO split the work cleanly. He handled product and growth, his cofounder handled the tech. So nobody was watching retention, cohort behavior, or pricing fit. Buzz became the metric. Buzz was free.

This is the trap that experienced PMs fall into more than juniors, because the craft they trust is launch mechanics. They know how to generate attention. What gets rusty is the part after: who actually used the product, who churned on day three, and why. Launch skills compound for a year. Retention skills compound for ten.

The second-order effect is that "good launch, bad business" is the most common failure mode for solo founders with corporate backgrounds. Forcing yourself to look at weekly retention before you celebrate signups is the cheapest way to avoid it. Source: r/ProductManagement, "12+ years as a PM. Then I built my own product failed for 1.5 years..." (https://www.reddit.com/r/ProductManagement/comments/1vlf5io/12_years_as_a_pm_then_i_built_my_own_product)

The headline number is good: PM jobs worldwide up 2.3% in July and 2.3% again in August, with 25,905 open listings. Volume is up 19% year over year.

The so-what hiding underneath is uglier. Total volume sits 0.2% below the six-month average. So we're growing on a tough comparison and stalling on the long-term trend. Regional patterns diverge hard. Growth markets are pulling volume up. Mature markets are flat or shrinking.

The second-order effect for working PMs: the market is splitting in two. Junior and mid PM roles are getting squeezed because companies are asking senior PMs to do more, or hiring "PM + builder" hybrids who can ship AI features themselves. The bar at the top is rising. The floor at the bottom is rising too. The middle is where it's crowded.

For a mid-career PM, what matters is where in this split you sit and whether you're moving up or staying still while the gap widens out. Headline growth can hide a stalled career if the bar in your tier has moved. Source: r/ProductManagement, "Product Management Jobs Report for August 2026" (https://www.reddit.com/r/ProductManagement/comments/1vlnbct/product_management_jobs_report_for_august_2026)

His list was Pricing, Positioning, Roadmap framing, Stakeholder management, and saying no without losing trust. Pricing leads, and he called it "dark arts" even after two decades in product.

The thing worth sitting with is why pricing stays hard while other PM skills got easier. It's because pricing is the one decision where the PM's judgment has no external benchmark. You can A/B test copy. You can run a feature study. You can look at competitor roadmaps. But the price you charge is a bet about how customers value something, and that bet is rarely falsifiable until months after you ship it.

The second-order effect: pricing is where PMs quietly ship by committee. Engineering weighs in. Sales weighs in. Finance weighs in. By the time the price is set, nobody owns the call. A PM who actually owns pricing, runs the tests, and updates quarterly is rare enough to be a competitive advantage at most companies.

When a senior PM says pricing still scares them after 20 years, the pattern DeanOnDelivery names is the honest one: pricing has no feedback loop fast enough to be self-correcting. Source: r/ProductManagement, "Which of these 5 PM topics make you sweat a bit?" (https://www.reddit.com/r/ProductManagement/comments/1vjq8i4/which_of_these_5_pm_topics_make_you_sweat_a_bit)

The PM wrote: "Our CEO is nervous about our status page being public and used against us by our larger competitors (none of whom seem to have a status page)."

The instinct to hide reliability data survives in leadership rooms mostly because nobody in the room has ever been the customer of a company that hid a status page. They have, however, been the customer of a company that had one and lost their data during an outage with no warning.

The so-what: public status pages aren't a competitive liability. They're a trust asset. Competitors reading your uptime history is a far smaller cost than customers discovering your hidden downtime through angry tweets and lost contracts.

The second-order effect is more interesting. Companies without status pages tend to have worse reliability, not better. The act of publishing uptime forces internal accountability. Once it's public, somebody has to own the SLO, the post-mortem, and the comms. That ownership almost always improves the system.

When leadership says "competitors will see we're down," the answer that holds up under audit is that customers will too. Source: r/ProductManagement, "Is your service status page public?" (https://www.reddit.com/r/ProductManagement/comments/1vkcx7b/is_your_service_status_page_public)

He wrote: "The idea was theirs, the code is mine. Partnership fell through. I offered them a cheap non-exclusive license so they could keep using it. They refused."

This is a real problem. The standard advice is "get a contract first," but that's a lawyer's answer to an emotional problem. He trusted a handshake because the relationship felt real. That's how indie devs get burned.

The so-what: in any unpaid or underpaid collaboration with a company, the leverage is in the artifact, not the relationship. The dev had leverage because he owned the repo. He gave that leverage away by building without a written scope. By the time he asked for payment, the company had a working product. The negotiation had flipped.

The second-order effect is for buyers, not builders. The cheapest move for a startup is to refuse a license. The most expensive is to ship someone's code without a license and then hire lawyers. Most IP disputes end with the startup paying more than they would have originally.

Contracts exist because trust isn't enough. The pattern is the same every time. Source: r/SaaS, "Company copied my code after refusing to pay for a license..." (https://old.reddit.com/r/SaaS/comments/1vltxz0/company_copied_my_code_after_refusing_to_pay_for)

He wrote: "Officially sold my B2B SaaS after 8 years of grinding. Got up to 175k MRR and was only spending 20% of my time on it in its final year."

175k MRR maintained by 20% of one person's time is the actual unicorn, even if the valuation wasn't. Most founders chase revenue growth and end up with a business that requires 100% of their time. This founder did the opposite. He built a product that ran itself and sold when it plateaued.

"Lifestyle MRR" is the underrated exit metric. A 175k MRR business you run 20% of the time is worth more to most buyers than a 500k MRR business you run 80%. The buyer gets cleaner financials and less key-person risk.

The second-order effect: this exit wasn't about the sale price. It was about optionality. Eight years of compounding choices got him to a point where selling was a choice, not a necessity. He could have run it forever. He didn't want to.

SaaS founders who exit too early, when the business still needs them, walk away with whatever someone offers. Building something that's already running without you is what turns the exit into a clean transaction. Source: r/SaaS, "Sold! 8 year grind..." (https://old.reddit.com/r/SaaS/comments/1vinckb/sold_8_year_grind)

They wrote: "The first sentence says what the product actually does, in plain English. No 'unleash the power of your workflow.' I can try it without creating an account."

That's the trust test. Plain language on the first line. No signup before you can see the product. The rest of the list (real screenshots, real customer quotes, pricing visible) was downstream of those two.

The so-what for PMs is uncomfortable. Most landing pages are written for buyers who already want to buy. They're not written for the 95% of visitors who arrived skeptical. The skeptical visitor wants proof in the first 10 seconds, not a pitch. A signup gate before the demo is the same as a bouncer at the door. It filters for people with high intent and filters out everyone who's curious.

The second-order effect: companies that gate the demo are paying acquisition cost for the wrong cohort. They get signups from people who already decided, who then trial with confirmation bias, who then churn at high rates because the product never had a chance to convert a skeptic.

Public demos are the feature that affects every other metric in the funnel. Everything else compounds from there. Source: r/SaaS, "What's the biggest green flag when you land on a startup website?" (https://old.reddit.com/r/SaaS/comments/1vgg90q/whats_the_biggest_green_flag_when_you_land_on_a)

He wrote: "I remember when I got my first Stripe payment, it was 47 euros. I feels unreal. Then I didn't sell for months. Before that I've build for 3 years. Yeah it was before chatgpt. Got into depression after this one sales. I just sold to 1 company then nothing."

Three years of building, one sale, depression, then 550 euros in a week. That's the actual arc of most indie SaaS founders. The "3 years to first dollar" phase is the median, not worst case.

The so-what is that almost every successful indie founder has a version of this story. They built for years with nothing. They almost quit. They didn't. Then something clicked, often suddenly, often not for any reason they can fully explain. The pattern is so common it should be the default expectation, not the worst case.

The second-order effect: founders who quit at month 30 lose. Founders who don't quite hit month 36 sometimes win. The difference is rarely product quality or marketing skill. It's the willingness to keep building through the silence. That's not a virtue. It's just the math.

A founder at month 24 feeling like quitting has a different read on the data than they think. Month 36 is when it starts to matter. Source: r/SaaS, "Almost quit my SaaS after 3 years without sales..." (https://old.reddit.com/r/SaaS/comments/1vlcjzw/almost_quit_my_saas_after_3_years_without_sales)

The post says: "I don't usually post personal things online, especially not like this. If you can't help directly, maybe an upvote, a share, or pointing me toward someone who might be hiring could help."

The post is a person, not a SaaS insight. The standard advice in the comments ("network harder," "reach out to recruiters," "spray and pray") is what everyone has already tried by the time they're posting in desperation.

The so-what is that hiring is broken for mid-career PMs and engineers right now. The companies that laid people off aren't rehiring at the rate they used to. The roles that exist require AI skills that weren't in the previous job description.

The second-order effect is for hiring managers reading this. The cheapest hire you'll make this year is the person who got laid off six months ago and has been ignored. They're available, motivated, and have reset their comp expectations.

Seeing one of these posts and sending an interview slot costs less than a recruiter. Source: r/SaaS, "I never thought I'd be the one making a post like this..." (https://old.reddit.com/r/SaaS/comments/1vhbgsg/i_never_thought_id_be_the_one_making_a_post_like)

The pattern he described: "Im sure im not the only one to notice these same posts being recycled over and over again. Its always meant to seem like the op is some startup founder who found the perfect marketing method."

This is the spam playbook disguised as authenticity. The post looks like a founder's lucky break. It ends with a quiet plug for a content-clipping service. Same sites, same scripts, same tone. The repetition is the tell.

The so-what for real founders is that the noise floor on indie SaaS communities is rising. When most "I grew to 10k MRR" threads are actually funnels, real builders stop posting. The signal-to-noise ratio drops.

The second-order effect is that the founders doing the spamming are trading long-term credibility for short-term affiliate revenue. Real founders who actually grew to 3k MRR have a harder time telling their story because the format has been poisoned.

When you see an "I accidentally did X" post, the format itself is the tell. Source: r/SaaS, "'I accidentally grew my app to 3k mrr' No you didnt" (https://old.reddit.com/r/SaaS/comments/1vjmkxd/i_accidentally_grew_my_app_to_3k_mrr_no_you_didnt)

He wrote: "Posting on Reddit has not only been good for SEO (I get some traffic from llms because of it), but it also got me my first few customers."

The interesting part is the SEO loop. Reddit content ranks in Google, and now LLMs cite Reddit posts as sources. So posting genuinely helpful answers in niche subreddits becomes a long-tail acquisition channel for months. The PM got traffic from ChatGPT citing his old Reddit answers about his problem space.

The so-what is that distribution and discovery are merging. A Reddit post becomes a permanent artifact that gets indexed by Google and surfaced by LLMs as a citation. The compounding effect is real. A founder who posts 30 thoughtful answers in their niche is building an acquisition channel that runs forever with no marginal cost.

The second-order effect: most founders ignore Reddit because it doesn't feel like marketing. It feels like answering questions. The founders who treat it like content get ignored. The founders who treat it like helping get customers.

The founders who show up consistently for a year compound something the ads-bought founders can't replicate. Source: r/SaaS, "I launched my SaaS about two months ago..." (https://old.reddit.com/r/SaaS/comments/1vgs2bu/i_launched_my_saas_about_two_months_ago_to)

His Lesson 1 was: "Solve a problem you actually understand. I built a tool for real estate agents. I was not a real estate agent."

This is the most common first-SaaS failure. First-time founders pick markets they don't live in because they sound big. Real estate agents. Restaurant owners. Gyms. The founder's understanding of the workflow is shallow. The product misses the job-to-be-done and ships to crickets.

The so-what is that domain knowledge beats market size in the early days. A real estate agent building software for other agents will out-execute a Stanford MBA building the same product with 10x more funding, because the agent knows what the workflow requires.

The second-order effect: this is why "scratch your own itch" advice is so durable. It's the cheapest possible way to acquire the domain knowledge you need to ship a product that real customers will pay for. Interviews and market reports are slower and less reliable than being the user.

The founders who learn this on their second SaaS almost always pick a market they actually live in. The ones who don't usually don't get a second SaaS. Source: r/SaaS, "I wasted months building a SaaS that failed. Here's what I'd do differently..." (https://old.reddit.com/r/SaaS/comments/1vhuunh/i_wasted_months_building_a_saas_that_failed_heres)

He wrote: "Most companies play on the fear driven marketing 'AI will replace you.' It's a tale as old as time. Also pitch decks right now are some version of 'replace your [.insert job]' but most of those products are dying."

After 20+ AI product launches, his pattern is the opposite of the headline. The "replace your job" pitches are dying. The "make your job 10x faster" pitches are selling.

The so-what is that the AI replacement narrative was always a marketing shortcut. It got investors excited. It does not get customers to pay. Buyers want leverage on their existing work, not a wholesale replacement that requires them to redesign their workflows.

The second-order effect is for the next wave of AI startups. Founders who position as a copilot for an existing workflow will compound customer trust. Founders who position as a replacement will plateau at early adopters, because mainstream buyers don't want to be the pilot case.

u/AIBuilder20's pattern across 20+ launches is that durable revenue sits in products that make existing workflows faster, not products that promise to swap them out. Source: r/SaaS, "Everyone's building AI to replace people. The money is in the opposite" (https://old.reddit.com/r/SaaS/comments/1vg9kbt/everyones_building_ai_to_replace_people_the_money)

He wrote: "I have written about 50 full-featured websites... And none of that is the reason that the two sites that worked made it. One of my sites, I just bought a domain name that was exactly what people were already searching for."

The insight is brutal. Effort didn't predict success. Domain luck did. He bought a domain that exactly matched what thousands of people were already typing into Google, and SEO did the work. The other 48 sites, built with insane effort, didn't have that alignment with existing demand.

The so-what for indie founders is that distribution is upstream of product quality for solo operators. A mediocre product with a domain that matches existing search demand will outcompete a brilliant product that has to build awareness from zero. The math is unforgiving.

The second-order effect: the same lesson applies to indie SaaS. Founders who pick names that customers are already searching for compound faster than founders who pick clever names and try to create categories. Matching existing demand is the cheapest SEO.

The product that aligns with existing demand wins with a fraction of the effort. Source: r/SaaS, "My second site hit 10k mrr, here's how" (https://old.reddit.com/r/SaaS/comments/1vhv3kj/my_second_site_hit_10k_mrr_heres_how)

He wrote: "Hey Saas. Been running a small AI software dev house out of London for the last 2 years. 6 people now and growing. Took the company from 0 to 6 figures and I want to do it again hopefully. I want to show this is possible to generate 150,000 in 15 days."

This is the format of a public build log. He's betting that documenting in public, whether it works or fails, will be more valuable than the 150k itself. The audience for a 15-day sprint is bigger than for a generic growth post.

Public execution has become the most leveraged founder activity. A 15-day build log on Reddit or LinkedIn compounds attention, distribution, and inbound leads. The founder gets leads, audience, and portfolio piece from one activity.

Second-order effect: founders who document in public are paid twice. Once in customers who find them. Once in opportunities from the audience. The 150k is the bait. The outcome is the audience. Source: r/SaaS, "Day 1/15 of Getting to $150,000 - Doing it again (almost)" (https://old.reddit.com/r/SaaS/comments/1vkln4k/day_115_of_getting_to_150000_doing_it_again_almost)

The first rule, surprising to most people. Use personal or creator account types, not business. If you go with business you cannot use most of the popular sounds, just some random commercial boring ones. Then a warning on buying accounts. Do not buy one unless you plan on running it from the same location and VPN, or you will get zero views very shortly.

The shadowban section is blunt. A creator who gets 30 to 200 views assumes they are shadowbanned. The post is clear. If you were actually shadowbanned, you would see zero views. 90 percent of the time, your content is not that great. The other 10 percent of the time, you are early. TikTok needs a few dozen posts before it can place you. The algorithm punishes inconsistency, not bad luck.

The general lesson for SaaS founders is that TikTok is a different craft than the rest of growth. It rewards personal-account volume, punishes one-off campaigns, and asks for the boring consistency that paid ads skip past. Most of the founders who fail at it are failing at the consistency, not the algorithm.

Source: Reddit, "SaaS thread, Read this before starting to advertise your SaaS on TikTok" (https://www.reddit.com/r/SaaS/comments/1vfb8li/read_this_before_starting_to_advertise_your_saas/)

The data, 30 days. Google: 150 clicks, 4.9K impressions, 3 percent CTR, average position 24. Bing: 5,000 clicks, 32.4K impressions, 15 percent CTR, average position 4. Same pages, same keywords. Bing sent 33 times more traffic.

The reason /u/ThaneBerkeley proposes is the niche. The product is an NSFW AI companion platform. Google's index is hostile to that category. No manual penalty in Search Console, no warning, just position 24 forever. Bing's index treats it normally. The best keyword ranks 1.4 on Bing with a 27 percent CTR, and on Google it might as well not exist.

The second-order point is the part most founders miss. Bing is bigger than people think. DuckDuckGo, Yahoo, and Ecosia all run on it, plus a bunch of AI chatbots pull from its index. Everyone is grinding for Google scraps while this whole channel sits there. /u/ThaneBerkeley is not dropping Google, but if you are in a category Google quietly de-prioritizes, ten minutes in Bing Webmaster Tools can be your biggest organic channel. The traffic is real and the downstream engines are bigger than they look.

Source: Reddit, "SaaS thread, Bing sends me 33x more traffic than Google. Never saw that coming" (https://www.reddit.com/r/SaaS/comments/1vfarpg/bing_sends_me_33x_more_traffic_than_google_never/)

The argument in one line. Polish used to arrive last. You earned the nice interface after surviving the edge cases, and half-built software looked half-built. The ugliness was information. It told you, roughly, how much work was left. Now the finished shell turns up on day one, so the missing parts stop announcing themselves.

The founder describes a moment in June. A client had vibe-coded a booking product over a few weekends. It looked polished. Around eighty paying customers. Then a customer asked what happens to the unused part of a plan when you cancel mid-month. The founder opened his own product and clicked around to find out. He was not embarrassed. He did not know, and did not see that as a problem.

The post calls this the missing signal. A beautiful screen cannot tell you that payment failures were never handled. The fix is a process, not a feature. Audit the edge cases before the polish arrives, because the polish will hide them otherwise. Most vibe-coded failures are not bugs. They are product decisions the founder never knew they were making.

Source: Reddit, "SaaS thread, The biggest problem with vibe coding isn't security" (https://www.reddit.com/r/SaaS/comments/1vdi46f/the_biggest_problem_with_vibe_coding_isnt_security/)

The setup. Their company has no real home page, just a giant page that dumps every product and service on whoever lands. /u/tallkidinashortworld pitched a true home page to the C-suite. The first strategy was the standard one. Numbers, best practices, click depth, OKR alignment, and a clear line from current revenue decline to the missing home page. They ran into a brick wall of resistance. The room kept repeating that the current page works and change would be risk.

The reframe that worked. Stop arguing about whether a home page is the right answer. Start by naming the belief the executives are defending. The post's read is that the resistance is not about data. It is about taste, ownership, and the implicit promise that the current setup is good enough. A pitch that respects the executive's mental model of why the current site is fine lands differently than one that tries to disprove it. /u/tallkidinashortworld's second pass did not open with more numbers. It opened with the risk the C-suite already worried about, then showed how a home page reduced that risk.

The lesson for PMs is that the second pass at influence almost never needs more evidence. It needs a different first line.

Source: Reddit, "ProductManagement thread, How to Pursuade when Running into a Wall" (https://www.reddit.com/r/ProductManagement/comments/1vdoajs/how_to_pursuade_when_running_into_a_wall/)

The pattern /u/Aloofempire describes will sound familiar to most PMs. The CEO asks why this feature, what problem we are solving, what is the evidence, why now, what are the trade-offs, how do we measure success. /u/Aloofempire has the context and the numbers. Under pressure, the structure collapses. The recommendation arrives as a string of facts without a defensible through-line. The CEO spots the gap fast.

The trap is to think the answer is more frameworks. Frameworks are free. The real work is taking a fuzzy topic, picking one framing, and writing a one-paragraph case before the meeting. /u/Aloofempire's instinct to write the recommendation down before the meeting is the right move. The hard part is cutting. The CEO is not asking for more evidence. He is asking for a bet. /u/Aloofempire already knows the context. The gap is in the moment of committing to a single recommendation, not in the data underneath.

Most new PMs in this position are one or two practice reps away from passing the bar. The mistake is treating every CEO question as a question about facts, when it is a question about which fact the PM is willing to bet on.

Source: Reddit, "ProductManagement thread, New PM struggling with structured product thinking how do I get better?" (https://www.reddit.com/r/ProductManagement/comments/1vhslhl/new_pm_struggling_with_structured_product/)