[brudgers]

'300 customers' means 300 people paid money for the service. If people are not paying money, then they are not customers. Requiring people to pay money is a good way to filter out people who are unlikely to trust your process and ultimately, if the goal is to have a business, then getting people to pay is a necessary step toward validation. Charging people is also a reality check on the product creating value. If it doesn't seem reasonable to charge for it then it might not be a good product.

If people are not completing the process, then the product might not meet the market. In that case it's not a matter of increasing conversions, it's a matter of creating a better product.

Good luck.

[leomayleomay]

yeah, that's true, to be more precise, we have 300+ users registered for less than two weeks. People are searching `visa` in App store then see our app, we have 300+ registered users in a short period of time, which means the need is there, people are not paying since we are not that trustworthy, i am still believing it's a good product, but we do need to do more reality check see how people are willing to pay for the service

[brudgers]

Because 'Visa' is also the name of a major credit card provider, there are likely to be a significant number of people searching under that term whose needs are entirely different.

My standard concern is that it is much harder to iterate and communicate with users when the delivery channel is an app in an appstore versus a website. It is also more difficult to anchor pricing to a sustainable level and offer personalized service.

Expertise navigating international travel is something that may have more value than a potential customer's flagship mobile device. In an app store, it is going to be nearly impossible to extract that value because...well there's somebody who will offer a service that is similar for free or $1.99. In the app store, the $1.99 service will be largely indistinguishable from a $999 service due to the standard format of app store sales pages.