Product · Sourcing & RFx

Strategic sourcing software for direct, indirect and MRO

Run RFI, RFP and RFQ events from the requisition that started them, score what comes back against weights you set, and award into a purchase order without re-keying a line.

One wizard, one data model and one comparison grid for every event type. The award writes the order; the contract starts from the same decision with its terms already filled in.

Requisition REQ-41088 · what carried across Illustrative
Part and spec
Carried with its snapshot
Quantity and UoM
As approved, not re-stated
Need-by
Earliest date on the requisition
GL and cost centre
Straight onto the line
Catalogue and contract-covered linesHeld back and reported — not sourced a second timeExcluded
System updatedThe event starts from the request that justified it
Inviting suppliers · checked as they are added Illustrative
On your approved vendor listInvited with no further stepInvited
Off the listAllowed, but the buyer has to state the reasonReason
Blocked or inactiveRefused outright — no invitation is sentRefused
Not in your system yetInvited by email on a single-use link, no account neededExternal
Rule appliedSole source means one supplier; single source means no more than three
Responses · made comparable Illustrative
System updatedOne currency, tiers resolved at your quantity, lump sums divided out
Award committed · what happens next Illustrative
Purchase orderOne per winning supplier, built from the awarded lines and sentCreated
ContractWizard opens prefilled — drafting and signature happen in CLMStarted
Requisition linesMarked as ordered and rolled up against the requestClosed off
Above your thresholdRoutes to an approver who has to leave a commentApproval
Human decisionThe award is per line, and a person always commits it

Lines, specification and dates carry across. Nothing is typed twice.

The same event. A mailbox, or a record.

Most sourcing still runs on attachments, a spreadsheet per event, and a folder nobody else can find.

Email and a spreadsheet
One event record
Email and a spreadsheetThe event is typed up again from the requisition
One event recordThe approved requisition becomes the draft, lines and all
Email and a spreadsheetQuotes arrive in four formats and three currencies
One event recordPrices normalise to one currency at a rate locked per line
Email and a spreadsheetSomeone rebuilds the comparison sheet each time
One event recordThe grid is the same on every event, with the deviations flagged
Email and a spreadsheetScores live in a side file, if they exist at all
One event recordWeights are set on the event and every score is recorded against them
Email and a spreadsheetChasing non-responders is a diary note
One event recordUnanswered invitations are reminded in the final day automatically
Email and a spreadsheetThe award is re-keyed into a purchase order
One event recordThe award writes the order, one per winning supplier

The comparison

What sits in every cell. Before anyone argues about it.

The grid is the same on every event. This is what it carries per line and per supplier, and where each figure comes from.

Normalised Unit price

Converted to one currency at a rate locked per quote line, with price tiers resolved at the quantity you actually asked for and lump sums divided out.

As offered Lead time

The lead time each supplier quoted on that line, sitting next to the need-by date the requisition set.

Per unit Carbon

Shown per unit alongside price wherever the supplier provided it, rather than in a separate sustainability report.

Only you see it Your target

The private target price for the line, with the percentage each bid sits above or below it. Suppliers never see this column.

Flagged, not buried Deviations

Spec deviations, partial quantities, minimum order quantities, payment-term and incoterm differences, alternate offers and applied price tiers, each as its own chip on the cell.

Frozen at publish The baseline

Contract price, last paid price and target, fixed when the event published so the saving is measured against a number that cannot move underneath it.

Per supplier The record behind the bid

Composite and questionnaire score, open corrective actions, open risk alerts, historical quality and on-time delivery percentages, and past purchase-order history.

How an event runs

Seven stages. Four of them are decisions.

The system does the carrying, the converting and the chasing. Every judgement is a person, and the award is always one.

  1. 01 Human

    An approved requisition becomes a draft

    A buyer converts it from the sourcing queue in one click. Part, quantity, unit of measure, specification snapshot, need-by date, cost centre and the requisition attachments all carry across. Catalogue and contract-covered lines are held back and reported rather than sourced again.

  2. 02 Rule

    The method is proposed, with its reasoning

    Rules and your category playbook propose RFI, RFP or RFQ, and the page shows why. Where the line arrived as free text, its category is classified first. Below a confidence threshold it asks rather than assumes, and the buyer can override either way.

  3. 03 Human

    The buyer builds the event

    Lines, questionnaire sections and their weights, the price weight, the due date, how many rounds, and whether a late bid extends the clock. A category template fills the defaults if you keep one.

  4. 04 Rule

    Suppliers are checked as they are invited

    Blocked and inactive suppliers are refused outright. A supplier off your approved vendor list needs a stated reason, or an approval, depending on the policy you set. Sole source means exactly one supplier and single source means no more than three.

  5. 05 System

    Responses are collected and made comparable

    Currency converts at a rate locked per line, price tiers resolve at your quantity, lump sums divide out and partial quantities are handled. Unanswered invitations get one reminder in the final twenty-four hours.

  6. 06 Human

    Scoring, then scenarios

    Scorers work their own sections without seeing price or each other. Where two scorers differ by more than your tolerance the cell is flagged for a consensus note. Then award scenarios: cherry-pick a supplier per line, or let a rule fill it and adjust.

  7. 07 Human

    The award is committed, and the order follows

    Above your threshold it routes to an approver who has to leave a comment. On commit, one purchase order per winning supplier is created and sent, and the contract wizard opens with the awarded terms already in it.

