4 Disciplines of MSP Service Development

One of the most under-appreciated success factors of an MSP is its capacity to develop services. We’re the purveyors of Managed Services; there are hundreds in the repertoire of any given MSP. This keeps us busy - going from concept to a product that can be sold and delivered is a long road. While product based companies have a process for product development, we service companies too often overlook the value in this powerful business practice, where all our innovation, differentiation, profitability and growth can be formulated in advance.

The trend of fragmentation in services - into verticals, delivery tools, integrations - just multiplies the need for planned process.

The usual development process for managed services providers is to do a project - develop something that solves a problem for (and with) a specific client and standardize it later. This can lead to long term future revenue, but without a clear process mixing up service development and the real revenue generating activity of the company will not only kill our internal productivity, but likely our relationship with the client, if everything they see is always in beta testing.

Let’s identify some basics to ensure our process is better than the average and pull ahead of the competition.

1. Value Proposition

The first important aspect of the service development process is the proper Value Proposition. We’re always ready to sell gadgets, tools and things we can use to solve something. Finding the problem it can solve usually comes second - “Hey, we have a Mobile Device Management feature in the RMM tool! Great, let’s sell it to clients.”

This is the approach of the average and uninspired MSP. If we instead use the Value Proposition Canvas, we start by understanding the client’s problem before designing the service itself.

We seek to discover things the client wants to get done, the obstacles in their way, and the results or gains they hope to get. This is the right hand side of the canvas. Then we can design the service value proposition on the left to solve the problems and the deliver their requested results. We build a bridge connecting their issues with the benefits of our services. Lastly we craft the service description itself.

Let’s see a Value Proposition canvas for the Slack and vCIO services to see how it works in real life. We even have a complete blog post for that one.

In that sense we know in advance precisely the mission of the service - why the client needs that - so if we develop it further all marketing, sales and delivery efforts will be aligned.

Development will also be made more agile. For example we’ll be deploying different maturity versions of the service. The first instance of Mobile Device Management may only cover basic functions like wipe and remote deployment, but later will be covered with BYOD policies and internal compliance.

We may even find we cannot solve the problem, or the problem isn’t actually worth the effort and expense, and we can drop the service development fairly early, so we and the client can both invest our time in better pursuits.

2. Demand Generation

The second step is to create some Demand Generation materials. I know...how can anyone not want to pay for our obvious expertise? We have the skills, but the customer inevitably makes the buying decision. If we can’t explain the service and its benefits clearly, we can’t drive demand and there’s no reason to proceed or invest further.

We have to learn fast, and active materials are best at getting quick feedback on our thoughts. Sending a one pager is not interactive - it won’t have the specifics - which feature is the most important, for example. Graders are great tools for asking questions about the problems clients have with a particular issue and actually measuring our marketing effort, the copy, the delivered benefits and interest.

Demand Generation is part of the Service Development process, not something marketing folks do after we finish. It gives us real-time feedback and clear understanding of what really needs to be solved, a crucial objectivity to the process to make sure we develop the service for the client and not for the engineer.

3. Sales 

Pricing and packaging is a big deal for services too. 

• Is the service included in an MSP package or stand alone? 
• Does the service have tiers, or should we scale it with GB, user, device?
• Does the service has a definitive process such that we can price based on the resources we put into it?
• Is it an open, listed price or customized per proposal?
• Do we sell it directly or through the account manager?

Again this is can’t wait until after the development process; it is part of it. We have to go out and test our assumptions. We can take a little advantage of our “early adopter” companies to go through experiments. We need the clearest understanding possible of all aspects before we scale.

Sell the service to the early adopters without a price tag. The goal is to find out whether they see the value without any price attached. Once we confirm the need we can find the price they will pay for the solution. In this case we can measure the value and the price independently. If the value isn’t compelling it won’t need to proceed to a price conversation. If it is a value, then we specify everything, and then create the perfect solution that both works and fits their actual budget.

To early adopters we can always offer a discount in exchange for their participation. We can get marketing contributions like testimonials, interviews etc. We can ask for contribution - content samples, real life data for presentations, and we for a flexible delivery schedule. We’ll only help ourselves if we state the discount clearly up front.

4. Delivery Processes

The last piece of the service development process is the Delivery Process definition. Usually we don’t consider this part from the beginning, but rather on an ad-hoc basis.

We start services sometimes as one time projects. A client needs something and we bring it to them as a project - making the common mistake of failing to look forward. We do so much to make one individual project come true, when we should treat every project as though it will become a repetitive service, so we generate service delivery process prototypes during our project work.

Therefore we’re going to need a quick service delivery prototyping tool. We’re going to use it to create service processes in real life and be able to reuse the materials later. Many people use Project Management or Process Management planning tools to create a project plan, or a process description. These are good for when we create documentation, but aren’t flexible enough and lack the feedback from real life as discussed above.

The best way is to fire up lightweight project management tools like Basecamp, Asana, Teamwork, etc. These have the flexibility for a prototyping situation (for instance your PSA’s project management is too robust, not flexible, lacks collaboration), and allow testing in the real world. You can open a workspace and quickly input the process deliverable items. Templates, Excels, Word docs, notes, todo lists, and everything else you think you need. As you start working on the project you’ll see a refinement of your efforts. Later of course, as we finish the project we can reverse the process, moving those todos and templates and deploying to a robust professional services automation when our goal is no longer flexibility but performance and efficiency.

Let’s put it together

To recap, create the Value Proposition, and test it internally first with broad (vague) definitions, then move forward with interactive Demand Generation materials to define the ideas more clearly, create Sales materials and scenarios of the Pricing and Packaging, then create agile Service Delivery processes.

We’re going to separate Production from Development. The development folks are going to hand hand off their work to the production team to deliver it. In the case of a small MSP we can at least separate the process virtually, if not physically.

As we need to be developing more and more services it will become harder to keep ahead of the curve without a solid Service Development process. Consider the services you’ve put together already, and how they’ve developed in terms of these four stages. It’s never too late to implement proven techniques.

How Slack app can be a revenue generator for your MSP

Last week we went through how we can stop giving out free advice and making consultation a revenue generator. Let’s see that in practice. Our example today is Slack app, the latest silicon valley unicorn (1B+ valuation). Slack, in most cases, is a free tool designed to enhance your internal communication. So how can we as cloud service providers deliver value and earn revenue with this great tool.

