Productize your agency by taking a SaaS-like approach
Quit the unpredictability of agency work. A product-based business model creates focus, synergy, and recurring revenue.
Isolated development, unified management and distribution. A product-based mindset solves all scaling issues, while focussing on the MRR that build a valuable business.
Tenant Snapshots
You can build, scale, and manage thousands of websites or web-products that look and act completely different, yet share the same functional core. How? Tenant Snapshots.
A WordPress-based SaaS
A SaaS-like approach to WordPress has to include Version Control, enabling an isolated development environment that can push changes to all your products at once.
Leverage the dominant cloud achitecture for SaaS
Build product-based WordPress solutions that compete with proprietary giants like Shopify, but are built upon an open-source ecosystem that is superior in every comparison.
No vendor lock-in. Client sites can easily be migrated to and from the platform
Leverage an easy to use cloud interface to build scalable WaaS solutions
Use your excisting WordPress skills. No additional skillsets are needed
Using WPCS, agencies can expand the retainer model over the entire lifecycle of a customer
These companies are already getting results.
Build a website product that automatically sets up everything that you would usually do manually.
Launch your product, and automate your WaaS as you continue to grow. Configure the API and new customers are automatically provided with their own website.
Yes, you can place a CNAME record in your domain registrar. This way, when customers sign up on your website you can provide them with a subdomain (example.com, subsite1.example.com, subsite2.example.com)
When customers are ready to launch their site, they can easily do so by changing their domain name. You simply have to add the main domain to the Tenant, Press verify and set it as the main domain. This can also be done using automations. We explain this in detail in our course.
Absolutely, we don’t have vendor lock-in. If one of your customers wants to leave, you can easily create an export of the website using the WP All in One Migration tool. If you want to leave, we will provide you with exports of your full stack at WPCS asap.
We are also working on the ability to download snapshots and tenant backups. This will allow you to host all the sites you have on WPCS on any traditional hosting solution.
It depends on what the SaaS/WaaS does. The most we can say is it won’t take much longer than if you’d build in WordPress elsewhere. We presume you also want to automate your business, which in total can amount to about a week. We include a full course after signing up for a trial.
We haven’t seen any plugins that are technically not supported so far. That being said, we do require plugins to ‘play nice’ with WordPress’ best practices. Especially when it comes to file management. Concretely: any plugin writing files must use the appropriate wp-content folder. (The path is found under the WP_CONTENT_DIR constant)
We enforce this rule as both a security measure and as a best practice to keep your development cycle orderly and sane. From there, however, plugins are free to write to disk as they wish. As for adding constants to the wp-config.php file, this is currently not possible.
We are working on allowing for tenant-specific constants to be defined before WordPress initialises. Until then, constants can only be defined in plugins or themes. If you have a specific case you’d like to discuss in this context, please let us know
