Many sourcing and procurement teams still run requests for proposal (RFPs) the traditional way. They work with business stakeholders over email, collect supplier responses in shared folders, track progress in spreadsheets and merge evaluations by hand. It works, slowly, and it leaves little record of why decisions were made.
For organizations that already run ServiceNow, there is a better option: run sourcing on the same platform as requests, approvals and supplier records. This guide, refreshed for 2026, explains the problems with the traditional approach, what ServiceNow brings to sourcing, and how RFPflow turns it into a complete source to contract workflow.
The trouble with traditional RFP operations
To run an RFP the traditional way, sourcing teams collect requirements by email, build the document in a word processor, send it to suppliers, collect responses in a shared folder and compile evaluations in a spreadsheet. Questions and clarifications live in individual inboxes. Approvals are chased one by one.
- Long cycle times from request to award
- Inconsistent evaluation between events and evaluators
- No single view of event status for stakeholders
- Little reuse of questions, templates or past responses
- Weak audit trail of how and why suppliers were chosen
- Manual handoff from award to contract
E procurement tools have improved this over the past decade, but many sit outside the systems where requests and approvals already happen, adding another place to look. Read about e sourcing.
What ServiceNow brings to sourcing
| Capability | Why it matters for sourcing |
|---|---|
| Searchable repository | Past RFPs, question libraries and responses can be found and reused |
| Integration hub | Connections to enterprise resource planning, finance and other systems already exist |
| Workflow and approvals | Requests, reviews and awards follow defined routes instead of email |
| Self service portal | Employees raise sourcing requests where they already raise other requests |
| Enterprise security | Independently audited controls the security team has already approved |
Employees spend less time waiting for responses and approvals, because the platform routes work and shows status. Procurement can see every request and event in one place.
How RFPflow extends ServiceNow procurement
RFPflow is Aavenir's sourcing app, built natively on ServiceNow. It adds what the platform does not provide out of the box: full sourcing events with supplier collaboration and structured evaluation.
- A sourcing request is raised through the ServiceNow portal or from a Sourcing and Procurement Operations request
- The sourcing manager creates an RFP, request for quotation or request for information from a template and question library
- Stakeholders review requirements and evaluation criteria in the same record
- Invited suppliers respond through a portal, including structured pricing
- Aavenir AI reads responses against the weighted criteria and drafts scores and summaries for evaluators
- Evaluators accept or change scores, and the award is approved through workflow
- The award starts a contract draft in Contractflow and supplier onboarding in Onboardingflow
See publish RFx and collaborate for the supplier side of the process.
Source to contract on one platform
The real gain comes from connecting sourcing to what follows. RFPflow shares data with Contractflow, Onboardingflow, Obligationflow and Invoiceflow, so the supplier, prices and terms selected in the event carry through to the contract, the supplier record and eventually the invoice check. Spend visibility improves because the sourced price and the paid price can be compared. The source to contract use case shows the full flow.
Aavenir's apps install from the ServiceNow Store and are also available standalone for organizations that do not run ServiceNow, with the same AI and security certifications.
For procurement leaders, that continuity is the main argument for running sourcing on the platform: decisions made in the event stay visible through every step that follows.
Governance and audit
Sourcing decisions are increasingly scrutinized by auditors, regulators and unsuccessful bidders. Running events on ServiceNow gives a complete record by default.
- Who raised the request and who approved it
- Which suppliers were invited, and why
- What questions were asked and how suppliers answered
- How each evaluator scored each response, with comments
- Which AI drafted scores were accepted or changed, and by whom
- Who approved the award and when
That record makes it easier to answer a challenge from a losing bidder, satisfy internal audit and show compliance with public or internal procurement rules. It also builds the history that improves the next event.
Getting started
- Pick one category with regular sourcing events
- Build templates and a question library from your best past RFPs
- Agree standard evaluation criteria and weights with stakeholders
- Run the next event in RFPflow and compare cycle time with the old process
- Connect awards to contract drafting and supplier onboarding
Keep the first event simple and well supported. A smooth first run, with stakeholders and suppliers who found it easier than the old way, does more for adoption than any feature list.
What changes for each team
Sourcing managers spend less time compiling documents and spreadsheets and more time on market analysis and negotiation. Business stakeholders raise requests in a familiar portal and can see event status without asking. Evaluators work from a ranked view with drafted scores and reasons rather than a folder of attachments. Legal receives contract drafts that already reflect the award. Suppliers get one portal, clear questions and consistent communication. Leaders get reporting on cycle time, savings and supplier performance across every event, drawn from the same records.
The bottom line
Running sourcing on email and spreadsheets wastes time and leaves decisions hard to defend. For ServiceNow customers, RFPflow brings sourcing onto the platform that already runs requests, approvals and suppliers, and connects every award to the contract and payment that follow.