Customer Segment Profile

First, we need to understand a problem most of our clients have. The sector of the industry we’re focusing on now is companies whose teams work together on processes, projects, and collaborating with both vendors and clients.

Jobs to be done: Like so many other aspects of modern life, most of them need to deliver more value with fewer resources.

Pains: Typically they communicate over email, getting 100 or more emails a day, without a clue as to how to handle this volume. They cc each other excessively just to keep everyone in the loop, and use a host of applications like Project Management, CRM, plus service automation, and so on. Even these are mostly cloud based, with no integration, so every one of these systems needs to be checked separately if they want the whole picture.

They’ll also try out new apps on a weekly basis in their search for solutions, install a few, run the 30 day trial, all while not having the time to properly evaluate them - and like Sisyphus’ rock they keep finding themselves at the bottom of the hill again.

Gains they are looking for: They want an overall improvement in their communication each other, vendors, and clients, so they can focus on their work instead of emails, and would love to get answers, reasonably quickly, from a system, application, or from each other regardless of location - in the car, office or at home.

But they’re already too busy...the last thing they need is the added task of creating this solution. What’s missing is someone to listen to their issues, understand them, figure a solution, and then not only implement it, but also train their people and support them in the learning curve so that they can get back to the business of their business.

We’ve observed that this is quite typical. even though we know the tools are out there...they just don’t get used or aren’t implemented and trained properly. That’s nothing new to us in IT: Owning tools is easy...finding the right one and using it properly is another matter.

Value Proposition Map

Discover how Slack with the proper consultation and implementation can help them achieve this communication improvement.

Gain Creators: As a product Slack helps teams communicate within a single space. This can happen in private channels, one to one communication, public channels, you name it, and it can manage topics according to need. It also integrates with thousands of applications, and so ususally gets the sought after information from disparate sources without logging into those applications. In essence it creates a unified platform for company-wide communication and replaces internal emails almost completely.

The tool is the first step. Also required however is the creation of the business case, context, and the process to properly implement it, training users, creating basic policies and enrolling the entire team and the company overall. Of course we could leave them to do all this on their own, but our value proposition is to make this process successful from the get-go. This is actually more important than the tool itself.

Pain Relievers: Teams are now working in all kinds of venues and access the information from a myriad of devices, anytime, and anywhere. They always have to share files and documents with each other. Even with cloud based file sharing it’s a time wasting task - to copy / paste the links, then use another app to send. Another problem is after sharing, nobody’s aligned on where the file came from, and have to re-check the email to access it again. Slack eliminates this speed-bump entirely, leaving the file in context, and with its robust search engine, one can find it easily with any other system of communication.

Still, most users will have questions, and Slack doesn’t have real one-on-one support that incorporates an understanding of their business context...it’s rather more general help on features. Our support can fill this gap. We’ll often be able to offer our technical skills in integrating many other applications into Slack - a not so obvious task. We can be the ones to make those integrations work and enhance them over time.

Product & Services

The ultimate solution for the opportunities / problems of the client is a Slack Implementation Project.

• Needs assessment
• Project kickoff
• Implementation
• Project management
• Training
• Documentation

Because this implementation project is largely common among all who would have it, it can be templated easily, so from our perspective is streamlined. A Slack implementation project in this sense with initial consultation, implementation, technical set up, training and initial support can fall into a $2500 - $3500 range. It leads to an additional MRR for support and subsequent enhancement projects.

Marketing/Sales

The best way to market this is with an eBook or a Grader. You can see an example of a Slack grader here. It asks the following questions from the client:

We can quickly score their answers and see whether Slack can be useful to them to show, try, and implement. It can lead us to a quick product tour and a kickoff meeting for the needs assessment.

Delivery

The delivery part is a canned project with

• Project Plan
• Process descriptions, hints and tips
• Pricing and packaging document, contract, agreement
• Task lists for the milestones
• Tasks for the necessary deliverables
• Meeting memos, agendas to manage the project efficiently
• One-page checklists for the discovery meetings
• Presentation decks for education/training
• Basecamp.com live client facing workspace with everything necessary to facilitate smooth communication with the client

Conclusion

Slack is a great tool, and boosting the tool with our implementation services is a big hit. Clients will understand that we’re no longer just a general infrastructure service provider but a real business ‘wingman’ or ‘wingwoman’ for them with respect to the creative use and implementation of technology solutions. It ushers us into the trusted advisory role and helps us reframe our clients to see that IT is not just cost-savings, but a huge competitive advantage.

The Fall of the Era of Free IT Advice

Many IT managed services providers (MSPs) and internet telephony service providers (ITPs) are suffering the challenges of charging for IT consultation. The IT industry has taught its customers that we sell big expensive boxed packages that come with free consultation, placing the value in the big boxes and none in the advice. There are no big expensive boxes anymore, but still the advice remains free. However a systemic shift is taking shape finally reversing this conundrum. It is about offering low-cost SaaS applications and solutions with high-grade consultation fees, placing more value in the advice rather than the tool.

Generate client engagement with five quarterly business reviews in 30 days

What has happened?

Let's go back over what happened. We sold expensive systems to SMBs such as MS Exchange with servers. The process of selling these projects included high-level consultation: checking the environment, creating architectural designs, and putting together migration plans well before we got the deal signed. Part of the sales process was to create a complete Project Plan (many unbilled hours) for the investment, deployment, and implementation of those items. Because everybody made a decent margin on those package items plus the accompanying service project and because the closing rate was high, we were happy to include the initial consultation work in the sales process.

But over the last few years most SMEs have been moving into the cloud to some extent. They are buying Office 365 monthly subscriptions instead of buying servers and exchange licenses paid upfront. We do earn commissions, but is there more? Do we need to plan things out? Do we need to integrate the systems? Do we need to do consulting work? Sure we do, and it’s just going to grow as the system gets more complex.

The fact is that clients never really get used to paying us for IT advice and IT consultation, but now we don’t have those big lucrative projects to cover our work.

Rise of the SaaS applications

The SaaS model is widely misunderstood. Most people think that the main benefit of SaaS was that you don’t have to install the application, making it easier to use. That’ just one of the perks along with all the other technical advantages such as mobility, platform independence, data storage and so on.

