Hmm, yeah I think I understand the revenue share part. I guess I'm wondering since you are hosting the service, are there minimum maintenance and costs (including your time) to ensure that it keeps on running smoothly and reliably?
Also, not sure if this is the case, but would you also assume that in the future they may want to add features or request changes?
Deploying to another environment with their keys for the 3rd party services like Stripe and others is very easy. Any updates we do for ourselves would be easy enough to add to our own deployment pipeline.
Costs would be a concern if they have a large amount of traffic, since it's deployed on AWS and uses sockets, it could easily pass the free tier. So I'd need to make sure they are aware of that and are paying for the cost of that.
My main concerns come from the support/recognition aspect. If a viewer has a balance of coins in CC and ends up on one of these streams, their balance wouldn't match up since they would be separate systems. So the viewer could be confused there, and the streamer may not be the best at explaining the disconnect. So at the very least, I think having our UI updated to look different is one thing that I'd need our team to do, which would be the most amount of work on this whole thing.
Additionally, from time to time creators and viewers just have issues and our support is very quick at resolving the issues. So, I'd propose a support clause in the white label, but if they don't go for that, then I'd be concerned that viewers may think that it's Crowd Control as a whole.
The streaming community is large but also very small and user experiences matter quite a bit to our reputation/brand.
I'm leaning towards exploring this with the client more and think overall it could be a good thing for us to offer to other agencies that are concerned with revenue share for their creators. But I'll need to try and figure out what makes sense based on their size and expected revenue from this.
Hmm, yeah I think I understand the revenue share part. I guess I'm wondering since you are hosting the service, are there minimum maintenance and costs (including your time) to ensure that it keeps on running smoothly and reliably?
Also, not sure if this is the case, but would you also assume that in the future they may want to add features or request changes?
Deploying to another environment with their keys for the 3rd party services like Stripe and others is very easy. Any updates we do for ourselves would be easy enough to add to our own deployment pipeline.
Costs would be a concern if they have a large amount of traffic, since it's deployed on AWS and uses sockets, it could easily pass the free tier. So I'd need to make sure they are aware of that and are paying for the cost of that.
My main concerns come from the support/recognition aspect. If a viewer has a balance of coins in CC and ends up on one of these streams, their balance wouldn't match up since they would be separate systems. So the viewer could be confused there, and the streamer may not be the best at explaining the disconnect. So at the very least, I think having our UI updated to look different is one thing that I'd need our team to do, which would be the most amount of work on this whole thing.
Additionally, from time to time creators and viewers just have issues and our support is very quick at resolving the issues. So, I'd propose a support clause in the white label, but if they don't go for that, then I'd be concerned that viewers may think that it's Crowd Control as a whole.
The streaming community is large but also very small and user experiences matter quite a bit to our reputation/brand.
I'm leaning towards exploring this with the client more and think overall it could be a good thing for us to offer to other agencies that are concerned with revenue share for their creators. But I'll need to try and figure out what makes sense based on their size and expected revenue from this.