Category Archives: Sourcing Innovation

Is Your Strategic Operational Sourcing Not Succinct Enough? Maybe You Need A DeepStream To Tackle That SOS Problem.

DeepStream is a Source-to-Contract (S2C) platform that was founded in 2016 in London, England to empower midsized organizations with affordable, modern, streamlined, but still sufficiently deep source-to-contract capability that would empower their customers to be more efficient, get more spend under management (and savings, or at least cost avoidance in today’s inflationary economy), and award with confidence.

DeepStream was founded by practitioners with experience, built with the guidance of expert consultants and industry leaders and beta customers, and overseen by former implementation consultants with a lot of experience implementing the S2C Mega-Suites (and who know all the issues customers have in implementing, integrating, and maintaining those systems as well as all the reasons they aren’t always the best solution for the mid-market) who are continually developing and improving the system over time.

While DeepStream is designed to very customizeable and very general purpose (and works great for indirect/finished goods and services in general), because it is impossible to be everything to everyone (even though the Big Suites will claim they are), especially from a consulting/guidance perspective, they are highly focussed on the industries their founders are experts in and related industries. Specifically, they are focussed heavily on Energy & Renewable Energy (and O&G), Utilities, MRO, Site/Port Operations, and Consultancies that support these sectors (be they public, private, or quasi — such as public funded, privately managed). (These are the sectors in which they have the process expertise to help you set up your category templates to streamline your sourcing efforts … more on this later.)

The platform started as a core sourcing platform (RFX and Auction), and evolved to support Supplier Information Management, Contract Management (primarily Governance in Sourcing Innovation Terminology), and now offers a public Supplier Network of almost 10,000 suppliers that grows daily (and significantly with every new client. This may sound small compared to the suite supplier networks that claim millions of suppliers, but you need to remember three things: 1] many of these mega-suite networks reach their number by simply importing every government business registry globally, and nowhere near that many suppliers are active in their customer base; 2] DeepStream are focussed on a particular set of sectors which don’t have a super large supply base, and all of their suppliers have been verified as active and being interacted with; and 3] DeepStream expects your ERP/MRP/P2P/AP to be the supplier master and advocates customers only import active suppliers).

Sourcing

Sourcing revolves around a templated event structure, which can be setup by a Full User, the DeepStream services team, or both. (On implementation they will work with you to setup one template per category, as that is their recommended best practice. They have found that trying to cover multiple categories with one template misses the nuances of the individual categories and requires too much customization for every event, and having multiple per category with only slight differences by product/service makes management and upkeep too much work.) These event templates don’t just capture the RFI/P/Q requests, but all stages, including, but not limited to NDA, Onboarding, Prequalification (which can be separate from the RFI to avoid repeated RFIs), RFI, Initial Bid Collection, e-Auction, etc. etc. etc.

When an event is instantiated from a template, which requires only some basic information (name and dates), it will have a pre-populated summary, stages, details, a default evaluation matrix, a team, a starting set of suppliers, and possibly an e-Auction. The buyer can quickly access each event section of each stage and customize as needed. The application supports all standard HTML form functionality for data collection, makes it super easy to build sections, subsections, and questions for data collection, just as easy to build grids for bidding (that can collect all cost elements associated with a product or service, including complex rate cards), even easier to upload bids from a spreadsheet and, if desired, even cut-and-paste spreadsheet/Excel based bids (because it’s not just the favourite tool of a Procurement organization that doesn’t have modern tech, but the favourite tool of Supplier Reps as well). In addition, once instantiated, the event structure is not locked, the request owner or super user can modify it as needed (if more time needs to be added to a stage due to technical or communication issue, if another stage needs to be added because the responses are not differentiated or competitive enough or more requirements are added, and so forth).

Reverse Auctions have a very simple and clean UX and were designed to be easy to grasp, and use, by both buyers and supplier bidders. There is also integrated chat for real-time communication if needed. Buyers see the current total lot cost and suppliers see the current lowest bids, or their rank, in a public or blind manner, and can keep bidding until the time is up or they’ve given their best and final bid.

Evaluation is done using a grid structure on each relevant event section, where sections can be added or removed, by one or more evaluators, who can see all of the bids and responses side by side, including either full details or just summary, filtering down to just what they need to make an evaluation (and eventual award if the event is completely price-based). In a summary evaluation, they can click into the full response history or bid details (especially if the product was broken down into multiple cost components) and if it’s a multi-evaluator event, drill in to see the individual evaluator scores. There’s no graphical representation for bids just yet, but they have added BAFO (Best And Final Offer) capability to clearly designate final bids as well as automatically computing the deltas in bid responses in both percentage (%) and dollar ($) value, which are highlighted in the comparison view. Additional enhanced valuation functionality is planned for future releases.

One very unique feature of the platform is built-in support for collaborators. Most platforms make it easy to add other organizational users, but not so easy to add consultants who are helping on specific categories or projects. In the DeepStream platform, you can define collaborator organizations and users within these organizations and then, on an event, or stage [“page”], basis grant collaborators access at whatever level of access they need (read, comment, evaluate, write, etc.). This means that the platform is also great for niche consultancies as they can add their client as a collaborator and give key stakeholders visibility while managing everything on the customer’s behalf. (And, of course, it’s super easy to add organizational users to each page and grant them the precise level of access they need.)