The big deal of SaaS is the business model. You might think that this is all about paying monthly instead of buying the license. This is a different and very important aspect. Paying $100/user for a decent CRM for five users is $18,000 for three years. The same with on premise, is you’ll pay the upfront license + 20% upgrades every year. Without the hosting fees it’s around a $12,000 CRM package just to start; we often forget that there are always implementation costs - we’ll get back to that later.

From a psychological point of view, paying $500 per month is a much lower hurdle than committing to a $12.000 upfront fee, if you sign a 12 month contract, which is now less often required. It makes SaaS applications selling easier.

From the perspective of the application developer however, this is a whole new game. Now the application company does not get $12,000 for the license upfront, and risks losing the client at any time. The app developer has a bunch of upfront costs developing the tool, and then more selling it. You (believe it or not), marketing, and sales and customer management can quickly eat up 50% of the lifetime value of the client. That means the motivation for the application developer is no longer just to sell the tool, but to acquire and keep the client as long as possible, and to upgrade to the highest package possible.

Now the goals of customer and the application developer are aligned: get as much value out of the application as possible. The big deal of SaaS is common motivation.

Distribution of work with SaaS

The second big shift very few people yet see clearly is the change in work distribution. Providing a $500 CRM service for five users is a pretty lean operation. This equals 3-4 hours of consultation rate, so the SaaS provider has no financial support to do the work for the client. The client has to do it for themselves.

Take a look at Hubspot. Hubspot is an inbound marketing application. It helps you put together a decent website, blog, email workflows, calls to action and to run a great web based system.

They have to educate their customers on inbound marketing strategies, copywriting, blogging, sharing content, grow-to-hack, choosing the right color for the calls to action - you name it. If they don’t, the customer is not going to build up a decent system, and won’t see the expected successes, benefits, or value, and will eventually drop out.

Hubspot is an extreme example of how much a client needs to put in to make an initiative successful, even with a great starting product.

The best part is the following: most clients have been there, done that and know that IT initiatives are the hardest to manage, and that they require their investment. Buying Hubspot and figuring it out along the way doesn’t work, and the costs of not paying attention are higher.

However most customers don’t have the resources or the people available to learn the best color for the calls to action and how to increase the traffic in the Facebook page. They rely on Hubspot certified partners to do the job. These partners are helping clients implement the tools, and further along the way. They have a huge upfront charge to kick things off as well as additional monthly recurring charges. In most cases the overall payment for the partner far exceeds the payment for Hubspot for the tool itself. 

The paradigm shift: they are paying for the success, not for the advice...

The latest IPO and stellar growth of the Hubspot partner community is proof this is happening.

Put it together

Ok. Let's recap the points:

1. we see that the old model was to sell the big upfront project with free advice, 
2. we see SaaS companies motivation is now 100% aligned with the customers’ success
3. we see clients are willing to pay for success if it is made tangible

What’s the point, you might ask? How do we make money as MSPs, we don’t know Hubspot!?

Many SaaS based applications are more affordable than complex packages and usually solve one problem, such as:

• Project Management tools (Basecamp, Asana, etc.)
• Lightweight CRMs (Zoho, Sugar, etc.)
• Process Management apps (ProcessPlan, ProcessStreet, etc.)
• Collaboration (Slack, Hipchat etc.)
• Meeting Management (Lucid Meeting, Do.com, etc.)
• Integration tools (CloudHQ, Zapier, etc.)
• Vertical based solutions

We can continue this list for a long time. Any ordinary 20+ sized company would need one application at least from the app categories above.

Let's check our SaaS application grader which helps you and your clients understand what part of the business is not leveraged with a lightweight web app:

The problem is still that they don’t have the resources to master these applications; they don’t have the time to choose, learn, implement and integrate. Even though these apps are solving basic problems, understanding the business process and implementing a Trello.com card system for managing it isn’t a trivial effort. Most companies don’t perceive a part of the potential these tools could do for them.

That’s the void; what’s missing. Both the application developer and the customer need this role filled.

How do MSPs make money with that?

A traditional MSP is not going to make a dime with this model. They are infrastructure focused companies, not application focused companies (yet). But they can easily step into this role, because they have the support and the client base, and are already familiar with the applications world.

1. Do not do hourly rates, but fixed scope projects

Selling it for $150 per hour is not going to work. But selling Slack the internal chat tool, putting together the basic processes and rules, with ten channels and five integrations for $2000 and $100 support per month is workable, predictable and drives success. The vCIO is the ideal candidate for those projects. He knows the business, understands the processes and can communicate the need.

2. Oversee the portfolio, not just the individual apps

As you deliver more and more apps to clients, someone has to be the owner of them, or there will arise islands of different types, with no integration and no control. Again the vCIO is ideal for the control of that management role: making decisions on which apps to implement, governance, subscription management, etc.

3. Come from the business world, not the technical

Don’t provide "ProcessPlan" as an app. That is not a value. Provide operational excellence with well defined processes and automation that uses ProcessPlan to deliver value. Again, being a virtual CIO, you are going to easily spot these opportunities and make it happen.

4. Have a platform, a business application solution stack, and vertical focus

For a base IT infrastructure, Office 365 or Google should be among your choices, and for all the typical applications - calendar, note, workflow, project, collaboration etc. - there should be a stack the engineers know can bundled together and integrated. Also be familiar with vertical based stacks for accountants, law firms, professional services, etc.

5. Test it, live it, support it

It’s important to use the same stack internally (you probably already are) so that your team has experience with it. The support will be more “User Enablement”, helping them with hints and tricks, to take away some of the heavy lifting from the vCIO’s shoulder. The Virtual CIO is busy doing the planning and the implementation. Then the team is backed to support it.

There are cases where managed services providers have bundled together a “SaaS Office Suite”, reselling, implementing and supporting many applications per user. In this case it’s an addition to the current MSP package but with licenses, subscriptions and services inside as well.

Our MSP switched to this mode 18 months ago and are now packaging the full SaaS application suite with all desktop support and remote monitoring in one bundle. That is a client experience of value.

Conclusion

Let's shift the paradigm from "Expensive boxes with free advice" to "Cheap applications with paid advice."

This is the fall of the era of free advice and the dawn of the profitable vCIOs!

Break Your IT Sales Barriers with Ian Altman

