BluepointATM Account Analysis — Over-Service & Scope Creep

Overview

The BluepointATM account terminated in March 2026 after approximately 8 months of service. The termination call between Wade Zirkle (BluepointATM) and Mark Hope (Asymmetric) surfaced a structural mismatch that had been building throughout the engagement: the agency was significantly over-serving a low-retainer account while the client's internal review burden created compounding friction that neither party addressed directly until the end.

This account is a useful case study in how over-service, misaligned client typology, and suppressed feedback can combine to produce a hostile churn event.

See also: ^[1] | ^[2]

Account Snapshot

The Over-Service Problem

At $5k/month, BluepointATM was receiving a full five-person team — a resource allocation Mark Hope internally acknowledged was roughly 2–3x what the retainer justified. The agency's own profitability reviews consistently flagged this account as the lowest return-per-hour in the portfolio.

The over-service was deliberate and relationship-driven: the client was a veteran, introduced through a personal connection, and operating as an early-stage startup. Mark made a conscious decision to absorb the loss and invest in the relationship's long-term potential.

The risk this created: Over-service without explicit acknowledgment sets an unsustainable baseline. The client has no visibility into the subsidy they're receiving, so they evaluate the relationship against their own experience of friction — not against the value being delivered.

The Client Typology Mismatch

Mark identified a structural problem during the termination call: BluepointATM didn't fit cleanly into either of the two standard client archetypes:

• Process-focused clients — marketing-literate, have internal teams, hire the agency to extend capacity. They engage deeply with deliverables.
• Results-focused clients — delegate fully, evaluate on outcomes, minimal involvement in execution.

BluepointATM had one foot in each bucket: Wade's team wanted strong results but also reviewed every deliverable closely, flagging product/market misunderstandings in social content and other outputs. This created a feedback loop where:

1. Agency produces deliverable
2. Client reviews, finds issues rooted in product knowledge gaps
3. Agency revises
4. Repeat

Mark estimated this loop caused 3x the effort on affected tasks compared to clients who delegate fully. The agency's internal ClickUp data supported this: all 375 completed tasks were agency-executed; every open item was blocked on client input.

The Product Knowledge Gap

Wade's stated primary reason for termination was not results — he acknowledged those were good — but the cognitive load of reviewing deliverables with fundamental product misunderstandings. Social media content in particular required heavy correction.

Mark's counter-argument was that this gap narrows over time and that 8 months in, the agency knew more about reverse ATMs than any competitor would on day one. This is likely true, but it doesn't address the client's lived experience of the review burden.

The underlying issue: For niche B2B products, the agency's learning curve is real and long. If the client must absorb the cost of that curve through review labor, the value proposition erodes — especially if the client isn't explicitly told this is a temporary phase.

The Feedback Suppression Dynamic

One of the most instructive failures in this account was the gap between Wade's stated satisfaction and his actual satisfaction.

• Mark used AI call analysis (Fathom) to assess client sentiment across all recorded calls. The tool characterized Wade as "complimentary" and "thankful."
• Wade explicitly rejected this framing: "An AI characterization of how I feel when I'm being polite on a business call is not a fair characterization of how I feel."
• Wade had raised concerns in December. Mark believed those were resolved. Wade did not.
• Wade's end-of-year survey contained frank negative feedback. The agency responded by changing account managers and clearing the task backlog — but did not confirm with Wade that the underlying issues were resolved.

The pattern: The client was professionally polite on calls, the agency interpreted politeness as satisfaction, and no mechanism existed to surface the delta between the two. By the time Wade was ready to act, he had already decided — the termination call was notification, not negotiation.

The Termination Escalation

Wade gave 60-day notice per contract. Mark, feeling the termination was "rude and disingenuous" given the agency's over-investment, immediately converted the notice to same-day termination and declined to provide any transition support.

The agency's position: the extra effort and personal commitment made the sudden departure feel like a betrayal, particularly given the absence of escalating complaints.

Wade's position: he had raised concerns (December conversation, end-of-year survey), they weren't resolved, and he was entitled to make a business decision.

The outcome: BluepointATM was given until Saturday, March 14 to migrate their website off Asymmetric hosting. No transition assistance was offered.

Key Lessons

1. Over-service without transparency creates entitlement risk

When an agency subsidizes an account without telling the client, the client has no basis to calibrate their expectations or feel gratitude for the subsidy. Explicit conversations about value delivered vs. retainer paid should happen proactively — not only during a termination call.

2. Politeness is not a satisfaction signal

Call sentiment analysis and survey scores are lagging indicators. Clients in professional contexts will often be polite even when dissatisfied. Regular structured check-ins that explicitly invite negative feedback — and create psychological safety to give it — are necessary to surface real sentiment.

3. Client typology should be established and documented at onboarding

Clients who want to be involved in process and results need a different engagement model than pure-delegation clients. Scope, review cycles, and approval workflows should be defined explicitly based on typology, not discovered through friction.

4. Feedback loops must be closed and confirmed

When a client raises concerns and the agency responds with changes, the client must explicitly confirm the changes addressed their concerns. Assuming resolution based on the absence of further complaints is insufficient.

5. Niche product knowledge gaps need a managed ramp

For clients with complex or niche products, the agency should set explicit expectations about the learning curve timeline, what the client can expect during that period, and when the review burden will decrease. This reframes early friction as a known phase rather than a persistent failure.

Related

• ^[1]
• ^[2]
• ^[3]
• ^[4]
• ^[5]