Skip to main content

Leverage Value Delivery (Weekly Summary Methodology)

Leverage’s Weekly Summary email reports hours saved and estimated value delivered based on your weekly PO execution activity.

Written by Andrew Stroup

What you’ll see in the Weekly Summary email

Each weekly email includes:

  • PO lines processed — total PO lines Leverage touched during the week.

  • Emails sent — outbound supplier emails generated by Leverage.

  • Responses processed — inbound supplier responses parsed and applied (including ERP updates when configured).

  • Hours saved — estimated time eliminated from manual email composition + response processing.

  • Estimated value delivered — proxy value based on confirmations, changes, exceptions caught early, and shipment visibility.

Time saved from eliminating PO email busywork

When PO execution runs through inboxes, buyers lose hours every week drafting emails, triaging supplier replies, and updating the ERP. Leverage automates the outbound communication and turns inbound supplier responses into structured updates—so buyers spend time preventing issues, not processing them.

How we calculate hours saved

Hours saved = (Emails Sent × 1 minute + Responses Processed × 3 minutes) ÷ 60

Worked example (sample week)

  • 473 emails × 1 min = 7.9 hrs

  • 1,082 responses × 3 min = 54.1 hrs

  • Total = 62.0 hours

Time savings benchmarks

Action

Business Impact

Industry Benchmark

Estimates

Outbound supplier emails automated

Eliminates manual drafting; consistent messaging; fewer “check-in” loops

Manual email composition

1 min/email

Supplier responses auto-processed + ERP updated

Removes copy/paste + data entry; faster status accuracy; fewer mistakes

Response processing + ERP updates

3 min/response

Time estimates based on industry benchmarks for manual email composition (1 min) and response processing with ERP updates (3 min).

Estimated value delivered ($)

Without proactive supply chain management, undetected exceptions become expedited shipments, missed confirmations drive delays, and manual follow-ups consume significant buyer time

How we calculate value delivered

Estimated value delivered =
(no-touch confirmations × $5/line) + (change requests × $8/change) + (exceptions × $15/exception) + (shipment visibility events × $3/event)

Value estimates benchmarks

Action

Business Impact

Industry Benchmark

Estimates

No-touch confirmations

Orders locked in without intervention—frees buyers for strategic work

APQC: Manual PO costs $5–15/transaction

$5/line

Change requests handled

Proactive management prevents surprise disruptions

IOFM: Unmanaged changes cost 3–5× more

$8/change

Exceptions caught early

Issues identified before they become costly problems

Gartner: Early detection reduces cost by 80%

$15/exception

Shipment visibility

Real-time tracking enables proactive planning

CSCMP: Visibility reduces expediting by 25%

$3/event

Value estimates based on industry benchmarks from APQC, IOFM, Gartner, and CSCMP research.

What we include to calculate value

Value delivered is a proxy based on per-unit estimates for:

  • no-touch confirmations ($/line)

  • change requests handled ($/change)

  • exceptions caught early ($/exception)

  • shipment visibility events ($/event)

What we exclude to calculate value

These estimates do not attempt to quantify:

  • line-down avoidance

  • revenue retention / churn impact

  • long-term supplier performance improvements

Avoiding double counting

We classify each operational outcome once. If a change request resolves an exception, it is counted under change requests, not both.

Did this answer your question?