How can AppFolio balance the need for comprehensive tenant screening in its leasing tools with the desire for a quick and seamless application process?

Introduction

Balancing comprehensive tenant screening with a quick and seamless application process in AppFolio's leasing tools presents a critical trade-off. This scenario involves weighing the need for thorough vetting against user experience and conversion rates. I'll analyze this trade-off by examining the product context, identifying key metrics, designing experiments, and providing a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on AppFolio's market position, I'm thinking this might be a response to competitive pressure. How does our current tenant screening process compare to our main competitors in terms of thoroughness and speed?

Why it matters: Helps understand the competitive landscape and urgency of the trade-off. Expected answer: Our process is more thorough but slower than key competitors. Impact on approach: Would focus on optimizing speed without compromising quality.

• Considering our revenue model, I assume faster applications could lead to quicker property turnover. What percentage of our revenue is tied to successful tenant placements?

Why it matters: Quantifies the potential business impact of streamlining the process. Expected answer: 30-40% of revenue is directly tied to tenant placements. Impact on approach: Would justify significant investment in optimizing the application process.

• Looking at user behavior, I'm curious about the drop-off rate during the current application process. At what stage do we see the highest abandonment rates?

Why it matters: Identifies pain points in the current user journey. Expected answer: Highest drop-off occurs during the document upload stage. Impact on approach: Would focus on simplifying document submission and verification.

• From a technical standpoint, I'm wondering about our current integration with credit bureaus and background check providers. How real-time are these integrations, and is there room for improvement?

Why it matters: Assesses technical constraints and opportunities for speed optimization. Expected answer: Integrations are not fully real-time, with some taking up to 24 hours. Impact on approach: Would prioritize improving API integrations for faster data retrieval.

• Considering resource allocation, how much engineering capacity do we have to dedicate to this project in the next quarter?

Why it matters: Determines the scope and timeline of potential solutions. Expected answer: We have a dedicated team of 5 engineers available for 3 months. Impact on approach: Would tailor the solution to fit within these resource constraints.