We are starting our "MSP 2.0 bestseller" monthly book review. We want to start strong, so the first book of this series is the new consultative selling holy bible, Same Side Selling. The co-author, Ian Altman, CEO of Grow My Revenue, is a sales visionary, bestselling author, Forbes contributor and keynote speaker.

While speaking with Ian it became clear he knows how to win the hardest battle IT managed services providers have ever faced: commoditization of the IT infrastructure services and the resulting price pressure, shrinking margins, and the lack of differentiation from competition.
One of our MSP 2.0 movement members suggested I read the book: Same Side Selling - A Radical Approach to Break Through Sales Barriers. He had told me that this is 100% aligned what we do in the Managed Services Platform IT Consultative Sales program. I read it and I was flattered. Most of what I’ve read on the subject involves large complex concepts, but this book was very simple, very practical and quite an eye opener. I think everybody who’s a little serious about MSP 2.0 should read his book.

You can read his articles each week on Forbes.com. If you do a search in business trends, he comes up #1. Business luminary Seth Godin recommends Ian’s latest bestselling book, Same Side Selling, as one of two must-read books on consultative sales. Ian is host of the Grow My Revenue Business Cast. He started, sold, and grew his companies worldwide to values of more than one billion dollars. 

I had a chance to chat with Ian last week and he was able to carve out time with us for a quick interview. The fun part is that he knows the industry well, so we had a great chat. I am not going to try summarizing the interview, as I think it’s better to just hear him for yourself.

Thanks again to Ian. Check out his webcasts at his website: http://www.growmyrevenue.com

12 mistakes most MSPs make with their Virtual CIO services

The Virtual CIO phenomenon is not new, yet the promises of the role have not been realized across the industry. Some mature MSPs who believe they have a functioning Virtual CIO practice, on closer inspection, still show challenges with delivery, scalability and profitability.

While we could go in depth to identify the root of these problems, instead here we'll highlight the twelve most common mistakes MSPs make with their vCIO. At the end of this article there is a questionnaire where you can measure yourself against other MSPs.

#update - We released this blog a year ago. This is an updated version covering the latest developments. It seems that the MSP 2.0 community was able to solve most of the issues during the last year. These mistakes now can be prevented. It has been a long year, for sure... :-)

Virtual CIO Strategy, Transformation Planning:

Mistake #1. Packaing the MSP and vCIO contracts together

Selling the vCIO built into the MSP contract makes you Virtual CIO of the IT Infrastructure. In this there are two pitfalls.

First, the vCIO capacity of the contract does not scale with the size of the organization like the other IT company related services do. It scales up with the complexity, changes and developments of the clients. That means ball-parking a user based price for a Virtual CIO is unlikely to be appropriate. This results in either the price being too much for the market (they don’t want to buy it), or the contract being more work than revenue supports (you don’t want to sell it).

Second, creating a solid offer on virtual CIO involves capacity time with a very expensive resource. That makes the MSP offering more expensive compared to the competition. For the client, the results and benefits of the "vCIO of the infrastructure" do not make much sense. Customers are apt to compare prices ‘apples-to-apples’ between competing IT managed services providers but rarely are the service offerings that comparable.

Virtual CIO can deliver a major competitive advantage. It needs a separate service offering with a distinct pricing strategy.

#update - Working with clients around the world, we have designed a smooth transition from vCIO Light to a real vCIO services. That means even if you packaged together, there is a way out. 

Mistake #2. Not creating the necessary budget to get results

Let's say we have a 50 seat "sweet spot" client set up with the needed virtual CIO core services like: yearly, quarterly, monthly and weekly cycles. This could eat up 70 - 170 hours easily with automation. (We refer to the virtual CIO here as a general one taking care of every IT-related business aspect: reporting, management systems, applications, budget, vendor management and so on.)

If you use a base $150 hourly rate it could reach $2.000 service price per month or $40/user. Your MSP contract simply does not have the space for that.

Further you do not have the necessary processes or approach for that, and you can’t afford that much time, so you under-deliver on your promise of virtual CIO. This damages the concept and the possible future of the service.

Again, if you are not able to create the viable budget for the monthly recurring service fee and communicate the value, either you do not profit or don’t sell the service.

#update - there is a formula now for calculating profitability regarding virtual CIO services, the services and service delivery processes, as well.

Mistake #3. Not using a framework to develop the system

The vast majority of the Managed Service Providers we’ve been able to talk to do not use any framework for their virtual-CIO-related activities, so they don't have a system in place to successfully deliver them. Instead they operate as "consultants" or arm’s length managerial resources for infrastructure-like projects.

This means they are not able to implement a standardized IT management structure with proper plans, documents or databases that align services across the IT ecosystem. Nor are they able to streamline communication of the duties, tasks, deliverables and responsibilities of the virtual CIO correctly. This makes it hard to achieve the expectations of the client for the role.

#update - a complete structure is ready for the various vCIO activities like Planning, Project Management, Education or Execution. The closed loop vCIO cycles have been completed with Annual, Quarterly, Monthly and Weekly cycles.

Demand Generation

Mistake #4. Not attracting the right audience

Demand generation needs to target the right audience. The virtual CIO job is best suited for companies with 50-150 office workers. If the MSP wants to target a 20-30 or even a ten-seat client, there will likely come a painful realization of the lack of interest and of financial background. Those in higher tiers are left to figure out some system for managing IT. We can go there, but with coaching and support, as a complement the CIO or the IT manager.

#update - content and tools to qualify visitors are now available, like graders, ebooks 

Mistake #5. The wrong content

The partner of the virtual CIO is not an office manager, not the CFO or COO. The partner of the virtual CIO is the president/director/CEO - the top-level manager of the company. We know that placing this role that high is a challenge for the average technology-oriented service provider, like most Managed Service Providerss, but it needs to be there.

Most CEOs are not interested in backups, new MS Office versions or the cloud in general. They spend their time on increasing cash flow, boosting sales, organizing their companies, servicing their clients, and developing their management team. The MSP’s marketing content has to reflect those perspectives and turn those opportunities into solutions supported by IT.

This content has to be consistent across the website, emails, blogs, calls-to-action, in lead-nurturing drip email campaigns, in LinkedIn and other social media communications and in marketing collaterals: ebooks, guides and whitepapers.

