cPanel plugin that generates monthly recurring revenue - feedback & beta testers wanted!

hansdesjarlais

I have been working on a project that will allow hosting companies to generate monthly recurring revenue from the listing & sales of WordPress themes.

I have built a cPanel plugin (cpAddon) which combines a WordPress auto-installer with a theme directory.

Instead of charging hosting companies a licensing fee to use my auto-installer, I will pass on a portion of the fees I charge theme developers to be included in the directory.

• Earn monthly recurring revenue* from the listing and sales of WordPress themes.
• Offset your cPanel license fee increases (due to recent price changes).
• Beginner friendly, simple & fast WordPress auto-installer.
• Reduce WordPress related support tickets (we provide links to documentation & tutorials for WordPress).
• Security minded - we set secure default usernames, passwords and database table prefixes.
• Clear & intuitive cPanel icon & title (so users don't have to search or ask support techs where to install WordPress).
• We only approve themes to our directory that meet our strict quality & security standards.
• Only the latest, stable version of WordPress installed (the plugin downloads the latest version directly from the WordPress.org repository and doesn't modify any of the core files).

Revenue: Fixed monthly earnings (TBD) per active cPanel account.

Details & demo available here https://github.com/ismaelyws/themely

I am currently looking to work with a small-ish (or medium) sized hosting company who is interested in installing and testing it out.

I need to determine how many theme downloads it will generate based on the number of cPanel accounts it is active on.

Essentially I need to figure out the math and if it will be attractive enough for hosting companies to want to use. Because if the numbers don't make sense there's no sense continuing.

If anybody is interested in working with me please respond to this post or use the contact information here https://github.com/ismaelyws/themely#get-helpsupport

Screenshot:
https://raw.githubusercontent.com/ismaelyws/themely/master/assets/themely-cpanel-screenshot.png

SirFoxy

webclouddev

@SirFoxy said:
![]

Wow dude you are woke

SirFoxy

@webclouddev said:

@SirFoxy said:
![]

Wow dude you are woke

they don't call me Joe Rogan for no reason btw have you ever tried dmt?

Dazzle

Man, I'm not offending your idea but when I read your post, the first thing pops on my head is this : https://www.zdnet.com/article/an-inside-look-at-wp-vcd-todays-largest-wordpress-hacking-operation/

Since you're the person controlling every themes delivered via Themely, how you'll respond if someone accuse you "may add backdoor" on themes?

hansdesjarlais

@D>; @Dazzle said:

Man, I'm not offending your idea but when I read your post, the first thing pops on my head is this : https://www.zdnet.com/article/an-inside-look-at-wp-vcd-todays-largest-wordpress-hacking-operation/

Since you're the person controlling every themes delivered via Themely, how you'll respond if someone accuse you "may add backdoor" on themes?

I think it would be quite a poor business decision and model if I allowed "nulled" themes into my directory. Hosting companies won't tolerate that which would essentially destroy the entire concept. Plus, just like WordPress.org and ThemeForest.net, I have a strict quality and security review themes must pass before they can be added into the directory.