General Consultant Discussion

 View Only
  • 1.  Best Practices Working with IT Service Providers as a Sage 100 Consultant

    Posted 12-30-2024 17:02

    Today has been unfortunate for a Sage 100 user because their new IT services provider chose to solve a problem outside of their skill set. The problem wasn't with Sage 100 software. We were contacted after 6 hours of being unable to resolve the issue. After 20 minutes we found that databases in SQL Server had a status of pending rebuild. The databases were rebuilt, and Sage 100 was up and running. The substantial time lost shipping at the end of the year will impact our mutual client.

    This isn't my first experience with an IT services provider with good intentions working outside of their area of expertise. IT service companies bundle application support into their service agreements but have difficulty delivering support of Sage 100.

    We want to be supportive of our mutual client. On the other hand, our position is that our business is not training IT Services companies who compete with us for support on Sage 100.

    How have other consultants addressed the challenges posed by IT Services companies?

    Do your support agreements have financial provisions when external IT service providers are involved?

    Other approaches you have found to work?

    Thank you.



    ------------------------------
    Myron Stevenson
    Consultant
    Clearis Consulting, Inc
    Duluth, MN
    218-525-6720
    ------------------------------


  • 2.  RE: Best Practices Working with IT Service Providers as a Sage 100 Consultant

    Posted 12-30-2024 18:03

    Honestly. Myron, that's why we started our own IT division at Bennett/Porter.  We've worked with many IT Providers over the years, but they often contradicted our advice because they considered us "Bean Counters" who knew nothing about networks.  We hired an IT liaison originally, who could speak both Sage 100 and IT, but we were giving away very valuable services and only helping the IT vendors.  So – we brought those services in-house and it has eased the workload incredibly.  Now, when a client's outside IT company calls for help, we can invoice either the client or the IT Company for that help.  And now the majority of our Sage 100 clients are also our IT Clients as well.

     

     

    Sue Bennett/President

    P. 503.620.3484 / E. sue@benpor.com

     

    Bennett/Porter & Associates, Inc.
    12559 SW 69th Ave / Tigard, OR 97223
    benpor.com / facebook / instagram

     

     

    A black background with a black square  Description automatically generated with medium confidence

     

    The information in this email and any attachments is considered confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

     

     






  • 3.  RE: Best Practices Working with IT Service Providers as a Sage 100 Consultant

    Posted 12-31-2024 09:19

    This is a frustrating (and growing) issue.

    IT Service Providers ( AKA MSP or Managed Service Providers ) are the new reality.

    This is also what we used to call outsourced IT. And you're right - they want to have a one call (monthly fee) solution to servicing the customer.


    I'll summarize what I've found to work:

    - Don't do hourly break-fix.

    - For one annual price cover these types of Sage 100 issues - if the customer is under a plan they shouldn't be afraid to call/email you first

    - Don't work/bill through an IT/MSP ever for any reason whatsoever.

    • Most ( but not all ) IT/MSP will be glad to know you have an agreement with the customer and should call you for Sage related issues
    • Candidly, I have one or two customers with these types of MSP relationships and I'm fine with it and I'm also not working as the MSP's unpaid support department. Don't be a bashful biller in these situations...

    In other business type news...

    What I learned in 2024: 

    • Triple any quote when you are having initial meetings with 2+ IT people / high security industries
    • Put a limit on the SOW for the time when work is going to begin and when it's going to end - and exceeding that is subject to a new project change request. In today's environment I'm running into reorganizations where the contact leaves and a new one comes in and wants me to be the handholder to walk them through what's happening in their own company. Better yet there should be a standard term that says if the contacts change the SOW gets repriced.
    • Any scheduled time in December or January is priced from the start ( on every quote ) at 250% above standard rates ( doesn't matter if the customer started talking about it in February and signed the paperwork December 1). I do not want more 12/31 work during the holidays and weather issues in the Northeast. Truthfully 99% of these "have to go live on 12/31" don't have to go live on 12/31 and they WON'T go live if given a quote that treats year-end work as premium priced. This year-end work frequently takes me away from loyal paying customers for one-off projects. 
    • Toward the middle of 2024 I was required to start re-billing for all sorts of third-party solutions/quotes which were previously billed/quoted direct to the customer. After trying to work out a happy medium way to make this process easier I saw no other choice than to build in a fee for being the middleman. My solution was to add 5% ( minimum $80 ) for handling re-billing or re-quoting on behalf of customers. This fee recovers any credit card payment the customer users as well as a small portion of my time to track this nightmare.
    • One thing that has worked very well for me on larger upgrades where before they used to drag their feet and the upgrade might go on for months beyond our planned go-live is to price the upgrade as a monthly fee and that the duration would be from mm/dd/yy to mm/dd/yy and if it exceeded that date then the monthly payments continue. I set the customer up for a recurring monthly payment ( I use Freshbooks) - build in a 5% payment processing fee which applies whether they pay by check or CC.  So if my price on the upgrade is $100 I just automatically add 5% and presume 90% of the customers will pay by credit card. 

    What I need to get better at in 2025:

    • Limit my check-in meetings or develop a price for them above a certain limit. On some days I've had up to 5 check-in meetings on various projects and candidly these are frequently nothing more than the customer not having done their homework and wanting you to do it for them on a video call. No thanks. And I need to be better about "I have a call in x minutes so I have a hard stop and need to leave this call".
    • Scope, scope, scope. Especially for new customer / one-off projects. Need a start and a stop date on projects ( are these ever truly "done"?). I'm finding some projects seem to go on forever and if allowed the customer starts to throw all sorts of "what about this". Maybe this is an off-shoot of suddenly finding myself in the midst of so many check-in calls. What I'm thinking of is that the project will be defined as starting on mm/dd/yy and ending on mm/dd/yy with x check-ins on each (day) at (time) with any work beyond that subject to a change request/new proposal.
    • I'm stealing some verbiage on dormant / cancelled work so that if the customer stops returning calls then I have a defined period after which the project is by default done and there are no refunds. This doesn't happen very often and I think the risk is mostly with new customers.



    ------------------------------
    Wayne Schulz
    wayne@s-consult.com
    Schulz Consulting
    (860) 516-8990
    CT
    ------------------------------



  • 4.  RE: Best Practices Working with IT Service Providers as a Sage 100 Consultant

    Posted 12-31-2024 09:57

    I'll echo what Wayne said - it's a very real, growing issue, and it's not looking to improve as MSPs become more commonly adopted outsourced solution providers. 

    To your questions...

    • How have other consultants addressed the challenges posed by IT Services companies?
      • I've focused less on the challenges of other vendors involved and focused on what I will deliver as their partner. The IT companies mean well, but one thing that I've found works really well is simply establishing yourself as the SME to the MSP. Candid conversations of, "I am the subject matter expert for this customer's systems (ERP, CRM, etc.) and can/will fix whatever you break, but I will bill the customer for my time and services, which may include added fees on top of an established agreement. Before you make sweeping changes to the server (updates/security patches, upgrades to other software, etc.), please let me know what the plans and timelines are for those so we [MSP and my firm] can take a proactive approach to managing the customer's systems and solutions. Thoughtfully planning changes goes better than reactive break/fix experiences - for [the MSP], for the customer, and for us." I've found that this transforms the narrative a bit by being very firm in who you are and the services you offer while giving them some guidelines as to when they should be reaching out to you. You're also making it very clear that your time is valuable and conditions of your agreement do not provide coverage for tampering within the environment which you're charging to manage. It also ensures the customer is aware that you're holding yourself accountable, but you're not overextending yourself or trying to cover the chaos that comes with IT consultants with an invulnerability complex.

    • Do your support agreements have financial provisions when external IT service providers are involved?
      • 100%. Whether it's a monthly agreement or an hourly statement of work - I ensure that my deliverables are what I can solely be held accountable to. I also call out changes to the server made by any other party besides my firm. Regardless of monthly agreements or SOWs, I specifically mention that time spent resolving issues created by any other party other than my firm are to be billed at an hourly rate above and beyond the agreed upon scope. This protects me and sets very clear expectations with the customer that you're not going to be held accountable or liable for situations created by people outside of your team.

    • Other approaches you have found to work?
      • I can honestly say that I have more approaches that haven't worked. @Wayne Schulz called out a couple of them already (never billing through an MSP - you become beholden to their agreements and terms in addition to your agreement with the MSP; get everything in writing about external/third parties as you can't warranty or guarantee things outside of your spheres of control, etc.). 
      • The most effective approach is what you put in your contracts/agreements with your customers. Explicitly cover what you can be held accountable/liable for while taking the same measure of exclusion when it involves third parties (MSPs, ISVs, etc.) and what those exclusions will cost your customer in the concepts of response times and additional costs. It's very much a "no surprises" type of billing arrangement.

    I hope that helps and your situation finds an amenable conclusion. Best of luck with your current situation.



    ------------------------------
    Best Regards,

    Basil Malik
    President/CEO
    e: basil@malik-inc.com
    ------------------------------



  • 5.  RE: Best Practices Working with IT Service Providers as a Sage 100 Consultant

    Posted 01-01-2025 11:18
    Edited by Gary Feldman 01-01-2025 11:22

    The relationship with MSPs and customers is deeply affected by your organizations size, specialty and objectives.   A traditional "value added reseller" is looking to grow its customer base, increase its valuation and other objectives that do not exist with sole practitioners or smaller consulting focused organizations.  Since "reorganizing" as a consultancy I try to avoid break fix support and focus on projects.  The reality is we all will have some level of "support" and we are all impacted by third party service providers whether they be MSPs, third party product developers, independent consultants or the actual value added reseller whom we are working with.

    As an independent I have learned from @Wayne Schulz, John Shaver and @Ed Kless to think more creatively of my relationship with customers and the other entities working with them.   Both Wayne and @Basil Malik point out the importance of the clarity in the services agreement.   Although none of us want books to cover every possible situation, we must outline the limits and conditions of our service.   I address many of these issues by being clear that we are not an on-demand consultancy but need to be scheduled.  Most of my engagements are sold on a monthly fee for a specified capacity, similar to a retainer.  We don't specify a number of hours, but do specify an anticipated scope for the period of the engagement, and when continued, typically for the upcoming quarter and clarified on a monthly basis.  Although this limits the number of customers an individual can work with at one time, I would rather work with fewer customers at a time with greater focus and profitability.

    With respect to the MSP situation, we recently encountered the resistance to cloud migration from the MSP who managed the local infrastructure.   We engaged them with the Cloud Service Provider and had to utilize a frustrating amount of our "capacity" explaining the obvious and mitigating their security concerns.  In the end, that investment of time clarified their ongoing role (and that they would remain entrenched), and that they were really only losing one monthly server fee.

    My advice is leave the local IT to the  people who want that work and move your ERP systems practice to a cloud partner who understands the product and wants to work with you as the consultant.  Upgrade and break fix support is a lower value service that will continue to migrate to the publisher.   Focus on the business value you can create as an application and business expert.   Publishers have continuously proven  that they are not as good at developing the close relationship to the customer that provides the best service experience.



    ------------------------------
    Gary Feldman
    Principal
    I-Business Network
    Marietta GA
    16786270646
    http://www-i-bn.net
    ------------------------------



  • 6.  RE: Best Practices Working with IT Service Providers as a Sage 100 Consultant

    Posted 01-04-2025 18:30

    The recommendations from seasoned vets Basil, Wayne, and Gary are excellent. I will put a somewhat different spin on them.

    1) We are NOT IT consultants, despite the common image we have among our customer's senior execs. We must work at talking about ourselves with that in mind. "We are your BMT support and consulting resource. We work to ensure that your operational data goes into the system as effortlessly and correctly as possible and that you get the information you need (and the whole point of your BMT investment!) as completely and timely as possible.

    "From that goal, we try to turn your BMT into a "black box" utility like your water or electric service. The ERP world is quickly moving to make this dream come true.

    "The only way we can affordably and effectively deliver on this promise is to let us have sole control over the systems on which the BMT software resides. We prefer to do this by putting the system onto a cloud utility provider and effectively turn this into an "app" with which your other IT consultants will very little interaction. (It makes their jobs easier and more effective too!). But as a next-best we require a single ERP server in conjunction with a dedicated RDP-type delivery server. "

    When you have the arrangement with the customer defined more-or-less this way, now you have sole responsibility for this. It ALSO lets us talk with senior management in a less convoluted manner. 

    2) Wayne's details about meetings, responses, etc. are spot on. We only do fixed-fee work, with good/better/best proposals. We define how many meetings to have, how much lead time for scheduling, the deliverables by each party, sessions for training, detailed definitions of completion and by whom, and how much time they have to respond to our questions, drafts, or other deliverables. We consider that task completed if we don't get adequate responses in the agreed time. If they want to change it after that, then a flat fee (usually starting at $300) is charged. If they try to schedule on a shorter time than included, it costs another $300. In other words, they pay more if they don't follow the expectations. 

    (BTW, we don't define how long virtual meetings will go. Nobody wants to sit for more than 2 hours. Same for training sessions: we define one as "not to exceed 4hrs, and they never go more than 3.)

    Like all our work, projects are prepaid and come with a money-back guarantee. Penalties are paid as they are incurred, or work stops.  

    The "good" option has reasonably tight deadlines, minimum number of "draft/review/fix" cycles, etc. If the project is not a new installation, it's pretty straightforward to define the deliverables/definition of complete. (But, it IS hard work for you to develop your first template for this, but but after that, they are easy to expand/modify for a new situation.)

    This lowest-level project plan is laid out as one that could happen if everybody is paying attention. But because management is painfully aware of how hard it is to herd their cats, and the penalty costs of not meeting them are quite clear, they always choose one of the other 2 options, which have looser deadlines, more meetings, more reviews, etc. 

    In more than 10 years, I've never had pushback on this approach. It makes obvious business sense to the buyer. 

    We must all figure out how to turn our customers' Sage 100 usage into something like Intacct or Acumatica. The longer we let the customers run it like they did in 2010, the faster the day will come when they leave all the IT BS for this essential function and move to a cloud system.



    ------------------------------
    Jerry Norman
    Smartbridge Partners
    (512) 653-7498
    ------------------------------