A second very unique feature is their document management capability. Most RFX platforms just allow upload, with simple version tracking, and that’s it. The DeepStream platform understands there is a workflow around document management, especially where contracts and detailed specifications must be agreed to, and has a detailed set of process-centric statuses that can be associated with each document uploaded (for information only, upload requested, upload deviation, accept, etc. — modifiable by the client if desired) so both sides clearly understand where the document is in a request or negotiation cycle, as well as the ability to tag in-platform messaging to a document, which not only allows for audit trails to be queried at the document level but allows for in-platform discussions around documents to be captured and not only centralizes document communications (which get lost in email) but simplifies acceptance and approvals (of contract-related documents).

Contract Governance

The system allows the storage and management of contracts — which are currently defined as a collection of documents and bids accepted by both sides that are included in an award. The user can define the start and end dates, milestones, review periods and notifications and the platform will notify the appropriate parties when a milestone is do (so the appropriate individual can login and execute that milestone when it is completed, which may include notes or documentation), when a mandatory review has been completed (along with appropriate documentation and possibly future milestone steps if a corrective action is needed), or when a renewal/termination date is coming up on a contract. They don’t have integrated e-signature yet, but it is coming. Nor can they output everything to one single amalgamated PDF, but they haven’t found that to be necessary when most of the documents in the system are stored as DOCX or PDF, and it’s much easier for a user to find and extract just the information they need (original contract, delivery schedule, pricing, spec sheet, etc.) when a contract is stored as a “package” of documents and related system artifacts.

Supplier Management

The foundation of Supplier Management in the platform is the Network where all uploaded suppliers have a common, basic profile, that consists of basic organizational identifies (name, business ids, primary location[s], primary contact[s], etc.), the UNSPSC codes that the organization provides, and the locations they can provide those goods and services to. This makes supplier discovery within their primary industries practical for their rapidly growing customer base.

On top of this, a user can add their own qualification profiles to collect, and maintain, the information they need on the supplier, and these are kept private. When they do this, or when they select network suppliers as their suppliers, they show up in their “My Supplier” view where they can be selected for starting (pre-approved) supplier lists for every sourcing event template that the organization believes they are suitable for.

Finally, each organization has their own “Activity” tab in the supplier view that shows all associated Pre-Qualification questionnaires, Sourcing/RFX events and Contracts with their related status. One click will take the user into the associated document or event.

Dashboard and Reporting

When a user logs in, they see their activity dashboard that summarizes their requests, contracts, notifications, pre-qualification/onboardings, and a few report highlights (mainly negotiated savings and request completion status). It’s kept simple and streamlined so a user can get right to what they need to do when they log in, especially since they are integrating other communication channels besides email for notifications so users only have to log in to do something, not to get a status update.

Reporting right now is very basic, and very process/cycle time centric (which should not be surprising as they do not do spend analysis, preferring to instead integrate with the organization’s current platform, and if the organization does not have one, help the customer find and integrate with an appropriate partner organization for spend analysis). The reporting is really focussed around:

  • Team Productivity: how many requests made, completed, etc., by category, and average cycle time(s)
  • Supplier Engagement: requests received, responded to, awarded, etc. and associated rates and durations

With regards to saving, it’s focussed around:

  • Total Negotiated Savings: that summarizes the total negotiated savings based on the current PPU/RPH, the award rates, and the total number of units/hours requested
  • Total Negotiated Savings from Auction: that summarizes the savings from auctions, as well as savings statistics on an auction basis

Other Features

Standard Drive functionality where the organization can store all of the document templates it needs for its various supplier (pre)qualification and sourcing events.

Easy Query Audit Trails: When you bring up an Event in DeepStream, you can see a history of every action that was taken at every step by every participant (buyer, collaborator, supplier rep, etc.), filter, and export at any time.

Great Help Library:
DeepStream has a very extensive help library that is organized by role and process, to help an average user find the help they are looking for based on where they are in their sourcing process. It also has a built in advanced search function (powered by a custom in-house AI-backed search algorithm trained ONLY on all of the help documentation they have available) that can quickly find the right section of the right document with a reasonably detailed search request. This AI also powers their integrated chat/online help function that can handle full natural language questions and guides the user to right help quickly and easily (if the help exists). Since their help library covers every function on their platform, as well as best practice sourcing processes, the help bot is able to direct a user to the guidance they need and complete a help request roughly 80% of the time.

Multi-Lingual:
The DeepStream platform, including all help documentation, is fully translated into English, French, Spanish, and Portuguese.

Easy Integrations:
Out of the box ERPs include IFS and Dynamics, which are the two most common in the mid-market in their target industries, but they can (and have) integrated with other ERPs and P2P/AP systems. They’ve also integrated with supplier qualification and certification systems (like Avetta) and you can expect more integrations as time goes on. They built on prismatic.io to allow them to integrate with any platform they need to quickly, easily, and in a standard fashion.

Easy Account Management:
In the DeepStream system, it’s really easy to define collaborator organizations, user accounts, notifications, and system preferences (around currency, notification, etc.). Remember, one of the main goals was efficiency, so the idea is that organizations and users can configure event templates precisely to their needs so it’s super easy for buyers to kick off and complete sourcing events.

