1

Hello everyone!

Apologies in advance if this is in the wrong forum.

Short Version: What actual steps should I take to put together a case for SpiceWorks?

Example: Make a list of all the workstations that SpiceWorks was able to correctly identify vs what the current software can.

Longer Version:

My IT department started using a paid service desk application when I joined, about 6 months ago. About a month into the job, I decided to try SpiceWorks out, installing it on my local PC.

The paid service desk application had a financial module for purchasing, as well as asset inventorying. It is able to churn out reports, and is able to keep track of contracts.

All well and good, except Spiceworks is free, and does things so much, well, better!

I don’t have much experience with medium-sized companies (this is only my second job in my career of 2 years), and there are hierachies of management I will have to impress - how do I do that?

Thanks in advance for your response!

-Sandra

31 Spice ups
2

maybe show him how it works. log him into the dashboard and let him poke around for a little bit then show him some of the advance features like warranty scanning and comparing assets.

2 Spice ups
3

When you get a successful result let us know!!

I’ve been using SW for about 2 years I reckon and while I’ve convinced other support admins to use it for the inventory part, getting the rest of ICT and management to use it for helpdesk (inc portal) is my everest.

1 Spice up
4

Why is it hard getting them to use the Helpdesk? How much more information needs to be crammed into a “HELP IT TEAM I JUST BLEW UP MY PC” request??

1 Spice up
5

It’s been my experience over 2+ decades that cost almost always wins out.

How have you found Spiceworks? Found it easy to use? Do you find it intuitive? Do you think others will find it easy to use? Does it do what you need done? Have you been able to get answers to Spiceworks questions from the Spiceworks community?

Is the current help/service desk app up for licensing renewal? Are you about to pay for a module so that it will do what Spiceworks already does?

Which app has a quicker/shorter learning curve?

From the answers to the above questions, and I’m guessing, your enthusiasm for Spiceworks, take all that to the Boss or put it in a proposal and pass it on to them.

At the end of your proposal, don’t forget to remind them which app is FREE!

1 Spice up
6

what you could do is setup a dns pointer on you internal dns zone for helpdesk, or just help, and point it to your sw pc.

so in theory all what they have to do is open a web page and type in help or helpdesk and they are directed to the portal.

or setup and email for spiceworks like helpdesk@yourdomain.com to listen to.

1 Spice up
7

Pull out a couple of Spiceworks reports for comparison to the ones that are in the paid package. Put together a document with some screenshots of the paid for package and screenshots from Spiceworks showing how it is an improvement over the package you pay for. If the paid package is subscription based you might still be able to convince him to use paid Spiceworks as it is inexpensive to remove the ads and support the company if the. If the paid package is less expensive than the paid package or the paid for package was a right out purchase then tout the free part of Spiceworks very loudly. Last give him an admin login and let him try it out.

Essentially you wan to build a business case for switching to Spiceworks. This involves showing a need for the product (in this case better than the current package you pay for) and how it will enhance productivity and save the company money, or if not saving money showing the ROI of a product.

I think there are improvement that could be made to the Spiceworks HelpDesk m but for the price combined with the other features it blows its competitors away.

1 Spice up
8

These might help:

1 Spice up
9

#1 - don’t do anything that you feel is contrary to what your boss(es) would be OK with.

#2 if you think you are not crossing any lines then I’d just install it (good workstation is adequate), build a reasonable version of a help desk, let SW scan your network, generate some reports, get a few willing accomplices try out the Help Desk informally, and schedule a demo and pass out information.

Then let those that should make a decision.

3 Spice ups
10

I´m currently doing the same, convincing my boss to use spiceworks. Here are the steps that I did.

  1. Installed spiceworks

  2. Gave access to few admins such as sql admin, licensing admin. With that I got them on my side.

  3. Get a meeting with the boss to show him the awsome stuff that spiceworks do. Got the other admins to fill in some of the questions why they like spiceworks. When I got him on my side everything looks good.

  4. Now I´m waiting because other bosses in my company need to see the features that rock in spiceworks and get them on my side.

  5. The final step, implementing spiceworks to our network.

1 Spice up
11

Sandra8796 wrote:

Hello everyone!

Apologies in advance if this is in the wrong forum.

Short Version: What actual steps should I take to put together a case for SpiceWorks?

Example: Make a list of all the workstations that SpiceWorks was able to correctly identify vs what the current software can.

Longer Version:

My IT department started using a paid service desk application when I joined, about 6 months ago. About a month into the job, I decided to try SpiceWorks out, installing it on my local PC.

The paid service desk application had a financial module for purchasing, as well as asset inventorying. It is able to churn out reports, and is able to keep track of contracts.

All well and good, except Spiceworks is free, and does things so much, well, better!

I don’t have much experience with medium-sized companies (this is only my second job in my career of 2 years), and there are hierachies of management I will have to impress - how do I do that?

