SuperLemon: $25,000 MRR in 14 Months for a Two-Person Shopify App That Stopped Raising Prices

Dollar amounts are US dollars, converted to yen at approximately ¥150/$1.

A business whose goal was “$1,500 a month”

SuperLemon (formerly WhatsApp Chat Button) is a Shopify app that adds WhatsApp-based customer chat to a store. It was built by two people in India, Preetam Nath and Sankalp.

What stands out is how low a bar these two set at the start. Each had roughly 12 months of savings to work with. Their survival line was $1,500/month, and their line for popping champagne was $3,000/month, about ¥220,000 and ¥450,000, respectively.

What they actually reached, 14 months in, was $25,000 MRR (about ¥3.75 million), more than 16 times their original target. And the single biggest decision behind that gap wasn’t “raise the price.” It was cutting a price they had already raised.

Numbers and timeline

1,500 paying out of 20,000 active gives a paid conversion rate of roughly 7.5%. At a price point around $10, 1,500 paying merchants lines up consistently with the MRR figure.

The decisive move was cutting the price

This case’s turning point is unambiguous: the drop from $29.99 to $10.

Nath explains it this way: “The majority of our users are small merchants doing a few hundred orders a month. By pricing high, we were alienating 90% of the potential paying users who came to our app.”

The mechanism here is worth spelling out. The distribution of store owners arriving at the Shopify App Store skews heavily toward small operators. For a store doing tens of thousands of yen a month, $29.99/month (about ¥4,500) is a fixed cost you can’t ignore. $10/month (about ¥1,500), on the other hand, fits inside “try it, cancel if it’s not for me.” Move the price band once, and the size of the addressable population shifts by an order of magnitude.

Inside an app store, that effect compounds. More paying users → more reviews (500+, averaging 5.0) → higher visibility in the store → more new installs. A high-price, low-volume strategy earns more per customer but slows this loop’s rotation. In marketplace-hosted micro-SaaS, maximizing per-unit price and growing the channel can pull in opposite directions.

The post-cut pricing design, “$10/month plus usage-based messaging”, also matters. It lowers the entry point while still capturing revenue from heavy-usage merchants based on volume. Given that 450,000 messages went out in a single month (June 2020), that usage-based component must have grown into a non-trivial share of revenue.

“95% users, 5% competitors”

Another factor at work: a time-allocation rule. Nath adopted a policy of spending 95% of his time on the product and users, 5% on competitor analysis.

That doesn’t mean ignoring competitors. In fact, he later reflects that “completely ignoring competitors let them close the gap.” The 5% figure was the landing point for a balance, not distracted by competitors, but not blindsided by them either. New copycat apps keep appearing in the Shopify App Store. Commenters have flagged imitators in the reviews themselves.

What did the 95% actually look like in practice? Turning features on with sensible defaults on first use (so value shows up without the user touching settings), embedding FAQs directly in the product to cut down support tickets in the first place, fixing recurring bugs, and moving the support channel from WhatsApp to email to reduce processing load. Supporting 20,000 stores with two people requires designing down the volume of support just as much as building features.

One surprising result: adding friction to onboarding doubled trial signups. Raising the bar from “anyone can sign up” filtered in users with genuinely higher intent. Not every case of removing friction is the right call. This is a counterexample.

What didn’t work, and the risk that remains

Nath names four failures himself: alienating small merchants with the high $29.99 price, ignoring competitors completely and letting them catch up, easing off the pace during a growth phase and hitting a plateau, and depending on a single channel, the Shopify Marketplace.

That last one is a structural weakness of this type of business. With nearly all acquisition riding on a single platform, any change to review policy, search algorithm, or Shopify building an equivalent feature natively could hit growth directly. The $25,000 MRR result was won in exchange for that dependence.

What generalizes, and what doesn’t

The pricing logic here generalizes well. Don’t just look at price times customer count. Look at the size of the population that price actually reaches. Especially for platform-hosted micro-SaaS, cutting price grows non-monetary assets, reviews and exposure, which in turn drive the next round of acquisition. This case is a usable counterexample to the assumption that raising prices is always the right move.

Reducing support load also generalizes, regardless of team size. Embedding FAQs in-product, permanently fixing recurring bugs, designing the support channel deliberately, the practical playbook of running 20,000 stores with two people can be referenced directly.

Some conditions are harder to reproduce, though. One is the regional specificity of WhatsApp, in India, the Middle East, South America, and Southeast Asia, WhatsApp is the primary channel for e-commerce customer contact, and demand here assumed that. Whether the same structure carries over to, say, LINE in Japan is a separate question. The other is the timing, 2019, when competitive density in the Shopify App Store looked very different from today. And the fact that both founders had 12 months of savings secured before starting is also an initial condition not everyone can arrange.

Related reading

• How Plausible Analytics reached $1M ARR — a small team that matched price to value without growing headcount
• Photo AI and Pieter Levels — the design choices behind running a product solo with minimal overhead