CSC Playbook / Start Here
Welcome
Your CSC Call
Success Guide
Your job is deceptively simple: find the people worth the CSS's time, warm them up just enough, and get a real calendar booking before you hang up. This guide gives you everything you need to do that on a cold outbound call — across all three funnels.
What this guide is
A CSC call is 5–15 minutes. There's no room for waste. Every step in this guide has a job. Use the right opener for the right funnel, run the call flow in order, and get the booking on the calendar before you hang up. That's it.
Before every call
Know which funnel they came from. Pull up the Openers tab and have the right script ready before you dial.
During the call
Keep the Call Flow steps open. Use them as a live reference. Six steps, 5–15 minutes. Don't skip any, don't linger too long on any one.
After the call
Log your notes for the CSS immediately. Two minutes. The CSS should never go into a Blueprint call flying blind.
When you hit resistance
Open Objections & Pushback. Six common responses — most aren't real objections, they're hesitation. Acknowledge, reframe, redirect to the booking.
Everything in this guide
Company
Company Background
Youtiva's mission, the ownership model, what gets built, the guarantee, and the one-sentence version for use on calls. Know this cold.
→
The Playground
14 live AI technology modules — for your own edification, not for sharing with prospects. Explore it so you know what you're representing.
→
CSC Call
Your Mission
What the CSC call is actually for, your three real objectives, the call flow overview, and the one rule that governs everything.
→
Pre-Call Prep
A checklist to confirm you've reviewed the prospect's profile before calling. Select the funnel to see the right items. Ends with a before-you-dial check so nothing gets missed.
→
Openers by Funnel
Three different openers — one for each funnel. The right opener depends on how they came in. Start here before every call.
→
Call Flow
1
Open the Call 0–1 min
Use the funnel-matched opener. Get permission, get them talking.
→
2
Surface the Trigger 1–3 min
Find the real reason they're here. One or two questions. You're not doing discovery — you're confirming there's a reason worth pursuing.
→
3
Qualify Quickly 3–5 min
Three checks: decision maker, operational complexity, genuine interest. Keep these conversational — not a checklist.
→
4
Educate Briefly 5–7 min
One or two sentences on what Youtiva actually is. Enough to set expectations, not enough to answer everything. Leave them wanting more.
→
5
Book the Blueprint Call 7–10 min
Open the calendar now. Find a time. Confirm it. Send the invite while they're on the phone. Never send a link and hope.
→
6
Log Notes for the CSS After the call
Takes two minutes. Do it immediately. Six things to capture so the CSS walks in with full context.
→
Post Call & Resources
CSS Handoff Form
Five sections: prospect basics, why they're here (in their exact words), what they said about their business, deal signals, and CSS Coordinator recommendation. Fill this out immediately after the call.
→
Who Gets Booked
Book vs. don't book criteria, the gray area rule, and the Client Success Coordinator's north star in one sentence.
→
Objections & Pushback
Thirteen objections across four categories — cold call specifics, hesitation, timing & readiness, and fit & credibility. Full responses for each.
→
The one rule that governs everything
You are not trying to close anyone. You are not trying to explain everything. You are trying to find the people who are worth the CSS's time — warm them up, give them just enough to be curious, and get a real calendar booking before you hang up. That's the whole job.
CSC Playbook / Company Background
Know your company
Youtiva Company Background
Know this cold before any call. The more fluent you are, the more confidently you handle questions and objections in the moment.
A message from the founder
The one-sentence version
What Youtiva is — memorize this
"We build private AI infrastructure for businesses — customized to how they work, owned by them outright. No subscription, no ongoing dependency on us. It's built once and it's yours."
The landlord analogy — use when they need a vivid frame
"Right now, most businesses are building on rented land. The AI landlord owns the property, can raise rent, change the lease, and benefit from everything you build on it. We help you buy the land."
What makes Youtiva different
Every AI tool
You rent access — someone else owns it
Limited context — can't hold your full operational depth
Built for everyone — optimized for no one
Can be repriced, deprecated, or shut down
What Youtiva builds
You own it — codebase, architecture, IP
Persistent memory — compounds over time
Built specifically for your workflows and data
Runs in your environment — no vendor dependency
How it works — three steps
Proof points — drop naturally, not as a list
70%
Reduction in EMR lookup time — healthcare group
98%
Fraud detection recognition — financial services
60%
Reduction in documentation time — professional services
<10 min
Tax research that previously took 2 hours — CPA firm
Industries served: law firms, healthcare groups, CPA firms, wealth management, sales organizations, compliance & regulatory, logistics, real estate, marketing agencies, media companies.
CSC Playbook / The Playground
Know the technology
The Youtiva Playground
The Playground contains 14 live, interactive AI technology modules — the same ones Youtiva builds and deploys for clients. As a Client Success Coordinator, you don't share this with prospects. It's here so you understand what you're representing before you get on a call.
Open the Playground
playground.youtiva.com — for your own reference only
Why Client Success Coordinators should know this
You don't need to demo the technology or explain it in detail — that's the CSS and engineer's job. But when a prospect asks "what does it actually do?" or "how is this different from ChatGPT?", having seen the modules yourself means your answer is grounded in something real. Confidence comes from knowing what's behind what you're selling.
Not for sharing on CSC calls
The Playground is a prospect-facing tool used by the CSS during and after Blueprint Calls. On a CSC call, if someone asks for a demo or to see what it does, redirect them: "That's exactly what the Blueprint session is designed to show you — our team will walk through the technology live with you." Don't share the link. Save that for the CSS.
What's in it
Inference & Analysis
Inference Engine, Document Analysis, Video Analysis, Audio Analysis
Real-Time Intelligence
Web Search, Video Avatar, Facial Emotion Detection
Automation Intelligence
Agents, Assistant, Browsing, Voice AI
Data & Systems
ML & Analytics, Simulation, Avatar Generation, Domain-Specific Systems
These are baseline models — not configured for any specific business. Think of them as the engine before it's been trained on a client's data and workflows. When Youtiva builds for a client, it behaves like this — but it knows their business.
CSC Playbook / Your Mission
CSC briefing
The CSC call is
where it all begins.
The CSS runs a 90-minute Blueprint Call that designs a system for someone's business. The engineer runs an architecture call that sells it. But neither of those conversations happens without you. You are the first human impression of Youtiva. How you run this call determines who gets in the door — and the quality of what follows.
Your three real objectives
01
Find the people worth the CSS's time.
Not everyone who fills out a form deserves a 90-minute Blueprint Call. Your job is to filter fast and accurately. Keep the obviously wrong ones out. When in doubt, book them and flag it — the CSS can assess in the first ten minutes.
02
Warm them up — not educate them.
One or two sentences on what Youtiva is. Enough to set the right frame, not enough to answer all their questions. If they're asking detailed technical questions, that's what the Blueprint Call is for. Redirect, don't answer.
03
Get the booking before you hang up.
Never send a link and hope they book. Open the calendar now, find a time, confirm it, and send the invite while they're still on the phone. Every minute between "yes" and a confirmed booking is a minute for doubt to creep in.
The call flow at a glance
CSC Playbook / Openers by Funnel
Before every call
Openers by Funnel
The opener changes based on how they came in — because their frame of reference is different. Pick the right one. Everything after the opener follows the same call flow.
Funnel 1 — Light form (cold-ish)
Ads → landing page → basic form → no booking yet. Automation has texted/emailed. You're calling cold-ish.
Funnel 1
If they answer — live opener
"Hey [First Name], this is [Your Name] calling from Youtiva — you filled out a form on our site recently and I just wanted to reach out personally. Did I catch you at an okay time? [pause] Great. I'll keep this short — I just wanted to make sure you got some follow-up and figure out if what we do is actually relevant to where your business is right now. Can I ask — what made you fill out the form in the first place?"
If no answer — voicemail
"Hey [First Name], this is [Your Name] from Youtiva — you expressed interest in what we do and I wanted to reach out personally. I'll keep it quick when we connect. Give me a call back at [number] or I'll try you again in a day or two."
Key reminder
They filled out a basic form — they may not remember exactly what Youtiva does. Don't assume context. The "what made you fill out the form" question tells you their intent level immediately.
Funnel 2 — Booked call (warm)
Ads → landing page → Calendly with light form → call already booked. They're expecting to hear from someone.
Funnel 2
Live opener — they booked, you're confirming and qualifying
"Hey [First Name], this is [Your Name] from Youtiva — I'm calling ahead of your scheduled session to make sure it's as useful as possible when you get on. I just have a couple of quick questions so I can put you with the right person. Is now an okay time for two minutes? [pause] Perfect. So before your call — can you give me the quick version of what's going on in the business that made this feel relevant?"
Why this works
Framing it as "making the call more useful" lowers their guard. They're already booked — you're not selling them anything yet, you're just preparing them. This makes the qualify questions feel natural, not interrogative.
Funnel 3 — Full application (highest intent)
Ads → VSL → full application submitted. Highest intent. They've told you a lot already — use it.
Funnel 3
Live opener — reference their application
"Hey [First Name], this is [Your Name] from Youtiva — I'm reaching out because you submitted your Blueprint application and I personally review every one before we schedule a session. I read through yours and I did want to connect before we book you in. Got two minutes? [pause] Great. So you mentioned [specific thing from their application — pain point, AI journey stage, or the workflow they flagged]. I wanted to make sure I understood that correctly before we put you in front of our team."
This is your strongest funnel
They've watched the VSL and written detailed answers — they're pre-educated and high intent. Reference something specific from their application in the first 30 seconds. It signals that Youtiva actually reads these and takes them seriously. That alone builds trust before you've said anything about the company.
CSC Playbook / Step 1 — Open the Call
Step 1 · 0–1 min
Open the Call
Get permission to continue and get them talking. Use the funnel-matched opener from the Openers tab. Everything after this follows the same flow regardless of funnel.
Purpose
The opener does three things in under 60 seconds: it establishes who you are, sets the frame for the conversation, and gets them talking about why they came in. Don't rush it and don't skip the pause. The pause after "is now an okay time?" is where they decide whether to engage.
Scripts
See Openers by Funnel for the exact scripts
The opener depends on how they came in. Funnel 1 (light form) → cold-ish live opener. Funnel 2 (booked call) → "making the call more useful" frame. Funnel 3 (full application) → reference something specific from their application.
What to listen for
Their first answer tells you a lot
How they respond to "what made you reach out?" calibrates everything. Specific pain mentioned immediately = high intent. Vague curiosity = needs more digging in Step 2. Defensive or rushed = flag it, adjust your energy.
CSC Playbook / Step 2 — Surface the Trigger
Step 2 · 1–3 min
Surface the Trigger
Find out why they're here — the real reason. One or two questions. You're not doing discovery, you're confirming there's a reason worth pursuing.
Purpose
You need to confirm there's a real trigger before you invest more time. A specific business problem is worth pursuing. General curiosity is not — dig one level deeper before moving on.
Questions to use
Primary trigger question
"What's going on in the business that made AI feel like something worth exploring right now?"
If they're vague
"Is it more about saving time on specific tasks, or is it more about not losing ground to competitors who are moving faster on this?"
If they gave context in their application (Funnel 3)
"You mentioned [X] — is that the main thing driving this, or is there more to it?"
What you're listening for
Specific problem vs. general curiosity
"We spend hours a week doing X manually" = a real trigger. Move forward. "I've just been curious about AI" = dig one level deeper before moving on. Ask: "Is there a specific part of the business where you feel like you're leaving time on the table?"
CSC Playbook / Step 3 — Qualify Quickly
Step 3 · 3–5 min
Qualify Quickly
Three things to confirm before you move forward. Keep these conversational — they shouldn't feel like a checklist.
Purpose
You're running three quick checks: is this person the decision maker, is this a business with real workflows, and are they genuinely ready to explore? All three conversationally, in under two minutes.
The three checks
Check 1 — Decision maker
"Are you the person who would ultimately decide on something like this — or would there be others involved in that conversation?"
If they're not the decision maker
Find out who is and whether that person would be on the Blueprint Call. If not, you're booking the wrong person. Try: "Would it be possible to have them on the call as well? The session is designed for the people who'd actually be involved."
Check 2 — Operational complexity
"How big is the team, and roughly what does a typical week look like operationally — are there a lot of recurring processes, client workflows, that kind of thing?"
What you're listening for
A business with real volume and repeatable workflows — not a solo freelancer or a brand new startup with nothing built yet. "We have a team of 15 and we do X every week for Y clients" = good. "It's just me and I'm just getting started" = nurture.
Check 3 — Genuine interest
"Are you at the point where you're ready to actually explore what building something like this would look like — or are you still in the early stages of figuring out if it's even the right direction?"
How to read the answer
"Still figuring it out" isn't a no — it's a nurture. "Yes, I'm ready to explore" means move forward. If they're hesitant, acknowledge it: "That's totally fair — the Blueprint Session is actually designed to answer exactly that question. You don't need to have it figured out before you come in."
CSC Playbook / Step 4 — Educate Briefly
Step 4 · 5–7 min
Educate Briefly
Before booking, make sure they know what Youtiva actually is. One or two sentences — enough to set the right expectations, not enough to answer all their questions. Leave them wanting more.
Purpose
If they show up to the Blueprint Call not knowing what Youtiva builds, the CSS spends the first 20 minutes doing your job. A two-sentence education now saves the CSS significant time and ensures the prospect arrives with the right expectations.
Script
The Youtiva education line
"Just so you have the right frame going into this — Youtiva doesn't sell software. What we build is private AI infrastructure, customized to your business, that you own outright. No subscription, no ongoing dependency on us. It's built once and it's yours. The Blueprint session is how we figure out what that looks like for your specific situation."
If they ask "how is that different from ChatGPT?"
"ChatGPT is a generic tool that anyone can use — it doesn't know your business, your clients, or your processes. What we build is a private system trained on your data, designed around how you actually work. It's the difference between renting a tool and owning infrastructure."
The hard rule
Don't go deeper than this
If they start asking detailed technical questions — that's the Blueprint Call's job. Redirect: "That's exactly what the Blueprint session is designed to answer — our team will walk through all of that with you." Don't try to answer it now. You'll either over-promise or under-explain. Both hurt the deal.
CSC Playbook / Step 5 — Book the Blueprint Call
Step 5 · 7–10 min
Book the Blueprint Call
Get the call on the calendar before you hang up. Never send a link and hope they book. Open the calendar now, find a time, confirm it, and send the invite while they're on the phone.
Scripts — use the right one by funnel
Funnel 1 & 2 — call it the "AI Audit"
"Based on what you've shared, I think the AI Audit is the right next step — it's a working session where our team takes a real look at your business and maps out what a private AI system could actually look like for you. It's not a sales call — you'll leave with something concrete. Let me get you booked in now. What does your calendar look like in the next five to seven days?"
Funnel 3 — call it the "Blueprint Session"
"Great — based on your application and what you've shared just now, I'm going to get you scheduled for your Blueprint Session. This is a 60–90 minute working session — our team will go deep on your business and by the end you'll have a clear picture of what your private AI system could look like. Let's find a time now. What works for you in the next five to seven days?"
Once a time is confirmed
"Perfect — I'm sending you a calendar invite right now. You'll also get a confirmation email. One thing I'd ask you to do before the call — just think through where your team spends the most time on repetitive work. The more specific you are, the more useful that session will be for you."
Before you hang up
Confirm two things before ending the call
1. They know what the call is called (AI Audit or Blueprint Session) and roughly what to expect — a working session, not a sales pitch.
2. The decision maker will be on the call — or you know exactly who will be.
2. The decision maker will be on the call — or you know exactly who will be.
CSC Playbook / Step 6 — Log Notes for the CSS
Step 6 · After the call
Log Notes for the CSS
Fill out the CSS Handoff Form immediately after the call while it's fresh. The CSS should never go into a Blueprint Call flying blind.
How to use the handoff form
The CSS Handoff Form combines everything from the prospect's original form with everything you learned on the call. It gives the CSS full context going into the Blueprint Call — who this person is, why they're here, what you learned, and anything they should watch out for.
Do it immediately
Fill it out right after you hang up — not at the end of your shift. Details fade fast. The prospect's exact words from the call are more valuable than a paraphrase two hours later.
How to flag a gray-area booking
Gray area flag — use the notes field in the handoff form
"Booked — but flagging: decision maker may not be on the call, stated budget hesitation but didn't disqualify, came in curious rather than pain-driven. CSS to assess in first 10 minutes."
The rule on gray areas
If you're not sure — book them anyway and flag it clearly in the notes field. A gray-area prospect is the CSS's call to make, not yours. Your job is to keep the obviously wrong ones out, not to over-filter.
CSC Playbook / Pre-Call Prep
Before the call
Pre-Call Prep
Work through this before you dial. Use it to confirm you've reviewed what the prospect submitted — and to identify the right opener and the key detail to reference in the first 30 seconds.
Which funnel are they from?
Funnel 1
Basic form, no booking
Funnel 2
Basic form + booked call
Funnel 3
Full application + VSL
Funnel 1 — basic form, no booking yet
They filled out the basic form but haven't booked a call. You're calling cold-ish. Their form context is minimal — the trigger question on the call is your main discovery tool. Use the Funnel 1 opener.
What's on their form — confirm you've reviewed this in the CRM
First name, last name
Company name
Company website — scan it before you dial
Email and phone confirmed
Quick website scan — 60 seconds
What do they actually do — in plain terms?
Who are their clients / who do they serve?
Any clues on team size or operational complexity?
Any signs of high document volume, recurring workflows, or AI mentions?
Before you dial
Opener selected — Funnel 1: "what made you fill out the form?"
You know what the company does and can reference it naturally if needed
You have the Funnel 1 script open and ready
CSC Playbook / CSS Handoff Form
After the call
CSS Handoff Form
Fill this out immediately after hanging up. This is what the CSS reads before the Blueprint Call. Your notes determine how prepared they walk in.
What this becomes
This combines what was on the prospect's form with everything you learned on the call. The CSS uses this to enter the Blueprint Call already knowing who this person is, why they're here, and what to watch out for.
01 — Prospect basics
02 — Why they're here
03 — What they said about their business
04 — Deal signals
05 — Coordinator recommendation
CSC Playbook / Who Gets Booked
Post call
Who Gets Booked
The Client Success Coordinator is a gatekeeper. Booking the wrong person wastes the CSS's time and dilutes pipeline quality. Use this to make the call quickly and confidently.
Book vs. don't book
Book the Blueprint Call
Has a real, specific trigger — not just curiosity
Established business with recurring workflows
Decision maker confirmed or will be on the call
Stayed engaged after hearing what Youtiva does
Willing to invest time in a 60–90 min session
Don't book — nurture or disqualify
Pure curiosity, no identifiable business problem
Early-stage, no real workflows or team yet
Decision maker unavailable and unwilling to loop in
Budget clearly not in range — said so directly
Looking for cheap SaaS or a one-time task
The gray area rule
If you're not sure — book them anyway and flag it clearly in your notes to the CSS. A gray-area prospect is the CSS's call to make, not yours. Your job is to keep the obviously wrong ones out, not to over-filter.
The north star
You are not trying to close anyone. You are not trying to explain everything. You are trying to find the people who are worth the CSS's time — warm them up, give them just enough to be curious, and get a real calendar booking before you hang up. That's the whole job.
CSC Playbook / Objections & Pushback
Resources
Objections & Pushback
The most likely things you'll hear on a CSC call. Most aren't real objections — they're hesitation. Acknowledge, reframe, redirect to the booking.
Common pushbacks
"I'm not sure I have time right now." ▼
Response
"Completely understand — and I wouldn't suggest it if I didn't think it was worth your time. The Blueprint session is 60–90 minutes, and people usually leave with more clarity than they expected. We can find a time two or three weeks out if that works better. What does your calendar look like in [timeframe]?"
The move
Don't fight the objection. Offer flexibility on timing, then immediately go back to the booking question. The goal is a date, not a debate.
"Can you just send me some information first?" ▼
Response
"I can — and I will. But I'll be honest with you: what we build is different enough from what most people expect that it's much easier to understand in a conversation than in a document. The session is free, and you're not committing to anything. Why don't I send you something and also book a time — that way you have both, and if the info answers your questions before the call, you can always cancel. Fair?"
Hold the booking
Always try to hold the booking. Sending info without a booked call usually means they disappear. Get the date first, then send the info.
"We're already using ChatGPT / another AI tool." ▼
Response
"That's actually really common — most of our clients were using those tools before they came to us. The difference is that those tools are generic. What we build is private, trained on your business specifically, and owned by you. A lot of people come in thinking they're already covered, and leave the Blueprint session realizing there's a gap they hadn't fully seen yet. That's exactly what it's designed to surface."
"How much does this cost?" ▼
Response
"It depends on the scope — which is exactly why the Blueprint session exists. That's where the team maps out what your system would actually look like and gives you a real number. What I can tell you is that it's a meaningful investment — this is infrastructure, not a software subscription. But the Blueprint session itself is completely free and there's no commitment. That's where it starts."
Don't quote a number
Even if they push. The Client Success Coordinator is not authorized to quote price — that's the CSS's job. If they absolutely won't move without a number, say "projects like this typically start in the five-figure range" and immediately pivot back to the call.
"I need to check with my partner / team first." ▼
Response
"Makes sense — and honestly, if they'd be part of the decision, it might be worth having them on the Blueprint call too. Would that be possible? The session is designed for the people who would actually be involved, so it might be more efficient to just do it together. Who would that be on your end?"
Use this to surface the real decision maker
A call with the right people is better than a call that has to loop back. Use this objection to identify who the real decision maker is and try to get them on the Blueprint Call directly.
"I'm not sure this is right for our business." ▼
Response
"That's actually the right thing to find out — and the Blueprint session is specifically designed to tell you that. If it's not a fit, we'll tell you directly and you'll leave with more clarity than you came in with. If it is a fit, you'll have a real picture of what it could look like. Either way you're not walking away empty-handed."
Cold call specifics
"How did you get my information?" ▼
Response
"You filled out a form on our site — [landing page / Blueprint application / Calendly booking]. You expressed interest in what we do, and I wanted to follow up personally rather than just send an automated email. I know that's not always expected, but I'd rather have a real conversation than have something useful get lost in your inbox. I'll keep it quick — is now an okay two minutes?"
Don't get defensive
This is almost never a real objection — it's a reflex. Answering it calmly and factually (they filled out a form) usually dissolves it immediately. If they're genuinely upset, acknowledge it briefly and offer to call back at a better time.
"I've never heard of Youtiva." ▼
Response
"That's expected — we don't advertise broadly. We take on a small number of clients each quarter and most of our work comes through referrals and targeted outreach. We've built private AI infrastructure for firms in [their industry / adjacent industry] — the kind of work you wouldn't hear about publicly because clients own what we build and don't share it. That's actually part of the model. The Blueprint session is how you'd get a real look at what we do."
Reframe obscurity as exclusivity
Being unknown isn't a weakness here — it's a feature of the model. Youtiva deliberately keeps a low public profile because the work is private by design. Lean into that rather than apologizing for it.
Timing & readiness
"We're too busy right now — bad timing." ▼
Response
"That actually makes a lot of sense — and it's usually the businesses that are the busiest that get the most from this. Being too busy is often the symptom of exactly what we help fix. I'm not asking you to slow down or take time away from the work right now — the Blueprint session is 90 minutes, and we can schedule it two or three weeks out when things settle. Would it help to have something on the calendar for [specific future timeframe] so you don't have to think about it again until then?"
Distinguish from "no time"
"No time right now" means schedule flexibility. "We're in a busy season / bad timing" often means they're not sure it's worth prioritizing. The response above addresses both — it validates the busyness and reframes it as the reason to act, not a reason to wait.
"We already have an IT team / developer building something." ▼
Response
"That's worth understanding — can I ask what they're building? [pause] The reason I ask is that what we build is different from most internal AI projects. Most in-house builds take 12–18 months, cost significantly more than expected, and end up as a configured version of a tool someone else controls. What we build is owned infrastructure — your codebase, your data, your IP. We've had clients come to us after an internal build stalled or hit limitations they didn't anticipate. The Blueprint session would tell you quickly whether what you're building and what we do are actually solving the same problem."
Don't dismiss their build — get curious about it
Asking "what are they building?" often reveals that the internal project is a configured SaaS tool, a prompt workflow, or a partially built system that hasn't launched. That's your opening. If they're genuinely mid-build on something solid, acknowledge it and flag in your notes for the CSS.
Fit & credibility
"I don't want to sit through a sales call." ▼
Response
"Neither would I, honestly — and that's not what this is. The Blueprint session is a working session. There are no slides, no pitch deck, no product demo. Our team spends the whole time understanding your business — how it works, where the bottlenecks are, what a system built specifically for you could look like. Most people leave with more clarity than they expected, even if they decide not to move forward. We only take six new clients a quarter, so we can't afford to waste that time on people who aren't a fit."
"What industry experience do you have?" ▼
Response
"We've built for [relevant industries from Company Background — law firms, healthcare groups, CPA firms, etc.]. The short answer is that the industries we work best with tend to be knowledge-heavy — businesses where a lot of the value lives in documents, processes, or specific people's expertise. That describes most of what we've built for, and it sounds like it describes [their business] too. The Blueprint session is how we figure out if there's a real fit — and if there isn't, we'll tell you directly."
Match to their vertical
Use the industries list from Company Background. If their industry is on it, name it specifically. If it's adjacent, name the closest match and explain why the work transfers. Don't claim experience you don't have — pivot to what the work has in common across verticals.
"We're a small team — this probably isn't for us." ▼
Response
"That's actually one of the most common misconceptions about what we do. Small teams often benefit more than large ones — because when it's a team of 10 or 15, one person's knowledge walking out the door or one workflow breaking down has a much bigger impact. The businesses we build for aren't usually enterprises with hundreds of staff. They're established operations with real complexity — firms, agencies, practices — where a well-built system does the work of two or three people. What does your team actually look like?"
Turn the size concern into a discovery question
Ending with "what does your team actually look like?" moves you out of objection-handling and back into qualifying. If they're genuinely too small (solo or pre-revenue), that's a disqualify. But most people who say "we're small" have 8–25 people — which is exactly the right fit.
The general principle
Most objections on a CSC call aren't real resistance — they're hesitation. People hesitate when something is unresolved. Your job is to find what's unresolved, acknowledge it directly, and redirect to the booking. Don't talk past objections. Acknowledge first, then reframe.