Objectives
Procurement
The Procurement objective helps organizations identify relevant vendors, evaluate how well they meet defined needs, and monitor meaningful changes that may affect an existing or planned relationship — using structured company understanding instead of static comparisons or scattered internal feedback.
Selecting Procurement does not create a separate understanding of a company. It changes what ASUME evaluates and which outputs it produces from the maintained understanding.
What Procurement evaluates
How ASUME applies Procurement
Maintained understanding → Procurement → Procurement outputs
ASUME forms a structured understanding of the organization's needs, constraints, priorities, and existing vendor relationships, together with a comparable understanding of vendors in the relevant market.
It then evaluates vendors against the Procurement objective so teams can see which options exist, how well they fit, and what has changed — without reducing the decision to a generic directory or a single opaque score.
Capabilities
Vendor Landscape
A procurement process is only as strong as the market it considers. Organizations often begin with vendors they already know, which creates a narrow field before evaluation has properly begun.
ASUME Vendor Landscape identifies companies operating within a defined area and structures the solutions they provide. The purpose is not to produce the longest possible vendor list. It is to establish a relevant and understandable field of options.
Example: A company needs software for supplier-risk management. Instead of returning every company categorized as a risk platform, ASUME distinguishes vendors focused on financial risk, cybersecurity, regulatory compliance, operational resilience, and continuous monitoring.
Vendor Evaluation
Selecting a vendor is not the end of evaluation. ASUME Vendor Evaluation connects the vendor's stated capabilities to the organization's requirements and incorporates the experience of the teams using or affected by the service.
For an existing vendor, structured feedback across teams should make disagreements visible rather than hiding them inside an average score. Weaknesses can become the basis for a structured improvement conversation, or a documented reason to search again.
Example: A company uses the same analytics vendor across Marketing, Finance, and Operations. Marketing values its flexibility, Finance identifies unexpected costs, and Operations reports recurring integration failures. Vendor Evaluation brings these perspectives together.
Vendor Watch
A sound procurement decision can become outdated when the vendor or the market changes. Vendors introduce products, discontinue services, revise pricing, enter new regions, obtain certifications, and change ownership.
Vendor Watch should not turn every website edit into an alert. It should identify changes that may affect fit, risk, value, or the organization's next decision.
Example: An organization selected a vendor partly because it offered data hosting in a required region. Vendor Watch detects that the vendor no longer clearly includes that region and shows why the change matters.
Workflows
Discovery
Vendor Landscape establishes the relevant field of options. A team searching for a new provider can start here before evaluating individual vendors.
A weak evaluation can also return the team to the landscape to identify alternatives.
Continuous governance
Vendor Evaluation determines how well a provider fits the organization's requirements and performs in practice. Vendor Watch keeps that assessment current.
The process can begin with an existing relationship. Monitoring can trigger a new evaluation, and evaluation can clarify which requirements should be watched.
Extending Procurement
ASUME is expanding the Procurement objective across additional workflows and developer interfaces. These extensions are planned.