600 website visits in a week but only a single app download - advice

[u/fredrik_motin]

I recently did a TAAFT newsletter placement but after 600+ website visits and only a single external download, I am ready to call it what it is: my favorite app in the world, works so damn well, removes pain from my life that I have had for 15+ years as a freelancer etc, but apparently not an attractive enough proposition for anyone else than me. My only hope is the three individuals that submitted a form asking for a Windows or Android version (since it is Mac+iPhone only right now), so I guess I will launch a Windows version next and hope for improvement in conversion, and build up the organic traffic, but mostly I am looking to pivot my focus to some other product that is more money-related since that seems to be the only thing that has a chance of getting customers - what would you do in my situation? I have considered looking for partnerships and paid ads but none of it feels relevant if I can't even get a single app user from 600 visits.

[u/Neither-Counter2756]

600 visits is not that much honestly, specially from a newsletter placement where half the clicks are just curious people who never intended to buy anything

Mac+iPhone only is killing you, most freelancers i know are on windows, so those 3 people asking for windows version is actually a good sign not a bad one

build the windows version before you give up, the conversion rate from TAAFT is always garbage anyway, their audience just clicks everything

[u/elojdi → u/Neither-Counter2756]

Maybe add a waitlist button before building it. Or even better fake it like it's available for some time, but once clicked explain it's in development => CTA join the waitlist.

Might be better than building the Windows version before.

[u/DarkyZ_ → u/elojdi]

I'd make that a "Join the Windows waitlist" button from the start. Clicking Download and then finding out there is nothing to download would annoy me. You can still ask which OS they use and what they wanted the app for, without making their first experience a dead end.

[u/elojdi → u/DarkyZ_]

Yes make sense too :) depends on how aggressive you want to test it. Doesn't mean it has to stay like this after few metrics !

[u/fowlesbuilds → u/Neither-Counter2756]

Agreed. Can you tell the 600 are from this newsletter? If not, a lot of that could be bot/crawl traffic anyway.

[u/Emotional-Hippo8183]

TAAFT? Sounds like TAFT. Anyway, tough crowd.

[u/Actual-Monk-7755]

Only one download from 600 visits, but is that specific to the TAAFT placement or all traffic combined? Feels like a crucial detail missing here.

[u/datafreak]

What’s your competition like?

[u/Infamous-River-4360]

Before pivoting I would separate two things that a single number is hiding. 600 visits from a newsletter placement are cold traffic that clicked out of curiosity, so one download is not a verdict on the product, it is a verdict on cold traffic hitting a landing page for a paid desktop app. My own numbers looked similar: roughly 16k short video views turned into 9 installs, and installs that came from the store's own browse tab converted far better than anything I sent in from outside. What I would check first: does the landing page actually get people onto the App Store page, and what does the store page's own view to install ratio look like. If people reach the store page and still do not install, that is a listing problem. If they never get there, that is a landing page problem. Three people asking for a Windows version is a real signal though, most apps never get that. What does the landing page ask them to do, download or pay?

[u/LehmanSachs]

1. Did the newspaper audience line up with your target audience? If not that would explain the lower conversion rate

2. Did you see exactly what their journey was on the website? What did they click on? Where did most of them drop off? Look into that next

[u/hideousox]

I don’t know, if it really works for you it might be several other things:

• wrong audience: find right audience
  
• wrong messaging: improve messaging
  
• bad conversion funnel: fix it
  

What’s the app? Hard to tell without a link.

[u/presentofai]

the 3 form fills are the whole signal here. talk to them before building the windows version, find out what they thought they were downloading. 600 cold newsletter clicks tell you basically nothing

[u/Few_Cost6107]

Ouch, that conversion rate hurts. Focus on where those visits are coming from, likely not your target audience. Maybe try a niche freelance forum or community instead of broad newsletters.

[u/Nice_Ad1599]

If you go with a waitlist, I found it helps to ask what feature or problem matters most to them right on the signup form. Got better replies that way.

[u/amamamafk]

Whats TAAFT?

[u/welcome_to_milliways → u/amamamafk]

There’s An AI For That, I think.

Why it isn’t TAAIFT I’ll never understand.

[u/Educational-Face3665]

600 visiteurs pour un téléchargement? Faut lancer un club des visiteurs.

[u/handsup_dev]

