For Checkr's Basic+ package, should we prioritize expanding the number of databases searched or reducing the overall turnaround time?

Introduction

The trade-off we're considering for Checkr's Basic+ package is whether to prioritize expanding the number of databases searched or reducing the overall turnaround time. This decision is crucial as it directly impacts the value proposition of the Basic+ package and could significantly affect customer satisfaction, market positioning, and operational efficiency.

In my analysis, I'll explore the implications of each option, considering user needs, business objectives, and technical feasibility. I'll then propose a structured approach to make an informed decision, including metrics to track and experiments to run.

Step 1

Clarifying Questions (3 minutes)

• Based on our current market position, I'm thinking this decision might be driven by competitive pressures. Could you share how our Basic+ package currently compares to similar offerings from competitors?

Why it matters: Helps understand if we're playing catch-up or innovating Expected answer: We're slightly behind in database coverage but faster in turnaround time Impact on approach: Would influence whether we prioritize breadth or speed

• Considering our user base, I'm assuming different customer segments might value speed vs. comprehensiveness differently. Can you provide a breakdown of our Basic+ package users by industry or use case?

Why it matters: Allows us to tailor the solution to our most valuable or growing segments Expected answer: Mix of high-volume hiring companies and specialized industries requiring specific checks Impact on approach: Might lead to a segmented solution or phased rollout

• From a technical standpoint, I'm curious about the current bottlenecks in our system. What are the main factors limiting our database search capabilities and turnaround time?

Why it matters: Identifies where we can make the most impactful improvements Expected answer: Database integration complexities and processing queue management Impact on approach: Could reveal quick wins or necessary infrastructure investments

• Regarding resources, I'm wondering about our current team capacity and budget allocation. How much additional investment are we prepared to make in either expanding database coverage or optimizing our processing systems?

Why it matters: Determines the scope and timeline of potential solutions Expected answer: Moderate budget increase approved, team at 80% capacity Impact on approach: Might necessitate prioritizing one aspect or seeking external partnerships

• Looking at our product roadmap, I'm thinking this decision might impact other planned features or improvements. How does this trade-off align with our broader product strategy for the next 12-18 months?

Why it matters: Ensures the decision supports long-term product goals Expected answer: Aligns with goal to increase market share in enterprise segment Impact on approach: Could influence whether we optimize for scalability or specific high-value features