#update - business related content is available in different formats like graders, ebooks, emails to quickly put business content to the MSP website. (even a complete Weebly based canned MSP 2.0 website is available now for early adopters)

Mistake #6. No clearly defined buyer’s journey

The buyer's journey covers the process that a prospect follows, from the first access of content to becoming and remaining a client. While a lot of MSPs have a decent website with a blog most of these blogs lack a call to action - no next-steps for the prospective customer, such as a downloadable e-book on the relevant topic.

These websites talk about available services instead of highlighting vision, possibilities and opportunities. The sales meetings are wired not to serve the clients and create instant value, but to "qualify" the techs - a focus on our opportunities instead of theirs.

The lack of a well designed buyer's journey will fail to attract the right prospect (the CEOs) to the website and assure them they will find the kind of service that will focus on their opportunities. The content needs to attract, engage and interest the right prospect with the wide scope on the business - make them eager to initiate contact and get a demo or have a meeting with the MSP.  

#update - various lead magnets have been developed to convert visitors to leads

Sales

Mistake #7. Not using consultative sales

Consultative sales is all about selling solutions. In solution selling our approach is not geared toward what to sell to the client. Instead we have a process to ask the thought-provoking questions that reveal overlooked opportunities and potential benefits. It is a process of discovery, of business opportunities where the MSP's solutions can help achieve their vision.

Virtual CIO is not a boxed product so it doesn’t have a standard price. Deep understanding of a customer's business is required before the solutions can be presented. Selling without context and understanding will put the virtual CIO in a very ineffective position, making it difficult to manage expectations.

This method is slower and takes more time, but necessary for engaging the client and crafting the offering within their business context. However exploiting business opportunities, and supporting them with technology solutions will mean more and higher value sales.

#update - consultative sales questionnaires, scoring, reports, targets, benchmarks and help are available for making the consultative sales easier

Mistake #8. Not selling the vision with stories

The virtual CIO's purpose is to make the client’s business more competitive in its marketplace, with the use of technology, to drive more revenue, cut costs and maximize the business continuity.

These general terms have to be in the context of the client and industry; we cannot really engage the client without selling the vision of competitiveness: being a better company, producing more revenue, and surpassing their competitors.

To sell the vision we have to craft compelling stories that grab the imagination of the CEOs.

#update - storytelling process for the first meeting with presentation slides have been created to help telling stories

Mistake #9. Not confronting reality with numbers

The reality of the situation - the hard data on the current state of business maturity, people, systems and numbers - sets the tension of the proposition. This tension helps make the buying decision.

The “score” needs to be readily attained and easy to understand in order to be compelling. That is why a business IT questionnaire that measures a company’s competitiveness with IT is a must. Without this, even if the vision is clearly defined, there are no quantifiable parameters to achieving it.

Imagine having a vision to run a marathon: a good start would be a full physical assessment. Make clear how hard you have to train, the time frame and the resources you’ll need to accomplish your goal.

#update - graders & new questionnaires are ready to get real with prospects and clients

Delivery

Mistake #10. Not using vCIO tools like automation or collaboration

Most IT companies are trying to use their existing PSA solutions like Connectwise or Autotask to manage their virtual CIO activities. It just doesn’t work, period. Again, the MSP 2.0 virtual CIO does not just focus on infrastructure. The virtual CIO has to manage people, processes and systems while communicating with the team, vendors and customers.

Most virtual CIOs do not have an integrated approach to managing all their activities in one place, or a system in which they can store all the IT management-related documents, memos, projects, databases, plans, budgets, and so on. Missing an integrated platform wastes a lot of valuable time for the virtual CIO.

#update - Basecamp integration is ready to collaborate with clients & vendors

Mistake #11. No clear differentiation between onging and project activities

Just as maintenance teams are separate from project teams because of different utilizations, focus, experience, etc.,  so should be the virtual CIO team.

One virtual CIO needs to manage the core virtual CIO cycles, like yearly planning, quarterly activities, monthly follow-ups, reports, weekly meetings, and so on.

An average virtual CIO could manage 10-18 clients, depending on the complexity of that focus.  Another virtual CIO has to manage the individual projects separately. It needs a different personality, different skills, tools and different daily and weekly routines.

#update - separated process for ongoing vCIO s     ervices and Project based vCIO services are available with templates and Basecamp workspaces

Mistake #12. IT-related service instead of business-related service

In a quarterly session, discussion should include questions about the client's cash flow, marketing initiatives, sales performance, internal projects, and competitor's moves first.

Then it can become a session with reports on the execution of the IT strategy, the quarterly plan, and the plans for the next quarter. It should not be focused on the technology roadmap or IT-related issues, problems, and challenges. It has to be focused on the business, processes, numbers, and business terms.

This can be difficult - there are so many cool IT projects an MSP can propose to a customer - however the conversation needs to remain about the business benefits and business accomplishments.

A successful CRM project is a great example. It highlights the improvements on sales collaboration, alignment, processes and results, instead of talking about the features of the technology solution.

#update - application related services (like Implmenting Slack) are available and also Business Modeling and other cool business focused workshops

Summary

Please check for these possible flaws in your practices. To improve on those, we strongly suggest signing up for the MSP 2.0 Quickstarter Tools. It has the tools to market and deliver the virtual CIO role right. If you would like to know more about the modern vCIO approach, let’s check this page.

#update - thanks for the contributors, our team and all clients to put this all together. A year ago it was just the mistakes, now the MSP 2.0 community can prevent those mistakes! Thanks guys!

STRUCTURE, MANAGE AND AUTOMATE YOUR ACCOUNT MANAGEMENT AND VCIO PROCESESS

10 ways MSPs are leaving money on the table

Keeping up the margins for IT managed services providers is getting harder and harder. The competition is catching up and while needs of the clients keeps growing, the price still seems to be dropping - and many IT companies are making a practice of leaving money on the table. Let's look at 10 things you can fix to prevent losing money every day.

1. Having no CTAs on your site

How many MSP Blogs have great content but nothing to do? Even if the prospect likes the content; that’s a dead end. There are no next-steps or call to action; no way to download something or move further into a workshop or webinar or launch a module and learn.

$$$ - invest in having visitors and do not convert leads

2. Talking about how cool you are

