|Jan 20||Feb 3||Feb 24||Mar 16||Apr 6||Apr 27||May 18|
|Requirements definition & scoping|
|Brand and Messaging|
|Additional requirementsUnique Coding|
|Data processing and load|
(Staged introduction to customers)
This example timeframe takes a common SaaS white label configuration of the wine management platform, and presumes a small amount of additional requirements such as bespoke reporting or adding new parameters to existing functions.
It factors in an interactive, agile approach to refining the technical specification, applying the brand and configuring the platform (collection management, dashboard, landing wine, warehouse configuration, notifications and alerts and reporting.
It presumes simple integrations such as single sign on or a data feed into accounts. Deeper integration with background systems or APIs into CRM (depending on how the CRM is configured) is likely to require more time but is variable dependent on the nature of the integration.
Data processing, clean-up and load runs concurrently with the whole project and the sooner that work stream is started the better. Elapsed time depends on the size of the existing product database.
Implementations can take as few as 3 months from start to finish including testing, or less where there is little legacy data. More complex integrations or configurations for multiple sites will take longer.