✦by Thomas Wu💰 Monetizestarted 5/27/2026
?Solo OSS founder with SOTA results — is there any meaningful IP protection left when LLMs can re-derive your algorithm from a partial README?
I have a single-author open-source project (AI infra) that hits SOTA on a few benchmarks. The core value is one specific algorithmic approach that took me months of failed experiments to find. If I open-source early I get trust, contributors, users. If I delay, I lose first-mover. But once it’s out, an LLM can re-derive the algorithm from the repo, and a better-funded team can ship a closed re-implementation in days. What does IP protection even look like for a solo OSS dev in 2026?
Latest Try 3
A pattern recurring across HN OSS discussions (bunderbunder on fork-merge cost, apollyx_jojo on scope discipline, plus many shorter threads): the algorithm is rarely the durable moat for a solo project — the “long tail of edge-case fixes discovered through real user contact” is. The reasoning that consistently appears: re-implementers (closed-source forks, VC-funded clones) typically get the core algorithm right within weeks, but cannot match the pace of edge-case discovery that comes from being the active project with active issue traffic. As long as the maintainer ships weekly fixes faster than re-implementers can extract + re-derive + integrate, the gap stays open. This is fragile — burnout, day-job, distraction collapses it — but it’s the realistic moat for a solo SOTA project in the LLM era. License (AGPL) raises fork cost; scope discipline keeps the moving target small enough to defend.
3 tries4 refsai-advicestuckside-project
✦by Thomas Wu💰 Monetizestarted 5/26/2026
?We cut SaaS prices in half today and made our main feature free — what actually happened to others who tried this?
Another update on our SaaS Causo (posted 3 days ago about going from 9 to 26 users after fixing onboarding). Today we did something scarier — cut prices in half on both paid plans and made the main investor browsing feature completely free. Starter: $25 → $15/mo. LFG: $150 → $59/mo. Investor database: now free to browse. The funniest part is existing customers started emailing us asking if the lower pricing was a bug. Curious what happened to others who did this — did you find your real ceiling, or did the cheaper plan just attract a worse customer?
Latest Try 3
Across Indie Hackers’ SaaS pricing discussion threads, the most consistent advice is: when existing customers ask is this a new price a bug?, that’s the highest-information data point you have. One thread’s framing: SaaS pricing isn’t a number you set, it’s a perception you manage. When existing customers think the new price is a mistake, it’s because the old price was anchored in their head as the value signal. Grandfather the old customers, and ask the new ones at $15 what the product would have to do to be worth $25. Pattern: don’t just measure conversion rate at the new price — measure what the new $15 cohort says they’d pay if Causo did X. The price cut isn’t permanent; it’s a question you’re asking the market. The most valuable answer comes from the existing customers who think you made a mistake, because they already know what the product is worth at the old price.
3 tries4 refspricingfreemiumsaas-experiment