Real messages, ready to copy

B2B SaaS tool, reaching a support team

Subject: routing tickets across two growing teams Noticed BrightDesk's been hiring for both Support and Sales roles the last couple months. Teams that grow on both sides at once usually start losing requests in the handoff, a ticket sits unowned because it's not clear whose queue it's in. We built a small tool that auto-routes tickets by content and current load, a support lead at a similarly sized team cut their unowned-ticket count in half within three weeks. Worth a 15-minute look, or is your routing already solid?

Freelance designer, reaching a small business owner

Been following [Company]'s site since the spring, the product's clearly further along than the storefront is. A lot of small teams end up with a site that reflects year one, not where the business actually is now, and it quietly costs conversions. I put together two quick before/after mockups of your homepage, no pitch attached, just what I'd change and why. Want me to send them over, or is a redesign not on the radar right now?

Early-stage founder, no case studies yet

Saw you mention switching invoicing tools twice this year, that kind of churn usually points to something structural rather than the tool itself, most often unclear payment terms or manual reconciliation eating up time. I don't have client logos yet, this is a new tool, but I ran your public pricing page through the audit we built and found three specific friction points. Happy to send the breakdown over, no charge, no catch. Want it, or is this not a live problem for you right now?

Comment-first, on a post in your space

This tracks with what we're seeing too, the teams that skip step two end up redoing step four. Curious whether you've tried flipping the order, or if that creates its own problems downstream.

Connection request, referencing something specific

Your post last week on [specific topic] was the first take on it that didn't just repeat the usual advice, especially the point about [specific detail]. Wanted to connect.

First DM after connecting, no pitch

Thanks for connecting. No pitch here, genuinely curious given your last few posts, how's your team currently handling [specific process]? Trying to understand how teams like yours are approaching it these days.

“Your price is higher than [competitor]'s”

That's fair, and I'd want to know the same thing in your position. [Competitor] is a real option, and on sticker price alone they're cheaper. Where the two tend to diverge is in [implementation time / support response / the specific thing that's actually true] — can I walk you through where that gap shows up in practice, so you can weigh it against the price difference yourself?

“We don't have budget for this right now”

Makes sense, budget cycles are real and I'm not going to argue with your calendar. Is it that the budget doesn't exist this quarter, or that it exists but isn't allocated to this yet? Those are different problems — one probably means revisiting this next quarter, the other might mean a smaller starting scope that fits what's already approved.

“We're already using something for this”

Good, that means you already know what you need this kind of tool to do, which makes this conversation easier, not harder. What's working about the current setup, and is there anything about it that still bugs you? If nothing's missing, we're not a fit, and that's a fine answer too.

“Just send me some information”

Happy to. Information tends to actually get read when it answers one specific question instead of covering everything, so what's the one thing that would tell you whether this is worth a closer look — cost, timeline, or something else? I'll send exactly that, nothing more.

Discount request, met with a trade

I can get to that number — if we move to a 12-month term instead of 6, the volume makes the math work on our end. Does that work for you, or would you rather keep the shorter term at the original price?

Phased-scope alternative, instead of cutting price

Rather than cut the price on the full scope, what if we start with [core piece] now, prove it out, then layer in [the rest] once you've seen results? Keeps the upfront investment smaller without cutting into what actually makes it work.

Trading a free add-on for something else

I don't want to just add that on for free — it'd mean cutting something else to make room for it. What matters more to you, having [X] included, or keeping [Y] at full scope? I can trade one for the other, just not both.

Direct close, no manufactured urgency

Sounds like we've covered pricing, timeline, and scope. Based on everything we've talked through, are you ready to move forward, or is there something still unresolved I should address first?