Your Cold Email Sounds Exactly Like the Last 11 They Deleted

Hi Sarah, I noticed your team at Meridian recently expanded from 40 to 65 people in six months — that kind of growth usually means your existing workflows are under serious pressure. We built Claro specifically for operations teams navigating that scale-up phase, and companies in a similar position have cut their project turnaround time by about 30% within the first quarter. I'd love to share how that would look for Meridian specifically. Would a 15-minute call on Thursday or Friday work for you?

Hi Sarah, I wanted to circle back with something specific. Since my last note, we published a case study with Halo Group — they were in a similar growth stage to Meridian and facing the same workflow bottlenecks. The results are worth a look: they reduced their project cycle time by 34% in 90 days. I've linked it below. If it resonates, I'm available for a brief call this week. If the timing isn't right, no worries at all — I'll follow up next quarter.

David, I've been following Westbrook's expansion into the APAC region — the operational complexity of scaling across three new markets simultaneously is significant, and it's a challenge we've helped several companies in your sector navigate. I'd welcome the opportunity to share a few specific insights from those engagements. Would 15 minutes on your calendar this week or next be feasible? I'm happy to work around your schedule.

Hi Sarah, thanks for the conversation yesterday. Two things stood out from our demo that I want to highlight. First, the workflow automation you asked about for your onboarding process — I confirmed with our team that we can replicate that exact sequence, and I've attached a short walkthrough showing how it would work for your use case. Second, the integration with your existing Notion setup is straightforward and wouldn't require any migration. I've put together a custom proposal reflecting what we discussed, including the team pricing for 65 seats. I'll send that over by end of day tomorrow. In the meantime, would it make sense to schedule a call with your Head of Ops to walk through the technical details?

Hi Sarah, we last spoke in January when your team was mid-reorg and the timing wasn't right for a new tool. Two things have changed since then that might shift the calculus. We launched an automated reporting feature that directly addresses the bottleneck you mentioned around weekly status updates. And based on your last quarterly report, it looks like the team restructure has settled — which was the main blocker last time. Worth a fresh 15-minute look? If not, just say the word and I'll check back after Q3.

That's a completely fair question, and I want to make sure the investment makes sense for your team before we move forward. Here's how I'd think about it: your team currently spends roughly 15 hours a week on the manual reporting process you described. At your team's average fully-loaded cost, that's approximately $4,200 a month in labor. Our annual plan comes to $1,100 a month. Even if we only cut that reporting time in half — and most teams see closer to a 70% reduction — you're looking at a net savings of about $1,000 a month starting in month one. I'd rather you see those numbers and make the call that's right for Meridian than push for a close that doesn't hold up.