What is the one business skill MSP leaders can teach their clients?

If you look at any well-run IT managed services provider, there are plenty of robust, systematized and documented processes in place. Service businesses are built on process management. Service desk, deployment, migration, and communication processes always require tweaking to be stay efficient, and efficiency is vital to a great MSP.

To enhance this process we use tools like PSA, RMM and dashboards full of metrics to quantify health and successful management. If you’re doing this you’re already in the top 1% of MSP leaders.

In all of this you must analyze processes, written process documents, education of your staff and colleagues, and staff metrics and management. Essentially you become a practitioner of business process management.

Most of your clients need that type of knowledge and experience to boost their companies as well. You can use these to kick off the business discussion and show some value in an area that is natural to you.

Now that we know you have the faculty let’s learn how to act as a IT consultant in the conversation. We have a sheet dedicated to “power questions” for this process in our MSP 2.0 Quickstarter Kit.

Try this: setup a meeting with one of your clients and focus on just one business area, using some of the power questions in the Quickstarter Kit. Choose something like sales, operations, logistics or procurement. Ask about their processes and procedures, where they feel they excel and where they struggle. I bet you can find a technology solution related to the latter. Don’t take my word for it, just try it. Have fun.

Trusted Advisor or Technician, Which Pays More?

Most IT managed services providers we work with suffer a fundamental problem: the definition of who they are. The lack of a clearly defined definition of the business can be the biggest obstacle they face to success in the MSP 2.0 environment. The statement "I am a tech" needs to change to "I am a IT consultant." Unfortunately people often underrate themselves because they lack an MBA or they’re uncomfortable with so called “sales.” This limits them and their teams in engaging with more clients and prospects in a meaningful business way.

However, being a business consultant is just a role, a mode of operation, a mindset and the subject can be anything technical. Consulting is a behavior, a set of skills and tools that anybody can learn and implement. We are creating a series about being a consultant so you can harness the power and reframe how your clients see you.

In this first blog episode I will show you the circumstances in which it is better to act like a "consultant" rather than an "technician"

What is the consultative (trusted advisor) vs. tech (technician) mindset

First, many MSPs are under the false impression that they are having business conversations with their clients.

Be aware of this! For your clients, discussing the ROI of a VOIP is still just tech talk. Even having a chat about the financial aspects (OPEX, CAPEX) of the cloud is still tech talk. Discussing how a CRM could boost their top line is still tech talk.

The reason these are all tech talks is that in many cases the problem is created by the solution, not the other way around. This means we need to switch the conversation to talking about a potential business opportunity which the given tech-related solution could exploit. In most cases, the client did not say: "I have too much telecommunication expense", "I have too much CAPEX and want to transfer to OPEX" or "I have a sales problem” but with your expert consultation, they will be able to relate those to a technology solution you can offer. The client might be relating to these ideas in mind, but not in heart. Purchasing decisions are made using emotions backed up by logic, not the other way around.

Unfortunately the logical mind of a technician wants to speak of solutions in logical terms. That is the "I know what is best for you" mindset. And that is the telling mindset. This serves your business more than your clients, and ultimately makes your offering an expense, rather than an investment.

What if we address the business issues first and let them come to the conclusion that they have a problem? Spending time on questions and going deep into the subject not only means we understand them, but that they feel understood. Every solution we bring will be the result of a dedication to solve the problem stated. In this case, the tech projects become business projects.

This is the vCIO consultative mindset we need, and has nothing to do with having an MBA or wearing Armani suits. It is about sequence, tool set and mindset.
Let's have a look where we could use this mindset in our MSP practice:

All meetings with prospects

Every time we have a meeting with a prospect, we should wear the consultant hat. If we do, we immediately stand out in a big way. The main differentiation is that prospects usually expect to have a tech talk with a geek instead of a business conversation with an informed and experienced business consultant.

If we do not overshoot the role but just ask the proper questions and be genuinely curious about their business, we might hear something like: "Hey, I have been talking to other vendors and nobody was asking these questions..." This is the distinction we need to make..

Be open and try not to sell; you will make the sale eventually. If we trust ourselves and are courageous enough to go off the solution and focus on the issues and the problems that could form, then we are smart enough to convert those problems into tech solutions.

Firing up solutions without the business context is only noise for the client, and a false assumption for us that we have created interest.

Quarterly, yearly client meetings

I have reviewed many mature MSP's Quarterly Business Reviews. My conclusion is: reviewing MSP services like technology roadmaps during meetings is not the right way to engage clients. A consultative role lets us ask questions about their sales performance, obstacles of growth and the processes with which they are are struggling. We have to find out why the CEO is not able to sleep at night, and then help with that. In this case the meeting would be the review of their business instead of a review of ours.

