InMail Response / Workflow SOP
Objective: Turn an InMail response into a qualified 15-minute coffee chat with as little unnecessary back-and-forth as possible.
Step 1: Read Their Reply
Put the response into the closest bucket:
- Interested / Tell me more
- What exactly do you do?
- We have this problem
- Already using AI / already have a system
- Send me information
- Price?
- Skeptical / challenge
- Not interested / not a fit
Then respond.
Bucket 1: Interested / Tell Me More
Examples:
Tell me more.
Interesting.
How does this work?
I'd be interested in hearing more.
Reply:
Absolutely.
We build a production environment around each client your agency manages — their voice, context, knowledge, rules, and examples.
New client requests run through that environment before they reach your creative team.
So instead of starting at zero, your people start at review and refinement.
The business case is pretty simple: more billable client work through the same team without quality falling apart.
If that's relevant to what you're dealing with, let's spend 15 minutes on it. Open to a quick coffee chat this week?
Do not add another qualification question unless their profile leaves serious doubt that they're an ICP.
They showed interest. Advance.
Bucket 2: What Exactly Do You Do?
Examples:
What is Callisto?
What exactly are you offering?
How are you doing that?
Reply:
We give each client brand its own production environment built around that client's voice, context, knowledge, and rules.
When a request comes in, we produce the first draft before it reaches your creative team.
Your team reviews, refines, and delivers instead of creating everything from zero.
We're selling production capacity: the ability for the same team to handle materially more client work without needing materially more payroll.
If that's a problem worth solving at [Agency Name], let's take 15 minutes and I'll show you exactly how we're approaching it. Worth a conversation?
Bucket 3: We Have This Problem
Examples:
Capacity is definitely an issue.
We're slammed.
Hiring has been difficult.
Turnaround time is killing us.
We're getting more work than the team can handle.
Do not keep qualifying.
They just told you they have the problem.
Reply:
Then that's exactly why I reached out.
Rather than interrogate you over LinkedIn, let's put 15 minutes on the calendar and look at whether Callisto could actually give your existing team more production capacity.
You open to that this week?
If they say yes, move directly to Coffee Chat.
Bucket 4: Already Using AI / Already Have a System
Examples:
We already use AI.
We built something internally.
Our team already uses ChatGPT.
We already automated this.
Reply:
Good. This isn't really an AI-adoption pitch.
The question is whether what you've built lets the same team take on substantially more client work without increasing editing, QA, or headcount.
Has it?
If NO / NOT REALLY:
That's the gap we're attacking.
Let's compare what you're doing now against our production model for 15 minutes. If there's nothing there, we'll know quickly.
Open to it?
If YES:
Reply:
Then you may already have this problem solved.
Roughly how much additional client capacity did it create for the team?
If they've genuinely solved the problem, do not force the meeting.
If their answer reveals significant remaining manual work, editing, QA, or headcount dependency:
That's the piece I'd want to dig into.
Let's spend 15 minutes comparing systems and see if there's actually anything worth pursuing.
Bucket 5: Send Me Information
Examples:
Send me something.
Do you have a website?
Can you send more information?
Give them what they asked for.
Do not hold information hostage behind qualification questions.
Reply:
Absolutely.
[LINK]
The short version: we build a production environment around each client brand so your team starts at refinement instead of creation.
The economic bet is that the same team can handle significantly more billable client work without adding equivalent headcount.
If that problem is relevant at [Agency Name], let's spend 15 minutes on it after you've taken a look.
If appropriate, include the Capacity Calculator as the link.
Bucket 6: Price?
Do not dodge the price question.
Reply:
We start with a $4,444 paid pilot.
We use two real client brands and real requests so you can judge the actual output and capacity gain before making a larger commitment.
If $4,444 is within the realm of reasonable for solving the capacity problem, let's spend 15 minutes seeing whether there's actually a fit.
If they ask about pricing after the pilot:
Ongoing pricing depends on the number of brands and production requirements.
But I don't want to sell you an ongoing engagement before we've proven the thing works.
That's what the pilot is for.
Bucket 7: Skeptical / Challenge
Examples:
I don't see how this is different from ChatGPT.
AI content isn't good enough.
This sounds like another AI content tool.
How can you possibly maintain every client's voice?
Do not become defensive.
Address the objection directly.
Reply:
That's a fair objection — and generic AI output isn't what we're selling.
The whole premise is that every client gets a separate production environment built around their actual voice, knowledge, examples, context, and rules.
If the output still requires your team to basically rewrite the thing, we haven't created capacity.
That's why we test it against real brands and real requests.
Worth 15 minutes to see whether it holds up?
Bucket 8: No / Not Interested / Not a Fit
Examples:
Not interested.
We're good.
Not something we need.
Please stop contacting me.
Do not objection-handle a clear no.
Reply:
Understood. Appreciate the reply.
Done.
Do not follow up.