frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

TOSTracker – The AI Training Asymmetry

https://tostracker.app/analysis/ai-training
1•tldrthelaw•25s ago•0 comments

The Devil Inside GitHub

https://blog.melashri.net/micro/github-devil/
1•elashri•46s ago•0 comments

Show HN: Distill – Migrate LLM agents from expensive to cheap models

https://github.com/ricardomoratomateos/distill
1•ricardomorato•47s ago•0 comments

Show HN: Sigma Runtime – Maintaining 100% Fact Integrity over 120 LLM Cycles

https://github.com/sigmastratum/documentation/tree/main/sigma-runtime/SR-053
1•teugent•1m ago•0 comments

Make a local open-source AI chatbot with access to Fedora documentation

https://fedoramagazine.org/how-to-make-a-local-open-source-ai-chatbot-who-has-access-to-fedora-do...
1•jadedtuna•2m ago•0 comments

Introduce the Vouch/Denouncement Contribution Model by Mitchellh

https://github.com/ghostty-org/ghostty/pull/10559
1•samtrack2019•3m ago•0 comments

Software Factories and the Agentic Moment

https://factory.strongdm.ai/
1•mellosouls•3m ago•1 comments

The Neuroscience Behind Nutrition for Developers and Founders

https://comuniq.xyz/post?t=797
1•01-_-•3m ago•0 comments

Bang bang he murdered math {the musical } (2024)

https://taylor.town/bang-bang
1•surprisetalk•3m ago•0 comments

A Night Without the Nerds – Claude Opus 4.6, Field-Tested

https://konfuzio.com/en/a-night-without-the-nerds-claude-opus-4-6-in-the-field-test/
1•konfuzio•5m ago•0 comments

Could ionospheric disturbances influence earthquakes?

https://www.kyoto-u.ac.jp/en/research-news/2026-02-06-0
1•geox•7m ago•0 comments

SpaceX's next astronaut launch for NASA is officially on for Feb. 11 as FAA clea

https://www.space.com/space-exploration/launches-spacecraft/spacexs-next-astronaut-launch-for-nas...
1•bookmtn•8m ago•0 comments

Show HN: One-click AI employee with its own cloud desktop

https://cloudbot-ai.com
1•fainir•10m ago•0 comments

Show HN: Poddley – Search podcasts by who's speaking

https://poddley.com
1•onesandofgrain•11m ago•0 comments

Same Surface, Different Weight

https://www.robpanico.com/articles/display/?entry_short=same-surface-different-weight
1•retrocog•14m ago•0 comments

The Rise of Spec Driven Development

https://www.dbreunig.com/2026/02/06/the-rise-of-spec-driven-development.html
2•Brajeshwar•18m ago•0 comments

The first good Raspberry Pi Laptop

https://www.jeffgeerling.com/blog/2026/the-first-good-raspberry-pi-laptop/
3•Brajeshwar•18m ago•0 comments

Seas to Rise Around the World – But Not in Greenland

https://e360.yale.edu/digest/greenland-sea-levels-fall
2•Brajeshwar•18m ago•0 comments

Will Future Generations Think We're Gross?

https://chillphysicsenjoyer.substack.com/p/will-future-generations-think-were
1•crescit_eundo•21m ago•0 comments

State Department will delete Xitter posts from before Trump returned to office

https://www.npr.org/2026/02/07/nx-s1-5704785/state-department-trump-posts-x
2•righthand•24m ago•1 comments

Show HN: Verifiable server roundtrip demo for a decision interruption system

https://github.com/veeduzyl-hue/decision-assistant-roundtrip-demo
1•veeduzyl•25m ago•0 comments

Impl Rust – Avro IDL Tool in Rust via Antlr

https://www.youtube.com/watch?v=vmKvw73V394
1•todsacerdoti•25m ago•0 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
3•vinhnx•26m ago•0 comments

minikeyvalue

https://github.com/commaai/minikeyvalue/tree/prod
3•tosh•31m ago•0 comments

Neomacs: GPU-accelerated Emacs with inline video, WebKit, and terminal via wgpu

https://github.com/eval-exec/neomacs
1•evalexec•36m ago•0 comments

Show HN: Moli P2P – An ephemeral, serverless image gallery (Rust and WebRTC)

https://moli-green.is/
2•ShinyaKoyano•40m ago•1 comments

How I grow my X presence?

https://www.reddit.com/r/GrowthHacking/s/UEc8pAl61b
2•m00dy•41m ago•0 comments