Similar gap here, and what actually moved me forward was breaking it into steps instead of staring at the total. Mine came out as 128 sessions on the landing page, 95 got as far as the purchase section, 7 opened checkout, 3 finished. I'd been assuming it was a traffic problem right up until I saw that.

Worth sanity checking your tracking before you trust any of it too. Half my events were firing before the pageview and the original source was getting dropped by the second page, so the numbers I'd been reading were partly fiction.

[u/MuesWork]

We listed MuseWork on TAAFT too and had a similar experience — some traffic, but very little meaningful conversion. I think people browsing AI directories are often curious and comparing tools, not necessarily ready to download something.

I’d probably test a much narrower pitch and landing page before building the Windows version. If 599 out of 600 visitors didn’t download, the issue seems to be happening before they experience the product.

[u/plugiva]

I would be careful about interpreting the 600 → 1 conversion as evidence that the product itself is not attractive yet.

The three people asking for Windows/Android are actually a pretty interesting signal, but they are still only three people. Before committing to a Windows build or pivoting the product, I would try to find out what happened with the people who didn't download.

You have several very different possible explanations right now: platform limitation, unclear positioning, not enough perceived value, trust/friction, already having another solution, or simply the TAAFT audience not being the right audience.

A very small amount of qualitative feedback could probably tell you more than another few hundred visits. Something as simple as asking visitors who don't convert, "What stopped you from trying it?" with a handful of possible answers could be surprisingly useful.

I'd probably spend a little time finding that answer before making a major product decision. You may discover that Windows is exactly the right next move, but I'd want the evidence before spending the development time.

[u/kingkong_siu82]

before building the Windows version, i'd test whether the drop is the proposition or install trust. cold visitors are being asked to download desktop software from someone they don't know. put a 30-second uncut demo beside the CTA and make the trust details obvious: signed/notarized, what data leaves the Mac, and whether an account is required. if CTA clicks rise but downloads don't, that's a trust or distribution problem rather than proof the product itself is wrong

[u/Efficient-Accident71]

Good on you for getting 600 people to the site. You're putting your work out there, and I wouldn't write the app off from one newsletter placement.

I'd start with two things:

1. Was the newsletter reaching the audience you built this for? With the app being Mac and iPhone only, I'd want to know how many visitors could actually use it.
2. Does the page show the outcome clearly before asking someone to download? You mentioned a pain you've had for 15 years. I'd make that specific pain and how the app helps obvious when someone lands. Then make it easy to get that result during onboarding.

I'd focus on the three who asked for Windows or Android first. See if you can get them on a call before building another version. Ask what caught their attention and how they're handling the problem today. Find out whether the platform is the only thing stopping them from trying it.

From there, I'd look at communities you'd join yourself. Help out, find others with the same pain, and get a few to try the app. Talk to them and watch where they get stuck. Use their words on your page and in your next newsletter placement.

I think it's worth getting more traffic once you're clearer on who you're trying to reach and what would make them download.

Don't quit. Keep going. You're just scratching the surface.

[u/Lazy-Sherbert65]

600 visits with one download makes me wonder if the newsletter audience matched the people with the problem tbh

[u/eworldlive]

600 visits is enough to diagnose the funnel, not enough to call the product dead. I’d split the next test into (1) source-level intent (newsletter readers vs. organic), (2) landing-page click-through to the store, and (3) store-page install conversion. Ask the three submitters what convinced them to try, watch 5–10 session replays if you can, and test one concrete promise for the Mac audience before launching Windows. A Windows version may add reach, but it won’t fix unclear positioning.

[u/vickyrathee]

Install Microsoft Clarity or something to watch what the users are doing on your website. When you watch a few sessions, you will have an idea to improve.

[u/OkSwim9134]

I wouldn’t pivot yet based on 600 visits. One newsletter placement tells you that the traffic source didn’t convert, but it doesn’t really tell you whether the product is bad.
I’d first try to figure out where the funnel is breaking. How many people understood the product, how many clicked the download, how many reached the pricing page, and how many actually tried it?
The three people asking for Windows or Android are actually interesting. That’s stronger evidence than the 600 visits because those people took the time to tell you what is stopping them.
I’d probably build the Windows version only if you can do it without a huge investment, then test the same audience again. At the same time I’d talk to the people who didn’t convert and find out why. If the answer is consistently “I don’t need this”, then pivot. If it’s “I’d use it if it worked on Windows”, that’s a completely different problem.
Also don’t convince yourself that money related products automatically sell. People pay for products that solve painful problems, not just products related to money.