Terminology Customization:
DeepStream understands that one of the biggest hurdle to adoption is trying to force an organization to switch to terminology they are not used to. Thus, in their system, the super use can define the language used in all system elements at each step of the event template. For example, some jurisdictions in the world might use bid envelope terminology, others might use bid package, the private sector just wants RFP, and so on. All of this terminology is customizable as needed.

Coming Soon!

As per our intro, they are constantly developing and a few features coming soon include:

  • Enhanced evaluation functionality with more auto-computed differentials/savings potentials and advanced ranking/weighting capability based on calculations;
  • Integrated e-Signature powered by Verify — which will be available at all stages of supplier interaction, as you may require an NDA to be signed before you can even invite a supplier for a bid
  • Microsoft teams and Slack for communications and reminders (which is in beta now)
  • More Language Support: the entire platform, including the entire help library, can be internationalized to a new language within three weeks; languages are being added based on customer prioritization

Coming Later

  • More Out-of-the-Box Supplier Certification/Qualification/Risk Integrations: to help buyers certify and qualify new suppliers for their operations without leaving the DeepStream platform
  • Category Template Library: they have a number they can set you up with if you don’t have any; right now they help you get your current (Excel) templates and processes templated
  • Supplier [onboarding] Questionnaires: there are best practice templates out there for IT/Cyber Security, Personal Data Protection, Health & Safety, regulations like the GSCA, etc. and no need for each organization to create their own from scratch; right now they will share what they have on request [enhanced onboarding is one of their newest capabilities and, as such, is still under active development]

In conclusion, DeepStream is a great sourcing platform for mid-markets who need to modernize and get efficient fast, especially in the Energy & Renewable Energy (and O&G), Utilities, MRO, and Site/Port Operation sectors (be they public, private, or quasi — such as public funded, privately managed). As the platform is true multi-tenant SaaS, it’s more or less a flick-of-the-software switch to instantiate a new instance, typically only a day or two to configure an out-of-the-box implementation, only a few days to a week for a non-out-of-the-box integration, only a few hours to pull in the active suppliers once the ERP/P2P/AP is integrated, and only a few weeks to get an organization’s category processes templated. Most customers are fully up and running within a few weeks (and a month at most), and some customers have even kicked off initial events (on a small set of suppliers pulled in through one of the out-of-the-box ERP integrations) within 24 hours (while the while the remainder of the active suppliers for near-term events were being onboarded and the remainder of the category templates built out for future events). If you’re a mid-market looking for modern sourcing tech, and especially if you are a mid-market in one of the target sectors, you should definitely consider putting DeepStream on your shortlist and checking them out.

Strategic Sourcing & Procurement for Technology Cost Optimization

Given that we recently published a piece noting that Roughly Half a Trillion Dollars Will Be Wasted on SaaS Spend This Year and up to One Trillion Dollars on IT Services, it’s obvious that one has to be very careful with technology acquisition as it is very easy to overspend on the license and the implementation for something that doesn’t even solve your problem.

As a result, you need to be very strategic about it. While you certainly can’t put the majority of your technology acquisitions (which can be 6, 7, and even 8 figures) up for auction (as products are never truly apples to apples to apples), you definitely have to be strategic about it. As a result, you should be doing multi-round RFPs and then awarding to the vendor who brings you the best overall value for the term you want to commit to, once all things are considered.

But these have to be well thought out … you need to make sure that you are only inviting providers that are likely to meet 100% of your must haves, 80% of your should haves, and 60% of your nice to haves (and, moreover, that you have really separated out absolute vs highly desired vs wanted but not needed because the more you insist on, especially when it’s not necessary, the shallower the vendor pool, and the more you are going to end up paying*).

To do this, as the article notes, you have to know what processes you need to support, what improvements you are expecting, what measurements you need the platform to take, and what business objectives it needs to support. Then you need to align your go-to-market sourcing/procurement strategy with those objectives and make sure the RFP covers all the core requirements (without asking 100 unnecessary questions about features you’ll never actually use in practice).

You also need to know what quantifiable benefits the platform should deliver, both in terms in tactical work(force) reduction (as the tech you acquire should be good at thunking), and the value that will be obtained from the strategic enablement (in terms of analysis, intelligence gathering, guided events, etc.) the platform should deliver. If it is a P2P platform, how much invoice processing is it going to automate, and, based on that, how much is it going to reduce your average invoice processing cost? If it’s a sourcing platform, how much more spend will you be able to source (without increasing person-power) and what is a reasonable savings percentage to expect on that? Understand the value before you go to market.

Then you need to understand how much support and help you need from the vendor. If you just want a platform that does a function, then you just need to know the vendor can support the platform in supporting that function. But if you need help in process transformation or optimization, customized development or third party tool integration for advanced/custom processes, etc. you need a vendor that cannot only provide services, but also be a strategic provider for you as well.

And so on. For more insights, we suggest you check out a recent article by Alix Partners on Strategic Sourcing and Procurement for Technology Cost Optimisation. It has a lot of great advice for those starting their strategic procurement technology journey.

*Just remember, if you’re a mid-market, and you’re flexible (i.e. define what a module needs to accomplish for you vs. a highly specific process) you can get your absolute functionality and most of your desired functionality for 120K in annual SaaS license fees, excluding data feeds and services. If you’re not flexible, or not really strict in really separating out absolute vs strongly desired vs nice-to-have, you can easily be paying four times that.

