As with any company that is committed eCommerce, there's a tremendous potential to grow revenue but it takes a base line investment in just overhead to maintain the site (similar to opening a retail store). Here's how a typical 20-hour plan/per month would break down. "Support" can include any or all the following items:
- General consulting about ecommerce platforms, tools, integrations and other related subjects
- Site coding and development
- Module installation
- Bug fixes
- Custom modules development
- Site speed optimization
- Integrations with additional third-party systems including ERP, marketing and fulfillment systems
- Security patch installation
- Site upgrades/updates
- Training on the use the platform and tools
Security patches on a fairly simple site generally range from 1 to 3 hours (there were 7 patches in 2018). https://magento.com/security/patches These are critical and required if we are hosting the site. They help to protect against credit card theft and other vulnerabilities. You will need these as well for PCI compliance.
Magento Upgrades: Average 3 to 4 hours per month.
Magento code version upgrades range from minor to "not so minor". On a site like yours these will typically not be too extensive each time but likely each quarter there will be update that needs to be applied. This means any 3rd party modules may also need to be updated. These typically happen quarterly.
Project Manager Collaboration: Average 4 to 6 hours per month based on 20-hour per month support plan.
Time your Project Manager spends reviewing tickets and working with you or development can be as little as 1 hour per week but it depends on the nature of the tasks and how much testing is needed.
Urgent or Unplanned Requests: Average 2 hours per month based on a 20-hour support plan.
Urgent or unplanned requests - In sites that are not too complicated there is usually not much required here each month. However, you might be setting up a new promotion in Admin and accidentally be giving product away for free. If you’re stuck, you will want your PM to get in there and fix it or show you how to fix it. Things like this happen and it’s good to leave a little buffer in the monthly planning for these unexpected items.
New feature coding and/or strategy planning:
This can be whatever budget you want to set. At 20 hours per month you would have 10 hours remaining each month. That might be sufficient if you’re not looking to roll out new features aggressively. During the Code Review we will lay out a roadmap so you can have a solid plan. This will also dictate the support plan level you may need.