Thanks in advance for your response!

-Sandra

Sandra I think you said it all when you said "All well and good, except Spiceworks is free, and does things so much, well, better! "

That should be enough convincing unless your current application is doing something that Spice can’t. It was an easy sell for me when I approached my boss. We were using Numara TrackIT and spending alot of money.

1 Spice up
12

Gisli_Kerfisstjori wrote:

I´m currently doing the same, convincing my boss to use spiceworks. Here are the steps that I did.

  1. Installed spiceworks

  2. Gave access to few admins such as sql admin, licensing admin. With that I got them on my side.

  3. Get a meeting with the boss to show him the awsome stuff that spiceworks do. Got the other admins to fill in some of the questions why they like spiceworks. When I got him on my side everything looks good.

  4. Now I´m waiting because other bosses in my company need to see the features that rock in spiceworks and get them on my side.

  5. The final step, implementing spiceworks to our network.

Nicely done!

1 Spice up
13

Sandra8796 wrote:

Why is it hard getting them to use the Helpdesk? How much more information needs to be crammed into a “HELP IT TEAM I JUST BLEW UP MY PC” request??

Simple. Request Tracker was in place before I joined the company and while it’s an old version it’s the main used helpdesk. Before we had two HD systems, Request Tracker and an access database using forms etc. So one simply did requests and was serachable with a web interface while the other had the inventory bit in place. Now we only use RT as I’ve shown the benefits of SW as an asset tracker, the db was only updated manually so with the auto scanning of SW it’s more accurate.

Doing the migration to SW from RT is a project I need to set down and work on what the gains and losses are…

1 Spice up
14

John Rehill wrote:

Do you still have your pros & cons list from that migration? We’re trying to put together some documents for other people to use:

http://community.spiceworks.com/topic/129748

1 Spice up
15

Unfortunately not, the change from the DB to SW was done about 2 years ago now.

Another thing that’s slowing down the changeover to SW fully is that we are going through a domain migration from Server 03 w/ Exch 03 to a newly named domain with Server 08. However while the user accounts are migrated and new usernames are created the accounts are still linked the the Exch 03 setup on the old domain.Eventually another Exch 03 setup will be done for the new domain but until then every user account in the new domain has an email such as username@new.domain instead of their proper email address.

Once the final migration happens and everyone gets their proper email address associated with their account, the portal and helpdesk will (hopefully!!) go live.

1 Spice up
16

I have just done this exercise, performing a full proof-of-concept analysis including a SWOT analysis of our department.

First of all, I defined what we are trying to achieve:

Introducing and Implementing an Inventory Records Management System Proof of Concept.

This proof of concept project is an opportunity to demonstrate the capabilities of Inventory Records Management (IRM) software in a controlled manner. The pilot helps determine whether the software is appropriate for use by the Hardware teams and how easily it can be configured, providing hands-on experience for managers, specialists and other users.

This document applies the principles and “best practices” of IT project management to a proof of concept demonstration pilot for IRM whose purpose is to assess whether the solution should be deployed in the Hardware, Windows, *NIX and Solaris arenas.

The content table of the document is here, if it helps you in any way:

  1. Scope

  2. Introduction

  3. Reference Documentation

3.1 Applicable Documentation

3.2 Associated/Support Documentation

  1. DEFINITIONS, ABBREVIATIONS AND ACRONYMS

  2. CONSIDERATIONS IN THE PROOF OF CONCEPT

5.1 SWOT ANALYSIS

5.2 REQUIREMENTS

5.3 PROOF OF CONCEPT

5.4 CAPABILITIES OF THE SPICEWORKS IRM SYSTEM

  1. CHALLENGES

  2. SAFETY, HEALTH and ENVIRONMENTAL MANAGEMENT

  3. DATA INTEGRITY

  4. INFORMATION SECURITY

END

  1. DOCUMENT REVIEW TRACKING SHEET / APPROVAL / AUTHORISATION PAGE
1 Spice up
17

^ Cool.

.

To convince a boss, benefits over features is good.

Easy on the detail, rather (executive) summary(s) or bullet points are good to maximize time. Pointers to the details IT needs to know are good for the IT members, and the “next” IT guy.

1 Spice up
18

As an addition to the above comments:

IF you really want to impress the decision makers and demonstrate your expertise, be sure you present your proposal (formally written and formatted nicely) with ample justifications and reasons for each fact you present. In other words, don’t leave any “holes” in your justification document.

Also, concentrate on cost savings, the extensive support available, and improvements to efficiency.

1 Spice up
19

@Steve1990,

Do you care to share the outcome? Would you be open to sharing your document(s)?

Thanks

1 Spice up
20

My manager was my accomplice for our case with our VP. We basically did just what David9459 suggested. We installed it on a workstation, started running scans, generating reports, and creating and replying to tickets, and were able to “sell” it.

1 Spice up