Sage News and Discussion

ICYMI (In case you missed it) , Sage appears to be shifting quite a bit of their communication from formal emails to partners to general communication via (a) Twitter and (b) Sage City. https://twitter.com/SageSupport is the main Sage Support Twitter account and appears to update quite frequently with various tech links. Unfortunately, these links are not product specific so you'll need to wade through links to product support areas that you don't regularly work with. Sage City is emerging as Sage's area to announce new products (the Sage 100 2017 release info first appeared here before Sage's hasty (and awful) email to consultants (I think it's fair from here on out to stop referring to us as partners because the signals Sage sends definitely don't seem as if they do). http://sagecity.na.sage.com/blog/b/sage-insights/archive/2016/10/31/three-year-end-tasks-you-can-do-now

Direct link to the Sage Year End Center 2016 - http://sagecity.na.sage.com/p/yearend

This is a pretty comprehensive landing page for year-end questions on Sage 100. It would be interesting to have a conversation between consultants at MOTM 2017 on how we can plan now so that we are not made irrelevant as Sage continues to reach out directly to end users. - Upgrades - Managed services (upgrades, product updates, some on-site visits) vs traditional phone support - Collaborative group projects (end users LOVE being able to ask for feedback on products and receiving a summary from our collective experiences - we should do a LOT more of this because the publishers really cannot match this depth) - Recognize that we likely need to concede the low end break-fix budget conscious market (we should really be in the speed of response and problem-solving market not the hourly break-fix) - Which customers to funnel to Sage's support and which to work to retain internally - Plan for the continuous ratchet down of margin both on maintenance and new licenses (migrate to a largely consulting $$ world)