Benchmark Proposal Turnaround Without Copying
Align metric definitions, investigate mechanisms and translate the comparison into a bounded local test.
24 minutes
Scenario
A design consultancy takes nine working days from approved brief to authorised proposal. A vendor claims top performers deliver in 48 hours, and one internal office reports four days using more standardised service packages.
- Your role
- Operations analyst designing a defensible benchmark study
- Method
- Benchmarking
Evidence pack
Local definition
Clock starts at first client call and includes waiting for missing brief data and internal error revisions.
Vendor claim
The report gives 48 hours but no cohort, denominator, case mix or validation method.
Internal office
The four-day office starts timing after a completeness gate and serves 70% standard packages.
Local mix
Only 35% of the target office's proposals use standard packages.
Mechanism
The faster office confirms scope, approved module and price range before narrative drafting.
Quality
Post-send correction is 3% in the faster office and 8% in the target office.
Constraints
- The vendor claim must retain source and evidence limitations.
- Raw and normalised results remain separate.
- The study cannot exchange current or future prices with competitors.
Case steps
Work through each prompt using the evidence pack. These guided cases support self-directed practice; server-scored attempts are not available yet.
Write the use decision and a complete turnaround metric definition.
Assess the vendor claim and internal office for comparability, provenance and limitations.
Propose a segmentation or normalisation approach and state the remaining defensible gap.
Write one mechanism hypothesis and a bounded local test with outcome and balancing measures.