Concept build · OBx Call IQ · seed data — no live transcripts yet
OuterBoxCall IQ
ML
Calls you personally joined.
Calls2
Proposal · analyzed automatically after the call

Kraken Oil & Gas — AI services scoping

Jul 7, 202642:18Google Meet · Gemini● you were on this call
84Strong call

Who was on the call

JAJordan AlvarezOBx · AE (rep)62%
PNPriya NairKraken · VP Operations26%
TBTom BeckKraken · IT Director12%

The short version

A discovery-led call that landed well. Jordan quantified the manual-dispatch pain in Priya's own words before pitching, then mapped it cleanly to the voice-agent scope. Two threads were left open — a live pricing number and the data-security review — but the buyer named their CTO as the approver, so the path forward is clear.
Do thisSend the security posture one-pager with the proposal and book the CTO call this week. Don't let the pricing question live in email.

What worked

Opened on their pain, not your pitch
Before I show you anything, walk me through what a bad week looks like right now.
Jordan · 03:58
This let Priya quantify the loss herself — “fifteen, twenty jobs a month.” That number is now your ROI anchor; use it verbatim in the proposal.
Clean multi-threading
Tom, this next part is really your call — how does that sit with your security model?
Jordan · 26:40
Pulled the technical stakeholder in by name instead of talking over the objection. Multi-threaded deals close more reliably.

Coach on this

!Deferred the pricing question
What are we talking about investment-wise? I need a rough number for internal.
Priya · 18:40
You said you'd “send something over.” A buyer asking for a number is a buying signal — deferring it cools momentum and hands control to email.
↳ Try instead
For a rollout this size we're usually in the $60–90K range for year one — I'll firm it up in the proposal, but does that order of magnitude work for the budget conversation you need to have?
!Acknowledged the security concern without answering it
Anything touching our SCADA data has to clear a security review.
Tom · 26:10
You replied “we can definitely work with your team,” which is reassurance, not an answer. This is the real gate on the deal — leaving it vague invites a slow internal review.
↳ Try instead
Good — here's how we handle it: your data stays in your environment, we're SOC 2 Type II, and I'll send the security packet your team will need so the review starts on day one, not week three.

Call signals

Talk ratio
62%
slightly high · aim 45–55%
Questions asked
14
strong discovery
Longest monologue
3:10
rollout explainer @17:30
Next step
Yes
CTO call named

Objections

openData security / SCADA accessAcknowledged but not addressed. Highest-priority follow-up.
resolved“Bigger platform felt heavy” (competitor)Handled well by contrasting scope and speed to value.

Key moments

Buying signal — pain quantified04:12Pricing raised by buyer18:40Objection — data security26:10Competitor mention31:55Commitment — approver named38:44

Topics & tags

Voice agentDispatch automationSecurity reviewProposal stageMulti-threaded

Seed data — analysis and quotes are illustrative until the live pipeline is wired.