• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Erm as a_servicev2
 

Erm as a_servicev2

on

  • 633 views

 

Statistics

Views

Total Views
633
Views on SlideShare
633
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Objective of the slide: Engage the customer in a discussion about his situation and requirements. Important: Be informed if and which SwetWise solutions the customer uses. Also check their intensity of the usage Emphasize that this is a summary of customer feedback we gathered and consolidated into one summary. Start explaining the first situation and what that really means (impact) for customer. Then go to the next situation and impact Conclude with a question to initiate feedback: “ As I said this is a summary of customer feedback we have received. How would you compare your situation to this? With which situation would you agree the most or do do have a different situation? If customers describe there individual situation always ask what the impact is on their work or on others work. Take time and drill down to get a detailed picture of your customer’s requirement.
  • Objective:
  • Below you will find a quick guide that goes over what criteria customers could use when evaluating ERM systems. The way I’ve structured this guide is to first describe the concepts customers have to consider and make decisions on. As a second section I have turned these concepts into concrete items that can be used to evaluate an ERM system. The last section provides an overview of which criteria SwetsWise eSource Manager is a good solution for and which ones it is not suited for. Concepts to be Considered When evaluating which ERM system to purchase, there are several questions customers have to ask themselves and based on those answers are they able to effectively compare the different offerings in the market. This enables them to make a decision for the offering that best suits their needs.
  • When evaluating which ERM system to purchase, there are several questions customers have to ask themselves and based on those answers are they able to effectively compare the different offerings in the market. This enables them to make a decision for the offering that best suits their needs. The first basic question that a customer needs to answer is what they expect an ERM system to do . Different vendors have taken different interpretations of what an ERM system means. This results in the different providers having systems that can’t be easily compared with each other directly. In many cases, a bundle of services from one provider will be equal to a single service of another provider.
  • In the most expanded definition of an ERM system, these are the areas that the ERM system should cover:
  • For many customers, some of the elements of an ERM system are simply not relevant (e.g. trial process workflow management) due to their internal structure and needs. For this reason it is key for a customer to not simply ask for an ERM solution, but to identify which areas they are interested in. Identifying these areas should not be done with only the present in mind, but also what they think will be needed two or three years into the future. It can be that at the moment the customer doesn’t have a large portion of e-journals and therefore usage statistics analysis is less important. Although in three years time it could be that the vast majority of the collection is comprised of e-journals, where usage statistics analysis and price per use calculations will become very important. Or at the moment eBooks are not part of the collection, but will be in the future and will have to be managed in the same system
  • Based on the current and future areas of interest the customer can establish the criteria that a vendor has to satisfy. These criteria also have to determine which elements are the most important for them. This will create a basis for a direct comparison of the different vendor solutions. As part of this, the customer also has to have a preference for what type of “user environment” architecture they want. Are they satisfied with having different systems from different vendors for different areas or do they prefer to have one system that does everything? The user environment is a very important element that can be even more important than if certain functionality is available or not.
  • Customers shouldn’t forget that once they have purchased such a system they will most likely have to remain with that vendor/system for at least two years and in some cases even longer in order to obtain some return in their investment. For this reason they have to not only have an idea of what they will need in the near future, but also what the plans of the provider are for the future of their solution. In which direction are they planning on taking the service and will future updates be made available at no additional cost or will the customer have to purchased them in addition to the original service fee. Customers have to ensure that what they find important for the future is also what the provider thinks is important.
  • Advice: Give demo of the solution/functionality (live or with clickable demo) Relate to the needs and requirements of the customer while you present functionality and processes If applicable ask open questions if the audience is to silent Be flexible to show other elements if the discussion leads you to it
  • conclusion , there are three critical things a customer should do when evaluating an ERM system: Define what they mean by an ERM system Set the criteria for each area of what is important to them Calculate the TCO of the solution including the administrative maintenance cost of the system By undertaking these steps customers will ensure that they are truly comparing similar offerings and making their decisions based on objective and quantifiable information.
  • Concrete Evaluation Points Below is a list of points on which a customer can make comparisons of the different ERM systems based on the different areas an ERM system can cover. Workflow Management Pre-populated with publisher specific license process (e.g. does this publisher require a license and online registration) Can the customer easily add internal process steps to the process Status reporting available Users can indicate steps have been completed License Conditions Administration Which fields are automatically included Can customer add their own fields in addition to standard ones Are license conditions pre-populated with the publisher’s standard conditions Are standard publisher conditions automatically maintained by the system Can licenses for different content types be managed (e.g. journals, databases and eBooks)
  • Content Available in Resource Does the system automatically provide a listing of the publications available under a specific license of a specific provider Are the bibliographic details of the publications and the link with publishers automatically maintained by the system (e.g. will title moves or mergers be automatically updated in the system) Can the customer indicate either manually or via a file upload which publications they have that fall under the specific license Is the list of licensed publications, or databases, integrated with an A-Z list system for end user access (e.g. if the customer adds a publication to a license, or a new license, will these new publications automatically display in the A-Z list for end-users)
  • Usage Statistics Analysis Does the system automatically collect usage statistics information from the different electronic resources Is the customer able to manually upload additional usage statistics to the system Does the system automatically match the usage statistics with the cost of the subscription Is the system pre-populated with the cost of the subscriptions if they are purchased via the same vendor Can the customer upload cost information in different currencies Will the system calculate the price per use for both the individual publications as well as for an entire resource Can the customer create their own customized reports to suit their needs
  • Advice: Give demo of the solution/functionality (live or with clickable demo) Relate to the needs and requirements of the customer while you present functionality and processes If applicable ask open questions if the audience is to silent Be flexible to show other elements if the discussion leads you to it
  • Advice: Give demo of the solution/functionality (live or with clickable demo) Relate to the needs and requirements of the customer while you present functionality and processes If applicable ask open questions if the audience is to silent Be flexible to show other elements if the discussion leads you to it
  • Advice: Give demo of the solution/functionality (live or with clickable demo) Relate to the needs and requirements of the customer while you present functionality and processes If applicable ask open questions if the audience is to silent Be flexible to show other elements if the discussion leads you to it
  • Advice: Give demo of the solution/functionality (live or with clickable demo) Relate to the needs and requirements of the customer while you present functionality and processes If applicable ask open questions if the audience is to silent Be flexible to show other elements if the discussion leads you to it
  • Advice: Give demo of the solution/functionality (live or with clickable demo) Relate to the needs and requirements of the customer while you present functionality and processes If applicable ask open questions if the audience is to silent Be flexible to show other elements if the discussion leads you to it
  • Objective: Engage the customer in a discussion about his situation and requirements. Import: Get information if you customer has already seen presentations from our competitors Emphasize that this is a summary of customer feedback we gathered and which become our motivation to develop a solution to alleviate the usage management tasks for them. Start explaining the first situation and what that really means (impact) for librarians responsible for usage management. Then go to the next situation Conclude with a question to initiate feedback: “ As I said this is a summary of customer feedback we had received. How would you describe your situation compared to this? Are there other situations/requirements your are missing?” If customers describe there individual situation always ask what the impact is on their work or on others work. Take time and drill down to get a detailed picture of your customer’s requirement
  • Está integrada en SwetsWise, en la pestaña de informes.
  • Podemos recoger automáticamente información de los títulos suscritos con SWETS y también de otras plataformas no necesariamente suscritas con nosotros. El sistema es flexible.
  • Información de cada título y de las plataformas a través de las que está incluido.
  • También tenemos una visión general de las plataformas: plataformas en las que nosotros recogemos estadísitcas y plataformas añadidas manualmente.
  • Hemos visto hasta ahora la gestión de datos. Ahora vamos a ver la creación de informes. Ofrecemos informes counter, pero lo más novedoso son los informes personalizados: percio por uso, análisis de tendencia y los informes personalizados, que permiten adaptar todos los campos a las necesidades de cada organización: tan solo unas plataformas determinadas, por materias, solamente un periódo de tiempo determinado, añadir y quitar información, etc.
  • This presentation is a presentation for customers Objective: Your customer should be motivated to built a business case (opportunity) with you or at least gives you a clear sign of no interest at all (exit) Important Make sure that you invited the right people to the presentation. If they are to distant from license management tasks and responsibilities, do not present at all. Find out who is you right contact persons.
  • Objective: Engage the customer in a discussion about his situation and requirements. Import: Get information if you customer has already seen presentations from our competitors Emphasize that this is a summary of customer feedback we gathered and which become our motivation to develop a solution to alleviate the license management tasks for them. Start explaining the first situation and what that really means (impact) for librarians responsible for license management. Then go to the next situation Conclude with a question to initiate feedback: “ As I said this is a summary of customer feedback we had received. How would you describe your situation compared to this? Are there other situations/requirements your are missing?” If customers describe there individual situation always ask what the impact is on their work or on others work. Take time and drill down to get a detailed picture of your customer’s requirement
  • Objective: Gather all information to scope the opportunity The questions are specified on license management purely. You can add other questions depending on your approach. For example if you are going to offer our services as an ERM solution than you need to formulate additional questions
  • Objective: Gather all information to scope the opportunity The questions are specified on license management purely. You can add other questions depending on your approach. For example if you are going to offer our services as an ERM solution than you need to formulate additional questions
  • Advice: Give demo of the solution/functionality (live or with clickable demo) Relate to the needs and requirements of the customer while you present functionality and processes If applicable ask open questions if the audience is to silent Be flexible to show other elements if the discussion leads you to it
  • Advice: Give demo of the solution/functionality (live or with clickable demo) Relate to the needs and requirements of the customer while you present functionality and processes If applicable ask open questions if the audience is to silent Be flexible to show other elements if the discussion leads you to it
  • Objective: Create a business case for the customer Based on the results of the opportunity identification and scoping phase you can create the final business case to justify the purchase of SwetsWise eSource manager Again, this is a great opportunity to involve the customer in building its own business case! The business case creation is divided in 2 essential parts: Evaluation of the impact of the current situation on the customer Comparison with the situation where SwetsWise It is essential that the business case is explained to the customer – iterations might be needed

