◆ SECTION 01
LEAD IDENTITY
CONTACT DETAILS
FILL FIRST
◆ HOW TO ASK — TELL US ABOUT YOUR NEEDS?
"Before I suggest anything, tell me in your own words what you need this system to solve."
Capture their exact wording. Reuse this language in Pain Statement and Objections handling.
◆ DYNAMIC INTAKE DASHBOARD (LLM + REINFORCEMENT)
Add need statement, then generate an intake plan.
◆ SECTION 02 · P0 — FIRST 60 SECONDS
WHO IS THIS?
LEAD CATEGORY — SETS YOUR TONE + PRICING RANGE
◆ HOW TO ASK — WHO IS THIS?
"To guide you correctly, tell me your setup first: retail, warehouse/distributor, or factory operations?"
This question sets your tone, expected scope, and tier anchor in the first 60 seconds.
📦 RETAIL TONE
Simple · 1 cam · Basic counting · Phase 1 ₹45–55K🏭 WAREHOUSE TONE
Multi-zone · Vehicle ROI · Shift reports · ₹1L–₹2.5L⚙️ FACTORY TONE
Authority · Gate validation · 5+ cams · ₹3L–₹5L · Anchor Tier 3◆ SECTION 03 · 5–8 MINUTES
DISCOVERY — 6 QUESTIONS
VOICE RECORDER NOW FLOATING
GLOBAL ACCESS
◆ USE FLOATING RECORDER
Open the floating VOICE RECORDER button from anywhere on this page.
This keeps call capture independent from Discovery, so you can record during any section.
01
What needs to be counted?
✓ Done
◆ HOW TO ASK THIS
"Tell me — what exactly needs to be tracked or counted at your facility?"
Let them answer fully. Don't suggest options — you'll hear their language and their pain naturally. If they're vague, follow up with: "Is it physical goods, vehicles, or people movement?"
02
Where does counting happen?
✓ Done
◆ HOW TO ASK THIS
"Where physically does the counting happen — is it at an entry gate, on a production floor, at a loading bay, or somewhere else?"
Location tells you camera angle complexity. Gate = fixed angle, easy. Multiple floor zones = harder config. This affects scope + pricing tier directly.
03
Manual or conveyor?
✓ Done
◆ HOW TO ASK THIS
"Is the counting happening on a moving belt or conveyor — or is it more of a manual flow, like people or vehicles passing through?"
Conveyor = high speed, frame rate matters. Manual/gate = slower, more forgiving config. If conveyor, ask speed — it affects detection accuracy and GPU requirement.
04
Approx daily volume?
✓ Done
◆ HOW TO ASK THIS
"Roughly how many [vehicles / bags / pieces] pass through in a day? Even a ballpark is fine."
Volume = justification for investment. High volume = stronger ROI argument. If they hesitate, say: "Even a rough number — is it hundreds per day or thousands?" Gets you close enough.
05
How many cameras?
✓ Done
◆ HOW TO ASK THIS
"How many entry points or zones would need a camera? Do you already have CCTV in those spots?"
Never ask "how many cameras do you want to buy" — that sounds like selling. Ask about zones/entry points instead. You determine camera count from their answer. More zones = higher tier = anchor Tier 2 or 3.
06
Current problem?
✓ Done
◆ HOW TO ASK THIS
"What's the main issue you're dealing with right now — what's actually breaking or costing you time?"
This is the most important question. Don't rush it. Let silence happen — they'll fill it. Their answer becomes your pain mirror. Write down their exact words if possible.
◆ SECTION 04 · PSYCHOLOGICAL ALIGNMENT
BUILD THE PAIN STATEMENT
ASSEMBLE FROM OPTIONS — READ BACK TO CLIENT TO GET "YES"
◆ HOW TO ASK — BUILD THE PAIN STATEMENT
"Let me replay what I heard: [situation + problem + impact]. Is that accurate?"
Don't pitch yet. First get a clear yes on the pain mirror, then move to solution and tier.
◆ BUILD THEIR PAIN MIRROR — CLICK TO COMPOSE
PART A — THE SITUATION
PART B — THE PROBLEM
PART C — THE IMPACT
Select parts above to build the pain mirror statement...
📣 SAY THIS OUT LOUD: Read the statement above back to the client, then ask: "Correct?" — wait for their YES. That YES = psychological alignment = they're ready to hear a solution.
DID THEY CONFIRM?
◆ SECTION 05 · HANDLE IN REAL TIME
OBJECTIONS RAISED
TAP TO OPEN · FLAG IF RAISED · USE THE RESPONSE SCRIPT
◆ HOW TO ASK — OBJECTIONS RAISED
"Before we proceed, what is your biggest concern right now?"
Handle one objection at a time. Acknowledge first, then respond using the scripts below.
"This is too expensive"
⚠ RAISED
▼
◆ RESPONSE — READ THIS
"We can optimise the scope to fit your current needs. The system doesn't have to start at full scale." — Then offer Phase 1. Reduce features, never reduce value or hardware quality.
"Another vendor is cheaper"
⚠ RAISED
▼
◆ RESPONSE — READ THIS
"Do they provide on-premise AI processing and custom calibration on your actual footage?" — If they say no or unsure, you've shifted the comparison. Don't attack the competitor. Shift the criteria.
"Why do you need a GPU?"
⚠ RAISED
▼
◆ RESPONSE — READ THIS
"To maintain real-time performance without any lag or delay. Without it, detection slows down and you miss counts. Think of it as the engine behind the accuracy." — Keep it simple. No tech overload.
"Can you guarantee 100% accuracy?"
⚠ RAISED
▼
◆ RESPONSE — READ THIS
"Accuracy depends on the visibility conditions at your site — lighting, angle, occlusion. That's exactly why we do a feasibility validation on your actual footage before confirming anything. We don't guess." — Never promise 100%.
"We'll think about it / not urgent"
⚠ RAISED
▼
◆ RESPONSE — READ THIS
"Completely understand. Let's keep it simple — just send us a short 2-minute clip from your site. No commitment, no cost. We'll assess and tell you honestly what's achievable. That takes the pressure off."
◆ ADD CUSTOM OBJECTION RAISED
◆ SECTION 06 · SCOPE ASSESSMENT
TIER & CLOSE STRATEGY
SELECT PROBABLE TIER — ANCHOR HIGH FIRST
DON'T SHARE PRICE YET
TIER 1 · Basic Counting
₹70K–₹1L
Single camera · Line crossing · No advanced logic
TIER 2 · Vehicle / Multi-Zone
₹1L–₹2.5L
Vehicle ROI · Multiple cameras · Tracking logic
TIER 3 · Industrial Multi-Point
₹3L–₹5L+
5+ cameras · Gate cross-check · Full dashboard
Say: "Let's start with Phase 1 validation." — 1 cam · counting module · on-site calibration. ₹45K–₹75K. Once deployed, 80% of clients expand.
◆ SECTION 07 · SET BEFORE HANGING UP
FOLLOW-UP PLAN
SET ALL DATES NOW — DON'T RELY ON MEMORY
DAY 1
Ask for sample video footage
DAY 2
Reminder — video not received
DAY 4
Send case reference / similar deployment
DAY 7
Final call — no video = mark cold lead
🧊 NO VIDEO AFTER 7 DAYS — MARK AS COLD LEAD. Stop active follow-up.