Accelerate sourcing: how it works and what to require
Sourcing cycles are long because of setup, chasing and manual comparison, not because commercial judgement is slow. Proconomy builds events from governed templates, invites eligible suppliers automatically, coordinates responses through agents and normalises them for comparison, so the decision arrives sooner.
Sourcing is mostly waiting. Very little of it is working.
Separating waiting from working is the first useful thing to do with a slow event.
Before the event
- Building the event from an old file
- Deciding who is eligible to invite
- Assembling current qualification status
- Getting the specification confirmed
- Agreeing the scoring approach
- Obtaining approval to go to market
During the event
- Waiting for supplier responses
- Chasing the ones who have not replied
- Answering the same clarification repeatedly
- Handling responses in five formats
- Converting to a comparable basis
- Re-running the comparison after a late bid
After the event
- Modelling award scenarios by hand
- Assembling the approval pack
- Chasing approvers individually
- Re-justifying the recommendation
- Creating the contract from the award
- Getting the order raised correctly
What compresses
- Setup from a template rather than a file
- Eligibility assembled automatically
- Scheduled chasing without a person
- Structured responses, normalised on arrival
- Scenarios modelled rather than built
- Approval routed with the evidence attached
Six changes. Elapsed time, not effort.
What compresses the calendar without touching evaluation or award.
| Mechanism | What it has to do |
|---|---|
| Templates per category | Question sets, scoring, documents and approvals configured once. Setup becomes selection rather than construction. |
| Eligibility assembled from live data | Qualification, risk and entity approval determine the invitation list without a separate check. |
| Scheduled follow-up | Invitations, reminders and clarification handling run to a schedule rather than to a category manager’s availability. |
| Structured responses | Suppliers respond in the format the comparison needs, so normalisation is not a manual exercise. |
| Scenario modelling | Split, single and multi-lot awards compared against cost, lead time, capacity and concentration before commitment. |
| Approval with evidence attached | The award routes with the scoring, the scenarios and supplier standing already in the pack. |
A description of what the practice requires, not a feature list.
Same cycle time. Different deadline by sector.
What the window is actually driven by, in your industry.
Automotive
Programme milestones. A sourcing delay moves a launch date, which is the cost nobody puts in the savings calculation.
Consumer electronics
Component availability windows, where a last-time-buy deadline is fixed and unforgiving.
Semiconductor and OSAT
Qualification gates that run in parallel with the commercial event rather than after it.
Building materials
Commodity index movement, where the window to act on a price position is short.
Five questions. Run on your own workflow.
Each takes minutes and none can be prepared for.
- Ask them to run one of your workflows in the session, on your policy and your thresholds.
- Ask what happens when reality varies from the happy path — that is where most of your work lives.
- Ask which decisions return to a person, and confirm those checkpoints cannot be configured away.
- Ask what the system did without a person overnight, and see the record.
- Ask what they would advise you not to do first.
Definitions. Asked and answered.
Sourcing time is mostly waiting, not working. Event setup, supplier chasing, rebuilding the comparison and routing the award are where the days go, and each is addressable. Bring one recent event and we will walk the timeline with you to show which delays disappear.
No. Eligibility is enforced at invitation rather than checked afterwards, which is generally stronger than the manual process it replaces.
Yes. Templates and agent coordination remove the administrative time; the deliberation, negotiation and stakeholder alignment run for as long as the category needs.
Agents follow up on the schedule you configure and escalate non-response. Whether to extend, proceed or invite additional suppliers is a decision your category manager makes.
Usually supplier follow-up and response consolidation, because those consume elapsed calendar time rather than working hours. Award routing is often the second largest.
Sourcing cycle time is the elapsed period from a sourcing need being identified to an award being approved. It is usually dominated by waiting — for responses, for clarification, for approval — rather than by analysis.
By removing coordination rather than steps. Templated setup, automatic eligibility, scheduled chasing and structured responses compress elapsed time while leaving evaluation, negotiation and award decisions exactly where they were.
Event construction and supplier chasing, followed by converting inconsistent responses into a comparable format. All three are coordination, which is why they respond to governed execution rather than to additional process.