| 16 | | 4. **CUSTOM-WORKS TO PLUGIN & STATS OF "TYPICAL WP PLUGIN BUYER" IN 2019**. By taking an example of mine Reservations plugin sold on Envato for ~2000 times, I can say, that only 15 people of those 2000 (less than 0,1%) had no idea of what they doing - meaning they tried to upload plugin as a theme, or whole package ZIP, not just the plugin's ZIP. 500 customers (20%) were individual developers, doing the website for their customer - they really did cared about security, and scalability-ensuring patterns (like BCNF-database structure and MVC). Then the majority of customers - 1500 customers, where the **Agencies** (with 3-10 employees, of whose 1-8 were developers), who are doing websites for their end-customers, which is often is medium to enterprise companies (100-1000 employees). 50% of them did **custom-works** to the plugin. And they bought the plugin just because they **can do the custom works** with it. Meaning they needed the **MVC**, **S.O.L.I.D.** and plugin support for **Unicode CLDR** (Key=>VALUE pairs) to add the Geo-Data in their language i.e. country names, city names, phone area names and so on, on what they are working, and they changed the plugin's behaviour to fit their medium/enterprise business customer needs, i.e. a business rule, that if object is rented in state X, for a Y days, and it was returned before the noon, then do not charge additional day costs - the rules that you cannot predict by filters or hooks - or you would need 100,000 filters and hooks support and 1 million pages documentation for all them. That would not work for the larger business, as nobody would want to learn now to hook to and what is the filter names of each bigger plugin. |
| | 16 | 4. **CUSTOM-WORKS TO PLUGIN & STATS OF "TYPICAL WP PLUGIN BUYER" IN 2019**. By taking an example of mine Reservations plugin sold on Envato for ~2000 times, I can say, that: |
| | 17 | a. **Only 15 customers of those 2000 (less than 0,1%)** had no idea of what they are doing - meaning they tried to upload plugin as a theme, or whole package ZIP, not just the plugin's ZIP. |
| | 18 | b. **500 customers (20%)** were individual developers, doing the website for their customer - they really did cared about security, and scalability-ensuring patterns (like BCNF-database structure and MVC). |
| | 19 | c. **1500 customers (75%)**, where the **Web-Development Agencies** (with 3-10 employees, of whose 1-8 were developers), who are doing websites for their end-customers, which is often is medium to enterprise companies (100-1000 employees). 50% of those adencies did **custom-works** to the plugin. And they bought the plugin just because they known **how to do the custom works** with it, withouting learning anything new. Meaning they needed the **MVC**, **S.O.L.I.D.** and plugin support for **Unicode CLDR** (Key=>VALUE pairs) to add the Geo-Data in their language i.e. country names, city names, phone area names and so on, on what they are working. So they changed the plugin's behavior to fit their medium/enterprise business customer needs, i.e. a business rule, that if object is rented in state X, for a Y days, and it was returned before the noon, then do not charge additional day costs - the rules that you cannot predict by filters or hooks - or you would need 100,000 filters and hooks support and 1 million pages documentation for all them. That would not work for the larger business, as nobody would want to learn now to hook to and what is the filter names of each bigger plugin. |