Let's be proactive and challenge our clients. The best way is to start where we have experience. Every managed services provider is a process machine. Our MSP business model is all about processes, streamlining and automation. That is why every managed services provider leader has great experience with processes, human aspects, software automation, and so on. Let's start analyzing the client processes. You are going to find holes and great solutions that you can implement. These will come from your core business competencies.

Before and during projects

Technology Projects are a great way to leverage our consultative mindset. Before the project we should understand why the results of the project are required. What business benefits or deliverables will the project provide? Create a simple "Vision Statement" collecting the expectations of all stakeholders; this is a small investment of time but can be put to use during and after the project.

Use the "10 points exercise" from our MSP 2.0 Quickstarter Kit to have a better, common understanding about the goals, benefits, and expectations.

And believe me, not so many IT companies have asked the accountant or the operations manager what their expectations of the project are beforehand. So focusing on their problems and them as individuals will pay off in the long run and distinguish you now.

Any request, call we have from the client's C level

Of course, if a C-level executive calls you with a problem, there is something behind it. Most of us tech people immediately jump to conclusions, and search for solutions and so on. But our consultative mindset has to make the hard stop and ask "why?" Why do we even have a problem? Why do we need a solution at all? What are the goals, the circumstances, the context? In most cases, this is what the client really needs - to think through the problem with someone with an outside perspective who can help them to see different points of view. After a session like that you will get more phone calls about solving business problems than about fixing routers… (don’t worry, you’ll still get those calls too).

These are great ways to engage clients and open up discussions about problems that need to be solved. From this point forward nothing is going to be a tech-based project, initiative or conversation.
 

Conclusion

If you can just change this one thing about your communication it will pay off heavily. It differentiates you; it teaches your people how to communicate and it shows your client who you really are. This will help you to define your purposes and to communicate them accordingly. It will help you to stay always curious and focus on what matters to the client, instead of the perspective of the tech.

12 mistakes most MSPs make with their vCIO services

The virtual CIO phenomenon is not new, yet the promises of the role have not been realized across the industry. Some mature IT managed services providers who believe they have a functioning vCIO 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 IT companies.

vCIO 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 MSP 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 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.

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.

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

The vast majority of the managed services 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.

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.

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 MSPs, 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.

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.  

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.

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.

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.

Delivery

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

Most MSPs 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.

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.

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.

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 Tool. 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.

Our first book: MSP 2.0 - The Managed Service Revolution

I have to admit we haven't done a lot of blogging lately and there hasn't been a lot of new content, sorry. We do have an excuse: we have completed a book about the MSP 2.0 business model.

We got your awesome feedback on our content- thanks - including the observations that our ideas were all in little pieces, lacking real connection. We needed a more comprehensive and linear format to digest this new concept, and thought that the best way to do so was to write a book. Have a look at what we have to offer in this format, and how you can become a contributing part of the story.

The concept of this book is first to analyse the current situation and then to create the practical but holistic approach to make MSP 2.0 a reality. We wanted to deliver a business-minded explanation about the industry we are in. We have an MSP (Hauser Canada) that we plan to make successful over the next 5-10 years. Everyone sees the problems and the turmoil in the industry, but not the complete solution. We didn’t want to talk tactics, or how to sell the cloud, how to price, or package better. We wanted to show a very viable strategy toward the next evolution of the MSP model and what is needed to move quickly on that path.

We observed that while there is proven prosperity in the MSP program, on the ‘break and fix’ model, but we didn’t have a complete business strategy. It has been a long process to change the model, and most IT managed services providers still have a majority of these contracts. Our goal is to clear the slate and see what’s next:

Introduction:

The MSP 2.0 business model is a great blend of the MSP fixed-fee model combined with the much broader scope of IT Consultancy. This book illustrates that new model such that you can see how an MSP can build a scalable business around it.

Chapter 1: Business Focus or Technology focus:

Many IT companies says they are "Business Focused" but what does that really mean? What are the prerequisites to be able to make that claim? What is behind the value proposition?

Chapter 2: Why the MSP 1.0 model is broken?

Unfortunately, the initial Value Proposition of the IT managed services providers is broken. Nobody really cares about the infrastructure any more. It is a commodity, like electricity, and thus the subject is not part of the C level conversation. 

Chapter 3: Opportunity of the MSP 2.0 model

Meanwhile a substantial untapped potential is arising from the client side: the quest to be more competitive with the help of IT...to grow faster, service clients better, and communicate more efficiently. How do you address this huge opportunity?

Chapter 4: Why is it so difficult?

Do you remember how hard it was to switch from the ‘break and fix’ model to the MSP? There are two major obstacles along the way to implementing the MSP 2.0. This is going to be work too, but there are shortcuts.

