Cloudworkz

Account Summary

Cloudworkz is a cloud and IT services company that engaged with OneAI in a concentrated two-week burst in September 2025 — four meetings focused entirely on script development, beginning with a kickoff on September 4 and ending with a script refinement session on September 17. The account never progressed past the scripting phase, never went live, and has had no contact in 8+ months. This account is almost certainly churned.

Use Case

The AI voice agent was intended to qualify leads in the cloud/IT services space — likely calling IT decision-makers or SMB prospects to qualify interest in cloud migration, managed services, or IT support contracts. The heavy focus on call script work suggests the team was trying to nail the agent’s pitch and qualification questions before committing to a launch.

Relationship Health

🔴 Churned — Four meetings in two weeks exclusively on scripting, no go-live, no contact for 8+ months. This account did not advance past configuration.

Key Contacts

• 3 contacts from cloudworkz.com (names and roles not documented)

What’s Working

• N/A — Account never reached live operation

Open Challenges

• Account went dark during script development — never reached go-live
• The tight two-week meeting cluster followed by complete silence suggests either the script work revealed a fundamental mismatch, or an internal decision was made to not proceed
• No documented reason for disengagement makes post-mortem learning difficult
• 8+ months of silence makes re-engagement unlikely without a specific trigger (new product, new contact, new budget cycle)
• No named contacts documented

Open Action Items

• Formally classify this account as churned if not already done
• Document the suspected reason for non-launch (if any internal knowledge exists) for future prospecting and ICP refinement
• If Cloudworkz is still paying as a customer, escalate to sales immediately — this would be a critical oversight
• Consider whether a brief win-back outreach at the next budget cycle (e.g., Q4 2025 or Q1 2026) makes sense, with a new angle or product update

Recent Meeting Highlights

• 2025-09-17 — Call Script (2nd session): Second dedicated script refinement session — the fact that a follow-up script session was needed suggests the first pass required significant iteration
• 2025-09-15 — Call Script: First script refinement session; two script sessions in three days indicates urgency but also difficulty getting the script right
• 2025-09-08 — Call Script: Early script session — all post-kickoff work was script-focused with no movement toward technical integration or go-live prep
• 2025-09-04 — Kickoff: Initial kickoff; the account moved quickly into script work but never beyond it

Prep Tips for Next Meeting

• There is likely no next meeting warranted unless a re-engagement signal emerges (inbound from Cloudworkz, referral, or product event)
• If re-engaging proactively: lead with what has changed in the OneAI product since September 2025 — new features, improved call quality, relevant customer case studies in IT/cloud
• Acknowledge the gap without dwelling on it: “We know it’s been a while — we wanted to reach out because [specific relevant reason]”
• Do not restart the scripting process from scratch; instead, check if any of the September 2025 script work is recoverable
• Have a clear, short path to go-live ready to present — the previous engagement stalled in script iteration, so a faster path forward would need to address that friction
• If the account is not viable for re-engagement, formally close and use as a signal for ICP refinement (cloud/IT services customers may require longer script development cycles)