Compensation for developing custom power BI visuals

[E12345]

Hi!

I just have a question (curious) - what is the cost associated with developing a custom PB visual? 

For example, if I developed a visual and got it certified, and it shows up as a free visual on the AppSource tab for everyone to use.

Does the developer get some sort of financial compensation for creating the product? Is there an average cost or a list of visuals and what they cost? Sorry if this is a silly question, but I would like to know if the developers of those visuals actually get paid for making them, and what is the process? Maybe you can share as link with the info. Thanks!

[Idrissshatila · Accepted solution]

Hello @E12345 ,

you can charge a subscription fee for people to use your custom visual.

there also this link that talks about custom visuals in store https://learn.microsoft.com/en-us/power-bi/developer/visuals/office-store

[dm-p · Accepted solution]

I'll provide some insight, as @smpa01 summoned me 🙂

When you publish a visual, you can specify whether it is paid or free. If it's free, you don't get any income, and it is expected that you will not offer any paywalls or paid content within the visual. It would likely cause you reputational damage as a vendor if you were to do this, as it would be seen as a bait and switch by users. You could provide details for people to sponsor your project through a suitable mechanism, e.g., GitHub sponsors if they feel it adds value for them and they wish to contribute somehow.

If your visual is intended to be "freemium" or paid, you submit it to AppSource using the Paid option and implement suitable gatekeeping of features and licensing in your visual to monetize it. Some folks will implement a licensing key system and handle the purchase and acquisition through their own site. Others might use the licensing API to handle the transactional side of things. Some might use both options.

Personally, I release all of my visuals for free, so I do not receive any remuneration for them, and I cannot provide any insight on how to implement either of the above options. I get nominal income via GitHub sponsors, which is just about enough for me to keep things like documentation websites and some other administrative needs going.

Awareness of your capabilities as a visual developer may lead to work opportunities where you can provide consultancy services, or a commercial vendor may see value in your skills and offer you work, and this is typically how I make an income from custom visual development. And this income effectively allows me to spend time developing and enhancing my visuals if I have a good month.

I personally don't think the licensing and transactability API is a suitable option for an independent developer as there are too many restrictions on where it can be used. In these cases, a separate licensing system would be required if you wish to service these use cases. It is effectively another acquisition channel for a visual developer.

[E12345 · Accepted solution]

dm-p,

Thank You so much for such a thorough and in depth reply! I am satisfied with the information you provided and will mark this reply as a viable solution. I do not intend to make or publish any custom visuals yet, but I was very curious about how they are monetised. Thanks again, and good luck in all your endeavors. 

[dm-p · Accepted solution]

I'll provide some insight, as @smpa01 summoned me 🙂

When you publish a visual, you can specify whether it is paid or free. If it's free, you don't get any income, and it is expected that you will not offer any paywalls or paid content within the visual. It would likely cause you reputational damage as a vendor if you were to do this, as it would be seen as a bait and switch by users. You could provide details for people to sponsor your project through a suitable mechanism, e.g., GitHub sponsors if they feel it adds value for them and they wish to contribute somehow.

If your visual is intended to be "freemium" or paid, you submit it to AppSource using the Paid option and implement suitable gatekeeping of features and licensing in your visual to monetize it. Some folks will implement a licensing key system and handle the purchase and acquisition through their own site. Others might use the licensing API to handle the transactional side of things. Some might use both options.

Personally, I release all of my visuals for free, so I do not receive any remuneration for them, and I cannot provide any insight on how to implement either of the above options. I get nominal income via GitHub sponsors, which is just about enough for me to keep things like documentation websites and some other administrative needs going.

Awareness of your capabilities as a visual developer may lead to work opportunities where you can provide consultancy services, or a commercial vendor may see value in your skills and offer you work, and this is typically how I make an income from custom visual development. And this income effectively allows me to spend time developing and enhancing my visuals if I have a good month.

I personally don't think the licensing and transactability API is a suitable option for an independent developer as there are too many restrictions on where it can be used. In these cases, a separate licensing system would be required if you wish to service these use cases. It is effectively another acquisition channel for a visual developer.

[smpa01]

This is an interesting topic; looping @dm-p  who can shed some light on this. I could be wrong but I doubt if you are financially compensated for giving an absolute free viz app to everyone except recogonition.

[Idrissshatila · Accepted solution]

Hello @E12345 ,

you can charge a subscription fee for people to use your custom visual.

there also this link that talks about custom visuals in store https://learn.microsoft.com/en-us/power-bi/developer/visuals/office-store