Is there existing research on the pricing of #FinTech API's?

It stands for allowing someone to continue doing or use something that is normally no longer permitted (due to changing regulations, internal rules etc.)

If you're not technical yourself, then you might not be able to gauge the efficiency of a candidate's algorithms or critique her code. But there are still some higher-level, more behavioral things that a non-technical interviewer should be looking for in a strong development candidate: 1. What are some tech blogs that you follow? Explain an interesting article to me that you read from one of them. The software development world changes all the time. Best practices are constantly evolving and new libraries are regularly released which make developers more productive. If a candidate doesn't keep up with the latest software news, that might be a red flag that they're not curious or trying to improve themselves. Also, having them explain a technical concept to someone who's non-technical is a great way to gauge their communication skills. Do they seem like someone you could work with and understand easily? Do they care about pausing to make sure you understand, or do they just drone on with jargon? If you feel overwhelmed while they're explaining this answer, imagine how you'll feel when they're telling you why the product has bugs or isn't going to be done on schedule. 2. Tell me about a time you ran into a big roadblock with something you were building. How did you get past it? It's inevitable that a software developer will get tripped up or have to solve some Gordian Knot. Everyone has to bang their head against the wall from time to time. Maybe an API didn't have the data they needed or some function was running too slow and they weren't sure how to speed it up. You're looking to see how they are as a problem solver. Did they come up with a clever but hacky solution? Were they methodical or did they fly by the seat of their pants? Did they go back to the stakeholders and see if the feature's requirements were flexible? Did they work on it for hours and hours trying new things? Did they ask for help from colleagues or on the internet? No right or wrong answers here, but you want to get the sense that this isn't someone who throws up their hands when they hit some friction. 3. Tell me about your favorite project that you worked on. What work are you most proud of? By asking them about the project they're most proud of, you'll get to see what it is that they value most. Maybe one candidate is most proud of a side project they built, even if it wasn't that technically complex, while another candidate is proud of their esoteric PhD project or some specific algorithm they improved. Again, no right or wrong answers, it really depends what type of candidate you're looking for. But it lets you see into their mind a bit, and get at some of the aspects that can make someone a strong development candidate. If you want to talk more specifically about hiring for your team, I'd be happy to do a call!

One of the best and most popular script used is Vbulletin. Most of the reputable forums are powered by Vbulletin. The second recommendation I'd have is phpBB. It is absolutely free and open sourced versus Vbulletin which is licence based. I have used both and had no problems with either of them. If you can fork out some money I'd suggest going with Vbulletin. Here is a list of the biggest internet forums http://en.wikipedia.org/wiki/List_of_Internet_forums. You can see most of them are powered by Vbulletin and the second most popular script is phpBB. Regarding fresh look you can simply hire someone or buy a Template.

As someone who has worked in pricing for almost 30 years, I know that one of the biggest myths of pricing is that you should only offer one pricing model. Offer two - both subscription & transactional. Customers will self-select &/or the market will segment, and you will quickly find out what is their preferred pricing model. As an aside, another pricing myth is that you can low-ball your pricing and raise prices later. Its successful in ~10% of attempts. By default, the choice of pricing models also states the obvious. Its not about what you want. Its about what the customer wants. And yes, you should have three choices. One choice gives you a 50:50 chance of closing the sale. Two choices forces the customer to make a price-based decision. Three choices, and the customer says "which one do I buy?" not "do I buy from this outfit?" and secondly they are forced to make a value-based decision. Also think about creating a decoy product, and on the pricing page on your website, lay the packages out dearest on the left, cheapest on the right. Happy to chat further about any of the above...or more!

Many well-known SaaS companies have doubled their prices. I've personally worked with a few that have gone through it. In most cases, your conversion rates stay the same and you see a huge jump in revenue. This is because people tend to under-price themselves. Also, your product improves over time so it provides more value and can support a higher price. But don't raise prices for old customers. Grandfather them in so their plans stay the same price. In the long run, it won't make a difference to your growth since most of them will churn out anyway. If you raise prices on current customers, you'll get a huge backlash. It gets nasty. I'm pretty sure that Zendesk tried it and had to reverse the price increase. I highly recommend raising your price by 100% for a month on new customers. Keep a close eye on your revenue and your conversion rates. If things don't go well, you can easily reverse it and discount everyone that paid for the more expensive plan. Either way, you'll know what your market will actually support.