Chapter 5: Requirements of the next generation program

If we want to tackle this in a systematic way, what do we need to address - the hurdles along the way we need to prepare for eliminate? What should be the scope for such a program, and what types of components should it have?

Chapter 6: The first Complete MSP 2.0 program

The complete program has many layers, like the framework, education, software, community, business building, and processes for each and every stakeholder. The client, who gets the value, the virtual CIO who delivers that value, and the leader of the MSP who is building the business.

Chapter 7: The Client Perspective

What does the client need to achieve competitive edge? Reduce the complexity of the IT, create transparency and a systematic approach to progress, ensure accountability, and effective collaboration.

Chapter 8: Virtual CIO Perspective

What the Virtual CIO needs to deliver is value in a scalable and efficient way: quick client discovery, implementation of core vCIO services and an IT management framework, effective management of IT Projects including collaboration with the clients.

Chapter 9: The Leader of the MSP perspective

What does the leader need to build a business? A Transition Blueprint Program, Self Assessment, Business Model Analysis, Creating the MSP 2.0 Value Proposition, Inbound Marketing Engine, Lead Generation engine, Predictable Sales, and Implementing the Virtual CIO services.

Chapter 10: The Roadmap for success

What is the typical roadmap for IT managed services providers of different maturities, size, and service offerings? What are the foundations and services needed to implement immediately and grow quickly?

STRUCTURE, MANAGE AND AUTOMATE YOUR ACCOUNT MANAGEMENT AND VCIO PROCESESS

Webinar Takeaways on Selling IT Security and Compliance

It was a really engaging talk with Steve Rutkovitz CEO of Choice CyberSecurity. He is a very successful MSP practitioner specializing in IT Security and Compliance.

We were talking about MSP challenges, strategies, IT consultative sales processes, IT security and compliance opportunities and partnerships, and I learned the following:

Generate client engagement

with five cyber security roadmaps in 30 days

• there are surprising similarities between the mainframe to PC era shift and the PC to Cloud era shift
• To become a successful MSP one of the most important traits is having best-in-class partners
• When you move up streams, you have to make sure you are able to manage management type people
• You have to develop a solid marketing / sales engine to teach your clients and prospects
• The Challenger sales is a great way to leverage the natural teacher inside IT managed services providers
• You can sell NIST Cyber Security and Compliance solutions without doing the delivery side
• The business model of selling IT security solutions through a partner
• The best foot-in-the-door tips and tricks to get front of CEOs
• The complete MSP sales process from “access to address” that maintains the IT security issues
• The natural advisory mindset of IT companies and the potential contained within
  
  

Thanks to Steve Rutkovitz for the wisdom and the honest, straightforward answers. I believe his thoughts could help IT managed services providers in any size and any maturity. You can bet this won’t be our last discussion with him.

Nist Cyber security Framework Quickstarter Pack

MSP Game Changer IT Sales Ideas From The Book - The Challenger Sale

The MSP 2.0 service offering in the 7C IT Management Framework

Upsell your clients with strategic QuaRTERLY BUSINESS REVIEWS and IT strategy meetings

Frameworks in general are good for:

• helping the service provider see all the client’s functions and service delivery areas
• helping the clients understand their situation and the context within a clearly defined system
• measuring the current state against the framework benchmark, define the goals for both parties, and attain team alignment
• creating a transition between the current state and the future state - the action plan

The goal is to move from an ad-hoc attack strategy to more systematic thinking.

This approach is more likely to give a comprehensive perspective so you can make an informed decision where to invest and where not to.

The 7C IT Management Framework was designed to solve the problems of small and medium sized companies. These companies do not usually have a full-time, fully trained CIO or VP of IT, and without a skilled person in that role, IT decisions are made by the wrong people, such as:

• The COO, CEO, or CFO, doing the job part-time, without the requisite experience of the full range of technologies and trends;
• The IT Administrator, doing the job but with no experience in managing projects or understanding business needs; or
• The outsourced, managed-service provider, with no understanding of the scope of the infrastructure and too technology-focused to have the most effective and productive strategy skills.

In many cases all employees work together on IT management. One will prepare a budget, another will plan the infrastructure, and a third will manage the projects. Often as IT managed services providers we are in the middle of this tornado, with no clear responsibilities, deliveries, or measurements. Everything is a bit foggy, but we try our best to do our best for the client.

The 7C IT Management Framework creates the following alignment:

• defining all the necessary elements that could be leveraged to get a competitive edge with technology
• measuring the current IT management maturity through a simple scoring system
• discovery of the business needs through a goal setting workshop
• creating an action plan to get to the target scores
  distributing the work and the responsibility across the IT ecosystem

