Communications Health Diagnostic

Pro Nails

Account Owner
Mark Ford
CSM
Not tracked in Salesforce
Customer Since
Not reported
Employees
Not reported
Account
001Hr00002HblweIAB
Assembled from 20 communications over 90 days, all through a single source (Gmail) — no Slack, Salesforce, or Jira activity exists for this account at any point. Scored against the preceding 90 days · 2026-05-14 → 2026-08-12 vs 2026-02-13 → 2026-05-14 (prior window: zero communications — this is a brand-new account). Source: Sturdy, reconciled to account.
Diagnostic· Composite
Composite
Signed, then silent
Red · driven by Engagement Vitality

Pro Nails signed a 3-year, $466,000 deal on July 7, and the relationship has gone quiet since. The customer's last inbound message was July 2 (board approval); as of today that is 37 days of silence, past the 30-day threshold this diagnostic treats as disengagement risk. Nothing has moved on either side — our own last outbound was the July 7 welcome note.

There is no negative sentiment on record to explain the gap (zero attributed critical signals), but there's also no positive sentiment banked, and 10 open threads still carry the customer's last word, one of them the exact item — implementation start date — that Sandra flagged as unresolved before she signed. Reads as a stalled handoff, not a churn signal.

Statecustomer condition · slow to reverse
SentimentEngagementBreadth
Executionours to fix
ResponsivenessFriction
Rule applied: Engagement Vitality is red (37 days since last inbound, over the 30-day cut), and any red state dimension escalates the composite to red on its own. Sentiment and Breadth are yellow. Operational Responsiveness is also red, but per the rollup rule execution can never drive the composite past what state already set — it is carried here as a fixable work item, not an additional emergency.
Diagnostic· Coverage
Coverage
Low
Single channel captured

Every one of the 20 comms in this window — and every comm on record for this account, in any window — came through Gmail. Slack, Salesforce, and Jira show zero activity for Pro Nails at any point, not just currently. Meeting content only appears as email recaps of calls, with no separate meeting-platform record to corroborate them.

Gmail Salesforce Slack Jira
State· Any red escalates the composite
Sentiment Load
Yellow
No goodwill banked yet

Zero attributed critical signals fired in the window — no Cancellation, Unhappy, Budget Issue, or Value Issue language from Pro Nails. On its own that reads green. It is not green, because zero positive-signal comms (Happy/Expansion) landed either, which triggers yellow by rule on its own.

The tone throughout is businesslike sales-cycle language — pricing, ROI, contract terms — even in the July 7 signature exchange. There's nothing to worry about here yet, but also nothing to point to if someone asks whether the customer is happy.

Attributed Critical
0signals
of 20 comms
Positive Signals
0180d
triggers yellow
Total Comms
20
current 90d
Attributed signals, current window
Critical
0
Positive
0
Critical (attributed) Positive (attributed) scale: share of 20 comms
Evidence
  • Let's get this signed — MSA + order form · 2026-07-07 · Warm, businesslike close ("Welcome aboard"); outgoing tone only, no customer sentiment signal attached.
  • CFO reference call before board approval? · 2026-06-23 · Sandra requests a peer-CFO reference before committing budget; process-oriented, not flagged critical or positive.
  • Pro Nails × YellowSail — Proposal & Implementation Timeline · 2026-06-28 · "Thanks — this looks solid" is the closest thing to a positive read in the window, but it did not fire the Happy signal. No attributed positive signals exist to cite.
Engagement Vitality
Red
37 days since customer last spoke

Sandra's board-approval note on July 2 is the last inbound message on record. That puts the account at 37 days of inbound silence today, past the 30-day threshold. Our side went quiet too — the July 7 welcome email was the last outbound — so this reads as a mutual stall at the handoff, not one-sided ghosting.

Inbound share over the full window is 60% (12 of 20 threads customer-led), which looks healthy in isolation. No prior-window comparison is available: this is a brand-new account with zero communications before the current 90-day window, so there is no trend to measure against.

Days Since Last Inbound
37days
threshold: 30
Inbound Share
60%
12 of 20 threads
Volume Trend
N/A
no prior-window history
Thread volume by period
Prior 90d
0
Current 90d
20
Who spoke last · current window
Final message
12 them
8 us
Inbound (Pro Nails) Outbound (Sturdy) bar width = share of period
Evidence
  • Let's get this signed — MSA + order form · 2026-07-07 · Sandra's countersignature confirmed; Marcus promises implementation lead outreach "this week." Last comm of any kind on the account.
  • Need to confirm implementation start date around fiscal close · 2026-07-01 · Marcus commits to proposing start dates around Pro Nails' Sept 15–Oct 15 close window. No dates have followed.
  • Today · 2026-08-12 · 37 days past the last inbound message with no kickoff scheduling visible in the record.
Relationship Breadth
Yellow
Concentrated in one contact

