Sourcing with Ivalua: make the most of your maximumfreedom
Maximum flexibility in sourcing — but still easy to use? This article shows how Ivalua makes complexity manageable.
Procurement is undergoing a fundamental transformation. Where simple RFQs and Excel spreadsheets used to be sufficient, today’s reality includes strategic sourcing events, ESG requirements, complex services, BOM structures, and global supply chains. Ivalua Sourcing is built precisely for this reality: as one of the most flexible and powerful sourcing modules on the market.
But this strength also brings a new challenge: complexity. Ivalua is not a “one-click tool.” It is a platform capable of mapping almost any conceivable procurement scenario—with sourcing project types, RFx types, options, templates, workflows, steps, auctions, questionnaires, cost models, and much more. This openness is both a gift and a risk.
When Freedom Becomes Overwhelming
In practice, we see the same pattern again and again: companies deliberately choose Ivalua because they don’t want to be forced into rigid processes. They want to reflect their own procurement logic—not that of a software provider.
However, once the system is rolled out “as is,” buyers are faced with questions like:
- Which sourcing type should I choose?
- What’s the difference between an RFQ, RFP, and cost breakdown?
- Do I need an NDA here?
- Why does one project have five steps and another twelve?
- Which options should I activate—and which should I avoid?
For experienced power users, this flexibility is a major advantage. For operational procurement, it quickly becomes a barrier. As a result, users fall back on “safe” standard paths, bypass functionality, or avoid the tool altogether.
Ivalua doesn’t have to be complicated—but it is intentionally not simplified. And this is exactly where the real work of a good implementation begins.
Rethinking Sourcing: From System to User Reality
The key question is not:
“What features does Ivalua offer?”
but rather:
“How does a buyer think in their daily work?”
Buyers don’t think in RFx types or project structures. They think in intentions:
- “I need three quotes quickly.”
- “I’m launching a strategic sourcing initiative.”
- “I’m buying a service.”
- “I want to compare suppliers.”
Users don’t make system decisions. They simply choose their goal—everything else should be orchestrated in the background. With the right design, a highly complex platform becomes an intuitive tool.
Structure Over Complexity
This is exactly where our approach at jupitos comes in. We don’t believe in rolling out Ivalua “in full.” We believe in carefully planning and purposefully structuring the implementation:
- A limited number of clearly defined sourcing paths
- Preconfigured templates instead of empty forms
- Fixed project structures instead of open building blocks
- Governance instead of uncontrolled growth
- Clarity instead of excessive choice
Our goal is not to simplify Ivalua by removing functionality.
Our goal is to make complexity invisible.
ntake Management: The Next Evolution
Our goal at jupitos is simple: a buyer should be able to get started in under five minutes—without training, manuals, or uncertainty.
With its latest releases, Ivalua itself is moving in this direction: Intake Management. Instead of guiding users through menus, types, and configurations, the process starts with a simple question:
“What do you want to do?”
- Buy something
- Request a quote
- Create a supplier
- Start a project
The system takes care of the rest.
Project type, RFx type, steps, ownership, governance—everything is set automatically. Sourcing is no longer configured; it is triggered.
For us at jupitos, intake is the key to unlocking Ivalua’s true strength:
A platform that can map any procurement reality—without burdening the user.
Conclusion
Ivalua is one of the most powerful sourcing systems on the market. Its openness allows companies to model procurement processes exactly as they truly operate. But high flexibility without structure leads to overwhelm.
The future does not belong to systems with fewer features—but to systems where complexity is intelligently hidden.
Our approach is to design Ivalua in a way that it doesn’t feel like a system, but like a natural part of everyday work: powerful at its core, simple to use.