Why Can a SaaS Have Users but No Sales?

On September 29, 2026, VoxCut passed 1,000 cumulative downloads across all channels: exactly 1,006, including 579 via GitHub and 282 via Google Play. But those downloads did not turn into sales in proportion to the apparent interest. Another of our products, VidScope, received about 83 unique visitors in ten days for three analyses run and zero orders.

This situation is more common than people admit: having users does not mean having customers. This article tells what our own numbers taught us, and proposes a method to find, in order, where a software funnel gets stuck. It is not a theoretical guide: every case comes from our products.

No, or only partially. A download measures a moment's curiosity: someone saw a listing, found the idea interesting, clicked. It says nothing about real need, frequency of use or willingness to pay. A product downloaded a thousand times by the curious is worth less than one used every week by ten professionals.

On VoxCut Android, the 14-day analysis showed 169 installs, 96% of onboarding completed, and 118 users who saw the purchase screen. Activation figures were good: the product worked and people used it. Yet no purchase was confirmed. Interest existed, but it did not convert, and the cause was not the one you would have guessed.

First habit to adopt: stop looking at the total, and look at the step where users disappear. A funnel is read in percentages from one step to the next, not in cumulative volume.

Origin matters too. On VoxCut, 579 downloads come from GitHub, 282 from Google Play, 104 from Softpedia, 36 from the Microsoft Store and 5 from the Snap Store. These channels do not attract the same audiences: someone downloading an executable from a code repository is not looking for the same thing as someone installing an app from their phone. Adding these figures up gives a flattering total, but turning it into an average conversion rate makes no sense.

In our case, the first blockage was purely technical. Over 14 days, 37 clicks on the buy button had been recorded, about 10% of installs, which is a real intent signal. But several of those clicks ended in an error: the product was not loaded from the store, or its identifier did not match. Customers ready to pay simply could not.

Before touching price or message, you must therefore check that the purchase path works, end to end, on a real device. It is a boring check, but it should come first: optimising a leaking funnel is pointless.

Once the technology is clean, two other causes remain. The offer: does the free version already give users what they want, or is the difference with the paid version blurry? And the audience: do arriving visitors actually have the need the product solves? For VidScope, much of the traffic landed on AI news articles, far from what the tool does. Lots of visits, no purchase intent.

Traffic matters less than its fit. On VidScope, Search Console showed 227 impressions and 3 clicks over 28 days, with queries unrelated to the product. A send of 115 prospecting emails brought only 3 measured visitors. It was not a problem of volume of actions: we had listed on some fifteen directories, written articles, commented on videos. It was a problem of channel choice.

There is also a structural hypothesis the numbers do not immediately show: occasional use. A YouTube viewer needs a tool like VidScope once in a while, so has no reason to pay. A technical content creator needs it for every video. Same product, two usage frequencies, two very different willingness to pay.

One last thing to examine: the promise. A home page that speaks to everyone convinces no one. We removed unfounded phrases from VidScope's page ('our community', 'join the creators') to keep only what the tool really does: it makes the product less spectacular, but more credible.

Keep in mind, finally, that time plays a part. A recent product has no word of mouth, reviews or track record yet. The first weeks mostly serve to check the foundations hold: the purchase path works, the promise is understood, the right people arrive. Sales come after, rarely before.

Here is the method we now apply, in order. One: measure the funnel step by step (visit, trial, core use, purchase screen, buy click, purchase) with the same sources each time, isolating each product if several share an analytics tool. Two: check the purchase path on a real device, in real conditions.

Three: look at who actually arrives. If traffic comes from off-topic articles, or from a directory whose audience lacks the need, it is an audience problem, not a product one. Four: question the offer. If the free tier covers the need, nobody will pay, which is good news about the product's usefulness but bad about its model. Five: talk to real users, even five, rather than adding another marketing action.

One rule has spared us mistakes: do not conclude on small numbers. With three analyses or forty visitors, no trend is reliable. The right answer is then to document, wait for a more significant sample, and change one parameter at a time to know what produced the effect.

In the order of effectiveness we observed: fix what technically prevents buying, align the promise with real use, then think about price positioning and when the purchase screen appears. Showing the paid offer right after the user has seen a concrete result, such as a first exported file, converts better than showing it when the app opens.

You must also accept an uncomfortable conclusion: sometimes the product really is useful, but not to those who find it. It is then better to narrow the audience than to multiply channels. Choosing the right audience weighs more than ten extra directories. The price question itself is covered in our article on how to price a SaaS product.

The first signal is the intent ratio. That 10% of installs lead to a buy click is rather encouraging for a small tool: it shows people understand the offer and are tempted. A product of no interest does not reach that figure. It is precisely because this signal existed that we had to look for the leak in the funnel rather than question the idea.

The second signal is repeat use. A tool you use once then forget will sell only if it solves a costly problem. Look at how many users come back a second, then a third time: if almost nobody does, the problem lies in the need or the experience, not the price.

The third signal is qualitative, and the hardest to hear: feedback from people who know the subject. A tester told us bluntly that one of our products was not worth paying for as it stood. That kind of feedback stings, but it is worth ten dashboards, because it says why. Note it, cross-check it against your numbers, and treat it as a hypothesis to test, not a verdict.

Users without sales do not mean a failed product, but a funnel to be read step by step: technology first, audience next, offer last. The approach is the same we apply to our clients' projects, and rests on a simple principle: measure before you change.

If you are building software and your numbers look like ours, an outside look at your funnel can save weeks. You can also read our comparison of custom tools and SaaS, or contact us from the contact page.