Also remember, if you’re enterprise, your absolutes and strongly desired are much more extensive, typically require a lot more advanced tech (like optimization, predictive analytics, ML/AI, etc.), and licenses fees alone will cost you in the 500K to 1M range annually at a minimum, not counting the 100K to 1M you will need to spend on the implementation, data cleansing and enrichment, integration, training, and real-time data feed access, so it is absolutely vital you get it right!

Take the Tedious out of the Tactical Tail and Autonomously Avoid Overspend with mysupply

The taming of the tail is tedious and that’s why it’s overlooked in many organizations beyond whatever a catalog can address. There are only so many strategic sourcing professionals, there are only so many projects they can handle, and only so much spend they can get under strategic management. After that, beyond what’s in the catalog, IF there is a catalog, it’s typically the wild wild west for Procurement — especially if it fits on a credit card or P-card. There just isn’t enough bandwidth to manage more than a measly modicum of the tactical tail in an average organization.

Many organizations believe it’s okay to ignore tail spend because it’s only 20% to 30%, and because they believe that overspend probably can’t be that high on small purchases. They’re wrong on both points. In most organizations, even when the strategic categories are defined to include 80% of spend, because products and services change all the time, organizational buyers and / or overworked sourcerers won’t always catch when new products or services should be included in a strategically managed category; and because p-card/T&E is never included in the initial estimate, tactical/tail spend that’s unmanaged is usually 30% to 40%. If it’s 40% that ends up being unmanaged when the expectation is 20%, that’s a lot. Secondly, spend analysts and tail spend analysts have regularly found that the average overspend in the tail is in excess of 10%, with some categories of spend routinely being in the 15% to 30% window because no one ever looks at it. And if your organization is losing out on 10% of 40%, that’s 4% that could go straight to the bottom line with a good tactical tail spend solution.

To put into perspective just how good 4% straight to the bottom line is, consider the fact that, in direct organizations, strategic events on carefully managed direct categories that are regularly sourced typically only net 2% as the categories have already been squeezed. It’s only the mid-tier categories where you will see higher savings rates, which will typically average in the 5% to 7% range at best as these categories at least go to auction or multi-round RFP regularly. So if you save 2% on the top 30% and 5% on the next 30%, that’s only a savings of 2.1% that hits the bottom line. In other words, if your organization has been actively strategically sourcing top spend for five or six years, your organization has twice the cost avoidance / savings opportunity in the tail. It may seem counter-intuitive, but it’s the truth. Let that sink in for a moment before you read on.

mysupply is the newest start-up that aims to tackle the Tactical Tail Spend space, which has been historically underserved since the first specialists popped up (and then disappeared) to tackle it in the early 2010s. Even today you can count the true tactical tail spend specialist solutions on one hand without a thumb, compared to the seventy-five plus sourcing providers, but the new generation of providers, and mysupply in particular, understands that no one wants their spend in multiple systems (as you can’t do integrated spend, PO, and invoice management otherwise, key for Procurement success) and are developing their system as an extension to current sourcing systems, not a replacement for.

mysupply, which is even available on the SAP app store for those that use SAP (Ariba) and want a quick-start into tactical tail spend management, was designed to integrate with, and feed into your existing sourcing / procurement platforms — and in the case of Ariba, will fully use the Ariba Catalog and Ariba PO system to manage all spend. mysupply allows for:

  • quick event definition for sourcerors short on time (though the App or ProcurementBot)
  • roll-out to organizational users who can do their own quick-hit RFPs/Auctions/Catalog buys (also through the app, if needed, or ProcurementBot)
  • integration with your intake platform of choice for event push to the sourcing team

While it’s not designed as a full intake (or intake-powered) platform, as it was built for tactical tail spend and not all organizational spend, it was built from the ground up with integration in mind (as their goal is not to replace any platform you might already be using, as they are going after the enterprise market) and has a lot of orchestration capability built in and could even serve as an intake platform if desired (and route requests that should be strategically managed spend to an existing strategic sourcing application or to mysupply, which can also be used for strategic sourcing if desired).

Event creation in mysupply can be super easy. Options include:

  • in-house LLM-assisted Event Creation and Management via API-powered ProcurementBot, that can be integrated through existing enterprise collaboration platforms (Microsoft Teams is in Production, further integrations are planned)
  • Existing event templates that define all of the items being sourced, data required for bids, and (pre) approved vendors (which can easily be augmented or removed) (any event can be saved as a template to kick off future events)
  • events from scratch, where the platform is very adaptive and you only need to specify as much information as is necessary to source the product/service, which, if already defined in the system, can simply be an RFP request and a due date

and, most importantly, all of these strategies can include

  • demand bundling, even if different products or services should be sourced using different strategies, which can be across buyers for a given timeframe (i.e. collect all requests for a week or a month and then source)
  • pre-selected, custom, or hybrid supplier lists
  • customized lots, as the platform allows sourcing by item (price) or lot (price)
  • multiple tender/go-to-market approaches (i.e. each lot can be designated for a different [type] of RFX or auction), where the approach doesn’t need to be selected until suppliers have confirmed interest AND initial bids are in (which is very relevant for tactical spend where you don’t know the market dynamics because you haven’t researched the market and/or don’t source the product or service regularly; it’s not like strategic spend where you know there are seven suppliers, and five will show up to a reverse auction)
  • automated negotiation via (lot-based) QuickBot or multi-line item QuickBot
  • multiple scenarios for negotiation award analysis (where the items can be broken up for further negotiation/award after an initial bid event based on total spend, number responses, etc.)

