Account: Brightpath SaaS, Key tier, $38,000 ARR
Primary contact: Rachel Kim, Engineering Manager (sole stakeholder on record at the time)
Contract end date: October 22, 2026
HubSpot ticket: #430768899280, "P1, PulseOps platform degradation affecting Brightpath SaaS," Priority High
Health Score: 36.25, Red, unchanged since the August 27 review. Relationship should improve at the next scoring pass; Usage has not.
On August 26, 2026, PulseOps ran with elevated error rates and delayed incident notifications for just over an hour. Root cause: database connection pool exhaustion introduced during a deploy. Brightpath's on-call team was mid-incident on their own systems and relying on PulseOps for notifications when it degraded, so the impact on them was direct.
+15 min: Reached out to Rachel Kim directly. Confirmed PulseOps was experiencing delays and under active investigation, update promised within the hour.
+1 hr: Root cause identified, database connection issue during a deploy, fix in progress, ETA given.
Same day: Resolution confirmed.
August 29 (3 days later): Postmortem delivered. The resolution message had committed to 48 hours; actual delivery ran a day past that.
Advanced feature usage, already this account's weakest adoption area, stayed at zero.
No one at Brightpath other than Rachel had ever spoken to us directly.
August 29: Requested a direct call rather than leaving it at the postmortem.
August 30: Call with Rachel Kim. Opened by naming it plainly: this happened while her team was mid-incident and needed PulseOps most, and that mattered more than how fast it was fixed. Offered a $1,500 service credit, roughly two weeks of contract value, and proposed a working session with the full on-call team.
September 3: Working session with Brightpath's on-call team, Daniel Osei, Wei Zhang, and Sofia Martins, first contact with anyone at Brightpath beyond Rachel. Walked through the root cause, the connection pool fix, and the staged-rollout safeguard added afterward. All three attended and asked real questions.