The requests dataset needs early warnings without letting a model decide what downstream users can trust.
Fast detection protects lead-demand reporting, while engineer review protects the definitions and records behind it.
Who you’d be doing this for
“I changed my budget after the leads looked busy, then my crew had a quiet week and asked what happened.”
Mika Murakami · Home Service Business Owner
A pro owner relying on lead availability and targeting decisions shaped by marketplace demand data.
What is at stake
Duplicate request records can make homeowner demand look larger than it is. You must decide what AI can flag automatically and what a data engineer must verify before data is held.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- early anomaly detection vs. engineer authority to hold data
- broad pattern coverage vs. alert precision
- product iteration vs. durable data contracts
- fast pilot learning vs. sustainable incident load
Why Thumbtack
Request records sit beneath the marketplace data used to understand homeowner demand and the paid leads offered to pros.
Written with these in mind
Not your kind of problem? 72 more at Thumbtack, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.