Working documents for the people doing the work.

ERP Strategy exists because most of what ranks for "how to select an ERP system" is either a feature checklist with no opinion or a funnel for a selection consultancy. This site publishes the phase calendars, requirements registers, demo scoring sheets, vendor comparisons, and industry-specific shortlists an internal team needs to run its own selection and its own program, with the reasoning shown so a reader can adapt it rather than follow it blind.

How the articles are built

Every figure traces to a published source or is labeled as this site's judgment, with the reasoning given in the text. Worked examples are framed as illustrations, never as a client story. We do not publish fixed-week programs, a consulting firm's methodology, or reproduced templates from another firm's materials; the templates in the selection toolkit are written fresh for this site.

Vendor neutrality

Every comparison gives each vendor in it at least one situation where it is the right answer. Criticism is specific and sourced or labeled as judgment. ERP Strategy is not affiliated with SAP, Oracle, Microsoft, Infor, IFS, Epicor, QAD, or any other vendor, and nothing on this site should be read as an endorsement.

For the people who approve the money

ERP Strategy is written for the people running the work day to day. Its companion publication, ERP Executive, covers the same decisions for the CIO, the CFO, and the board: what a program costs, which support deadline forces a choice, and what independent assurance catches before the status report admits there is a problem.

Contact

Editorial and research enquiries: [email protected]. For program or selection support, use the contact form.