Claimed by paid web service that 'it is meaningless to repeat slight changes to improve conversions'
by Tim Gouw
People who wish to raise profits by launching a fee-based net service will make various changes so that users can use paid services even a little. Many developers think that it is necessary to constantly make improvements in order to raise conversions even a little by changing the position and size of the buttons and changing the order of the display while " Pedro Cortés , a consultant for startups, argues that it is necessary to think about whether change has led to profit?
Why Tweaking & Split testing a SaaS Website is stupid (do this instead)!
https://www.cortes.design/post/saas-website-conversion-split-test
Developers are taking much time and effort to improve the conversion rate, but what you really have to think is " customer acquisition cost (CAC)". You should consider how much it took to navigate to your website, how much it costed to become a customer, and took a huge leisure time to raise a small conversion rate It seems that it does not make sense.
In most cases, even if detailed refinement of service is repeated as "It should be able to obtain more profits if better service is offered", it is early in service start that we get the corresponding return in return As time elapses from release, improvements due to improvement will be less.
Also, some developers prepare multiple site patterns and do a split test in order to find out what kind of websites are going to raise the conversion rate ?. However, 95% of the net service that carries out this test seems to have not obtained satisfactory results. Split testing is effective when there is consistently a lot of traffic, and many net services say that there are not many original traffic so that useful data can be obtained by performing a split test.
by Startup Stock Photos
The important thing is to distinguish between the parts that do not have power on the site and those that do not, and focus on improving returns that just spend effort and time. Regarding the part to put emphasis on improving CAC, the following parts are considered mainly.
◆ Maintaining the page leading to the purchase of the service <br> The revenue of the service is obtained by the user starting to use the paid service. Therefore, the route to the purchase of services such as "page of the website the user first visits" "page describing the fee for the service" "page to conduct free trial service or real registration" "page immediately after service start" It needs to be maintained.
◆ Answering questions and doubts Users are not always going smoothly until the start of service, and they have questions or doubts about the contents of the service on the way. If it can easily solve the question on the website, the user can start using the paid service feelily. For this reason, it is important for developers to prepare pages that answered questions or doubts that were expected or actually posted, so that they can access from any page on the site.
◆ Responding to customer's request <br> It is important to receive feedback from customers who actually use it, actually make a call or make a review. If the user requests "I want this point to be inconvenient because it is inconvenient" requests, 20 times as many users as "behind this point are inconvenient, but let's let go of contacts because it is troublesome" to be incomplete I should think that it is leaving.
by Christina Morillo
In developing deployment of paid services, "We should emphasize" how much profit was actually obtained as a result of labor and time spent ", and if we focus on improving the details that we do not know whether limited resources are needed or not It is summarized that it is important to focus on the point that correct results are obtained.
Related Posts:
in Note, Web Service, Posted by log1h_ik