Pipeline Analysis & Revenue Forecast

SalesIntermediate60 min
Workflow Format (Staged)

This challenge runs as a locked, multi-stage workflow simulation. You submit one stage at a time. Once submitted, a stage becomes read-only and later stages build on your earlier decisions.

Stage 1: Scoring Model
Locked after submit

Design the initial qualification + routing system. This stage is locked after submission.

Required inputs

  • Qualification rubric
  • Routing logic
  • Duplicate handling rule
Stage 2: Batch Routing
Locked after submit

Apply your model to a batch and explain what you did. You can’t change Stage 1 after submitting.

Required inputs

  • Lead scoring explanation
  • Routing decisions
  • Dedupe explanation
Stage 3: Stakeholder Conflict
Locked after submit

New constraints force tradeoffs. Update your approach without rewriting earlier stages.

Required inputs

  • Revised routing strategy
  • Tradeoff explanation
Stage 4: Verification Loop
Locked after submit

Demonstrate verification discipline and explain where errors could occur in scoring, dedupe, and routing.

Required inputs

  • Manual score justification
  • Duplicate resolution explanation
  • Risk explanation
Stage 5: Final Artifact
Locked after submit

Submit the final artifact: final routing logic summary + prioritized queue + operational improvement + follow-up workflow outline.

Required inputs

  • Final routing summary
  • Prioritized queue explanation
  • Operational improvement recommendation
  • Repeatable follow-up workflow outline

What gets graded (later)

The backend grader will score workflow quality across stages: decision quality, verification, consistency, and the clarity of your final artifact.

Scenario
You’re RevOps support for an inbound sales team inheriting a messy lead batch. Leads come from multiple sources and may be duplicates or low-quality despite high scores. You must balance speed, fit, data quality, and routing tradeoffs under pressure.
Workflow Checkpoints + Outputs
  • 1.Scoring Model
  • 2.Batch Routing
  • 3.Stakeholder Conflict
  • 4.Verification Loop
  • 5.Final Artifact
  • 6.Lead table (conceptual)
  • 7.Scoring rubric + routing decision field
  • 8.Duplicate resolution logic + owner assignment
  • 9.Prioritized queue + next-step field
  • 10.Session token field (conceptual for now)
Session Requirements
  • Locked stage submissions (no editing after submit)
  • Stakeholder constraint injection forces revisions (Stage 3)
  • Manual score justification + duplicate resolution proof (Stage 4)
  • Final artifact includes follow-up workflow outline (Stage 5)
  • Proof-of-work signal (simulated text for now; backend wiring later)
Dataset Actions

Dataset access stays locked until you start the workflow session (timer start).

Open Stage 1 to start the timer and unlock the first dataset.

Available Before Stage 1

0 files
Start the workflow session to unlock datasets.

Only the initial dataset is shown here. Additional files unlock inside the workflow as you move through stages.

Allowed Tools

AI Tools

ClaudeChatGPTSalesforce Einstein (if available)Notion AI

Analysis Tools

ExcelGoogle Sheets
Scoring Rubric
Calculation accuracy30 pts

Correct weighted value, coverage ratio, stale deal total

Rep analysis25 pts

Correctly identifies Sarah (value) AND Marcus (speed) as different leaders

Pipeline diagnosis25 pts

Identifies correct stall stage and stale deal risk

Communication20 pts

VP briefing is specific, data-driven, and actionable

Workflow Session

Start Stage 1 when you’re ready. Each stage locks after submission and later stages build on earlier decisions.

Work stage-by-stage. Use explicit headers and keep decisions consistent across stages.

Recommended Time

60 min