The website should be about the clients and how they can benefit rather than descriptions of ourselves, especially on the main page. You have to grab their attention and quickly engage them. Focus on talking about their IT problems, issues and challenges and the potential solutions.

$$$ - lower conversion rate on your site

3. Talking about IT

IT talk is for IT people. Business people are looking for business talk. If you are talking about Office 365, or Virtualization or the Cloud, you are going to lose their interest. Talking about margins, productivity, process management and salesforce automation is how to keep the attention of your prospects.

$$$ - lack of differentiation puts you in the herd

4. Offering consultation on the first page

Very few visitors will be engaged enough on the first page to book a meeting with you. They are probably open for discovering solutions to their issues and reading informative content. Only then should you move toward getting their email address.  First nurture the relationship - after this is established you can start talking about a potential appointment for a meeting.

$$$ - feels too salesy or pushy

5. Pushing the Network Assessment

In the good old days, prospects were begging for the Technology Assessment, and you were even able to charge for it. Now, however, most IT systems are robust and the assessment is no longer required, so making that in the central feature of the sales process can be lethal.

$$$ - not closing deals

6. Having only one service package

Yes, in 2008 there was only one iPhone - now you can buy three sizes in four colors. Client expectation is rising as the industry matures. Limiting your prospects’ choice to one offering is preventing your them from becoming clients.

$$$ - not closing deals

7. Building the Virtual CIO into the MSP packaging

The surest way to squander the potential of the Virtual CIO revenue stream is to bundle it together with the MSP package. It downplays the value of the Virtual CIO to just a tech advisor doing tech roadmaps and warranty notifications, instead of capturing the opportunity to maximize their competitive edge.

$$$ - eliminate margins and give free advise

8. Developing Virtual CIO practices in-house

Development of Virtual CIO service offerings requires strong management skills as well as a lot of trial and error to get it just right for the specific instance. Developing it in house eats up the time of valuable resources and can lead to dissatisfied customers during the development phase.

$$$ - huge internal cost and time investment

9. Executing Virtual CIO without structured processes

Executing Virtual CIO activities without repeatable processes requires highly skilled people who, even if they can be found, will be asking for a fee. Teach one smart person the vCIO processes and give them tools to help them to deliver value to your clients in a profitable and scalable way.

$$$ - no margin for vCIO services

10. If it's not broken, din't fix it

This is an adage that is misapplied to this industry.  It is misguided to think nothing has changed and there is no sense of urgency around this change. Complacency has brought down many large, otherwise successful organizations in the past. Taking commoditization lightly can cost you your entire enterprise in the end. Take advantage of this new standard and turn your organization in the right direction, fast.

$$$ - fix a broken business model instead of changing it

Conclusion:

The MSP 2.0 movement is catching fire and re-energize the commoditization of traditional MSP services. The traditional MSP marketplace has changed a lot, and without proper strategy and actions it can damage any IT service provider.

Take action and learn more about the MSP 2.0 movement.

How to transition from the server room to the boardroom

This week's question: How do I become a virtual CIO when I'm “just a tech?”  This week Denes and Myles Olson discuss a path to transition to the virtual CIO role. You may be more comfortable in the server room, but now you're needed in the boardroom.

To learn more, visit our MSP 2.0 Business Building Platform. 

Delivering Business Focused QBRs

ADAM WALTER AT VIRTUAL C

You would like to be a high-value business partner in your client’s eyes rather than a basic technology service provider. Your QBR process is a critical part of influencing their engagement up to a higher level. Watch this recorded webinar with our vCIO expert guide, Adam Walter, who has shared his 5 step process to make any technical QBR into a business-focused one.

6 Best Practices of Top Performing vCIOs

ADAM WALTER AT VIRTUAL C

Watch this interview with our vCIO expert guide, Adam Walter, to learn how to be more engaged with clients by finding best practices for becoming a trusted business advisor in 6 single steps.

 

The secret to making money for IT consultation

We have been using a very basic management tool called the 10 Point Exercise, where the goal is to channel client issues into a defined consulting "product" rather than just having discussions pro-bono….getting people together to ask specific questions, getting everything out on the table and developing a plan. It’s easy to learn and it turns IT tech guys into business advisors in 20 minutes.  Most importantly though it let them charge for their knowledge instead of giving it away. Let's see how...

Get long term client loyalty with regular and strategic Quarterly Business Reviews and IT strategy meetings

We aren’t going to teach how to use it here. You can learn and practice the 10 Point Exercise in many ways.

Our focus now is on how it can be used to turn your free advice into something that both helps the client and generates revenue.

Create a process to solve problems

Let's imagine we run into our client who happens to have an issue with their IT, people or systems and are actively seeking advice. Of course we engage and try to help them. However, we do not have a process; so we miss the chance to understand the root problem together, from the start. We probably sit d

own with the client several times, as we’re often their Trusted Advisors for IT, and we don’t want them to go somewhere else. Ironically this can mean both that they don’t get immediate value, and we don’t get paid for that service.

Now imagine you have a process to turn vague issues and problems into tangible results. When next you discover one of these issues just say: "This is a perfect place to have a 10 Point Exercise!" This means sitting with a few people and doing a quick and easy exercise.

There are telltale signs to identify the proper 10 Point Exercise for solving the problem based on their scope and goals. We need to keep end goal in mind: what we want to achieve.

Create alignment

Usually when these issues/opportunities for improvement arise there are differing perspectives.  While there may be agreement on the symptoms, there is no alignment about what causes the problem, so no clear diagnosis. This is vital to get at the beginning. 10 Point Exercise questions like these can help: “What are the most common reasons our employees spend so much time searching?”, “What are the underlying causes of the low productivity of office workers?”, or “What are the most important issues behind our apparent problems with working together as a team?”

Solve a problem

Our goal now is to find how we can solve the given issues. We have alignment on the problem, we’ve defined it, but we do not have a strategy to solve it yet. There are methods that work on a general level. Questions like this can help: “What are the next steps we can take to solve the internal communication problem?”, “How can we ensure we solve the team productivity problem by the end of this month?”, or “What specific actions can we take to reduce time-wasting document searches?”

Opportunity discovery

We need to clearly identify a business opportunity out of this issue, and what we need to do to capture it. Questions like these can help: “How can we improve our internal processes?”, “What is the best way to leverage our current IT tools for better collaboration?”, or “What actions should we take to make sure we can develop the service on time?”