Erm as a_servicev2 Erm as a_servicev2 Presentation Transcript

  • ERM SOLUCION COMO SERVICIO Guido Smallegange Santiago 5 agosto
  • Que es lo que dicen nuestros clientes? Algunos clientes no disponen de herramientas eficientes para la gestion de sus recursos electronicos. Tampoco encuentran soluciones faciles de usar Gastar mucho tiempo en gestionar recursos electronicos y falta de overview unificado (acervo, financiera, licencias) Algunos clientes no quieren adquirir solución software debido al costo elevado inicial y pagos e mantenimiento No se toman decisiones y el potencial identificado no puede ser aprovechado Situación Impacto Algunos clientes no quieren lidear con la complejidad de ERM seleccion y proceso de implementacion Nada cambia, perdida de oportunidad para mejorar
  • Que significa para usted un ERM? Beneficios Valor
    • Una solución modular con las herramientas para gestionar sus eResources en su ciclo de vida completo y proveer acceso intuitivo para sus usuarios
    • Pre Populado con todos los detalles de su coleccion (holding) incluyendo licencias, reportes financieros. Permite personalización
    • Software on demand Implementación rápida. Acceso inmediato y uso
    • Actualizaciones frecuentes con mejores continuas basado en retroalimentación de los clientes
    Incremento productividad Mayor control Mejor valor de su inversión
  • ERM como servicio – Agenda Guia Rapida criterios que podran utilizar evaluando sistemas ERM
    • Descripcion conceptos que tienen que considerar y tomar decisiones en base a ellos
    • Usar conceptos en puntos de accion que puede ser usados para evaluar sistemas ERM
    • Evaluacion criterios ERM Swets
  • I) ERM Conceptos a Considerar
    • pregunta basica: que espera de un ERM
    • Cada proveedor tiene diferentes interpretaciones
    • No se pueden comparar diferentes sistemas
    • Comparando uno con otro, combinacion de servicios de un proveedor = servicio unico
  • ERM como servicio – consideraciones
    • Definicion mas amplia ERM system:
    • Gestion de flujo firma licencias
    • Administracion Condiciones Licencias
    • Manejo de que contenido esta disponible bajo licencia
    • Gestion de flujo trials
    • Analisis estadisticas de uso
    • Precio por Uso
    • Listado A-Z de todas las publicaciones con enlaces al contenido actual
  • ERM como servicio – consideraciones
    • Para muchos, algunos elementos no son relevantes (gestion de flujo trials)
    • Indentificar areas de interes, no solo solicitar sistema
    • Pensar en migracion a e-, estadisticas de uso creceren en importancia (costo por click)
    • Tambien eBooks pueden no ser parte de la coleccion actual pero si lo seran, tendran que ser manejados en mismo sistema
  • ERM como servicio – consideraciones
    • Basado en interes actual/futuro , establecer criterios que proveedor tiene que cumplir
    • Estos criterios determinan cuales le importan al proveedor
    • Solo esto crea base para comparacion real entre diferentes soluciones de proveedores
    • Que tipo de “user environment” architecture requiere el cliente?
    • Diferente sistemas de diversos proveedores para areas diferentes vs un sistema que hace todo?
    • Entorno del usuario muy importante que hasta puede ser mas importante que el sistema teniendo una funcionalidad especifico o no
  • ERM como servicio – consideraciones
    • Comprar o ‘ alquilar’ ?
    • Atado con proveedor minimo 2 anos y mas para obtener retornos a inversion
    • Por eso, no solo conocer propio futuro pero tambien el del proveedor
    • Que desarrollos futuros/ actualizaciones/ costos adicionales
    • Asegurar que percibida importancia =importancia proveedor
  • ERM como servicio – consideraciones
    • hosted solutions: reducido operabilidad vs local
    • PERO tomar en cuenta TCO
    • Locally installed TCO alto, infraestrtuctura IT, hardware, software etc
    • En TCO incluir costo implementacion, admin
    • Mayoria sistemas ERM caja abierta que necesita de llenarse con data cliente
  • ERM como servicio – consideraciones
    • Conclusion : 3 criterios para evaluar ERM sistema:
    • Definicion cliente ERM
    • Definir criterios para cada area para saber que es importante
    • Calcular TCO de la solucion incluyendo admin costo de mantenimiento
    • Estos pasos aseguran que hay comparacion verdadera y justa de ofertas para toma de decisiones objectivas y cuantificables
  • II)ERM como servicio – Puntos Concretos Evaluacion
    • Workflow Management (gestion de flujos de informacion), proceso firma licencias
    • Pre populado con especifico proceso licencias de editor (editor requiere licencia/ registro online?)
    • Puede cliente agregar procesos internos al proceso de manera facil?
    • Reporte de Estatus disponible?
    • Usuarios pueden marcar pasos completados
    • Administracion de Condiciones de Licencias
    • Que campos se incluyen automaticamente?
    • Puede agregar propios campos aparte de los estandares?
    • Licencias estan pre populadas con las condiciones estandar del editor?
    • Se actualizan automaticamente las licencias estandares de los editores?
    • Se permite gestionar licencias de diferente tipo de contenido( jrnls, ebooks, paquetes etc)?
  • ERM como servicio – puntos de evaluacion
    • Contenido disponible en diferentes recursos
    • El sistema provee automaticamente listado de publicaciones disponibles bajo una licencia especifica de un proveedor especifico?
    • Detalles bibliograficos de publicaciones y enlaces con editores actualizados pro el sistema? (ej: titulos cesados, fusiones etc)
    • Puede bajar en un listado (manualmente o con file upload), que publicacioens tiene bajo una licencia especifica?
    • El listado de publicaciones bajo licencia, o bases de datos, integrado en su AZ listado para usuarios finales y su acceso (e.g. si cliente agrega agrega publicacion a licencia, o nueva licencia, los nuevos titulos aparecen de manera automatica en listado AZ del usuario final?
  • ERM como servicio -puntos consideracion
    • Analisis Estadisticas de Uso
    • Sistema recolecta de manera automatica estadisticas de uso de diferentes fuentes electronicos?
    • Puede manualmente subir estadisticas adicionales al sistema?
    • Sistema puede cruzar estadistica de uso con costo suscripcion?
    • El sistema esta prepopulado con el costo de suscripciones si se adquieren a traves de otro proveedor?
    • Puede subir informacion de costo en diferentes monedas?
    • El sistema calcula precion por uso para tanto la publicaicon individual como el recurso entero?
  • ERM como servicio – puntos consideracion
    • A-Z Listado
    • El sistema provee un listado AZ para usuario final para que accede publicacion adquirida?
    • Puede AZ listado mostrar cualquier tipo de formato disponible (e.g. revista impresa, electronica, eBooks, base de datos
    • Permite en listado agregar informacion adicional para el usuario final
    • Se actualiza la informacion bibliografica para las publicaciones disponibles en el listado?
    • Implementacion y Mantenimiento
    • Hosted vs instalacion local
    • Promedio tiempo de implementacion desde compra-uso final admin
    • Cual es Tco?
  • III) ERM como servicio – ERM Swets Workflow Management proceso firma licencias-sw subscriptipons  - Simple License Workflow Process  - Pre-populated with publisher specific license requirements  - Customer can easily add steps to process  - Basic status reporting     - Extensive License Workflow Process Support X - Fullly customizable workflow process X - Extensive workflow reporting and reminder system X     - Trial Workflow Process X             License Conditions Administration esource manager   - License Conditions Pre-populated with publisher standard conditions  - Standard publisher conditions automatically maintained  - Customer can add additional fields that are tracked per license  - Licenses for different content types possible (e.g. e-journal and eBook)  - Customer can customize conditions of licenses     
  • ERM como servicio – componentes Content Available in Resource esource manager   - Publication list per resource pre-populated  - Customer can indicate which publications are actually part of license  - List of publications customer has is automatically maintained  - Publication list per resource automatically maintained  - Bibliographic details of publications automatically maintained  - Publications included in licenses automatically displayed in A-Z listing              Usage Statistics Analysis (via SwetsWise Selection Support)   - Automatic collection of usage statistics  - Customer can manually add usage statistics  - Pre-populated with cost of subscriptions  - Customer can manuall add subscription cost information  - Price Per User calculation on both publication and resource level  - Customer can create customized reports  - Customer can take advantage of predefined reports 
  • ERM como servicio – componentes A-Z Listing (via SwetsWise Title Bank)   - Integrated A-Z listing for end users  - A-Z listing can display all content available (e.g. e-journal and eBook)  - Customer can add data to be displayed to enduser  - Bibliographic details of publications are automatically maintained              Other Considerations   - Single user ID and password to maintain all information  - Vendor hosted system on subscription basis  - Locally installed system X - System customization possibilities X    
  • Total cost of ownership (TOC) - ejemplo
  • ERM como servicio –SWETS ERM
    • • SwetsWise Library Edition = workflow management
    • • SwetsWise eSource Manager= license conditions+content available
    • • SwetsWise Selection Support= usage statistics
    • • SwetsWise TitleBank= AZ listing
  • SwetsWise Subscriptions Library Edition= workflow management
    • Información sobre el estatus del proceso de activación del acceso electrónico
    • Información de los requerimientos de la licencia antes de ordenar
    • Historial detallado de reclamaciones e información del estatus para rastreo
  • E-Acces Activation
  • E-Acces Activation
  • SwetsWise Title Bank AZ
    • Beneficios:
    • Punto único de acceso a su colección completa
    • Enlace a todos los recursos disponibles del cliente.
    • Acceso directo al texto completo de los títulos ubicados en SWOC y administración automatizada.
    Solución que le permite crear una lista única personalizada de todas sus suscripciones y enlaces hacia donde podrán tener acceso completo los usuarios.
  •  
  •  
  • Analyze. Compare. Decide. Usage statistics
  • Selection Support (estadisticas) Que dicen los clientes Cliente tiene que bajar estadisticas de uso de cada editor Time-consuming to retrieve reports and consolidate usage statistics Estadisticas de uso y informacion de precios estan separados Time consuming and difficult to match those decision parameters manually Situacion Impacto No hay solucion pre-populated para crear reportes consolidados Difficult process to create reports to support informed collection decision
  •  
  • Propósito del servicio
    • SwetsWise Selection Support integra las estadísticas de uso y los datos e información sobre sus revistas+bases de datos en una sola plataforma de gestión, suministrando información relacionada con el uso y valor de su colección.
  • Primer paso: Ver sus títulos y plataformas
    • SwetsWise completa de forma automática el listado de títulos que tiene a través de nuestra plataforma
    - Navegue, busque y elija entre todos los títulos, su precio para el año en curso y el uso del contenido online. -Vea todos los títulos suscritos a través de SwetsWise & ScholarlyStats de forma automática -Pinche en un título para acceder a la página de detalles.
  • Información detallada para cada título Dispondrá de ocho campos para clasificar el título, incluyendo la categoría temática y el campo de “comentarios adicionales” Listado de las plataformas en qué está incluido este título, precio y uso.
  • Su colección de plataformas Selection Support ofrece una visión de sus plataformas y de los informes disponibles para las mismas seleccionadas: Pinchar sobre el título para introducir información para logarse en la plataforma – Selection Support la va a necesitar para obtener sus estadísticas de uso!
  • Tercer paso: !Crear Informes! Ahora, usted puede seleccionar entre las diferentes clases de informes disponibles y/o crear sus propios informes personalizados!
  • Ejemplo de informe: Gráficos
  • Price Per use Report
  • Trend Analysis Report
  • SwetsWise eSource Manager
  • Que dicen nuestros clientes Licencias de editores varian mucho (condiciones diferentes, politicas y derechos) La situación legal acerca del uso de los productos e- no siempre es del todo claro Mayoría de las licencias estan disponibles unicamente en impreso y/o almacenados en diferentes sitios Bibliotecas dedican mucho tiempo a digitar licencias, importarlos y luego conectarlos con los recursos Gasto tiempo en buscar y actualizar licencias lo que por ende se hace muy poco Tiempo valioso perdido con tareas admin en vez de atender usuario Situación Impacto
  • Preguntas Cualitativas
    • LICENSE CONTENT ADMIN+ CONTENT AVAILABLE IN RESOURCES
    • Cuántas licencias de recursos e- tienen en su biblioteca
    • Cuántos Licencias maneja usted mismo?
    • Cuánta gente gestiona el resto de las licencias?
    • Cuales son las tareas en gestionar licencias (actualizar, revisar, importar, conectar)
    • Cuanto tiempo ocupa esa tarea? (por mes /hora etc)
    • Cual es el impacto de NO tener un overview de todas las licencias?
    • Dado el crecimiento en recursos electronicos, cree tener que lidiar mas con licencias en el futuro? Cuanto y para cuando?
    • Qué le gustaría hacer que no fuera gestionar licencias y porqué?
  • Que es eSource Manager
    • desarrollo propio de Swets que le permite:
    • Almacenar en un solo sitio todas las licencias de sus recursos electrónicos. Usted las puede personalizar según usted negoció con el editor si este no es el estandar.
  • Base de Datos Pre Populado de Condiciones Estandares Detailed information on 45 fields of more than 850 standard publisher’s licenses automatically maintained for your convenience
  • Base de datos pre populado de Publicaciones Predefined lists of publications available within a resource
  • Informacion actualizado Publications automatically added to your resources when they are purchased via SwetsWise Bibliographic data automatically maintained for all publications including title moves, publisher acquisitions and mergers
  • Crear tus propios campos Add your own fields that are included in every license available in your account. You can add 5 free text fields, 10 y/n fields and 5 selection menus.
  • Agregar Licencias Add licenses and resources by either searching the database of standard publisher licenses or by typing in everything manually
  • Incluir propio proceso gestion de flujo de trabajo Include up to 5 steps in the license process to reflect your internal workflow Keep track of the status of the process and view when a step has been completed
  • Vision General de todas las fuentes y su estatus View the complete list of your resources in one clear listing Providing you a clear overview of the status of each resource quickly and easily Quickly view all the publications attached to a resource
  • Reportes Download all the details of your licenses or the list of publications included in the resource Schedule the reports to be run automatically at the frequency you require
  • Master your electronic resources
  • ERM como servicio RESUMEN –SWETS ERM
    • • SwetsWise Library Edition = workflow management
    • • SwetsWise eSource Manager= license conditions+content available
    • • SwetsWise Selection Support= usage statistics
    • • SwetsWise TitleBank= AZ listing
  • SWETS ERM- Inversion
    • • SwetsWise Library Edition = workflow management
    • gratuito
    • • SwetsWise eSource Manager= license conditions+content available
    • usd 5,000
    • • SwetsWise Selection Support= usage statistics
    • A partir de usd 3,000
    • • SwetsWise TitleBank= AZ listing
    • A partir de usd 1,500
    • Total + bundle discount usd 6,375 (25% precio consorcio min 5 participantes)
  • Creating the business case