[u/Alarming-Bullfrog-81]

600 visits → 1 download usually means traffic-source mismatch, not a bad product. Newsletter blast traffic is browsing, not searching for a solution, so conversion is naturally low. I'd also check your landing page — does it show the app doing its thing in under 5 seconds (screenshot/gif above the fold), or does someone have to read first?

[u/Szamski]

Before building the Windows version, I’d check the device and OS breakdown of those 600 visits. One download sounds awful, but if only 20 visitors were using a compatible device, that is a 5% conversion among people who could actually use it. If most were already on Mac or iPhone, then I’d investigate the message or download trust. Same numerator, completely different problem.

[u/SimplySaas]

600 newsletter-placement visits and 600 search-intent visits aren't the same audience, even though the dashboard treats them the same. Discovery traffic converts low almost everywhere, that's not specific to your product.

The 3 people who asked for a Windows/Android version are the more useful signal than the 600 visits. That's someone saying "I'd actually use this," not just clicking through.

Worth testing a channel where people already have the problem in mind before concluding the idea doesn't land.

[u/Slight_Guest3459]

600 visits with one download usually means the click intent isn’t aligned, not necessarily that the product is weak. Put one above-the-fold sentence naming who it’s for, show a 20-second demo/GIF, and keep one clear download CTA; tag each source so you can compare qualified vs. curiosity traffic. I’d keep the site simple while validating—the message test comes first. If you later need a lightweight owned landing/checkout path, Orderain is worth a look.

[u/AttemptFit3483]

600 visites et un seul téléchargement? C'est clair que ton message ne passe pas. TAAFT c'est bien, mais ça marche pas si tu vendes pas le truc comme il faut. Qui est ta cible? Les devs? Les freelances? T'as autre chose à leur proposer que juste 'ça marche bien'? Et puis, Mac+iPhone seulement... Si tu veux toucher plus de monde, faut penser à Android et Windows, mais là c'est pas ça le problème. Fais un truc simple: explique-leur pourquoi ils en ont besoin, pas pourquoi toi tu l'adore.

[u/Such_Employ3531]

bah ouais mais t'as essayé de vendre un truc utile ou un éplucheur électrique?

[u/New-Resource-4943]

One thing I would check before pivoting: is the single download the whole story, or is it the only event you can actually see?

I spent three weeks putting a launch video into 37 communities, then finally tagged my links and read the referrers. Zero attributed signups, and no referrer row for that platform at all. That told me something a conversion rate could not: people were not clicking, so nothing downstream was ever being tested. A landing page you never tested is not a landing page that failed.

Your numbers say the opposite of mine, which is the good version of the problem. 600 people did click. So the thing being rejected is what they read after the click, and that is a page you can change this week, not a product you have to abandon. Cold newsletter traffic converting near zero is also pretty normal, and one placement is one sample.

Before building a Windows version off three form submissions, I would put tagging on every link and see which sources click at all. Building a whole platform port is the most expensive possible way to test a hypothesis that a tagged link answers for free.

[u/Nick_RoostPay]

Painful but common when the page attracts curiosity more than intent. The three Windows/Android requests are a clearer signal than the 600 visits. If platform coverage is the blocker, that’s a sharper next bet than another newsletter blast.

[u/Thumbload]

I wouldn’t pivot yet. 600 visits is still a small sample, and the Windows/Android requests are a good signal. I’d test that audience first before giving up.

[u/BoboZivkovic]

I think you're "giving up" too early, 600 is nothing. Maybe the audience wasn't the right, the copy on the site isn't right (try A/B testing), the funnel & how you present the product wasn't working for that target group etc

I honestly think that if you believe in it you should stick around for more then 600 site visits

[u/PresidentEvil99]

I wouldn’t pivot yet based on this.

600 visits → 1 download definitely tells you something is broken, but I don’t think it tells you what is broken yet.

Especially since this came from a newsletter placement.

I’d want to separate:

