---
title: Account Handoff — Karly Oykhman (2025-12-12)
type: article
created: '2025-12-12'
updated: '2025-12-12'
source_docs:
- raw/2025-12-12-weekly-call-w-108479355.md
tags:
- blue-point
- account-management
- handoff
- client-retention
- hubspot
layer: 2
client_source: BluepointATM
industry_context: b2b-services
transferable: false
---

# Account Handoff — Karly Oykhman (2025-12-12)

## Overview

During the [[wiki/meetings/2025-12-12-weekly-ops-call|2025-12-12 weekly ops call]], Mark Hope decided to transition the Blue Point account from Melissa to Karly Oykhman. The handoff was driven by ongoing performance issues that had damaged client trust. Mark will join all Blue Point calls going forward to provide support and manage the client relationship directly.

## Account Snapshot

| Field | Detail |
|---|---|
| **Client** | [[wiki/clients/current/bluepoint/_index\|Blue Point]] |
| **Monthly Retainer** | ~$5,000/mo |
| **Incoming AM** | Karly Oykhman |
| **Outgoing AM** | Melissa |
| **Effective Date** | 2025-12-12 |
| **Mark on Calls** | Yes — all calls |

## Reason for Transition

Melissa's management of the account had deteriorated to a point where client satisfaction was at risk. The specific incident that triggered the handoff:

- A HubSpot marketing automation was built by Chris in **October 2025** with a **manual enrollment** trigger.
- Melissa told the client the automation was live and running.
- The automation was **never enrolled** — no emails went out for two months.
- On a call in December, the client asked for a performance update. Melissa opened HubSpot live on the call and discovered zero sends, with no explanation ready.
- Mark had to intervene after the call, enrolling the list himself in ~3 minutes, which immediately triggered ~2,000 emails.

> *"How can you go two months and not even look? If you know you're running automation, wouldn't you go check it like once a week?"*
> — Mark Hope

The broader issue was a lack of proactive account awareness: not reviewing client sites and tools regularly, not preparing for calls in advance, and not understanding the technical state of deliverables before client-facing meetings.

## Expectations for Incoming AM (Karly)

Mark outlined the account management standard he expects, which applies to Blue Point and all accounts:

1. **Daily site check** — Each morning, briefly visit each client's site to confirm it's live and functioning. Takes ~2 minutes per client.
2. **Task awareness** — Know what each client is paying for. Keep a reference of deliverables per client and verify they're being executed.
3. **Pre-call preparation** — Before any client call, anticipate the 4–5 topics likely to come up. Have relevant tools (e.g., HubSpot, Google Ads) already open and already reviewed. No surprises on the call.
4. **Proactive monitoring** — Don't wait for clients to surface problems. If something is running (automation, ads, etc.), check it periodically.

## Client Profile Notes

- Blue Point is a **demanding client** — they know what they want and expect it to be delivered.
- They are not always technically sophisticated, which can lead to misaligned expectations about complexity and timelines.
- Mark's presence on all calls is intended to provide a senior buffer and ensure the relationship stays intact during the transition.
- The account is worth retaining: ~$5k/mo is a significant retainer.

## Related Account Changes

As part of the same restructuring decision, **Citrus America** is being reassigned from the current owner to **Sebastian**. See [[wiki/clients/current/citrus-america/_index|Citrus America]] for details.

## Action Items

- [ ] Assign Blue Point account to Karly in project management system (@Mark Hope)
- [ ] Mark to join all Blue Point calls going forward (@Mark Hope)
- [ ] Karly to review Blue Point account history, active deliverables, and HubSpot setup before first call (@Karly Oykhman)
- [ ] Assign Citrus America to Sebastian (@Mark Hope)

## Source

Discussed at [[wiki/meetings/2025-12-12-weekly-ops-call|Weekly Call — 2025-12-12]] (~17:22–21:36 in transcript).