<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: evermike</title><link>https://news.ycombinator.com/user?id=evermike</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 03 May 2026 23:17:11 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=evermike" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Do Discounts Help Your Startup Grow?]]></title><description><![CDATA[
<p>I’ve always believed discounts should help you earn more, not less. So giving them out “just because someone asked” never felt right.<p>Volume discounts for big clients worked fine and helped us close deals.<p>Annual discounts are also a good win-win, but to convert well the difference has to be significant. At 30% off signups spiked. At 15% the effect was much smaller.<p>Urgency campaigns surprised us. For a few months, every last week we ran “Sign up in the next 5 days and get 25% off.” Conversions went up on those days, but the real win was retention. These customers stayed longer because they didn’t want to lose their deal.<p>Still, we never made it a regular thing. It feels unfair to existing customers who paid full price. And if you repeat it too often, people just wait for discounts. That only cuts your revenue.<p>We never tried lifetime deals. For B2B, in my opinion, it doesn’t really fit. Small clients don’t want to pay a big sum upfront and large ones make it unprofitable. Honestly, it can even cheapen your product in their eyes. Maybe you have a different opinion.<p>We also tested “cancel discounts,” showing an offer when someone clicked “cancel subscription.” Some stayed, but fewer than we expected. Plenty of people already know the trick, so they unsubscribe on purpose to see if a deal pops up.<p>Curious to hear your take. What discount strategies have you tried in your product? What worked, what didn’t and what have you decided to avoid completely?</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45372226">https://news.ycombinator.com/item?id=45372226</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 25 Sep 2025 13:05:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=45372226</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45372226</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45372226</guid></item><item><title><![CDATA[New comment by evermike in "I'm gonna write 1 email every day for 365 days to teach myself discipline"]]></title><description><![CDATA[
<p>I think it would be useful if at least the first email could be read without a subscription. Just to understand the content, tone of voice, and so on. I believe the conversion rate would be higher after that first read.</p>
]]></description><pubDate>Fri, 19 Sep 2025 06:08:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=45298429</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45298429</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45298429</guid></item><item><title><![CDATA[New comment by evermike in "10 Years, 10 Pricing Mistakes: What We Learned Building a SaaS Without VC Money"]]></title><description><![CDATA[
<p>What we didn’t try<p>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.<p>We also avoided usage-based pricing tied to API calls or account activity.<p>We never tried monetizing through ads or selling anonymized data — and we never plan to.<p>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.</p>
]]></description><pubDate>Fri, 19 Sep 2025 06:02:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=45298400</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45298400</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45298400</guid></item><item><title><![CDATA[10 Years, 10 Pricing Mistakes: What We Learned Building a SaaS Without VC Money]]></title><description><![CDATA[
<p>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.<p>Tiered pricing.<p>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.<p>Per-user billing.<p>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.<p>To fix this we set a 5-seat minimum.<p>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.<p>Flat-fee pricing in our Trello add-on.<p>$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.<p>Grandfathering.<p>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.<p>Discounts.<p>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.<p>Billing mechanics lesson.<p>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.<p>Eventually moved to per-seat billing.<p>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.<p>Lessons.<p>- 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.<p>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</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45298374">https://news.ycombinator.com/item?id=45298374</a></p>
<p>Points: 7</p>
<p># Comments: 1</p>
]]></description><pubDate>Fri, 19 Sep 2025 05:56:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=45298374</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45298374</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45298374</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>No, as far as I know. But as a merchant, in theory you can block that customer from making future payments. But probably only their specific card or email.</p>
]]></description><pubDate>Tue, 16 Sep 2025 05:31:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=45258375</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45258375</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45258375</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>I’d say if a chargeback does happen, the chances of winning =0, unless you can convince the customer to withdraw it. I realized this especially after my last dispute, where I was 100% sure I would win. But that’s it. I have no faith in the process anymore. What’s left is just the internal struggle, I always want to respond to something unfair and try to prove my case. But here it’s not worth doing.</p>
]]></description><pubDate>Mon, 15 Sep 2025 17:44:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=45252700</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45252700</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45252700</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Of course we would never do anything like that. In the post I just shared two different cases to give some perspective to the community.<p>From everything discussed in the article, there are a 2 major takeaways:<p>1) You need to avoid chargebacks as much as possible.<p>2) If a chargeback does happen, the chances of winning are basically zero — unless you can convince the customer to withdraw it.</p>
]]></description><pubDate>Mon, 15 Sep 2025 17:28:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=45252505</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45252505</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45252505</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Yeah, we have that</p>
]]></description><pubDate>Mon, 15 Sep 2025 17:06:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=45252234</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45252234</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45252234</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Thanks for sharing. Appreciate.</p>
]]></description><pubDate>Mon, 15 Sep 2025 13:06:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=45249213</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45249213</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45249213</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Sure, and that’s the right approach. We also issue refunds, but for that, the customer needs to write to us and ask.</p>
]]></description><pubDate>Mon, 15 Sep 2025 13:04:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=45249192</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45249192</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45249192</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Sorry, I probably misunderstood and confused things. I was of course talking about the Apple App Store, when users file complaints about the app itself.</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:53:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=45249068</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45249068</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45249068</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Well, I treat other companies and people the way I’d like to be treated myself. Knowing that a chargeback is unpleasant and creates extra costs, I always first write to their support.</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:51:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=45249047</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45249047</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45249047</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>I appreciate your attention. Let me explain.<p>In the post I mentioned that we build several products. I didn’t want to list them all, because I always feel a bit awkward about self-promotion. My goal with the post was to spark a dialogue, not to advertise.<p>RE pricing page: yes, we do state that there’s a minimum of 5 seats. But there are no chargebacks here, since we don’t take a card upfront and we don’t bill in a hidden way. In the worst case, if you missed or didn’t read that detail, you can simply decline and not subscribe after the trial. You’ll see the price in Stripe before giving us your card. And if you prefer, you can stay on the free plan for up to 5 ppl.</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:46:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=45249006</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45249006</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45249006</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>As I mentioned in the article, this is extremely rare for us, but it has happened a couple of times. And that’s where I start having questions and frustration about the process itself.<p>I’ve shared examples in the article.</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:36:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=45248922</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45248922</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45248922</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Email about an upcoming charge is automatically sent a couple of days in advance, that’s Stripe standard feature. The other question is whether the user actually check their email (or which email they registered with).<p>As for cancellation, the problem is that even though it’s easy to cancel a subscription, chargebacks usually happen afterwards. It doesn’t matter how simple cancellation is, what matters is that the user first cancel and then still goes and files a chargeback.</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:25:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=45248844</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45248844</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45248844</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Neobanks definitely have this feature. For example Revolut. There’s a “Block future payments” button, and once you click it, no more charges from that merchant will go through.</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:19:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=45248787</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45248787</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45248787</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>We always issue a refund if a customer asks, or at least try to find a compromise if the payment was made a very long time ago. In that case, it’s usually more about a pro-rated refund.<p>But recently I asked for a refund from a very popular project management system, and it was a nightmare, an absolutely terrible experience. After that, I gained a new level of respect for our own support team ))</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:17:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=45248773</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45248773</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45248773</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>To be honest, I’ve never personally filed a chargeback, so I don’t really know how difficult the process actually is ))</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:12:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=45248727</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45248727</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45248727</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>I know for sure that if users start filing complaints against you with Apple, they can simply ban your account entirely and for long. Some companies never recover from that and end up shutting down.</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:06:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=45248686</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45248686</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45248686</guid></item><item><title><![CDATA[New comment by evermike in "The madness of SaaS chargebacks"]]></title><description><![CDATA[
<p>Yes, we’ve had a few cases where people tried card testing through us. But we noticed quickly and introduced the proper limits. In general, if you redirect the user to Stripe Checkout after clicking Subscribe button, all of that should be handled by Stripe itself and not affect your account. I guess ))<p>But this is a slightly different story. With chargebacks, almost every time it was just a customer not wanting to admit fault. What’s strange is that they could have simply written to us and asked for a refund. But I guess they realized they were in the wrong, so instead of contacting us, they went straight to their bank.</p>
]]></description><pubDate>Mon, 15 Sep 2025 12:04:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=45248672</link><dc:creator>evermike</dc:creator><comments>https://news.ycombinator.com/item?id=45248672</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45248672</guid></item></channel></rss>