Sage News and Discussion

A tentative meeting this Friday was set with Tim Sullivan, Joe Langner and possibly one other to discuss the role of JobOps in any strategy at Sage. They initiated the meeting with me. Not happening now, because I was told ""interest in JobOps is low"". I told Tim that's the problem. This has always been true, so I'm not really surprised. Whatever - I have some cross-selling to do and sell add-ons to the installed base customers, as Joe is going to review at the Partner Webcast on Monday. I always considered JobOps to be a cross-sell opportunity that drives Sage sales, but Sage apparently doesn't bother with metrics on that.

Interesting - I was at the ITA conference where Sage held a public briefing and the Job Ops guy (at least he identified himself as from Job Ops) was rushing to see Joe with his business card. My guess is maybe that was the meeting they were trying for ? Quite a few years back when I went with Sage on my one and only trip that I went anywhere with Sage (for a Sleeter Conference) I remember asking why they didn't buy Job Ops (sometimes I know the answer but I like to hear the response). Sage essentially said that the problem was the knowledge that was bottled up in the people who had created and who maintained the software. If those people were to leave - and I don't think Sage is big on integrating any remote offices - then there probably would be a problem maintaining and upgrading the software.

Wayne, you saw through my phrase """"the role of JobOps in any strategy at Sage"" or maybe it was obvious. Yes, it really was a consideration of integrating it through acquisition. It's my impression that some of the past acquisition activity was not completely wise, so Sage is being careful with what they do in this regard. Alchemex was a natural fit for their BI strategy, but this may not be. The problem I see is that there is little of no real knowledge of what JobOps is at the channel sales level and even less at the upper management level. That's been true with any of the costing and manufacturing solutions - Job Cost and Work Order. If they really understood those, they would not have been left behind.

Plus Sage seems to be focusing on adding features that can be rolled across product lines. If it only works for one, they're not interested.

Yes, Robert, that's always been an issue. I tell them that they should take functions such as the configurator and redesign for general integration with other packages, because it's such a powerful tool. The primary problem is that Synergistic has limited resources. What's happening in the case of the configurator is that some clients are customizing web interfaces to accomplish the same thing.

I think Robert has it nailed. Plus look at how Sage tried to take Timberline Estimating and integrate that to Job Cost. I'm not sure anyone ever bought it but for a release or two I think there was an integration. The real tip that Sage is not likely to move on this is that the WO,MRP, PR are all still non-framework. I just think it's too late in the game and Sage will soon raise the white flag that they are a wholesale distribution package and if they fit for light mfg then fine - and if not then they won't chase it with R&D or acquisition. The other problem with Job Ops is that it's a fairly complex sale in a channel that is not well versed in manufacturing -- largely because that's not where Sage's roots have ever been (save for light mfg which is often sold as add-on modules to existing customers)

I remember being at a meeting in Minneapolis back when JobOps 4.1 was being planned. They asked a room full of VARs whether they should redo it for 4.1 a part of SO, etc like it was in 3.71, or redo it as a completely separate module. The vote was loud & clear for ""separate"". If they had listened then, they would now be able to connect it to other products.

Phil, I remember that meeting and that decision pretty clearly, too. ""strategic thinking"" hasn't been part of Synergistics' playbook since Kevin Cooper left. It's a shame, too.