with Plant identification app · Plant identification app
LenderHawk analysis. Not affiliated with or endorsed by Acquisitions Anonymous.
The hosts see the only plausible upside as turning the app into a community for plant enthusiasts, but they doubt that justifies the asking price versus building a similar product from scratch.
A 6.5x revenue asking price is hard to defend when the business is still losing money and appears to require ongoing paid acquisition.
Charging $5 per week creates unusually high payment friction, which makes churn and refund behavior especially important to diligence.
The absence of churn data is itself a warning sign when the product is a consumer app with a trial-like use case.
Free alternatives can destroy pricing power quickly when the product is easy to replicate or compare against in the app store.
If a product's core function can be absorbed by Apple, Google, or on-device AI, its standalone value may be temporary.
The only convincing long-term upside in a commodity utility app is to turn it into a community or identity-based product, not just a tool.
Revenue multiples on small software businesses can mislead buyers if gross margin, customer retention, and growth quality are weak.
The listing asked $4.5 million for a company with $690,000 of trailing 12-month revenue, implying a 6.5x revenue multiple.
The hosts opened the review by reading the MicroAcquire teaser and estimating the multiple.
The app charged $5 per week, which works out to about $260 per year for a subscriber.
They used the weekly pricing to estimate how much a user would pay annually.
The business reported a trailing 12-month loss of about $29,000.
The hosts noted that the company was not yet profitable despite meaningful revenue.
The listing said the app had been founded in October 2020.
The hosts used the founding date to contextualize how early-stage the business was.
The seller said the app was available globally but was currently focusing on 29 countries.
This came up while discussing the company's operating footprint.
One competitor mentioned was iNaturalist, which was described as free and funded by institutions and donations.
The hosts used this as evidence that pricing pressure could be severe.
The hosts referenced Twilio trading at around 4x ARR with roughly $3 billion of ARR as a public-market comparison.
They used Twilio as an example of how public valuations had compressed.
Diligence churn before you believe a subscription app's revenue run rate.
Why: A weekly consumer subscription can look strong on paper while masking rapid cancellations and low retention.
Stress-test whether the product could be replaced by a free or built-in alternative.
Why: If the feature is easy to commoditize, the buyer may be paying for a business that cannot defend its pricing.
Treat revenue multiples with skepticism when profitability, retention, and marketing efficiency are unclear.
Why: Revenue alone can overstate value in structurally unprofitable software businesses.
Look for a community or identity layer if you want a commodity utility app to have durable value.
Why: The hosts think the only real bull case is turning the product into a hub for plant enthusiasts rather than a simple scanner.
Build free or low-cost products with an upsell path instead of relying on aggressive sales and marketing.
Why: They argue that software businesses can be stronger when the base product is free and monetization comes from optional premium features.
The hosts walked through a listing for a one-person, France-based plant scanner app that charged weekly subscriptions and still showed a small loss. They treated it as a case study in how easy it is for a consumer software product to look like a business while depending on paid acquisition and fragile retention.
Lesson: A high-revenue app can still be a bad acquisition if the core utility is easy to copy and the retention story is weak.
They compared the plant app to the fictional app that could identify food, noting that the show eventually revealed the business was only reliably good at identifying hot dogs. The analogy was used to illustrate how a seemingly broad AI-assisted utility can be narrower and more fragile than it first appears.
Lesson: A narrow, gimmicky use case may not justify a broad valuation unless it can expand into a deeper product or community.