EXPECTED DELAY FOR DATA ENTRY

 

As Toogo is structured around a database, before it can be used initial data must be entered.

This stage can be long and tedious; however, Toogo has been designed in such a way as to reduce this to a minimum, with as few obstacles as possible.

This is achieved notably due to the use of tools and practical functions:

• “Data importation” tool
  This allows for the migration of data (suppliers, clients…) directly from a spreadsheet (Excel format).
  > mass data importation with just a few clicks
• Standard pre-entry of multiple “parameter” fields
  As soon as you connect to Toogo, default parameters related to user profiles have already been set.
  > significant time savings during installation
• “Templates” function used for categories
  All the objects in the database (products, trips, clients, suppliers…) can be regrouped in categories which when entered define templates. These are essentially sets of data that will be automatically attributed to objects belonging to this category when they are created.
  > significant time savings when creating objects
• Generalization of the “copy” tools
  All of the objects in the database can easily be copied to serve as the basis of a similar object.
  > significant time savings for everyday use

 

In practical terms

 

Configuration of Toogo

This is the setting of initial parameters for Toogo using the data proper to each user: regions and places operated (location, description, photos); currencies and exchange rates; languages used…
Allow for 5 days of work (based on 7 productive work hours per day).

Object entry (products, suppliers, trips, clients)

Let us consider a medium sized, non-specialized receptive operator, operating only one destination, therefore approximately 1.500 objects distributed as follows:

• 1000 products (nights at hotels, meals at restaurants, guide services, transport, etc…)
• 400 suppliers (hotels, restaurants, guides, carriers, etc…)
• 50 standard trips
• 50 “institutional” clients (agencies, tour operators)

And let us allow for 10 minutes (on average) for entry of an object in the database.

To enter the entire set of objects, allow for 1.400 x 10 = 14.000 minutes,
> that is 250 hours,
> or about 36 days (based on 7 productive work hours per day),
> or about 7 weeks (based on 5 working days a week).

Total implementation completed

 

By 1 person: 8 weeks
By 2 people: 4 weeks
By 3 people: 3 weeks