Back to Hub

Negotiatus: Vendor Analysis (Part 2 — Product Strengths and Weaknesses, SWOT, Selection Checklist)

10/09/2019 By

In our last Spend Matters PRO brief, we introduced you to Negotiatus, an upstart P2P provider out of New York City that’s offering a fresh take on how to solve the root causes of common purchasing headaches. Taking the view that procurement should route users and payments through one (consolidated) invoice approach, Negotiatus aims to help its customers drastically reduce the number of transactions they need to process. In this view, purchasing automation represents a symptom of dysfunction rather than a panacea to inefficient business processes, and many of Negotiatus’ strengths thus reflect its guiding philosophy of simplicity and elimination of unnecessary work.

This approach, complemented by its supporting technology and rapidly growing client base, was a central reason we named Negotiatus to this year’s inaugural Future 5 list, which highlights standout start-up companies in procurement technology. 

But such a philosophy may not be a fit for every procurement organization, and by its own admission, Negotiatus is often a better fit with younger, more “forward-thinking” procurement organizations than corporate stalwarts. Its functionality lags accordingly when compared with peers that strive to “check the box” on requirements expected by a more classically minded procurement group.

Part 1 of this brief provided some background on Negotiatus and an overview of its offering — from ordering/shopping and catalogs to invoicing and payment.

In Part 2, we will provide a breakdown of what is comparatively good (and not so good) about the solution, a high-level SWOT analysis and a short selection requirements checklist that outlines the typical company for which Negotiatus might be a good fit. We also give some final conclusions and takeaways.

This article requires a paid membership that has access to AP Automation / Invoice-to-Pay, E-Procurement, or Procure-to-Pay.
Please log in or create an account to view this article