cope. Having somebody you can turn to when you've got a crunch on and a bunch of games coming out, it's helpful. A great 2PP platform has a lot of good integrations, plenty of access and several distribution channels. Maybe you want to try a new market which you're not currently active in. With a 2PP platform, you have a partner who's got access to that market already and can get you in there in which case, why not work with them for the time being? And if it turns out to be a great market, then maybe you'll take it in-house.
We've got quite an interesting position on this at Fincore as we can license our source code. So, what we find quite a few studios are thinking is, look, I want to work with a 2PP partner for those benefits just mentioned. But I’m worried long-term I'm not going to have control of my destiny.
We have that source code license on the table, meaning that people can work with us confident that they can get going, get games live quickly, but long-term they will have the opportunity to bring this in- house should they choose. What we've found is that most of those studios keep going with the service because it works. And if it ain't broke, why fix it?
Is the licensing of source code something that's unique to Fincore or is it something that 2PP competitors offer?
I'm sure if I say it's unique, I'll have 10 emails telling me it's not straight afterwards. But it's unusual in this space to take that approach and we think it's quite a mature one to take. We think it's the right way of working and a positive collaboration with studios and operators to have that opportunity. But I think we're unusual in doing it. I'm looking forward to being told otherwise.
As CPO, are you part of that sales process in terms of talking about how these collaborations will work from a technical point of view, or is that somebody else's remit?
We've got a commercial team who go out and find these partners, establishing who's best to work with and who we should be doing business with. Te role of products in this is to make sure that there's a usable, strong platform to work with. Te most important thing for studios is knowing that they can build their game smoothly, they can get them through certification first time, the engines do what they need to do, and the client integration piece is quick and easy. Tat
73
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116