Core capabilities

What strategic sourcing software has to get right.

One event model, three event types

RFI, RFP and RFQ in one wizard, one data model and one comparison grid

  • An RFI can be promoted to an RFP or RFQ, carrying its lines, attachments and shortlist
  • Questionnaires with weighted sections and scored items sit on RFI and RFP events
  • A closed, un-awarded event can be converted to an auction, with the quotes seeding start prices

Built from the approved requisition

The event starts from the request that justified it, not from a blank form

  • Part, quantity, unit of measure, specification snapshot, need-by, cost centre and GL all carry
  • Catalogue, punchout and contract-covered lines are excluded and reported, not re-sourced
  • Identical part-and-spec lines are bundled; mixed line types split into separate events

The method, proposed with its reasoning

A recommended event type you can see the argument for, and overrule

  • Your category playbook, the history of that part, and the buyer’s own past events
  • A free-text line is classified into your category tree before the method is chosen
  • Below a confidence threshold it asks instead of assuming, and the buyer always decides

Weighted scoring, scored separately

Price and non-price weighted your way, with scorers kept apart

  • Composite is your price weight against the questionnaire score, on a nought-to-one-hundred scale
  • A scorer sees only their assigned sections — no prices, no composite, no other scorers
  • Disagreement beyond your tolerance flags the cell and asks for a consensus note

Mandatory requirements that actually bite

A rule that fails a bid, rather than a note somebody has to notice

  • Gate rules on questionnaire items, each with the reason it exists
  • A failed bid is excluded from price normalisation and carries no composite score
  • It stays visible, dimmed and labelled — and it cannot be awarded

Award scenarios

Try an allocation before you commit to it, and see what it costs

  • Pick a supplier per line by hand, or fill it with a rule and then adjust
  • Lowest landed, exclude deviating bids, follow the recommendation, favour the incumbent, cap supplier count
  • Each scenario shows total, delta against baseline, supplier count, deviations and concentration

Award recommendation, with its workings

A per-line pick across eight weighted dimensions, computed rather than guessed

  • Price landed, lead time, quality, compliance, risk, readiness, carbon and concentration
  • Weights are set per category, so an MRO event is not judged like a direct-materials one
  • Deterministic arithmetic — the optional written summary narrates a result it did not decide

The award writes the order

One purchase order per winning supplier, created on commit

  • Price, quantity, specification, deviation notes, need-by, ship-to, GL and cost centre carry across
  • Payment terms resolve from the order, the contract, the supplier record, then your default
  • The contract wizard opens from the same award with supplier, currency, term and lines prefilled

Features

Strategic sourcing software that holds its own rules.

Five groups of features, and not one of them depends on someone remembering the policy.

Rules the event applies on its own

Who can be invited, what a failed requirement does, and what stops being editable when.

  • Blocked and inactive suppliers are refused outright at the point of invitation
  • A supplier off your approved vendor list needs a stated reason, or an approval
  • Sole source means exactly one supplier; single source means no more than three
  • A bid failing a mandatory requirement is excluded from pricing and blocked from award
  • Scoring weights lock once evaluation begins, and every change before that is recorded

How the decision is made

Weights you set. Scores you can trace.

  • The composite is your price weight against the questionnaire score. Both halves are visible, and the price curve is a setting rather than a secret.
  • Scorers see only the sections assigned to them. No prices, no composite, and no sight of what another scorer gave.
  • Where two scorers differ by more than the tolerance you set, the cell is flagged and asks for a consensus note before it settles.
  • Changing a weight is recorded with who changed it and when, and weights lock once evaluation begins.
  • A bid that fails a mandatory requirement is excluded from the price comparison and cannot be awarded. It stays on screen, labelled, rather than quietly disappearing.
  • The award recommendation is deterministic arithmetic over eight weighted dimensions. The written summary that explains it narrates a result it did not decide.
  • Above the value threshold you set, an award routes to an approver who has to leave a comment. The decision, the comment and the time are kept with the event.

Two events. Two different shapes.

1

A machined component, three suppliers, two rounds