• more revenue to leveraging technology on the Value Proposition, Marketing, Sales, and Customer Loyalty parts of the company
• lower expenses in leveraging the technology on the Operations, Business Processes, People, and Systems parts of the company
• maximized business continuity, ensuring smooth operations and minimizing the impact of ‘disasters’ on the performance of the company

The 7C IT Management Framework

• Continuous: What is the level of the IT security/NIST Cyber Security?
• Competent: How efficient and professional is the IT ecosystem?
• Charged: How proactive and responsible is the IT ecosystem
• Conscious: How strategy and business focused is the IT ecosystem?
• Controlled: How measurable, governable is the IT ecosystem
• Clear: How transparent or clear is the IT ecosystem?
• Cost effective: How well are costs controlled in the IT ecosystem?

These seven Cs are the key questions every CEO has to answer in order to have a competitive edge in IT. That also makes them the areas in which every MSP has to provide service, in order for the same goal.

As an MSP, you are providing value-added services to your client like backup management, disaster recovery planning, IT strategy building, and providing proactive services.

However, if you do not create a clear structure for clients you won’t inspire confidence. These are interrelated services, but if there are no defined boundaries, structures, or systems built around these individual services you will fail to maximize their potential.

7C, like any framework, is intuitively and expansively organized. The backup management and the disaster recovery are in the Continuous block; The IT strategy is on the Conscious block and the Proactive Services are in the Charge and the Competent blocks. If you can map every service you are doing and show your clients every management area in which there are deficiencies you’ll become aligned and effective.

Use 7C to map all your services and show the clients the big picture. It will also help discover the maturity level of your current service offering, and what services you should develop next.

7C is not a delivery framework. Its goal is not to tell you how to do better backups, or how to develop a better IT strategy. Its goal is to help clients understand what you are doing as an IT service provider, and for you to be able to get aligned on the service with prospects and clients.

One of the most important parts of 7C is the IT competitiveness quotient, which measures all of the 7C building blocks on the client side. It is an award-winning tool, which measures current maturity and generates an action plan based on the client's delivery areas.

Let's look at the defined service delivery areas based on different building blocks.

Upsell your clients with strategic QuaRTERLY BUSINESS REVIEWS and IT strategy meetings

1. Continuous: Services to Increase the level of NIST CYBER security 

Backup management implementation

Keep the data safe and sound, without any chance of data loss as a result of any single point of human error, lack of responsibility, or technical failure.

• Backup policy, regulation implementation
• Backup process implementation
• Backup process responsibilities setting
• Data recovery testing & implementation
• Offsite backup implementation
• Data recovery plan implementation
• Offsite backup solution implementation

Have a plan for when a disaster happens. It is a practical document that walks through all possible scenarios in case of an emergency event.

• Business Assessment
• IT Assessment
• Disaster Recovery Plan development
• Disaster Recovery Plan implementation
• Disaster Recovery Plan audits

Implement the best practices that can help to drive a smoother, safer, and more secure environment. This involves both systems and people.

• Corporate Information Security policy and regulation implementation
• Corporate Information Security guidelines, education & implementation
• User role and Lifecycle management implementation
• BYOD management implementation
• Password management implementation
• Risk management implementation
• Ethical hacking testing services
• Physical IT Security protection implementation
• IT Security, policies and procedures implementation
• IT Security governance implementation

Implement some very basic tools to increase the protection of the IT environment, devices, storage and systems.

• Mobile Device Management implementation
• Encryption management implementation
• Access management implementation
• Onsite data access management implementation
• Online access management implementation

2. Competent:Services for a more Efficient and Professional IT Ecosystem   

Managed Service Implementation
Create the most advanced and efficient IT service environment. The infrastructure management is a core functionality and has to be done in a very professional manner. Using the latest automation and management tools, centralized services, and monitoring key to success.

• RMM Service Implementation
• PSA Implementation for Ticketing, Project Management, and Asset Management
• Knowledge Base implementation
• NOC service Implementation
• Disaster Recovery Plan Implementation
• Asset Management Implementation

Achieve high level proactivity. IT is here to maximize overall productivity, but often even if we have the latest software in place, the client team is not aware of the advances and can get frustrated when the interface moves buttons. There is no shortage of personal productivity tools around but they are losing their potential business impact when the team is not shown how to use them to create a personal operation system with to-dos, calendars, and emails.

• Proactive End User Training Program Implementation
• Proactive Internal Self Service Knowledge Base Implementation
• Proactive Personal Effectiveness Program Implementation
• Proactive Business Process - IT Alignment Practices Implementation
• Proactive System Integration Practice Implementation

Create and generate as high tenancy as possible for the given budget. You could influence the uptime of the overall systems with the professional services. Most of the job is proactive maintenance, standardized infrastructure, and redundancy. Discipline is the watchword here.