Project visualization

The goal in this is to be aligned with the team on what we need to achieve at the end of the given IT project. Regardless the type of IT project and before anybody jumps in and starts planning, we know what success means to every stakeholder. Questions may include: “If we think about the Document Management project, what are the deliverables we expect from this?”, “What exact results are you looking for at the end of the productivity improvement project?”, or “How would you define the success of the collaboration project?”

Decision making

Now we need to make decisions and have a commitment to particular solutions, the scope of projects and needed deliverables. Questions may include: “Which collaborative solution are we choosing for implementation?”, “What are the expected deliverables and priorities for the productivity project?”, or “Which application should we use for internal chat?”

The more complex the problems the more sessions involved. We can start to clarify the issue with an Alignment session, then have a Problem Solving session and then jump into a Project Visualization. The sequence can be 2-4 sessions in a row, or on an improvised schedule as it progresses. There can be a natural sequence here. The outcome of one session can be the input for another. As we move forward we have to set expectations about how far we need to go in certain exercises.

If the team is bigger, we need more of the same exercise and to aggregated results. Do the same exercise in smaller teams and compare outcomes. Afterward, summarize the results and present that to the board.

Nice, but how do we make money?

Most of the time we are going to charge for these sessions. On one hand, we can do it ad-hoc, but we think it’s best to have prepaid packages of 5 x 10 Point Exercises, or part of the vCIO engagement.

If we see that one session takes 60 minutes of our time not including travel, prep and follow-ups, a session can easily cost us $250-$400.

We should demonstrate the exercise in real life first, so as to prevent the client from seeing it as a cost. We want them to see it instead as a great investment to solve problems with an outside party. Being unaligned, spinning the wheels and having arguments last for weeks, are very inefficient ways to solve IT problems. The $150 to $400 we are asking for the exercise has a significant return.

An IT related project can easily cost the client tens of thousands, plus applicable internal utilization of resources. Having a 3-4 session sequence of workshops can leverage that investment in a big way. Having more precise projects, better alignment and more teamwork is worth the investment and can get rid of unmanaged, ad-hoc projects.

Conclusion:

Learn and use the 10 Point Exercise, to create an entry type Virtual CIO service. The service leads you naturally to formulate and close more projects. Your time will be monetized, and your clients will come to expect to pay for reliable and prompt solutions. They’ll get a process to solve problems while you get funding for spending time with them as a vCIO.

Convert a business problem to an IT problem with ease

A basic truth of sales is that you need to associate your services and products with the pain-points of your customers, so that what you offer is thought of when those problems arise. IT managed services providers are selling high-level concepts when the client has manifesting pain-points: slow server, slow internet, outages, severe duty service, etc. But what can an MSP do for a client who doesn’t recognize the snags and hurdles they have? Let’s take a look at an easy 5 minute solution to this problem.

Your clients have their own jobs to do - generating more revenue and growth, reducing costs, enhancing operational excellence, HR, and so on. These are the concerns that the owner/CEO/president wants to see fixed.

Our job is to identify the pains within these concerns and ease them. We can easily find some around these areas: most business leaders experience issues around growth, competition, staff and managers. Where they see an obstacle is where they want to find a business solution.

For example, business owners once were fraught with IT technology problems. It was slow, unfunctional, and poorly serviced. It slowed their growth, inflated operation cost, and dragged down efficiency, so these CEOs solved their business problem by subscribing to Managed Services.

Unfortunately that means now IT is so problem-free for most companies that they’ve stopped seeing it as a business problem. They have reliable internet, often all the software they need, and stable workstations. IT is not hurting the company goals anymore, so it’s no longer on the agenda for most leaders. This is causing managed services providers some sales issues.

Ok, but we also know they are far from getting maximum positive results from Information Technology. There’s a lot of room for improvement in their reports, communication is somewhat distracting, and collaboration is usually weak. They have the necessary tools, but most aren’t using them to achieve much competitive advantage.

What if we stop asking our customers and prospects IT related questions, and try to find their real pain points? As we’ve shown, they’re no longer incorporated within IT services.

At least not directly....

Consider the idea of business growth. Growth calls for more sales. More sales can be achieved from new clients. Of course acquiring new clients requires processes, and processes can be automated with a CRM.

So there is an IT related solution here, but it is not directly attached to a pain-point, and the chain of connection from that point to the logical IT related answer is longer.

If we start with the pain-point, we can get to the logical IT related answer sooner. This process is the consultative sales process, but it requires a lot of skill to master the questions and guide the conversation.

We’ve seen patterns - of business problems and IT solutions matching indirectly - so we’ve created a process that gets from the pain to the solution faster.

This is what the "IT Competitiveness Graders" do.

Little surveys ask questions about potential business problems in a very relaxed way. The client answers yes or no for several named problems. After the survey, with 6-10 questions, we can see how many problems they have in various areas. We attach a little hint and some available education for every problem they identify, and give them a general score. In this case, they can "Grade" themselves in a variety of business concerns.

Let's check it out live, (it’s much easier), with an example Grader on productivity.

Take the grader to see how it works  You’ll receive a report with your grade just as your clients and prospects will.

There are questions on meetings, collaboration, managing emails, files, among others. These are business tasks. The client is able to review their scores and the potential issues. We’ve now converted their business problems to IT problems with IT solutions.

We can also use the graders on our website for prospecting. Salespeople can send them over to qualify clients. Account managers can use them before quarterly reviews to collect business problems. You can use the Grader scores and information in meetings to elaborate on the subject and make it a business solution - skip the IT part, nobody really cares. If we find the pain, we can fix it with a solution.

To put it simply...ask business questions and then turn them into IT solutions.

The 6 Reasons MSPs Tend to Over-Deliver

One of the most common laments we hear from IT managed services providers is over-delivery of too many different services. They feel they serve their clients more than needed and the services go unused by the clients. Account managers end up doing more IT consulting than they should, demands for IT consultation are unlimited, and the IT company invests time on IT projects that never start. Here we delve into the root of the problems and learn what to do about them!

Clients will start with questions like “What is the best application for this problem? Why are people not productive? How do we manage various IT related vendors?”, etc. However most IT companies do not have the right model for IT consultancy, and try to address those needs without a viable revenue model.

