The setting
is an online marketplace that connects homeowners with independent professionals who offer local services for home projects. is the side that those professionals use to get found and hired.
The refund-change record moves faster than the evidence behind it.
Launch readiness protects a consistent pro experience, while premature certainty hides unresolved service dependencies.
Who you’d be doing this for
“I marked the lead as work we don't do, and I'm still explaining it again days later.”
Claudio Ribeiro · Plumbing Business Owner · a character in this brief
Pays for leads and relies on refund protection when a request falls outside the services the business can take.
What is at stake
Refund-policy changes are approaching review while Jira, Salesforce, and Slack disagree about unresolved work. You must decide what AI can reconcile and what Program Managers must verify before acting.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- frontline usability signals vs documented completion status
- one programme record vs work spread across systems
- lower coordination overhead vs human ownership of dates
- automation coverage vs service-case access boundaries
Why Thumbtack
Paid-lead refund protection shapes whether local service businesses keep trusting the leads they purchase.
Written with these in mind
Not your kind of problem? 80 more at Thumbtack, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Thumbtack. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Program Manager, Vendor and Scaled Operations (opens in a new tab)
- Own Thumbtack's vendor and outsourcing strategy for Service Operations - sourcing decisions, make-versus-buy recommendations, capacity strategy across internal, vendor, and partner channels, and the case for expanding, consolidating, or exiting a partner.
- Proficiency in program management tooling (e.g., Jira, Linear, Coda, Smartsheet) and fluency across Agile and Waterfall approaches.
- Project Manager (Service Operations) (opens in a new tab)
- Partner Operations Analyst (opens in a new tab)
- Support new pilots and partnership launches, from fulfillment and refunds to pro surveys and early program feedback.
- Senior Automation & Process Specialist (opens in a new tab)
- We work closely with our frontline Service, Business Apps, QA, Enablement, and Analytics teams to identify friction points in customer and pro support journeys and redesign them using AI driven automation and improved processes.
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about money moving incorrectly, late, or twice.
A Pay in 4 programme has conflicting readiness updates across Jira, Salesforce, and Notion.
You have to decide what AI can reconcile safely and what a Program Manager must confirm.
Billing-query cases lack a single, reviewable payment story, so merchants repeat details while cases move between teams.
You must decide how far the AI carries a case brief between the Salesforce case notes and the SQL payment results, and which explanations the Finance analysts still reconstruct themselves.
Completed jobs can show an invoice while payment remains absent from the owner’s view.
You must decide which investigation work AI can assemble and which judgment engineers must retain.
The same setting, from another role
Each is set around Thumbtack’s Thumbtack for Pros, written for a different role. They’re separate briefs, not the same scenario.
Pros lose paid leads after an initial message because they cannot tell which quiet homeowners may still respond.
You have to weigh stronger follow-up against wasted crew attention and homeowner trust.
Several plumbing and electrical markets appear short of pros after owners cut lead budgets following higher prices.
You must weigh homeowner match availability against committing acquisition capacity to a signal that may not last.
Eight percent of paid leads in affected categories are later marked Not what I do.
You have to weigh tighter relevance against the matches homeowners and pros still need.
Other problems with a similar purpose
In each of these, as in this one, the aim is to use evidence to make delivery leaner and more efficient without treating reliability as something to trade away.
Mine operations managers are waiting on fixes while reviews reopen for missing vehicle evidence.
You must decide whether AI marks uncertain evidence or holds the change for an engineer to investigate.
Worker-type concerns are appearing repeatedly across payroll API migration feedback, but their source evidence is scattered.
You must decide where the drafting of clusters from Operations and Compliance feedback stops and where a product manager's own reading of the source examples has to begin.
Daily event-air exceptions are producing conflicting explanations for the same cost and service variance.
You must decide what AI can match and draft, and what reviewers must verify before finance acts.