The buyer converts an approved requisition from the sourcing queue and the draft arrives with the part, quantity, specification snapshot and need-by already on it. Three approved suppliers are invited without a reason code; a fourth off the list needs one. After the deadline the grid normalises the prices, and a second round reopens to everyone with their own previous bid visible only to them. The award goes line by line — one line to one supplier, the other to another — and commits into two purchase orders.

2

A service RFP, weighted on more than price

The buyer builds questionnaire sections with weights and gate rules, sets the price weight to thirty, and assigns scorers to sections. Suppliers cannot submit with a required item blank, and a bid that answers a gated item wrongly is excluded from the price comparison and blocked from award. Scorers work independently; where two disagree beyond the tolerance, the cell asks for a consensus note. The composite then combines the agreed technical score with price.

Where it starts, and what it creates

It owns the event. Not the systems around it.

It starts from an approved request, or from nothing

The main path is converting an approved requisition. An event can also begin from a template, a duplicate of a past event, a promoted RFI, or a blank wizard when no request exists yet.

Supplier records come from supplier management

Approved vendor lists, supplier status and restrictions are read at the point of invitation. A supplier who is not in your system yet can be invited by email on a single-use link.

The award creates the purchase order here

One order per winning supplier, built from the awarded lines, sent without a second button. Your ERP keeps the books, and the order number is a Proconomy reference rather than one your ERP issued.

The contract is started, not signed

A button opens the contract wizard with supplier, currency, term, incoterms, payment terms, awarded prices and quantities already filled. Drafting, approval and signature all happen in contract lifecycle management.

Bring one category you source by email today.

We will build the event from a real requisition of yours and show you the comparison grid with your own lines in it.

Request a demonstration

Security, compliance and recognition

Checked by auditors. Judged by the industry.

Where each compliance programme stands, and what the procurement industry has given us so far.

Security and compliance

Awards

Five, presented on stage at three industry events.

  • Autonomous Procurement Platform of the Year
  • Procurement Technology Innovation Award
  • Unified Procurement and Supplier Management Platform
  • Procurement Startup of the Year
  • AI in Procurement or Supply Chain Award — Solution Provider

See the events and the trophies

Before you book anything. Answered honestly.

What is strategic sourcing software?

Strategic sourcing software runs the competitive part of buying — building an event from a defined need, putting it in front of the right suppliers, collecting what comes back in a form that can actually be compared, and recording how the award was decided. The part that separates a useful one from a document store is what happens at the two ends: whether the event starts from the request that justified it, and whether the award carries into an order without anybody re-typing it.

Which event types does it support?

RFI, RFP and RFQ, built in one wizard on one data model, so the comparison grid and the audit trail are the same whichever you run. An RFI can be promoted into an RFP or RFQ later, carrying its lines, its attachments and the suppliers who responded. Questionnaires with weighted, scored sections are available on RFI and RFP events. A closed event that has not been awarded can also be converted into an auction, with the quotes already received seeding the starting prices.

Does the event have to start from a requisition?

No, though that is the main path and the one that saves the most work, because the lines, specification, quantities and dates carry over instead of being typed again. You can also start from a category template, duplicate a previous event, promote an RFI, or open the wizard with nothing behind it when the need has not been through intake.

How are responses made comparable?

Currency is converted at a rate locked per quote line, so the comparison does not move if the rate does. Price tiers resolve at the quantity you actually asked for, lump sums are divided out per unit, and partial quantities are handled rather than ignored. Differences the system cannot resolve — unit of measure, incoterms, specification deviations — are flagged on the cell as chips for a buyer to judge, rather than being averaged away.

Can several people score an event?

Yes, and they are deliberately kept apart. Each scorer is assigned sections and sees only those, without prices, without the composite and without sight of another scorer’s marks. A manager sees every score and the spread between them. Where two scorers differ by more than the tolerance you set, the cell is flagged and asks for a consensus note before it settles.

What happens when we award?

The award commits per line — each line goes to one supplier. A purchase order is created for each winning supplier from the awarded lines and sent, without a separate step. Contracts are not created automatically: a button opens the contract wizard with the supplier, currency, term, incoterms, payment terms and awarded prices already filled in, and the drafting and signature happen in contract lifecycle management.

Does an award need approval?

Above the value threshold you set, yes — it routes to an approver who has to leave a comment, and the decision is kept with the event. Sole-source and single-source events, and any award to a supplier who has not completed onboarding, also route for approval regardless of value. Below your threshold the commit goes through immediately, which is a setting rather than a fixed behaviour.

Can suppliers who are not in our system take part?

Yes. A supplier can be invited by name and email, and they get a single-use link to respond without creating an account. Proconomy checks for an existing supplier with a similar name or the same email domain first, so you are warned before creating a duplicate. If one of them wins, the award is held until they have been onboarded properly.

One requisition. One finished event.

No slides. Your lines, your suppliers, and the purchase order the award writes at the end of it.

Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.