• Redundant Infrastructure Implementation
• Standardized Infrastructure Implementation
• Server Side Patch Management Implementation
• Desktop side Patch management implementation
• Life-cycle, Recycle Management Implementation

Manage the IT ecosystem at the most professional level possible. Most IT management jobs are done by one of the C-level executives with an internal admin assistant and perhaps a third party MSP. These three roles don’t cover the needed management capacity. A Virtual CIO and a third party IT consultant need to be in place for the following activities.

• vCIO Role implementation for IT Strategy Development, and Leadership
• vCIO Role Implementation for IT Strategy Execution, and Leadership
• vCIO Role Implementation for General IT Leadership
• vCIO Role Implementation for IT Infrastructure Management
• vCIO Role Implementation for IT Security and Risk Management
• vCIO Role Implementation for IT Consultancy, and Representation

3. Charge: Services to Increase the Level of IT Service Maturity

Managed Service Implementation
Implement Managed Services not just for the professionalism but to maintain responsibility as well. That means creating a service offering around the overall responsibility and accountability of IT using tools, policies, systems, and best practices to make sure nothing falls through the cracks and customer expectations are always met through assured alignment.

• Ticketing System Implementation
• Disaster Recovery Plan Implementation
• SLA and Ticketing System Implementation
• Dedicated Service Manager Implementation
• SLA for Overtime Implementation
• SLA for Special Device Implementation

Create all the necessary proactive services to prevent problems or fix them as soon as possible. Monitor, optimize, and remediate if required. This is not just related to the infrastructure but for the business processes as well. 

• Proactive Maintenance Practice Implementation
• Proactive End User Training Program Implementation
• Proactive Optimization Practice Implementation
• Proactive Onsite Support and User Feedback Implementation
• Quarterly Business Analysis and Reviews Implementation

Manage the responsibility and accountability of many internal, external , and third party resources and vendors. On average a "Virtual IT Department" consists of at least 15 parties (ISP, Software Companies, Consultants, Hardware Vendors, and Service Providers etc.). Who is the boss? Who is responsible for what? The issue here for the CEO is that if no one is responsible then ultimately he/her is responsible. These workshops are a great tool to align and organize the team.

• Responsibility Matrix - Including the CIO Role Implementation
• Responsibility Matrix - Main Categories Implementation
• Responsibility Matrix - Education Implementation
• Responsibility Matrix - Main Categories Implementation with Ticketing System Aligned
• Responsibility matrix - Attached to the Contracts

4. Conscious: Services to increase the level of strategic IT focus

IT Strategy Planning Retreat
Create a rock solid IT strategy in a very short timeframe. Executives’ time can’t be wasted sitting and talking for days. What is the best practice for spending 4-16 hours of work to create a very solid IT concept, roadmap, or strategy? The answer includes processes, best practices, efficient data collecting, and decision making techniques.

• IT Strategy, External Review, SWOT Session
• IT Strategy, Internal Review, SWOT Session
• IT Strategy, IT Ecosystem, Infrastructure Audit Session
• IT Strategy, Business Modelling Session
• IT Strategy, Virtual IT Department Evaluation Session
• IT Strategy, Business Functions Mapping Session
• IT Strategy, Business Processes Mapping Session
• IT Strategy, IT Functions Planning Session
• IT Strategy, Strategic Initiatives Planning Session
• IT Strategy, Development Roadmap Session

Create detailed guidance for the execution of the strategy. This should be a year long plan with all the deliverables, initiatives, projects, priorities, and responsibilities necessary for flawless execution. Most small businesses do not have these plans in place. They often see it as too much work to create them, so the cost/benefit ratio precludes it. Again the keys are the processes, templates, and best practices to do the work in the very small amount of time.

• IT Operational Plan, Budgeting Session
• IT Operational Plan, Capacity Planning Session
• IT Operational Plan, Priority Setting Session
• IT Operational Plan, Resource Redistribution Session
• IT Operational Plan Finalizing Session

Execute the plans adeptly. The agile methodology helps to create closed loop systematic rhythms around the execution. The key is to foster alignment on the deliverables and set expectations on time and budget. The most often overlooked factor is the personal time capacity planning. You have to set aside time for managing and doing all the project related work.

• Quarterly IT Execution Plan Implementation
• Monthly IT Execution Cycle Implementation
• Weekly IT Execution Cycle Implementation
• Project Execution System Implementation
• Quarterly Performance Management Implementation

Upsell your clients with strategic QuaRTERLY BUSINESS REVIEWS and IT strategy meetings

5. Controlled: Services to ensure a robust IT Ecosystem with Agile IT Governance  

