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
Two questions to answer before you dial: what do you already know about this prospect, and have they booked a call yet? The second one changes your entire opener.
→
Call Flow
1
Open & Surface the Trigger 0–3 min
The right opener based on booking status, the trigger question, and how to go one level deeper based on what you already know.
→
2
Qualify Quickly 3–5 min
Three checks: decision maker, operational complexity, genuine interest. Plus graceful exit scripts for when it's not a fit.
→
3
Educate & Frame the Call 5–7 min
What Youtiva is in one sentence, and what the Blueprint Call actually is — a working session, not a pitch.
→
4
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.
→
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.
→
Training Videos
Live call recordings and examples — placeholder cards ready to embed video URLs when recordings are available.
→
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
Who we are
Mission
What Youtiva is and why it existsYoutiva builds private AI infrastructure for established businesses that have outgrown what generic AI tools can do. The company exists because most AI in the market is rented — and rented intelligence never compounds for the business that uses it.
The one-sentence version — memorize this
We build private AI infrastructure so your business owns and compounds its intelligence — instead of renting it from platforms you don't control.
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."
Core positioning statement
We help serious operators evolve from experimenting with AI to owning intelligence infrastructure. Not a rescue story — an elevation story. From AI user to intelligence owner.
The ownership model
Differentiator
What makes Youtiva different from every AI toolThis is the most important concept to internalize. The difference isn't features — it's the fundamental model: ownership vs. rental.
What every AI tool is
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
Your intelligence strengthens their platform
What Youtiva builds
You own the system — codebase, architecture, IP
Persistent memory — compounds over time
Built specifically for your workflows and data
Runs in your environment — no vendor dependency
Your intelligence stays inside your business
How to say this in one breath on the call
"What we build isn't software you subscribe to. It's infrastructure you own. Once it's deployed, it runs in your environment — no ongoing dependency on us. You're not renting access to something we control. You own it completely."
What gets built
Product
The four layers of a Youtiva systemWhen a prospect asks "what exactly do you build?" — walk through these four layers. Each one is meaningful on its own. Together they form a unified intelligence that compounds.
1 — Context ingestion
We encode the business — products, terminology, client history, edge cases, workflows. The system works from your knowledge, not general internet knowledge.
2 — Memory architecture
A persistent knowledge layer that grows with use. Every document processed, every decision made — the system retains it. This is what makes it compound instead of reset.
3 — Decision logic & routing
We embed the specific rules and judgment calls that define how the business operates. The system doesn't just retrieve information — it knows what to do with it.
4 — Private portal & deployment
The system lives in the client's environment — their private cloud, their servers. Accessed through a private portal under their domain. Everyone draws from the same intelligence layer.
Simple way to describe this on a call
"Think of it as a brain built specifically for your business. It knows your workflows, remembers everything, makes decisions the way your best people do — and it runs inside your company, not inside our platform."
Fit
Fit criteria
Who Youtiva is for — and who it isn'tOnly six new clients are taken per quarter. Youtiva is deliberately selective — this isn't a volume play. Knowing who's a fit helps you qualify fast and confidently on the call.
Right fit
Established business with real operational complexity
Already using AI tools — knows their limitations
Ready to invest in infrastructure, not another tool
Wants ownership — not a subscription
Decision maker is engaged and involved
Willing to invest time in the Blueprint session
Not the right fit
Still exploring whether AI is relevant
Looking for cheap automation or task hacks
Early-stage with no established workflows
Needs to be convinced ownership matters
Wants a strategy document — not a build
Budget clearly out of range
The north star for fit decisions
When in doubt, book them and flag it for the CSS. Your job is to keep the obviously wrong ones out — not to over-filter. A gray-area prospect with a real trigger and a real business is always worth a Blueprint Call.
How it gets built
Process
The 120-day build processThree steps from first conversation to live system. The first two steps happen before the client pays anything — clarity before commitment is a core part of how Youtiva operates.
How to describe the process on a call
"The first two steps are free — we design the system and show you exactly what it costs and what it returns before you commit to anything. If it makes sense, we build it in 120 days. If it doesn't, you leave with more clarity than you came in with."
Risk removal
Guarantee
The 120-day delivery guaranteeOne of the most powerful trust points in the Youtiva offer. Lead with it confidently when prospects hesitate — it signals Youtiva carries the execution risk, not the client.
If we don't deliver — you don't pay.
No partial payment. No kill fee. No ambiguity. If the system we blueprinted isn't deployed within 120 days, the engagement is free.
How to use this on the call
"We don't ask you to commit to something you don't fully understand. You see exactly what gets built and what it costs before you decide. And once you're in — if we don't deliver what we blueprinted in 120 days, you don't pay. The execution risk is ours."
Credibility & proof
Proof
Results, industries & team credentialsUse these when a prospect asks "has this worked for other businesses?" Drop them naturally — don't recite as a list.
Results — say these with specificity, not enthusiasm
70%
Reduction in EMR lookup time — multi-clinic healthcare group
98%
Fraud detection recognition rate — financial services
60%
Reduction in documentation time — professional services
<10 min
Tax research that previously took 2 hours — CPA firm
Who's been served
Law firms
Healthcare groups
CPA firms
Wealth management
Sales organizations
Compliance & regulatory
Logistics operations
Real estate firms
Marketing agencies
Media companies
Team credentials
6+ years building AI systems — not a newcomer to this space
Founded and sold a SaaS company — understands both sides of building and depending on software
Engineers with backgrounds from Netflix, Meta, and Tesla
Multi-industry deployments across professional services, healthcare, finance, and operations
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 / Step 1 — Open & Surface the Trigger
Step 1 · 0–3 min
Open & Surface the Trigger
Get permission to continue, get them talking, and confirm there's a real reason worth pursuing — all in under three minutes. Select the tab that matches your situation before you dial.
Select your situation
No booking yet
Calling to get them on the calendar
Already booked
Confirming & qualifying ahead of the call
Full application
They filled out the AI Blueprint application
No booking yet — your goal is a confirmed date before you hang up
They filled out a basic form but haven't booked yet. They may not remember exactly what Youtiva is — referencing "the AI Audit" gives them an immediate hook. Context is minimal, so the trigger question is your main discovery tool.
Live opener
"Hey [First Name], this is [Your Name] calling from Youtiva — you filled out a form on our site recently requesting an AI Audit 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 request an AI Audit in the first place?"
Voicemail
"Hey [First Name], this is [Your Name] from Youtiva — you requested an AI Audit, and I wanted to reach out personally to go over a question or two and get that scheduled for you. 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. Thanks!"
When they answer — follow-up questions
If their answer is 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 give a real trigger — go one level deeper
"That makes sense. Is that the main thing driving this, or are there other areas of the business where you feel like you're leaving time on the table?"
What you're listening for
A specific, recurring problem — not a general interest in AI. "We spend 10 hours a week doing X manually" is a real trigger. "I've just been curious about AI" is not — dig one level deeper before moving to qualifying.
Don't skip the pause — for any opener
The pause after "is now an okay time?" is where they decide to engage. Let it breathe. If they say it's a bad time: "No problem at all — when's a better time? I just want to make sure you get a real follow-up."
The goal of this step
What you need before moving to qualifying
By the end of Step 1 you should be able to say to yourself: "They have [a real problem] and it's [costing them something specific]." If you can't say that yet, ask one more question before moving on. Don't advance to qualifying on vague curiosity.
CSC Playbook / Step 2 — Qualify Quickly
Step 2 · 3–5 min
Qualify Quickly
Your job here isn't to run through a checklist — it's to establish three things before you move forward. Some may surface naturally from the conversation. Others you'll need to draw out. The goal is always to sound like a thoughtful person, not an interviewer.
The three things you need to know
1 — Are they the decision maker?
Is this the person who would actually say yes — or is there someone else who needs to be on the Blueprint Call?
2 — Is there real operational complexity?
Is this a business with established processes and recurring workflows — or is it too early stage for what Youtiva builds?
3 — Are they genuinely ready to explore?
Do they have a real problem and a real willingness to act — or are they just curious? "Still figuring it out" is a nurture, not a disqualify.
How to approach this
You're not running through a checklist — you're having a conversation where you happen to need specific information. Most of it should surface naturally if you're listening. Only ask what hasn't already been answered, and when you do ask, make it sound like curiosity, not a form.
Basic form
Funnel 1 or 2 — establish all three
Full application
Funnel 3 — confirm and read between the lines
Basic form — you know very little, so let them talk first
All three things need to be confirmed, but many will surface naturally as they answer the opener. Let the conversation develop before reaching for a question. Only fill in what's still missing.
If team size or complexity hasn't come up
"Just so I have a sense of scale — how big is the team, and is this a business with a lot of recurring processes day-to-day?"
If decision maker status isn't clear
"And are you the person who would typically lead a decision like this, or would there be others involved?"
If readiness to explore is unclear
"Are you at the point where you're actively looking to do something about this, or still in the early stages of exploring what's out there?"
If they're not the decision maker
Find out who is and whether that person can be on the Blueprint Call. "Would it be possible to have them join the session? It's designed for the people who'd actually be involved — it'll be more useful for everyone."
The mindset for this whole step
You're not interrogating — you're having a conversation where you happen to need specific information. Most of it should come out naturally if you're listening well. Only ask what hasn't already been answered, and when you do ask, make it sound like curiosity, not a checklist.
If it's not a fit — how to exit gracefully
Not every call ends in a booking. When a prospect clearly isn't a fit — too early stage, budget nowhere close, no real problem — the most professional thing you can do is be honest, warm, and brief. A graceful exit leaves the door open for later and protects Youtiva's time.
Too early stage — no established workflows yet
"I really appreciate you taking the time — and I want to be straight with you. Based on what you've shared, I think the timing might be a little early for what we do. The businesses we build for typically have established processes and a team that's running them — and it sounds like you're still in the process of building that foundation. That's actually a good place to be. I'd rather have this conversation with you in six to twelve months when we can actually design something around a live operation. Is it okay if I put you back in touch at that point?"
No real problem identified — pure curiosity
"I really appreciate the interest — honestly. But I want to make sure our team's time is useful for you, and the Blueprint Session works best when there's a specific problem we're solving. It sounds like you're still in the early stages of figuring out where AI fits. What I'd suggest is staying connected — follow what we're putting out, and when something clicks and you have a clearer picture of where the bottleneck is, I encourage you to reach back out. We'll be here!"
Budget clearly not in range
"I appreciate your honesty — and I want to match it. What we build requires a meaningful investment, and I'd rather tell you that now than have you sit through a 90-minute session and feel like your time was wasted. It might not be the right fit right now, but that doesn't mean it won't be later. I'll make a note and check back in when the timing may make more sense. I appreciate you taking the call."
The rule on graceful exits
Always leave them feeling respected — never dismissed. A warm exit today is a referral or a re-engagement six months from now. End with something specific ("I'll follow up in six months" or "stay connected with what we're publishing") so it doesn't feel like a door closing.
CSC Playbook / Step 3 — Educate & Frame the Call
Step 3 · 5–7 min
Educate & Frame the Call
Select your situation, then work through the three steps. Every path ends the same way — they agree to come prepared.
Select your situation
Basic form
Not booked yet
Basic form
Already booked
Full application
Already booked
Basic form, not booked — walk through all three steps
They may not remember what Youtiva is or what they signed up for. Each step sets the right expectation before you ask for their time and commitment.
Step 1
What Youtiva doesCover what Youtiva is, what makes it different from SaaS tools, that they own it outright, and where it runs. Keep it conversational — this is a frame-setter, not a product pitch.
Script
"Just so you understand a bit better what Youtiva does before going into this — Youtiva is not another subscription or SaaS product. What we build is private AI infrastructure, customized to your business, that you own outright. Once your solution is built, there's no ongoing dependency on us, although we're always here to expand your system throughout your business as you wish. But the bottom line here is that once it's built, it's yours. It can run in your own private cloud or on-premise servers. This is your own AI that you will own fully."
Step 2
What the AI Audit isTransition directly from the Youtiva explanation into what the AI Audit actually is — a working session, not a pitch. The "as long as that makes sense" bridge connects the two naturally.
Script
"Now as long as that makes sense and sounds like what you're after, the next step is to get you scheduled for your AI Audit — it's a 60 to 90-minute working session with our team. There are no slides or pitch deck. It's a deep-dive conversation where we go through your business, your workflows, and what a system built specifically for you could actually look like. You'll walk away with a real picture of what's possible — and if it's not a fit, we'll tell you that directly. There's no commitment involved."
Step 3
The prep askConfirm they want to move forward, describe what prep looks like, get their agreement, and promise the link. All four in sequence.
Confirm they want to move forward
"Does that sound like something worth your time? I want to make sure this feels right before we get anything on the calendar."
Describe the prep
"One thing I want to flag before we book — this session works best when you come in with some context ready. Specifically: the workflows where your team spends the most time on repetitive, knowledge-intensive work; what AI tools you're already using and where they're falling short; and the one outcome that would have the biggest impact on your business in the next 12 months. The more specific you are, the sharper your session will be."
Get their agreement
"Can I count on you to come in with that prepared?"
Promise to send the prep link
"Perfect. I'll send you a link right after this call with everything laid out — it'll take you five minutes to read and it'll make the 90 minutes with our team significantly more valuable. Let's get you booked in."
Don't go deeper — for any situation
If they start asking detailed technical questions, redirect: "That's exactly what the session is designed to answer — our team will walk through all of that with you live." Don't answer it now. You'll either over-promise or under-explain.
Why the prep agreement matters
Getting a "yes" is not optional
An unprepared prospect wastes the CSS's time and produces a weaker Blueprint. A verbal "yes, I'll come prepared" creates a small but real commitment — and most people who agree actually follow through. Those calls are meaningfully better for everyone in the room.
CSC Playbook / Step 4 — Book the Blueprint Call
Step 4 · 7–10 min
Book the Blueprint Call
Step 3 ended differently for each situation. Pick up from exactly where you left off.
Select your situation
Basic form
Not booked — open the calendar now
Basic form
Already booked — send the link and close
Full application
Already booked — call is closed
Step 3 ended with "Let's get you booked in" — this is that moment
The prep ask is done and they've agreed. Now open the calendar, find a time, confirm it, and send the invite while they're still on the phone. Never send a link and hope — book it live.
Open the calendar
"What does your schedule look like in the next five to seven days?"
Once a time is confirmed
"Perfect — I'm sending the invite right now. The prep link will come through in the confirmation email. Thanks so much for your time today — I'm excited to hear how your AI Audit goes. Talk soon!"
Before you hang up — confirm one thing
The decision maker will be on the call — or you know exactly who will be.
CSC Playbook / 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
Two things to establish before you dial: what you already know about this prospect, and whether they've booked a call yet. The answer to the second one changes your entire opener.
Step 1 — Have they booked a call yet?
No booking yet
You're calling to get them on the calendar
Already booked
You're confirming and qualifying ahead of the call
Full application submitted (Funnel 3)
They've watched the VSL and answered detailed questions — use everything they gave you
Calling to book — your goal is a confirmed date before you hang up
They filled out a basic form but haven't booked yet. Automation has followed up. You're calling personally. Their context is minimal — the trigger question on the call is your main tool. Don't assume they remember exactly what Youtiva does.
What's on their form — review in CRM before dialing
First name, last name
Company name and website
Email and phone confirmed
60-second website scan
What do they do — in plain terms?
Who are their clients and how do they serve them?
Any signs of team size, recurring workflows, or operational complexity?
Anything you can reference naturally in the first 30 seconds?
Before you dial
You know what the company does and can speak to it if needed
You have Step 1 (Open & Surface the Trigger) open — no booking opener ready
Goal is clear: qualify and get a date on the calendar before hanging up
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 / calendar 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.
CSC Playbook / Training Videos
Resources
Training Videos
Live call recordings and examples. Watch these to study what great CSC calls look and sound like in practice — how to open, how to qualify naturally, and how to get the booking before hanging up.
Live call examples & recordings