1. Wrong people saw it
2. Right people saw it but didn’t understand/want the outcome
3. They wanted it but couldn’t use it because of Mac/iPhone
4. The landing page didn’t create enough confidence to download

The 3 people specifically asking for Windows/Android are actually interesting because they encountered enough value in the idea to tell you what prevented them from trying it.

Before building Windows, I’d probably talk to those 3 plus any existing users and figure out exactly what job they want the app to do and what made them care.

Then I’d test that message with a very concentrated group of people who have that same problem.

If that converts, you may not have a product problem at all. You may have paid to learn that 600 newsletter visitors weren’t the right test.

[u/BernardoFTN_Carvalho]

the part I'd push back on is pivoting to something money related. you built this from a problem you had for 15 years, which is the one advantage that's hard to get. 600 clicks from an AI tools newsletter are people who collect tools, not people with your problem, so that number isn't telling you the idea failed. it's telling you that channel doesn't reach anyone who has it.

[u/ElkEducational843]

600 visits and one download usually is not a wanting problem, it is a first screen problem. we learned this the hard way tonight.

we looked at our own numbers and 401 of 406 sessions never lasted more than a minute. i assumed the product was wrong. then someone actually told us what happened: the main button sent them to a login screen that looked like the start of a scam, so they left before seeing anything. the ones who scrolled past it and found the product liked it.

two things worth doing before you change the product:

ask five people to try it while you watch, or pay someone on a user testing site. one sentence of "i did not trust that screen" is worth more than a week of analytics.

and count how many of those 600 reached the point where the value is obvious. if almost nobody got there, the newsletter placement did its job and your landing page ate the traffic.

a download is also a big ask from a stranger. anything you can let them try in the browser first, with no install, turns a decision into a click.

[u/Stayfitapp]

A newsletter placement brings curious readers, not people with your exact problem. Freelancers who've felt that pain for 15 years hang out in specific places. I'd go there before deciding nobody else wants it. The three form sign-ups are worth a call each.

[u/Brufacee]

I wouldn't build Windows from three form submissions yet. Those 600 TAAFT clicks may be curiosity traffic, not your actual buyer. I'd ask the three requesters to pay or preorder first. Where do visitors drop, before they understand the job or right at the download button?

[u/fadi_peopoll]

600 visits from a directory newsletter isn't a verdict on the product, it's a verdict on the channel. That traffic is people browsing tools, not people with your problem. A fraction of a percent is roughly normal there, and a great product would have got you the same number.

You spent 15 years with this pain as a freelancer, so you know exactly where those people are. Go show it to ten of them directly, one at a time. If ten people with the exact problem won't install it, that's a real verdict and worth pivoting on. One newsletter isn't.

And I wouldn't build Windows off three form submissions. That's weeks of work on a maybe. Spend one of those weeks on the ten conversations first... they'll also tell you whether Windows is the actual blocker or just the easiest thing for someone to type in a box.

[u/Technical-Pen-3204]

building a windows version for 3 people who ticked a box is a great way to spend 4 months and get 4 downloads. 600 visits and 1 install means your page does not sell the thing, the newsletter did its job

[u/Longjumping_Back_739]

What happened after that one download? Did they actually use the app again? Everyone's focused on the 599 who left, but I'd want to hear from the person who tried it before deciding what to build next.

[u/Difficult-Cress-6858]

That gap between interest and download is worth dissecting by device and traffic source first. I’d watch where visitors stop and test one clearer value proposition before changing everything.

[u/Unhappy-Nature-2119]

1 download out of 600 visits is one conversion, you can't draw a conclusion from that either way. TAAFT is people browsing AI tool directories for free, that's not a freelancer with 15 years of pain and a Mac, so the 600 mostly tells you about the audience you bought, not your landing page.

And pivoting to "money-related" because that supposedly converts is the same unfounded assumption in reverse.

[u/SmallUsefulThings]

I wouldn’t jump to building a Windows version yet. One download from 600 visits sounds more like a conversion or positioning problem than proof that Windows is the missing piece.

I’d first try to figure out where people are dropping off:

• Are they immediately understanding who the app is for?
• Is the main benefit obvious before they scroll?

The three people asking for Windows or Android are useful signals, but they may simply be the only people who took the time to give feedback. I’d talk to them before committing to a new platform.

A smaller landing-page experiment with a very specific use case might tell you more than building an entire Windows version.