For the requester, integrated LLMs through ProcurementBot help the requester:

  • identify the product or service being requested
  • capture demand and critical requirements
  • select the category
  • be presented with the appropriate sourcing approach: catalog, self-service, or central sourcing (team)
    • for catalog, immediately make the buy by presenting the user with the available catalog options and allowing them to select one and complete the purchase (and then the bot completes the process in the source system)
    • for self service, flesh out tender specifics and select (pre-approved) suppliers and then ProcurementBot sends out the tenders and, when they are all returned, or a certain time has passed (as configured by the category manager in the mysupply platform) returns the quotes to the buyer through the initial chat channel (where they can select one)
    • for central sourcing, it collects the request and, if appropriate, bundles it with others that are then rolled up into a managed tender that is then put into a central buyer’s queue for management, which may happen before or after initial quote requests are sent to suppliers (if an event template has already been pre-configured)

Let’s dive into some key sections / capabilities for the sourcing professional.

Demand Management / Bundling

As above, the system can be pre-configured to bundle demand over a period of time for all requests for the same product or products in a pre-defined lot, but for the rest of the requests that come in, there is the demand management/bundling section. In this section, the buyer can see all of the requests, have mysupply suggest a bundling, and either pick a suggested bundle or create her own bundle. She can quickly search and filter to create custom sourcing project bundles and then immediately kick off a workflow to define a new sourcing project bundle.

When a new sourcing project is kicked off, the user is taken to a screen where they can select starting pre-defined supplier groupings that are relevant for each item requested in the demand bundle (and, of course, the system will not include duplicate invites if the supplier is in multiple supplier groups, so the sourcing organization doesn’t have to create intersection groups, just groups for each commonly requested item).

Standard Sourcing Process