IT Performance Management Best Practices Implementation
The goal here is to maximize reliability through implemented best practices. Quarterly and monthly target setting measures performance and creating action plans drives costs down and increases efficiency.

• IT Performance Management Framework Implementation
• IT Infrastructure Planning and Monitoring
• IT Management Planning and Monitoring
• IT Strategy Planning and Monitoring
• IT Vendor Planning and Monitoring
• IT User Development Best Practices Implementation

While it’s great to think big-picture during the IT strategy session and develop fancy projects we need to reach our goals, we have to use specific IT related project and program management best practices to make sure that we are not just dreaming, but executing flawlessly.

• Key IT Initiatives Management Best Practices Implementation
• Key Project Budget, Risk Management Best Practices Implementation
• Key Project Visualization, Planning Best Practices Implementation
• Key Project Change Management, Communication Best Practices Implementation
• Key Project close Best Practices Implementation

Ensure everything is safe and sound and works as we think it should be working. The various types of audits not only let us sleep better, but also keep up awareness of specific areas. To create such internal compliance requires a higher operational maturity.

• Independent Auditor Service Implementation
• IT Audit Process Design Based on Best Practices
• Data Security Audit, Disaster Recovery Audit, Data Backup Audit implementation
• Server Management Audit, Network Audit, Server Room Audit, IT Services Audit Implementation
• IT Management Audit Implementation

Organize the IT Ecosystem. This is a virtual department with 20 to 30 different vendors. Who is the boss? Who is working together? Who needs what information? How do we assist communication? It is worth the effort to establish order to get maximum value from our vendors and internal resources.

