Post by account_disabled on Dec 26, 2023 4:09:51 GMT -5
We knew that when we launched a third-party solution, feedback and requests would come in, but we wouldn't have the ability to take them into account. The ability to provide and create personal relationships, not only for our affiliates but also for our administrators, was something we couldn't have done without. We love data and we need data! How else could you make strategic decisions? It was also necessary to extract reporting data from our complex enrollment plan system. Going deeper, we knew that once we opened the affiliate system to the general public, we couldn't stop.
Sure errors are fixed, but if we needed to change payment Buy Bulk SMS Service providers, we couldn't simply put our affiliates on hold while we withheld the money they were owed. Additionally, flexibility was one of our biggest concerns. What would have happened if we had to change the subscription management rules (this actually happened)? Would we have been able to handle multiple languages and currencies? And what about add-ons developed over time, such as Redis , hourly backups and so on. Could we have built an extensible dashboard for our users? From a technical point of view, using someone else's software turned out to be completely redundant .
Since we have a very unique way of managing subscriptions through Stripe , we needed to create a system based on what we mean by referrals and what the change mechanism is for upgrades and downgrades. Stripe While I'm sure many solutions have APIs, writing the code to send our data to the API would have been 80% of the work. Why not add another 20% and create our own user interface, which we do very well anyway. Costs Involved Another big concern was the price. There are cheap products on the market, but the price cut is due to reductions in functionality or flexibility.
Sure errors are fixed, but if we needed to change payment Buy Bulk SMS Service providers, we couldn't simply put our affiliates on hold while we withheld the money they were owed. Additionally, flexibility was one of our biggest concerns. What would have happened if we had to change the subscription management rules (this actually happened)? Would we have been able to handle multiple languages and currencies? And what about add-ons developed over time, such as Redis , hourly backups and so on. Could we have built an extensible dashboard for our users? From a technical point of view, using someone else's software turned out to be completely redundant .
Since we have a very unique way of managing subscriptions through Stripe , we needed to create a system based on what we mean by referrals and what the change mechanism is for upgrades and downgrades. Stripe While I'm sure many solutions have APIs, writing the code to send our data to the API would have been 80% of the work. Why not add another 20% and create our own user interface, which we do very well anyway. Costs Involved Another big concern was the price. There are cheap products on the market, but the price cut is due to reductions in functionality or flexibility.