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.
A named function does not settle who owns a partner request.
Commitment context keeps requests intelligible, while recorded priorities protect leadership attention from becoming an approval queue.
Who you’d be doing this for
“I held two mornings open for those jobs, then my office had to ask again whether they were actually coming.”
Dalal Abbasi · Owner of a local electrical business · a character in this brief
Depends on partner-generated homeowner projects becoming work the business can actually accept.
What is at stake
Eleven of 36 requests for leadership attention bounced between functions despite naming an owner. You decide whether AI can propose a destination from recorded ownership when Salesloft activity suggests a commitment that the named function disputes.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- requester intent vs recorded authority
- standard destinations vs work without a natural home
- partner urgency vs frontline capacity
- fewer agenda items vs unresolved dependencies
Why Thumbtack
Partner commitments must become staffed, tooled, supply-ready execution before local businesses receive the homeowner projects those commitments promise.
Written with these in mind
Not your kind of problem? 84 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.
- Manager, Launch and Growth Operations (opens in a new tab)
- Initial priorities will include launching new partnerships, scaling Call Center, and advancing our Partner Operations foundation, but your portfolio will evolve alongside the needs of the business.
- Build and scale new business capabilities: Take emerging opportunities from concept through launch and scale, establishing the operating processes, systems, and cross-functional model required for reliable execution.
- Manager, Operational Foundations (opens in a new tab)
- Reporting to the Senior Manager of Partnership Operations, you’ll manage a globally distributed team of three to four people across the U.S. and the Philippines and own core functions spanning partner onboarding, integrations, partner finance, reporting, and internal tooling.
- Own developer and partner onboarding: Lead the end-to-end intake process from application through launch, defining acceptance criteria, review SLAs, approval workflows, ownership, and handoffs.
- Sr. Manager, Success Operations (opens in a new tab)
- Own headcount and capacity forecasting, business reviews, and executive narratives that translate fulfillment and supply signals into staffing plans and actionable directives.
- Serve as the single Commercial Ops liaison to Partnerships, translating new partner commitments and growth spikes into staffed, tooled, supply-ready frontline execution.
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 turns on moving faster inside a system others depend on.
Follow-ups from weekly marketplace decisions are being lost across Slack, Google Drive, and Confluence.
You have to decide where a captured line from a review stops being a note the chief of staff checks and becomes a reminder sent to a decision owner.
Event-related requests are arriving without enough detail and waiting for an owner.
You must decide where the routing system stops and a coordinator takes over when a request may carry a duty-of-care signal or a financial-control exception.
Program managers reopened 17 of 46 infrastructure requests despite completed intake fields.
You decide whether conflicting owner claims should halt enrichment or enter planning as competing proposals.
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.
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.
Pros are contacting Service after paid leads because contact choices changed what refund protection they expected.
You must weigh a clearer pro moment against the need to preserve fair review for legitimate refund cases.
Some pro cases are marked closed even though QA says the refund decision was incomplete.
You have to weigh immediate service coverage against a partner model that may repeat the same errors.
Other problems with a similar purpose
In each of these, as in this one, the aim is making daily workflows and product experiences feel coherent, calm, and dependable rather than effortful.
Thirty-one percent of captured tasks still have no owner after 24 hours.
You need to weigh faster capture against the accountability project managers need to move work forward.
Promising discovery calls are losing momentum while sellers rebuild notes and account research by hand.
You decide at which point between the call record and the account plan a drafted next step passes to the seller who has to stand behind it.
Project managers are rebuilding fields and types for recurring work, leaving portfolio reports inconsistent.
You have to weigh fast reuse against the flexibility enterprise workflows need.