Local Service Spotlight project leads serve contractors by owning a business outcome from source data to weekly action. An A player does not route every question or random item through Dennis; they use the team, name one Accountable owner, and bring Dennis only the bounded finance or judgment calls that require him.
A players only is an operating standard
“A players only” is not a motivational slogan and it is not a score for raw talent. It is a role-fit standard: can this person reduce the load on the team while helping a contractor get found, get chosen, and get booked?
An A player asks for the goal and the source of truth once, finds the relevant training and prior work, chooses the right teammate, and returns with a result someone else can verify. They surface a real blocker early. They do not wait to be chased, report activity as impact, or make one busy founder the default router for the whole company.
“Do not treat Dennis as your assistant” means use the team
The problem is larger than asking Dennis to paste a comment or find a link. It is routing every question, approval, and random item to him one-to-one because that feels easier than learning to work in a team. That creates a founder bottleneck and hides the fact that no one else has taken the Accountable seat.
Keep the work in the shared project thread. Search the documented process. Ask the person who owns that function. When a task crosses functions, name the one person who owns the result and the teammates who own the component work. Read Why People Shouldn’t Solo Message Me for the communication symptom and Basecamp Basics for the source-system mechanics.
A good escalation is small enough to answer: “Approve up to $300 for this tested campaign by Thursday; the live dashboard and rollback plan are here.” A poor escalation is “What should we do?” followed by a pile of context the project lead has not analyzed.
RACI for a contractor account
RACI prevents a group of helpful people from becoming a group with no owner. The Accountable person is not the one who performs every task. They are the one who makes sure the right work happens, the evidence is checked, and the next action has one owner and one date.
| Seat | What it means on a contractor account | Evidence |
|---|---|---|
| Accountable | Owns the business outcome and the weekly decision. There is exactly one A. | Current MAA, named owners, due dates, source links, and closed loops. |
| Responsible | Executes a component: ads, site, content, analytics, sales follow-up, or client coordination. | Published change, platform receipt, checked deliverable, or source-system update. |
| Consulted | Supplies expertise before the decision: the contractor, finance owner, channel specialist, or subject expert. | A bounded question and a recorded answer, not an open-ended handoff. |
| Informed | Needs the result, not every intermediate message. | Concise update with decision, impact, next owner, and next check. |
Dennis may be Consulted for a strategic tradeoff, Informed on a material result, or Accountable where he is explicitly the finance source owner. His availability does not make him the A for every project.
The contractor outcome comes before channel activity
A contractor does not buy posts, ad clicks, schema, or reports. They buy profitable growth. The project lead has to connect diagnostic work to the contractor’s operating numbers without pretending attribution is cleaner than it is.
| Business outcome | Useful leading indicators | Counterbalancing check |
|---|---|---|
| Collected revenue and contribution profit | Booked jobs, sold estimates, qualified calls | Refunds, discounts, ad spend, fulfillment cost, and jobs not yet collected |
| Profitable customer acquisition | Cost per qualified lead, booking rate, answer rate | Close rate, average job value, lead quality, seasonality, and service-area fit |
| More local demand | Maps visibility, branded searches, direct traffic, video watch time | Calls and booked jobs; visibility by itself is not profit |
| Stronger trust | Reviews, proof-rich pages, case studies, response speed | Conversion rate and sales feedback; content volume is not proof of persuasion |
Label impact DIRECT only when the source system supports it. Use INFLUENCED when several channels contributed, and UNKNOWN when the plumbing is incomplete. Honest UNKNOWN is more useful than invented precision.
The weekly MAA is the proof of ownership
Every Accountable lead should produce one weekly Metrics → Analysis → Action tied to the contractor’s money path. It is not a dashboard dump or a list of completed tasks.
- Metrics: Compare the current period with a useful baseline. Lead with booked work, qualified opportunities, collected revenue, contribution profit, and spend when available.
- Analysis: Explain the non-obvious signal and its counterbalancing metric. Separate creative quality, audience fit, offer fit, sales follow-up, site conversion, and measurement gaps.
- Action: Make one or two changes with one owner, one due date, a spend or authority boundary, and the next measurement window.
What A-player behavior looks like
Operating as an A player
- Returns with the answer, source, and next action.
- Uses shared threads so the team can see and help.
- Names uncertainty and verifies public or financial effects.
- Delegates components while retaining accountability.
- Connects work to contractor revenue, profit, or a verified leading indicator.
- Finds and develops other people who can own outcomes.
Not operating as an A player yet
- Sends Dennis unsorted questions that another teammate or the source can answer.
- Moves decisions into solo messages and leaves the team blind.
- Calls drafts, optimistic UI, or activity “done.”
- Reports views, traffic, or revenue without the cost and quality check.
- Waits for reminders instead of maintaining the next checkpoint.
- Says “I understand” without producing a verifiable result.
Verification, not acknowledgement
The 30-day proof test
Do not close onboarding because someone read this article or said they understand. Give the person one real contractor outcome and verify four artifacts:
- One-page charter: goal, baseline, source of truth, RACI, guardrails, and next checkpoint.
- Three weekly MAAs: each anchored to live sources, including one counterbalancing metric and one owned action.
- One clean team handoff: a component assigned to the right teammate in the shared thread, with acceptance test and read-back.
- One business-impact closeout: direct, influenced, and unknown impact separated; profit or the nearest honest proxy shown.
Pass: the contractor outcome moved or the lead produced a clear evidence-backed learning, the source systems match the report, and the team needed less founder intervention by the end of the month. Do not pass: attendance, effort, a quiz, a read receipt, or a polished report with no source receipts.
Questions new project leads ask
Should I never ask Dennis a question?
No. Ask when the decision truly needs his finance authority, access, relationship context, or judgment. First reduce it to one bounded decision and include the source, recommendation, downside, and deadline.
What if I am not skilled enough to do every component?
You do not have to be. The Accountable lead assembles the right Responsible people and verifies the combined result. Ownership is not solo execution.
What if the contractor’s revenue data is missing?
Mark it UNKNOWN, assign the measurement gap, and use the nearest honest operational proxy until finance or the CRM can supply the real number. Do not turn visibility metrics into invented revenue.
Does one mistake mean someone is not an A player?
No. A players surface mistakes early, correct them, and improve the system. Repeatedly outsourcing the same basics, hiding uncertainty, or requiring chase behavior after onboarding is the role-fit signal.
Where do agents fit?
Agents can gather evidence, execute bounded work, check deliverables, and keep recurring loops moving. They follow the same standard: use the canonical source, preserve authority boundaries, and return a verifiable receipt. Start with New Agents Start Here.
Originally published .