What's the cost of the most expensive Super Bowl ad slot?

https://ballparkguess.com/?id=5b98b1d3-5887-47b9-8a92-43be2ced674b
1•bkls•42m ago•0 comments

What if you just did a startup instead?

https://alexaraki.substack.com/p/what-if-you-just-did-a-startup
5•okaywriting•49m ago•0 comments

Hacking up your own shell completion (2020)

https://www.feltrac.co/environment/2020/01/18/build-your-own-shell-completion.html
2•todsacerdoti•52m ago•0 comments
Open in hackernews

10 Years, 10 Pricing Mistakes: What We Learned Building a SaaS Without VC Money

7•evermike•4mo ago
Back in 2015 we launched our first SaaS with no VC and little experience. Most pricing choices came from gut feeling or advice we shouldn’t have taken. Looking back, what feels obvious today wasn’t obvious back then. We learned the hard way.

Tiered pricing.

On paper it looked fair. A team with 15 users paid $39 but adding one more jumped it to $119. Inside a tier customers were happy as cost per user dropped. But crossing a tier made them furious. People churned, demanded discounts or sent angry emails. Instead of rewarding growth the model punished it.

Per-user billing.

Finally revenue scaled with customers. But it attracted many solo users and tiny teams. Because Everhour syncs with project tools, even one freelancer could flood the system with hundreds of projects and tasks. They paid almost nothing but created huge load and were the loudest group: angry tweets, refund requests, endless tickets. Larger teams were calmer and more loyal.

To fix this we set a 5-seat minimum.

You could use fewer but still pay for 5. It filtered out freelancers, raised our average check and aligned us with the right customers. Some complained it was too expensive but those who valued the product stayed. Later we added a free plan for up to 5 users without integrations. This gave small teams a way to stick around and got us listed in “Top Free Tools” blogs. It worked more as marketing than monetization.

Flat-fee pricing in our Trello add-on.

$10/month, unlimited users and projects. Out of 30,000+ active users only ~500 paid. Everyone else left the moment we asked for money. The product was too simple for upsells.

Grandfathering.

If someone signed up on old plan they could keep it forever. No forced upgrades, no surprise hikes. Many are still paying today. We tried nudging them to newer plans with extra features and loyalty discounts, but only a small percentage switched. If their plan worked fine, the barrier to paying more was too strong.

Discounts.

Volume disc for large clients worked well and helped close deals. Urgency promos like “Sign up in 5 days and get 20% off” gave a small conv boost and improved retention. Those customers stayed longer because they didn’t want to lose their deal. But it felt unfair to existing users. Some even tried canceling and resubscribing. We eventually stopped.

Billing mechanics lesson.

First we billed per user and deferred prorates to next cycle. Logical in theory, messy in practice. Customers canceled before renewal and we lost money, especially on annuals. Others didn't recognize totals on bank statements. We tried charging prorates immediately when someone was added. That fixed revenue issues but created too many micro payments and invoices. Customers hated multiple charges when swapping users.

Eventually moved to per-seat billing.

Buy seats in advance, use them flexibly and the invoice stays clear. Still not perfect. Some forget to remove empty seats and complain later. But overall it’s far cleaner. Today it’s basically the SaaS standard.

Lessons.

- Tiered pricing looks fair until you cross tiers. Then it makes customers angry. - Solo users overloaded our system while bringing little revenue. - “Micro” plans added support costs without conversions. - Flat-fee pricing attracted 30k+ users but barely any paid. - No minimum seats meant tiny checks and the wrong audience. - Multiple plans added complexity. Most picked the same one anyway. - Upselling grandfathered users failed. If old plans worked, they wouldn’t pay more. - Discount promos helped short term but felt unfair and were abused. - Per-user prorates turned invoicing into a mess and cost us money. - Free plans drove marketing visibility, not upgrades.

This is near the 4,000 char limit here. More details and screenshots: https://medium.com/@citizenblr/lessons-from-10-years-of-saas-pricing-experiments-4ed45f552171

Comments

evermike•4mo ago
What we didn’t try

For example, charging based on customer revenue (like ChartMogul). It doesn’t really fit our case, but I just don’t like this model overall.

We also avoided usage-based pricing tied to API calls or account activity.

We never tried monetizing through ads or selling anonymized data — and we never plan to.

And unlike many SaaS companies, we never forced existing customers to accept price increases. I know some businesses calculate churn vs. uplift and decide it’s worth it. We’ve stayed away from that path.