Three named contacts appear in the window: Sandra Voss (CFO, economic buyer), Tina McLovin (business/ops sponsor), and Dre Xzbit (technical/integration lead). Tina carries 55% of thread presence (11 of 20), above the 50% concentration line that triggers yellow.

This isn't attrition — there's no prior-period roster to compare against since Pro Nails is a new account, and no one has dropped out. The risk is structural: most of the relationship currently runs through one non-economic-buyer contact.

Contacts
3
no prior roster to compare
Top Contact Presence
55%
Tina McLovin
Business-Side Reps
2
CFO + ops sponsor
3 people 1 CFO, 1 business sponsor, 1 technical lead Concentrated
SV
Sandra Voss
sandra.voss@pronails.io
Last Seen
36d ago
CFO · economic buyer
TM
Tina McLovin
tinamclovin@pronails.io
Last Seen
45d ago
Business sponsor · 55% of threads
DX
Dre Xzbit
dre.xzbit@pronails.io
Last Seen
37d ago
Technical / integration lead
Evidence
  • Business Case & Budget Alignment – Quick Check In · 2026-06-13 · Tina frames the internal business case and compliance risk ahead of Sandra's review, consistent with an ops-sponsor role.
  • CFO reference call before board approval? · 2026-06-23 · Sandra requests a peer-CFO reference before taking the number to her board, confirming her role as economic buyer.
  • Multi-state payroll tax handling — need written confirmation · 2026-06-29 · Dre is the sole contact on technical/integration threads.
Execution· Fixable this quarter · two reds escalate
Operational Responsiveness
Red
Ten threads, customer had last word

10 threads in the window are unresolved with the customer's message left last — twice the red threshold of 5. The oldest, a one-line "Quick Question" outreach, has sat 71 days without a closing reply.

Depth isn't the problem — the median of the five longest threads is just 3 messages. This is a closure backlog, not a complexity problem, and per the scoring rule it stays a work item: execution alone cannot push the composite to red.

Open Loops We Own
10
threshold: 5
Oldest Open Loop
71days
threshold: 30
Median Depth (top 5)
3msgs
not the driver
Messages to resolution · major workstreams
MSA & Order Form
5
HR Ops Intro
5
Signature Close
3
Start Date
3
Payroll Tax
3
High effort to resolve Normal bar width = share of 5-message scale
Evidence
  • Quick Question · 2026-06-02 · Ryan O'Connor's outreach to Tina has sat unanswered for 71 days, the oldest open loop on the account.
  • Need to confirm implementation start date around fiscal close · 2026-07-01 · Marcus's promise to send proposed go-live dates is the exact open item Sandra flagged as unresolved before signing; still open today.
  • Implementation Readiness Sync Recap — still need the migration plan · 2026-06-03 · Named deliverable (migration plan) referenced as outstanding, no closing reply visible in the record.

Action: Have the assigned implementation lead confirm the kickoff date with Sandra Voss and close the start-date thread by end of this week — it is both the oldest customer-facing commercial commitment outstanding and the trigger most likely to end the current silence.

Adoption Friction
Green
Nothing to measure yet

Zero How-To, Slow-Loading, or Confusion signals fired in the window, and no structural blocker (failed authentication, an unfulfilled data-source setup) is evident in the record. Implementation has not started, so there is no product usage for friction to attach to.

Treat this green cautiously — adoption friction typically shows up once implementation and usage begin, which is exactly the phase currently stalled behind the engagement gap above.

Friction Signal Rate
0%
0 of 20 comms
Structural Blockers
None detected
from correspondence available
Friction signal rate
Prior 90d
0% · 0 comms
Current 90d
0% · 0 comms
How To, Slow Loading, Confusion bar width = share of 20% scale
Data source status
  • Gmail live, sole source of every comm on this account
  • Salesforce no comms activity captured, any window
  • Slack no comms activity captured, any window
  • Jira no comms activity captured, any window
Evidence
  • Pro Nails × YellowSail — Proposal & Implementation Timeline · 2026-06-28 · Customer requests a completed security questionnaire by July 17; this is a pre-implementation ask, not a friction signal, but worth tracking to closure alongside the kickoff.
Method· Known limits

Method and known limits

Attribution filtering is applied. No attributed critical or positive signals fired in the window, so no exclusions were needed on that front. Several commercial-posture signals fired repeatedly during the sales cycle — Perceived ROI Issue, Pricing Issues — and are excluded from scoring by design, per this project's scope; they describe deal dynamics, not post-sale relationship health.

Thresholds are judgment-set, not calibrated. This v1 uses hand-set cut points. Portfolio percentile anchoring is not yet applied, so treat the colors as directionally sound and not yet comparable across accounts.

Coverage is low. Every comm in this window, and every comm on record for this account at any point, came through Gmail. Salesforce, Slack, and Jira show zero activity. Sentiment, Friction, and Breadth are consequently scored on a single channel with no cross-source corroboration.