Typical Implementation
Hub Implementation
Getting going with the Hub is simple and very quick. There are no upfront fees and data migration tools are available for importing product inventories, clients and suppliers. So you can get going immediately with a new business system designed ground-up for your business.
If you would like to plan a migration and need help from our specialists, we can work with you on a scope of work to meet your requirements. For example, if you are moving from a legacy system and need help understanding the database design in order to extract the right data, wish to import a large amount of historical information, or intend to move onto a new accounting package. Prices and timescales are on application.
Typical Implementation for enterprise wine management platform solutions
Hub Webshop and POS
Warehouse management
Inventory management
Private client reserves management
Self directed brokerage and consignment
Trading exchanges
| May 30 | Jun 13 | Jul 4 | Jul 25 | Aug 15 | Sep 5 | Sep 26 |
|---|---|---|---|---|---|---|
| Requirements definition & scoping | ||||||
| Brand and Messaging | ||||||
| Additional requirementsUnique Coding | ||||||
| Configuration | ||||||
| System Integration | ||||||
| Data processing and load | ||||||
| Testing | ||||||
| Production ramp (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.