Once the buyer defines a basic event through one of the workflows (kicked off from a single request or request bundle), the platform takes the user to the event summary. From there they can:

  • define the automation and starting strategy — the event can be setup to automatically select all approved suppliers, send the request out at a certain time, remind suppliers, automatically advance to evaluation when all starting bids are in or the deadline is reached, kick off automated negotiation rounds (where suppliers are given a chance to update bids based on rank information and built-in game theory negotiation strategies), and basically free the buyer until it’s time to evaluate the first round of bids and either award, or kick off another round — at this point, the buyer can change the negotiation strategy, and even split the event up into multiple parts; this is different from most platforms where the entire event structure, and strategy (single round, multi round, Dutch action, etc.) has to be defined up-front and cannot be changed — something which makes no sense in tactical tail spend sourcing where you don’t know the supplier interest or current market dynamics; note that the starting strategy can be multi-pronged based on event value (if the award can be done under 10,000, then just award the lot to the current lowest bidder; if under 25,000 use autonomous QuickBot negotiation and award to the lowest bidder on an item basis; if over 25,000, do a 2nd round RFP with the three best suppliers and more negotiation/bundling to motivate better pricing; etc.)
  • flesh out the request — quote breakdown (while it is tactical tail spend, you may still want shipping, handling, taxes, service fees, etc. broken out), basic information required, documents required, delivery and payment details that must be accepted, compliance requirements, etc.
  • invitation of the selected suppliers (where you can add or remove suppliers that were pre-populated from supplier groups appropriate to the items in the request)
  • the evaluation of the bids that come back – manually, autonomously, or a combination thereof;
    the platform supports best price strategies, threshold strategies (which allow the strategy to be dependent on the amount of the bid, i.e user-driven negotiation above a range, best price negotiation within a range, and best-price auto-award below a range), QuickBot single lot auto-negotiation, Multi-Item QuickBot, English auction, Dutch auction, ranking (based on weighted responses and costs), buyer awards (no auction/negotiation); it supports lot strategies (best distribution by single-item award or all split); it also supports multiple rounds if desired with pre-scheduled negotiation windows (for RFQs and auctions); and, finally, it supports automated awarding if strategies that permit automated awarding are selected (subject to conditions that can restrict auto-award based on LDO — Least Desirable Outcome — or MDO — Most Desirable Outcome — scenarios; however, note that this is just the starting strategy;
  • select one or more bids for negotiation and make an award (unassigned/unawarded items are summarized and the user can see, through color coding, the lowest cost among all offers, select one, and send it to the e-Procurement system; the user can even dynamically kick-off new rounds of the RFP/auction, which may have a smaller supplier set or introduce new suppliers if the responses weren’t acceptable )
  • manage Q&A with the suppliers

A great feature of mysupply is it is not built to replace your current strategic sourcing platform (which most organizations have), your existing catalogs and catalog management applications (they integrate with them through their extensive API support), or your ERP/MRP/AP system which manages your purchase orders (as they integrate with those too). It’s meant to fill the tactical / tail spend sourcing hole in most organizations and, in particular, help organizations with tactical sourcing teams and help desks become considerably more efficient so overall savings can be increased though effective category management practices that capture and encode organizational knowledge so the end users can make the right buys on their own as often as possible, ensuring that the tactical team can focus on higher spend tail spend categories and new categories (and develop the right strategies to manage those going forward).

If your organization does a lot of tactical / tail spend sourcing, mysupply is definitely a platform you might want to check out, especially since its ProcurementBot allows it to do intake through third party platforms organizational users are already familiar with (such as Microsoft Teams).

Does Your Procurement Process Take Too Long, Maybe You Need to Zip Through It!

Zip is an interesting player. Started in 2020 to innovate the (lack of) intake in the Procurement world, they managed, through sheer ease of use and organizational friendliness, to embed themselves in a number of large organizations, get major investor attention, and, in less than four years, catapult themselves to a unicorn valuation.

However, as a result of those investments, they’ve been hiring good engineers as fast as they can find them, beefing up the orchestration, extending the product footprint (with baseline source-to-contract as well as some procure-to-pay capability), and launching a new integration platform, which is essential for source-to-pay-plus orchestration. They are making quite rapid progress in a space where many (but not all) larger companies have considerably slowed in their introduction of new innovation.

Marketing itself as procurement orchestration, Zip was founded to address the facts that:

  • purchasing is now distributed across numerous departments, and individuals, in today’s organizations,
  • (significantly) more cross functional approvals are required to control cost and risk, and
  • the ERP is not enough, and the plethora of apps and systems a modern organization needs are disconnected.

Now that they have powerful workflow creation capability, integration capability, and overall orchestration capability that can enable whatever you have (including Workday, Ariba, and Coupa), they now address the core problems they were formed to solve.

With the Zip platform, you can:

  • connect all individuals who need to purchase with all departments that need to be involved and vice-versa,
  • integrate all of the departments that need to review and approve purchasing (related) decisions, and
  • get visibility into each stage of the process across ALL of the organization’s systems (and even complete some tasks in the Zip platform where it has the corresponding Source-to-Pay capability).

On top of this you can:

  • integrate third party data feeds as well as applications to get insights and power analytics you need at any step of the process,
  • run cross-platform reports across performance and timelines as well as all spend, risk, and related data in the system,
  • manage your vendors and their data (which could be spread across a dozen systems) from one central viewpoint, and
  • manage your organizations (and subsidiaries) by department, category, etc.

The two-fold reason that you can do all this is because the Zip platform is really good at:

  • workflow management and
  • platform, and most importantly, data integration.

We’ll start with workflow management.

In the Zip platform, workflows are incredibly customizable. Workflows can:

  • have as many steps as required
  • which can be defined as sequential or parallel … and the workflow will not advance until all parallel steps are completed
  • have as many states as is needed (though most will only need a few states: locked, ready, in progress, approved, rejected (and sent back), rejected [and process terminated], etc.)
  • have as many sub-tasks and/or associated approvers as needed (so if the Legal Review needs two sign offs due to different policies that have to be met or the Finance Review needs two sign offs to ensure transparency, no problem)
  • have as many conditions as necessary for workflow selection / triggering (so you can have different procurement workflows by sub-category by geography if need be)
  • have as many triggers and dynamic data pulls defined as needed to instantiate a step once unlocked (e.g. bring up all vendors associated with a product, all approvers associated with a role, etc.)
  • link to as many external systems as required, with each (sub)task associated with the app/system in which the integrated party may perform his or her task
  • have as many details and associated documents as necessary
  • for Procurement, link to associated products, vendors, and / or contracts
  • etc.

And this is why the Zip Platform is so easy to use by, and attractive to, the average purchaser / requisitioner in an organization.

When an average user wants to buy, all they have to do is

  1. log into Zip via SSO (which can be configured to orchestrate organizational workflows beyond Procurement),
  2. indicate they want to purchase something
  3. select what they want to purchase
  4. make a few category/specification sub-selections to help the platform narrow in to the appropriate workflow (e.g. Facility Services, Janitorial; Computing and Electronics, Laptop;)
  5. if there are pre-approved vendors and/or products, the vendors/products; if not, they can select their own vendors/products
  6. answer a few [sub]-category dependent associated questions on the contract type, corporate or personal data that will be shared, etc.
  7. indicate the budget (amount) they wish to use (if appropriate)
  8. and submit the request …

The process is kicked off, the requisite data / document / survey collection is begun, those involved in the process are notified (and have visibility into the tasks they (potentially) have (coming), and the requester has full visibility into where the process is at all times (as the system will synch with external systems on predefined intervals between 15 minutes and 24 hours, usually depending on how often the external systems are used and what restrictions there are on access [e.g. some systems don’t have an API and do daily exports, and for systems with real-time APIs, the user can force synch anytime they want). But, most importantly, events that used to take hours to create and weeks to coordinate, can be created in minutes and the coordination effort is non-existent — the system handles everything for you.

When a user logs in, they can go to their (task) dashboard and see all the projects they are involved in, all the tasks they are assigned in those projects, and drill into all of the open tasks they need to work on now. They can also see how long the task has been open, when it is/was due, the average time taken on a task of that type, and the average time the user takes to do the task (if they drill into the appropriate report).

Moreover, if vendors are involved, vendors are invited and taken to their own portal where they see the event and only see what additional information is required (as anything requested upon onboarding is already available.

It’s also very easy to setup and administer, which is also critical for a modern platform. At any time, a user with appropriate authority can:

  • define, modify, and even inactivate workflows, as appropriate using a very easy to use no-code workflow builder where the users visually define the steps; select the actions; define the rules, actions, and triggers, etc.
  • define or modify (approval) statuses
  • define or modify the organization’s category hierarchy
  • define or modify new or existing survey templates which allow the user to add sections, questions, selection lists, etc.
  • create new system fields and documents and associate them with the appropriate system objects
  • create or modify the lookup types
  • add or modify user access rights, down to geographies, departments, workflows, function access rights
  • define or modify the organizational hierarchy (subsidiaries, departments, queues, locations, GL entities)
  • define roles, users, and permissions
  • define bank accounts and vendor (virtual) cards
  • add (out-of-the-box) or modify integrations, or launch the new low-code Zip Integration Platform that allows customers to build their own connector to any system with an Open (REST) API
  • define the default reports (vendor, spend, performance, etc.)

While we’re not covering them in this post, we should note that Zip has a P2P module (that 42% of its customers use) and a new Sourcing Module, and that Zip is actively working on new capabilities and module(s).

The new capabilities we can discuss now, on the Q1/Q2 roadmap, are:

  • NLP-based intake for even easier usability and up-front integration of Slack, Teams, and other collaboration platforms to allow workflows to be kicked off in those platforms
  • predictive analytics — the analytics module is being upgraded and it will include recommendations for spend management and process improvement using trend analysis, machine learning, and other techniques that can be used to provide the user with additional insight

In other words, Zip, which has well over 300 enterprise customers, is zipping along and intends to keep doing so. The great thing is that you don’t need to replace any of your enterprise systems, including any best of breed systems you have for sourcing or procurement, but instead connect them together to maximize the value you get out of them. Zip is an(other) I20 — intake to orchestrate — system that is certainly worth being aware of and checking out if system, process, or stakeholder orchestration and collaboration is a challenge in your enterprise.

COUPA: Centralized Optimization Underlies Procurement Adoption …

… or at least that’s what it SHOULD stand for. Why? Well, besides the fact that optimization is only one of two advanced sourcing & procurement technologies that have proven to deliver year-over-year cost avoidance (“savings”) of 10% or more (which becomes critical in an inflationary economy because while there are no more savings, negating the need for a 10% increase still allows your organization to maintain costs and outperform your competitors), it’s the only technology that can meet today’s sourcing needs!

COVID finally proved what the doctor and a select few other leading analysts and visionaries have been telling you for over a decade — that your supply chain was overextended and fraught with unnecessary risk and cost (and carbon), and that you needed to start near-sourcing/home-sourcing as soon as possible in order to mitigate risk. Plus, it’s also extremely difficult to comply with human rights acts (which mandate no forced or slave labour in the supply chain), such as the UK Modern Slavery Act, California Supply Chains Act, and the German Supply Chain Act if your supply chain is spread globally and has too many (unnecessary) tiers. (And, to top it off, now you have to track and manage your scope 1, 2, and 3 carbon in a supply chain you can barely manage.)

And, guess what, you can’t solve these problems just with:

  • supplier onboarding tools — you can’t just say “no China suppliers” when you’ve never used suppliers outside of China, the suppliers you have vetted can’t be counted on to deliver 100% of the inventory you need, or they are all clustered in the same province/state in one country
  • third party risk management — and just eliminate any supplier which has a risk score above a threshold, because sometimes that will eliminate all, or all but one, supplier
  • third party carbon calculators — because they are usually based on third party carbon emission data provided by research institutions that simply produce averages for a region / category of products (and might over estimate or under estimate the carbon produced by the entire supply base)
  • or even all three … because you will have to migrate out of China slowly, accept some risk, and work on reducing carbon over time

You can only solve these problems if you can balance all forms of risk vs cost vs carbon. And there’s only one tool that can do this. Strategic Sourcing Decision Optimization (SSDO), and when it comes to this, Coupa has the most powerful platform. Built on TESS 6 — Trade Extensions Strategic Sourcing — that Coupa acquired in 2017, the Coupa Sourcing Optimization (CSO) platform is one of the few platforms in the world that can do this. Plus, it can be pre-configured out-of-the-box for your sourcing professionals with all of the required capabilities and data already integrated*. And it may be alone from this perspective (as the other leading optimization solutions are either integrated with smaller platforms or platforms with less partners). (*The purchase of additional services from Coupa or Partners may be required.)

So why is it one of the few platforms that can do this? We’ll get to that, but first we have to cover what the platform does, and more specifically, what’s new since our last major coverage in 2016 on SI (and in 2018 and 2019 on Spend Matters, where the doctor was part of the entire SM Analyst team that created the 3-part in-depth Coupa review, but, as previously noted, the site migration dropped co-authors for many articles).

As per previous articles over the past fifteen years, you already know that:

So now all we have to focus on are the recent improvements around:

  • “smart scenarios” that can be templated and cross-linked from integrated scenario-aware help-guides
  • “Plain English” constraint creation (that allows average buyers & executives to create advanced scenarios)
  • fact-sheet auto-generation from spreadsheets, API calls, and other third-party data sources;
    including data identification, formula derivation and auto-validation pre-import
  • bid insights
  • risk-aware functionality

“Smart Events”

Optimization events can be created from event templates that can themselves be created from completed events. A template can be populated with as little, or as much as the user wants … all the way from simply defining an RFX Survey, factsheet, and a baseline scenario to a complete copy of the event with “last bid” pricing and definitions of every single scenario created by the buyer. Also, templates can be edited at any time and can define specific baseline pricing, last price paid by procurement, last price in a pre-defined fact-sheet that can sit above the event, and so on. Fixed supplier lists, all qualified suppliers that supply a product, all qualified suppliers in an area, no suppliers (and the user pulls from recommended) and so on. In addition to predefining a suite of scenarios that can be run once all the data is populated, the buyer can also define a suite of default reports to be run, and even emailed out, upon scenario completion. This is in addition to workflow automation that can step the buyer through the RFX, auto-respond to suppliers when responses are incomplete or not acceptable, spreadsheets or documents uploaded with hacked/cracked security, and so on. The Coupa philosophy is that optimization-backed events should be as easy as any other event in the system, and the system can be configured so they literally are.

Also, as indicated above, the help guides are smart. When you select a help article on how to do something, it takes you to the right place on the right screen while keeping you in the event. Some products have help guides that are pretty dumb and just take you to the main screen, not to the right field on the right sub-screen, if they even link into the product at all!

“Plain English” Constraint Creation

Even though the vast majority of constraints, mathematically, fall into three/four primary categories — capacity/allocation, risk mitigation, and qualitative — that isn’t obvious to the average buyer without an optimization, analytical, or mathematical background. So Coupa has spent a lot of time working with buyers asking them what they want, listening to their answers and the terminology they use, and created over 100 “plain english” constraint templates that break down into 10 primary categories (allocation, costs, discount, incumbent, numeric limitations, post-processing, redefinition, reject, scenario reference, and collection sheets) as well as a subset of most commonly used constraints gathered into a a “common constraints” collection. For example, the Allocation Category allows for definition “by selection sheet”, “volume”, “alternative cost”, “bid priority”, “fixed divisions”, “favoured/penalized bids”, “incumbent allocations maintained”, etc. Then, when a buyer selects a constraint type, such as “divide allocations”, it will be asked to define the method (%, fixed amount), the division by (supplier, group, geography), and any other conditions (low risk suppliers if by geography). The definition forms are also smart and respond to each, sequential, choice appropriately.

Fantastic Fact Sheets

Fact Sheets can be auto-generated from uploaded spreadsheets (as their platform will automatically detect the data elements (columns), types (text, math, fixed response set, calculation), mappings to internal system / RFX elements), and records — as well as detecting when rows / values are invalid and allow the user to determine what to do when invalid rows/values are detected. Also, if the match is not high certainty, the fact-sheet processor will indicate the user needs to manually define and the user can, of course, override all of the default mappings — and even choose to load only part of the data. These spreadsheets can live in an event or live above the event and be used by multiple events (so that company defined currency conversions, freight quotes for the month, standard warehouse costs, etc. can be used across events).

But even better, Fact Sheets can be configured to automatically pull data in from other modules in the Coupa suite and from APIs the customer has access to, which will pull in up to date information every time they are instantiated.

Bid Insights

Coupa is a big company with a lot of customers and a lot of data. A LOT of data! Not only in terms of prices its customers are paying in their procurement of products and services, but in terms of what suppliers are bidding. This provides huge insight into current marketing pricing in commonly sourced categories, including, and especially, Freight! Starting with freight, Coupa is rolling out a new bid pricing insights for freight where a user can select the source, the destination, the type (frozen/wet/dry/etc), and size (e.g. for ocean freight, the source and destination country, which defaults to container, and the container size/type combo and get the quote range over the past month/quarter/year).

Risk Aware Functionality

The Coupa approach to risk is that you should be risk-aware (to the extent the platform can make you risk aware) with every step you take, so risk data is available across the platform — and all of that risk data can be integrated into an optimization project and scenarios to reject, limit, or balance any risk of interest in the award recommendations.

And when you combine the new capabilities for

  • “smart” events
  • API-enabled fact sheets
  • risk-aware functionality

that’s how Coupa is the first platform that literally can, with some configuration and API integration, allow you to balance third party risk, carbon, and cost simultaneously in your sourcing events — which is where you HAVE to mange risk, carbon, and cost if you want to have any impact at all on your indirect risk, carbon, and cost.

It’s not just 80% of cost that is locked in during design, it’s 80% of risk and carbon as well! And in indirect, you can’t do much about that. You can only do something about the next 20% of cost, risk and carbon that is locked in when you cut the contract. (And then, if you’re sourcing direct, before you finalize a design, you can run some optimization scenarios across design alternatives to gauge relative cost, carbon, and risk, and then select the best design for future sourcing.) So by allowing you to bring in all of the relevant data, you can finally get a grip on the risk and carbon associated with a potential award and balance appropriately.

In other words, this is the year for Optimization to take center stage in Coupa, and power the entire Source-to-Contract process. No other solution can balance these competing objectives. Thus, after 25 years, the time for sourcing optimization, which is still the best kept secret (and most powerful technology in S2P), has finally come! (And, it just might be the reason that more users in an organization adopt Coupa.)