The result of over-delivery is diminished return on service investment. Not only do we do too much but at the same time we set unreasonable expectations with the client. We teach them that we do it for free, or that any request is covered already, and that blocks our ability to implement a profit model, if we even have one.

Let's quickly see the six causes of over-delivery and review a solution.

STRUCTURE, MANAGE AND AUTOMATE YOUR ACCOUNT MANAGEMENT AND VCIO PROCESESS

1. No Boundaries on Services

We have clear boundaries in regards to traditional tech related IT services, but the clients have new needs. IT Management related issues like application deployments and cloud transitions are increasing.  Deploying Office 365 to a small business office is more of a consulting job than deployment now. MSPs are missing a best practice for creating boundaries of what is included in the traditional service package.
 

2. Mixing Sales and Consultation

In many cases we do a IT consultation to sell something. They are interested in centralized management of IT, and we teach them about virtualization and all sorts of technologies to help them. What we do is IT consultation, but because we are selling the IT projects, we do not ask for it separately. This is fine until we close most of the projects and make money, but sets a precedent that we do free IT consultation.
 

3. Mixing Project Management/Implementation 

Another fault in doing free IT consultations is that in most of our future projects we do not deploy anything in the technical sense. We keep doing the projects, but there will be less billable technology work. The client doesn’t separate the different types of work - a SaaS CRM integration (we do not deploy a server, just manage the project) from an On-Premise ERP update (we upgrade the servers that are behind, then implement the project). On the one hand we have to make money for the consultation and project management (because there is no tech related work), on the other we generate revenue by utilizing engineers.
 

4. Mixing Account Mananger and vCIO

Our account managers tend to manage the account health and satisfaction loyalty. Most of the time the job is about solving a technology based problem related to our services. However, clients do not naturally differentiate what is related to our services and what is not. Our account managers are thus likely to do additional consultative services as well (and often not realize it). In this sense, they are operating as a mini virtual CIO and managing the accounts IT related issues. The problem is that we do not charge for this service. Again we’re teaching them we do it for free.

5. No Clarity, Definitions, and Alignment

The contracts and other legal items of the engagement may not be suitable for managing a dynamic and adaptive service. The technologies and client needs are changing faster than those formulas. We usually need to adjust to the client’s real needs a lot after we start the engagement, so even if we have a solid contract on the service side, it needs to be flexible throughout the process. After a while some contracts can even become obsolete, unable to serve the common ground with clients and our services.

Another factor is that some clients signing these contracts do so blind. They do not take the contract apart word by word, but just trust the service provider. In most cases they were referrals, and this can cause a misalignment in expectations.
 

6. Lack of Processes 

Over-delivery can be caused by poor execution. We do not have well defined processes in place for consulting work, or if we do, they are not put into practice. It causes vague capacity plans, which we usually overshoot. We are not following best practices, and we tend to work on the same issues repeatedly, spinning our wheels and not moving forward.
 

Thoughts Toward Solution

We will consider a couple of ideas and thoughts about fixing the problem.  This is not a comprehensive description, rather just some ideas that will lead to the solution.

Act on the Changing Client Need

A change in the operations or processes of a client is an excellent opportunity to create a well-defined and entirely separate service offering for IT management and IT consultation.  We should separate the service, so everybody can understand why the traditional package does not have these items. We can still assure the client about what is in the background but if they have a need for more IT consultancy, then you can serve them in a better way outside of the MSP contract. We all have problems upgrading clients to something they might see as included in the service.  We need to have a clear new service with a very professional approach, and deliverables that have clearly visible impact. Reduce how often they assume “this is included.”

Create Boundaries with Mapping 

Mapping out the clients different IT management needs helps to craft services with boundaries. The client's CEO may need some ‘CEO coaching’ and you give them three 30 minute sessions, one in person and two on the phone. They may need to work on their processes - a ‘Process Efficiency Workshop,’ and you give them one meeting per month. They need more training on the infrastructure of what they have, so line up an "IT Enablement Training series" every two weeks with different topics. Each session needs to be a step to solving the problem rather than a series of attempts to make the entire accomplishment.
 

Standardization and Customization 

The great thing about LEGO is that you can build anything with standard blocks. The result is customized while the parts are generic. The same idea is behind creating standard workshops, brainstormings, and teaching sessions. You can teach your organization how to do them. Your clients have different needs, and you can solve those needs by using a custom mix of standard blocks of services and deliver the series of standard elements as a custom result. Of course this is where the mapping of defined boundaries can influence selection of these modular blocks.  You can craft your best offering based on standardized, tested methods.
 

Project Management is the Product

Project Management is usually misconstrued as a by-product - not the real goal, but to get results, we need to do it. If we turn this idea around and make Project Management a product, it helps us a lot. This means we first need to educate clients about the value of well-rounded project management, and we have to make it more tangible.  Implementing an easily put together productive Project Management method is crucial.  These methods help determine and define the deliverables which are needed in their service. The automation behind this can cause additional benefits like more clarity, reporting, etc; however, most of the PSAs (Autotask, Connectwise) have project modules and they do not give us any Project Management Frameworks to use. We have to have our own and implement it within our professional services automations project modules. 

Well Crafted Packaging

We can use a well crafted virtual CIO package with deliverables and processes to offer a service with clear outcomes and deliverables in a scalable way. The packaging has to manage all the changing expectations with all the needed tiers involved. The packages need to be a monthly recurring subscription like your MSP package and at least an annual commitment. Craft an annual delivery plan for the client showing all the deliverables solving their problems, guiding strategy, and exploiting opportunities. This will help them see the goals and what you do to help them achieve them. You can put some to work upfront, as well as have monthly and quarterly recurring tasks, and have fully budgeted hours for the year.  In this case, you can measure profitability the same way as you do for the MSP. 

Conclusion 

A profitable consulting business faces the same challenge as a beneficial MSP service - expectations of management and processes. The problem is common among managed services providers. The IT consultation is less tangible than the tech-related work. It is trickier to demonstrate the tangible deliverables of consultative services that are the basis of our profitable vCIO services. Designing services with clear outcomes crafted in a structural way is a critical first step.

STRUCTURE, MANAGE AND AUTOMATE YOUR ACCOUNT MANAGEMENT AND VCIO PROCESESS