LawsonGuru.com Forums
- Lawson HR170 Jobs Index
- IPA Question - Filtering Employees by XRef Cost Center Across Person and HR Modules
- Lawson S3 to SAP S/4 Hana Migration
- Deleting an Orphan Time Record with MS Add-ins
- Secure 2.0
- More.... ic81.2
- Uploads
- Lawson Security Admin (LSA) - Securing Print Manager to self only
- Lawson Add-in
- Anyone getting PO 0000 not found for company error in PO23?
LawsonGuru Blog 
Likely to be the truth, but also likely to be exagerated. Perhaps St. Paul was overloaded with R&D costs and the offshore moves represent a shift towards balancing the global enterprise. One thing is clear, executives at the Fortune 1000 level need to see a committment to cost stablization from its vendors, and the consensus is that offshoring initiatives are the best way to do that. We saw this play out for manufacturing and supply chain industries in the 80’s, and now it’s happening in the IT sector. So the proof is in the pudding so to speak. Lawson will need to keep its licensing and fees competative. They will need to offer new applications and functionality. And finally they will need to penetrate new markets. I hear Lawson is starting to do more and more business in India. I can also see the M3/S3 convergence here in America.
The LawsonGuru Letter made a very good point by saying clients may not perceive any value from switching to Landmark. I think there is a lot of risk in launching Landmark now. It’s just too much for the company to handle. If I had to make a prediction, some point in the future, Lawson will supply Landmark to its new clients who will never have known the old COBOL product. Then, any and all new functionality will be developed in Landmark code and never retrofitted to COBOL. So if our old clients want to progress, they will need to convert over (eventually).