• IT Operation Process Best Practices, IT Operation Policies Best Practices Implementation
• IT Operation Manual Best Practices Implementation (Knowledge Base, Administrator's Guide, Responsibility Areas)
• Collaboration Platform Implementation, Ticketing, Project, Yearly, Quarterly Planning, Alignment
• IT Organizational Chart Design
• Competence Management and Personal Growth Plans

6: Clear: Services to maintain transparency of the IT ecosystem 

 
IT Reporting Practice implementation
Develop the necessary reports to be able to measure the performance of all departments and groups. What we can't measure, we can’t manage. This is not an exercise in flooding the C level with reports. It means delivering critical weekly, monthly, quarterly, and yearly metrics of business performance.

• Reporting Framework Implementation
• IT Infrastructure Reporting Implementation
• IT Management Reporting Implementation
• IT Strategy Reporting Implementation
• IT Vendor Reporting Implementation
• IT User Reporting Implementation

Establish clear aligned definition of who is doing what. Going through the 200+ responsibility areas, from checking on the backup to aligning the technology with the business needs is going to raise a lots of questions. Who should do what to make sure nothing is ignored or forgotten. Again the takeaway for the CEO is that if no one is responsible for an element of the matrix, ultimately the CEO is. It is better to know who does what before you need them to. 

• Responsibility Matrix Audit, Interviews and Workshop
• Responsibility Matrix Management Implementation
• Team Dependency and Risk Analysis

The goal is to create the Service Level Agreement (SLA) internally. That means identifying all the necessary services the company need, make decisions on the needed quality, speed, cost, and create alignment on this. The internal audits could make sure the agreement is not just a paper on the shelf.

• Internal SLA Creation based on Template
• Internal SLA Enforcement

Use the most efficient tools as possible in IT management. If IT wants to make the company more competitive, it first needs to be competitive itself. Using the latest and best efficiency tools is key to drive costs down.

• Execution Management Tool Implementation
• IT Maturity Management Measurement Tool Implementation
• IT Document Management Tool Implementation
• Password Management Tool Implementation
• Budget Management Tool Implementation

Make clear that the client is in the driver's seat and not the vendor. Vendor management means yearly negotiations on prices and services, switches if needed, mediation on tough problems, and enforcement of the service level agreement. Make sure they are creating the value we agreed on.

• ERP Vendor Management Implementation
• Telco Vendor Management Implementation
• Cloud Vendor Management Implementation
• General Vendor Management Implementation
• Printer Management Implementation

7. Cost Effective: Services to minimize the costs of the IT ecosystem 

IT Budget Management Services Implementation
Create and manage the most cost-effective IT budget. What is included in the budget needs to be strictly defined because everyone has to be on the same page when we’re talking about costs, expenses, budgets, targets, etc. Setting a budget is incomplete without proper governance, reconciliation, reporting, and solid decision making.

• IT Budget Planning
• IT Budget Controls Implementation
• IT Budget Reports Implementation

Analyse all the IT related processes in the organization. Are there any new tools we could use? Is education required to use the current systems? Is there any integration that could be done to make their processes leaner? A service offering encompassing these topic is a great tangible source of continuous improvement and total quality management.

• Continuous Process Improvement Implementation

Manage every aspect of IT in a lean and straightforward framework. We create and implement the 7C Framework based on the 7C methodology.  We must understand that the vCIO is a high level IT Executive and can be a third party. The framework he/she implements, manages, and further develops is based on;

• 7C Methodology Implementation
• 7C Certified vCIO Implementation
• 7C vCIO Toolkit Software Package Implementation
• 7C vCIO Community, Continuous Education Implementation

Manage all IT expenditures of a company and keep them as low as possible. Set up rules around purchasing, and create standards to achieve a homogeneous environment including managing all software subscriptions - key to keeping the costs down.

• Purchase Policy Implementation
• Standardized Device Policy Implementation
• Software License, Subscription Service Implementation
• Purchase Process Policy Implementation

Conclusion

The services discussed here are not new. What is new is the perspective. We can see the goal, see what the different services are about, and how to frame the services so that the client understands their value. It is an alignment tool to help clients understand their situation and to help them make informed choices.

You are able to help your clients without having capacity, knowledge, and experience in every service. You are able to be the one and only trusted advisor and vCIO, and outsource the rest of the work, with partners who excel at creating a budget, strategy, or security. That is your value in using the framework: being the big-perspective guide on IT, and ensuring the smooth, natural delivery of a professional trusted advisor.

The process of becoming the Trusted Advisor

For Managed Services Providers (MSPs) the ultimate goal is becoming the ‘trusted advisor’ on all things IT.

We’ve created a process which enables MSPs to earn this trusted advisory role as fast as possible. The key is to understand the client, and in turn help them understand their situation and their opportunities.

Looking into the 7C Methodology and processes can be a tad overwhelming at first, we know. It’s so effective because it’s comprehensive, so there is a learning curve. However in our continuous effort to make everything as simple as possible, we’ll start by emphasising a couple of core concepts.

One of the crucial elements is the client reframing process. From the client’s perspective it’s a discovery process, the goal of which is to make the necessary transformation to start working with the client at a new level. The key component of the process is the Reframing 7C canvas workshop, where we ask questions of the client’s business in order to help the client rethink basic assumptions about IT and its management. Normally such a fundamental shift is a tough, very high level process, but if you’re properly prepared to ask the right questions and challenge the client, it can be a very easy and straightforward process.

Client Discovery

So to be able to conduct the workshop - the central element - with confidence, we have to be as informed as possible regarding the client, as well as the nature of the company itself: the key players, industry etc. We need a streamlined data acquisition process to be able to immediately focus on what matters. With an established client this is much easier...it’s the new for whom you must prepare a bit more.

If you peruse the 7C Report, you’ll find it entails all this needed information about your client in IT function and their IT management perspective.

To be able to get the necessary data from the client and to be able to make the analysis and build the report, you need input. This input comes from the questionnaire you get your prospective client to fill out - not the client's ‘IT guy’, or service provider, but the CEO of the company -the one responsible for the IT in general at the senior level. We’ve provided several helpful methods encourage them to fill out this questionnaire. If it seems like a big deal for them you can infer either that they do not trust the value of the process, or that they see little value in IT generally. In either case you can make the transition with the workshop, so do your best to get started with the questionnaire.

This is the discovery of the client that prepares for the workshop.

Reframing Workshop

In the workshop you are going to use the 7C Canvas as a companion. It goes on your wall and comprises all the building blocks of the competitiveness of IT.

This is meaningfully accessible to the client: there is the IT execution segment, and the IT management - both cost-effectiveness and the competitive edge. It creates a conducive platform for talk about the company's challenges, issues and the possible IT related solutions.

First of all the Canvas will assist your confidence in the meeting, with the information on the wall 100% aligned with the report, scores, etc.

Secondly, it outlines the structure of the session, which in turn helps you to facilitate it.

Thirdly, it engages the clients in conversation - this is a workshop, and your goal is to work together and strengthen the relationship.

Fourthly, unlike some workshops, the Canvas remains, a good basis for further conversation between the CEO and the rest of the company.

The outcome of the meeting is some initial action items involving overall objectives, directions, and possible initiatives or projects.

Action Plan

Your next duty is to build a comprehensive action plan for them based on the results, and set a possible achievable target score, and to put everything in context, set priorities, state realistic expectations about IT project sizes, IT budgets, possible results, and the necessary capacity from the senior level or from staff.

So now you are becoming a natural leader of their Global IT, not just the infrastructure, background, support etc, and you can come up with big projects and industry changing initiatives with IT. This is the process of how to start your work, what you need to achieve the first quarterly plan.

As you start the first company-wide quarterly plan (the cornerstone and "trial" of the MSP 2.0 model), you are incurring more information, more trust, and even more loyalty.

Here’s where we kickstart the MSP 2.0  onboarding process to implement all necessary parts of the model - where you are able to start the complete IT management operation with the client.

Conclusion

Maybe you see this is a long process, but slow is fast and fast is slow in this arena...the initial investment of preparation will soon lead to a pivotal element, the inflection point which is the workshop. You get the client’s attention and from there are able to reframe them.  Discovery and the preparation, workshop, action plan, and finally trial quarterly management - these five components give you the proven process of client reframing.

Why are clients lately needing more consultative work from MSPs?

So we all agree that IT companies are facing challenging times, right? We all need to figure out a new business model in the near future. But what about the clients? Are they facing a similar problem? We have to take a good look at what’s happening on the client side to understand the trend.

We’ll use a chart to make the explanation easier. We’re looking at how things have changed in the last couple years, and where it could go. 

In this chart the horizontal axis is the business impact of IT. It shows how in time, the overall IT influence has changed on the client's side. How the IT impacts their everyday activities, but also product development, communications, service offerings, manufacturing and so on.

On the vertical axis you can see the overall complexity of the IT ecosystem, showing that over time it also has changed on the client's side: the number of different processes supported by an IT system, the amount of software and, hardware, connections, and network infrastructure in their ecosystem.

We graphically emphasize the overall IT management challenges with bubbles. The bigger the bubble gets the bigger the management challenge on IT.

So meet Carla, who runs a travel agency with 75 people and in a growth mode which she started in the mid-eighties. She’s quite IT savvy, and so has several legacy custom software applications still in use from way back then - word processors etc. IT wasn’t always a big deal, nor so complex, and had a very limited impact on her business.

In the nineties, they all upgraded to PCs, fax modems, better software, Windows - the big boom of the PC era. At first only the IT-savvy few were using that software, but as Carla upgraded to a more integrated ERP, the whole company started to. IT was getting more and more complex, with more software and hardware.

Even the reliability of a smooth running system was a big issue, but because everything was still backed up in hard copy, in the case of an outage the operation wasn’t catastrophically ground to a halt. When such management issues came up, someone internal who was familiar with the systems did the techy work.

Since 2000 the internet has become ubiquitous in business, so they upgraded again to a better ERP with CRM, and more communication to clients, and invested heavily in infrastructure with servers.
Because collaboration and email was a daily use they had to keep up with new tools as well as products being constantly developed. Every three years they’ve had to change the whole infrastructure with PC-s servers and softwares.

The local IT person was no longer able to manage so they switched to a IT Managed Services Provider, who was able to support all their systems from a technical standpoint, including helping them figure out upgrades, projects, and developments related to the IT infrastructure.

That was the “BC” era... Before the Cloud. In 2010 the cloud became the new standard, and we’re now ‘AC”...After the Cloud.

Carla has several internet based applications running. Now she can acquire and usually run nearly every IT function from the net.

Still she does not want to put everything in the cloud; just the most basic things, both to be more efficient and to incur less expense as a service. She enjoys the continuous development of the services without having to involve herself in big projects, upgrades, or infrastructure investments.

Small companies next emerged in the beneficial new milieu of AC, and had very cheap products available immediately without any server, or PC work. So they decreased their budgets supporting the old-fashioned infrastructure. They switched to Office 365, relying heavily on Google Apps with clients, using mobile devices with dropboxes, etc...hundreds of applications tied to devices without any coherent structure or defined boundary.

So Carla missed the direct but responsibility-laden control of the infrastructure in a way, but is prepared to move on. All she really needs is someone who can give her the control back, but the myriad vendors, ERP, CRM, B2B, B2C, cloud applications, integration software developers, and web developers are overwhelming her.

The MSP is doing his job, but there’s a role going unfilled: someone who puts all this together. The business impact is enormous now; if a system goes out, the company can be entirely missing a part of the operation.

The complexity of the ecosystem is now very high, and aching for adequate control.

This new role needs to be a very high level non-technology oriented management duty. Currently only the structure of the IT is managed. Unfortunately her MSP is focusing on too much on the technology side, which is not an issue. She is missing the management part - the Global IT budget, the management of vendors, the direction of projects, security in global, real IT strategy and so on. The MSP is performing their job at a high level, but aren’t able to give a comprehensive solution for her IT altogether.

So we see the challenge of Carla is to get something that seems beyond the scope of her current Managed Services Provider. She could go the path of developing an internal staff, and solve the problem sooner or later, but it would be far more competitive if the IT company could transition to the MSP 2.0 business model, which is basically management of IT with a global approach to give a competitive edge. Carla is willing to pay the additional fees to the MSP, as they have an established relationship, and she trusts she’ll get the functionality and performance she needs.
 
Carla needs a new working model from the MSP.