Use case

RFP creation and vendor evaluation.

From the field, AI native workflow redesign of rfp creation process within Strategic sourcing Procurement function.

Get the playbook
Convolving expertise

A senior Convolving delivery team partnered with the strategic sourcing function for one sprint. Operators from our expert network – with forty combined years inside enterprise procurement organisations – scored the redesign at each checkpoint. Forward-deployed engineers built inside the team's Coupa instance and vendor data systems. One flat fee, artifact out, no retainer creep.

Situation

Today a sourcing event runs two to four weeks from intake to recommendation. One sourcing manager owns the cycle.

The intake conversation produces a Word scope document. Vendor research happens in browser tabs and old RFP folders. Outreach goes by email; responses land in attachments and shared drives. Scoring is a spreadsheet exercise rebuilt every event. The sourcing judgement that earns the role – which supplier fits, which price is right – sits in the last day.

Cycle time 2–4 weeks Intake to recommendation
Events per FTE 8–12 Per sourcing manager per quarter
Time on construction 75% Of cycle hours, not on judgement
Vendor coverage 5–8 Vendors evaluated per event

Click any node to see the activities and tools behind it. Open the canvas in fullscreen for the horizontal view.

Complication

Largest obstacles and inefficiencies.

A two-to-four-week cycle anchors business velocity.

Business partners learn to either route around procurement or pad their timelines by a month.

Three-quarters of cycle hours are construction.

Drafting, list-building, outreach, and scoring consume the cycle. The judgement work that earns the role sits in the final day.

Vendor coverage stays narrow.

Five to eight vendors per event is the practical ceiling when the manager builds the list by hand.

Resolution

The AI-native cycle.

Same five steps. Click any node to see what the redesign does in that step.

Cycle time 3–5 days ▼ 70% vs today
Events per FTE 20–28 ▲ 2× vs today
Time on construction 20% ▼ 55 points vs today
Vendor coverage 12–20 ▲ 2.5× vs today
Key changes

What the redesign actually shifts.

Cycle compression

  • Two to four weeks to three to five days, intake to recommendation.
  • Construction work runs in parallel; scoring is bounded by AI throughput.
  • Business partners get an answer in the same week they ask the question.

Sourcing capacity

  • Events per FTE roughly doubles, from eight to twelve to twenty to twenty-eight per quarter.
  • Construction time drops from 75 percent of the cycle to 20 percent.
  • The freed time goes to category strategy and supplier development.

Vendor coverage

  • Average shortlist grows from five to eight to twelve to twenty vendors.
  • Better-matched vendors enter the funnel; long-tail competitive pressure rises.
  • Past-event vendor data compounds rather than being rebuilt event by event.

Audit and standardisation

  • Every vendor scored by the same rubric, every cycle.
  • Recommendation cites the source line for every claim.
  • Sourcing manager edits feed back into the style guide for future events.

Deploy this in your team.

The redesign above ships as a step-by-step playbook. Intake template, RFP scoring rubric, vendor enrichment pipeline, and the rollout cadence we use on engagements.

Get the playbook Or book a coffee