ProgressPlus

• Requirement for public, published security attestations (e.g., SOC 2, ISO 27001) unless vendor can provide them privately.
• Requirement for SaaS-only, browser-first deployments with self-serve pricing and trial access.
• Heavy reliance on out-of-the-box e-commerce connectors and cloud automation unless the vendor can demonstrate equivalent capabilities.

• No public known-issues tracking page or public roadmap was found in the captured material.

• Material located in the review detected a customer move away from a competitor (Emax Systems) toward ProgressPlus attributed to perceived shortcomings at the competitor; independent evidence of customers leaving ProgressPlus for other vendors was not found in the public material accessed during this research.

• Greater pricing transparency and easier procurement for some cloud competitors.
• Broader published integration ecosystems and app marketplaces among cloud-native MRP/ERP vendors.
• Publicly available security/compliance documentation is more common among some SaaS vendors.

• Vendor case studies and testimonials cite faster vendor responsiveness, stronger handling of manufacturing documentation/traceability (certificates, tests), and a desire to digitize production and improve WIP visibility.

• Several vendor-published testimonials emphasize prompt responsiveness from vendor support and a perception of close, hands-on support.
• In vendor case studies, customers describe vendor responsiveness and the ability to address production documentation and traceability needs.

These statements are vendor-hosted and therefore reflect selected customer perspectives; independent corroboration was limited in the sources reviewed.

• Theme: implementation to improve foundations and integrate visibility into process, with emphasis on vendor responsiveness.
• Critical note: vendor materials did not include independently audited metrics such as on-time delivery improvements or lead time reduction in the captured snippet.

• Theme: digitize production and reduce paper-based data handling.
• Critical note: the published material lacked quantified before/after metrics in the accessible extract.

• Theme: customer needed improved documentation workflows and traceability that they reported not receiving from a prior supplier.
• Critical note: this is vendor-hosted content and therefore selection-biased; it does provide a checklist of documentation and traceability requirements to validate during demos.

• Theme: implementation downtime is acknowledged as a potential short-term cost for longer-term operational benefits.
• Critical note: downtime references are qualitative; independent, quantified downtime or rollout timelines were not provided in the captured material.

• A third-party customer post stated that their ProgressPlus deployment had gone live and referenced the vendor being developed and supported in the UK. This post is not a formal review but provides corroboration of UK-based support claims.

• Likely fit: small-to-mid-sized manufacturers (tens to a few hundred employees). Could scale to larger organizations that accept the administration and architecture requirements of a Windows/on-prem deployment.

• Precision engineering, plastics, electronics, sheet metal, and composites, based on vendor customer examples.

• Decision makers: Operations Director, Manufacturing Manager, Production Engineering Manager, Finance/FD.
• End users: planners, buyers, shop-floor supervisors, quality managers, dispatch and invoicing staff.

• Limited WIP visibility and work-order tracking.
• Paper-based quality and traceability documentation.
• Insufficient job costing and disconnected workflows between quoting, purchasing, production, and invoicing.

• Make-to-order, batch, or short-run manufacturing processes.
• Need for traceability and document outputs (certificates, tests).
• Preference for a vendor-led implementation with active vendor support.

• Primary target: small and medium manufacturers performing batch, short-run, bespoke, or one-off work (make-to-order / engineer-to-order environments).
• Positioning: the vendor presents ProgressPlus as production control software that emphasizes service/support and practical manufacturing workflows rather than offering the full breadth of generic ERP functionality.