Author
Alex spent most of his career in tech sales and revenue enablement, where he saw a consistent gap - the most important data in go-to-market lived in conversations, but couldn't be structured or used.
Semarize is built to change that: turning conversations into something systems can actually operate on.
Posts by Alex Handsaker
How to Extract Zoom Cloud Recording Transcripts via the Zoom API
The Zoom cloud recording transcript API isn't one endpoint. This developer guide covers the Server-to-Server OAuth scope, listing recordings, the recording_files file_type model, downloading the VTT transcript with a bearer token, and webhook versus backfill ingestion, then where the extracted text becomes structured JSON.
What’s a Good Sales Call Score? Benchmarks and How to Set Your Own
There's no portable average SaaS sales call score, because a score only means something relative to the rubric behind it. Here is why a universal good sales call score benchmark doesn't exist, how to set your own baseline from calls you already have, and how to keep it comparable over time.
Zoom Revenue Accelerator Alternatives: Get Structured Call Data via API
Zoom Revenue Accelerator gives teams on Zoom Meetings a capable coaching and deal-analytics surface. Teams look for a Zoom Revenue Accelerator API alternative when they need structured call data they own: typed JSON fields for CRM enrichment, warehouse analytics, and automation. Here is where ZRA fits, and where Semarize fits alongside it.
2026 Transcript Analysis APIs: Structured Extraction, Ingestion Mechanics, and the Comparison That Actually Matters
Most teams don't fail at transcript analysis because the model is bad. They fail because the API can't turn transcripts into the structured fields their workflows need at predictable cost. This comparison covers what to evaluate: structured extraction, NLP output fit, ingestion mechanics, and pricing you can forecast before you commit to volume.
From Raw Transcripts to Durable RevOps Signals: Pipeline Health, Rep Performance, and Buyer Engagement
Raw call transcripts are archives, not RevOps signals. The schema-first approach starts from the questions forecasting and capacity planning actually need answered, defines the structured extraction targets that would answer them, and builds a pipeline that lands durable, queryable fields in the data warehouse and CRM.
Committed Next Steps or It Didn't Happen: Deterministic Extraction for RevOps
Most call summaries conflate commitments with discussions. A deterministic next-steps Brick extracts the specific action, owner, and timing from transcript evidence, scores it against a clear commitment standard, and routes it into CRM tasks and Slack alerts automatically. No summary required.
Send Conversation Intelligence to HubSpot Without Corrupting Your CRM
The call analysis dashboard is not the product. The product is the set of HubSpot deal and contact properties that RevOps can query, filter, and automate from. This guide covers the step-by-step workflow for defining a property schema, wiring webhook delivery, validating the output, and writing reliably to HubSpot without duplicate processing or corrupt values.
CRM Field Extraction From Sales Calls: Brick-Based, Validated, Webhooked
Most conversation intelligence programmes fail at CRM enrichment not because the model is wrong but because fields get filled with summaries instead of typed evidence. A Brick-based extraction contract, a validation gate, and webhook-driven automation fix each part of that in sequence.
CRM Enrichment From Sales Calls: The RevOps Playbook for Salesforce and HubSpot
A reliable CRM enrichment pipeline from sales calls depends on three decisions made before the first webhook fires: which fields are worth extracting, how Brick output types map to CRM field types, and what the update policy is when the same deal has multiple calls. This playbook covers each.
Why Coaching From AI Scorecards Usually Fails (And What the Score Actually Needs to Measure)
Most AI scorecards measure rep activity, not buyer understanding. Coaching from activity scores improves script adherence, not deal quality. The score that changes coaching behaviour measures buyer-side evidence: what the buyer said, confirmed, and left unaddressed.
Gong to Structured JSON: The Developer Guide to CRM-Ready Conversation Intelligence
Exporting Gong transcripts isn't conversation intelligence. Conversation intelligence is typed JSON fields you can score, route, and measure in CRM. This developer guide covers the Gong API, evaluation Bricks, and the pipeline pattern that delivers structured output to Salesforce, HubSpot, or a data warehouse.
Audit Discovery Calls Like RevOps: Turn Playbook Criteria Into Deterministic Scoring and Coaching Gaps
Most teams don't have a discovery call quality problem. They have an evaluation problem: they can't measure buyer understanding against their playbook, so coaching runs off noise. Turn playbook criteria into evaluation Bricks, score every call, and route rep and team gaps into coaching workflows.
How to Vibe Code an Internal Sales Enablement Dashboard
Vibe coding tools have solved the frontend half of building an internal sales dashboard. The data half, turning call transcripts into typed, queryable fields, is what Semarize handles. This is how the two fit together: Kits and Bricks for the extraction layer, Lovable or Bolt for the interface.
Turn Sales Call Transcripts Into CRM-Ready JSON: Schema, Extraction, Validation, and Scoring
The gap between a call transcript and a CRM opportunity record is a schema design problem. Define the fields, extract them from the transcript with typed criteria, validate the output, and write it to the CRM. Every source works. No rep data entry required.
Bricks and Kits: How to Build a Stable Evaluation Schema That Never Drifts
AI call evaluation drifts when the schema is implicit. Bricks are single evaluations with a fixed answer format. Kits group them into versioned schemas. Together, they produce call scores that are consistent across runs, comparable over time, and reliable enough for production reporting.
Sales Call Analysis APIs in 2026 for RevOps: Transcript Ingestion, Typed JSON, and CRM Integration
The best sales call analysis APIs in 2026 aren't the ones with the flashiest dashboard. They are the ones that turn transcripts into typed JSON fields that fit your scoring schema and land in CRM without glue. Here is how the leading options compare on the criteria that decide integration success.
Best Tools to Get Conversation Data Into Your Data Warehouse in 2026
To get conversation data into your data warehouse in a queryable form, you need the right tool at four layers: speaker-attributed transcription, customer-defined structured extraction, reliable orchestration, and a connector that writes typed fields with join keys. Here are the options that work in 2026, and who each one fits.
How to Vibe Code a Call QA Dashboard in an Afternoon
Manual QA review doesn't scale and its results aren't auditable. This guide shows how to turn scored call JSON into a call QA dashboard with filters, failed-check flags, and evidence quotes, built in an afternoon on top of the Semarize API output.
Conversation Intelligence Platform vs API-First: The Ownership, Integration, and Cost Decision
Conversation intelligence platform vs API-first is a decision about operating models, not features. Compare who owns the evaluation logic, how the output integrates, and what each model really costs before you sign, so the choice doesn't show up later as lock-in and surprise spend.
MEDDIC Without the Admin: Automated MEDDIC Scoring for Every Discovery Call
MEDDIC fields in CRM reflect what reps remember and choose to enter, not what buyers said. Automated MEDDIC scoring runs one typed Brick per element against the transcript, returns structured JSON, and writes qualification data back to the opportunity with no rep admin.
The 2026 Sales Call QA Stack That Actually Scales: AI Scoring, API-First Tools, and Auditable Results
A sales call QA stack limited by reviewer time can only sample. A stack with automated, auditable scoring covers every call and frees analysts to chase exceptions. Here is what each of the four layers needs to be, and which tools fit where.
Zoom Transcripts to CRM-Ready Sales Signals: An API-First Pipeline for Scoring and Field Extraction
Transcript access isn't the same as usable data. Here is how to turn Zoom transcripts into CRM-ready sales signals with an API-first pipeline: webhooks, scoring built around buyer understanding, and typed field extraction into CRM or BI.
Why Clean Conversation Inputs Matter More Than Your LLM Choice
Clean conversation inputs, the transcript structure, the evaluation schema, and the delivery, decide output quality more than your LLM choice. Swap in the best model and a messy transcript with vague criteria still produces inconsistent scores. Here is the order of operations that actually fixes it.
How to Get Conversation Intelligence From Zoom and Teams Without Buying Another Platform
Zoom and Teams already generate the transcripts you need. This guide shows how to get conversation intelligence from Zoom and Teams by routing those transcripts through an evaluation API, producing CRM enrichment, coaching signals, and QA coverage without adding a recording platform or paying per-seat for a duplicate transcript.
Symbl.ai Alternatives for Structured RevOps Data
A buyer's guide to Symbl.ai alternatives for teams that need deterministic, typed output rather than real-time summaries. Stay with Symbl.ai for live meeting intelligence; move to a structured API like Semarize when CRM enrichment, MEDDIC scoring, and RevOps automation need fields you can route, score, and audit.
The Best Conversation Intelligence APIs for Product Teams in 2026
A buyer's guide to the best conversation intelligence APIs for product teams in 2026. The category hides four jobs, recording, transcription, extraction, and real-time delivery, and the right pick depends on which one your product needs to own. Compare Semarize, AssemblyAI, Symbl.ai, Deepgram, and Recall.ai by fit.
Evaluate AI Agents at Scale With Structured Checks
To evaluate AI agents at scale you need a locked, deterministic evaluation schema grounded in your knowledge base, not a stronger judge prompt. Here is how typed checks score response relevance, instruction adherence, hallucination, tone, safety, and drift on 100% of conversations.
Automated Sales Call Scoring
Most automated call scoring measures whether reps followed a script. Script compliance isn't the same as buyer understanding, and the scorecard that improves while win rates stagnate is the clearest sign the rubric is measuring the wrong thing.
Gong API Alternatives for Structured Output
Most teams that struggle integrating Gong data into RevOps workflows describe it as an API problem. It is almost always a requirements problem. Before evaluating alternatives, write the exact JSON fields your downstream systems need and test vendors against that contract.
How to Build a Win/Loss Analysis Tracker Without a Developer
Win/loss surveys arrive too late and from too few buyers to be reliable. Structured signals from call transcripts give you coverage on every deal automatically. This is how to build the tracker using Make or n8n, with Semarize providing the scored call data.
What BI Teams Need From Conversation Data
Conversation intelligence platforms export data designed for human review. BI teams need typed fields, stable schema, and joinable keys for warehouse analytics. The gap between those two things is why conversation data almost never makes it into production reporting.
Conversation Intelligence API Evaluation Criteria for 2026
Most teams evaluate conversational intelligence on transcript quality and coaching UI. The evaluation criteria that actually matter for downstream automation and CRM enrichment are schema stability, webhook delivery, and JSON output quality, and almost nobody tests them before signing.
5 Ways to Automate MEDDIC Scoring Directly From Sales Calls
Automated MEDDIC scoring from sales call transcripts removes rep compliance and recall from the equation entirely. Here are five concrete approaches, from no-code Make and n8n flows to direct API integration and Salesforce Flow orchestration.
How to Turn Your Note-Taker Into a Serious Sales Enablement Source
Most sales teams have transcripts from every call they've ever recorded. Almost none of them are using that data for coaching analytics, CRM enrichment, or QA at scale. The gap isn't the recording - it's the extraction layer that turns transcripts into structured signals.
Conversational Intelligence API vs AI Note-Taker: What Changes?
AI note-takers produce prose summaries for humans to read. A conversational intelligence API produces structured data for systems to consume directly, and that difference determines what you can build.
Where Vibe Coding Actually Makes Sense for Internal Teams
AI coding has moved faster than most of the discourse around it. The question is no longer whether you can build with AI; it’s where to direct the effort, and the people best placed to answer that are the ones already closest to the problem.
Conversation Intelligence for Sales Enablement: Stop Measuring Deal Signals, Start Measuring Skill Lift
Most enablement teams measure the wrong thing. Deal signals tell you whether a deal progressed. Skill signals tell you whether a rep developed a capability. The two require different schemas, different measurement windows, and a different definition of what you are trying to prove. Here is how to design for skill lift specifically.
GTM Engineering in 2026: Revenue Data Engineering Explained
GTM engineering has matured on the workflow layer. The constraint has moved. Most teams building AI-augmented revenue pipelines are hitting a data problem: the conversation layer where deals actually progress is still unstructured, inconsistent, and inaccessible to the systems that need it. That is what revenue data engineering is for in 2026.
The Best APIs for Building Internal Sales Tools in 2026
The GTM engineering stack for internal sales tooling is well settled in 2026. Here is what each layer looks like, which tools are worth building around, and what RevOps and enablement teams are actually assembling from them.
Start Evaluating Agents the Way You Should Be Evaluating Humans
If you're running structured evaluation on every human rep conversation, your AI agent conversations should go through the same contract. Vendor metrics tell you how the agent performed against the vendor's model of a good interaction. Your evaluation standards are different. The same deterministic Kit you use for human reps applies directly to AI agent conversations: same schema, same grounded Bricks, same structured JSON output at 100% of production volume.
AI Call Scoring Is Theatre Without a Knowledge Layer
AI call scoring that runs on a good LLM with a well-written rubric can look accurate until you test it against what actually happened. The failure isn't one missing check. Every commercial dimension worth assessing has multiple facets, and each facet requires its own grounded document to evaluate properly. A knowledge layer is what makes scoring checkable across all of them rather than plausible about none of them.
Conversation Intelligence for Developers: Don't Build a Fragile Pipeline, Don't Buy a Black Box
Most teams don't fail to add conversation intelligence because the model is bad; they fail because the integration is fragile and unstructured. The fix isn't a better LLM pipeline or a platform API you can't control. It's a layer that takes a transcript, runs it against a versioned Kit, and returns deterministic typed JSON you can test, version, and route into your product.
Conversation Data Warehouse: Consistent Call Fields for BI
BI teams can't query transcripts. They can't join AI summaries to CRM objects. To make conversation data useful for analytics, it needs to arrive as consistent typed fields - booleans, scores, text fields, lists - with join keys that connect calls to opportunities, accounts, and contacts. This is the pipeline, the schema, and the governance model that makes sales call analytics possible in your warehouse.
100% QA Scoring Without Manual Review: Deterministic Rubrics for Every Call
Manual QA sampling at 2–5% has two problems: coverage and consistency. Automated scoring with deterministic rubrics solves both - every call gets scored the same way, with no reviewer required to generate the result. The shift isn't just efficiency - it changes what coaching is built from and turns compliance verification from sampling into complete coverage.
Conversation Intelligence Produces Signals, Not Workflows
CI vendors sell outcomes - better forecasts, improved coaching, higher win rates. The outcome claims are accurate for teams that wire CI signals into their downstream workflows. For teams that don't, the dashboards fill up and the outcomes don't move. The gap between running CI and seeing results is always an implementation gap, not a vendor gap.
Churn Risk Shows Up in CS Calls Before It Shows Up in Health Scores
Most churn detection models catch the consequences - usage drops, NPS decline, support spikes - after the customer has already started disengaging. The predictive signals are in CS call recordings: escalation language, stakeholder engagement changes, absent expansion mentions, deferred follow-through. Knowledge-grounded extraction turns these into signals calibrated to your definitions - making early intervention possible in a way generic extraction can't.
Stop Running Win/Loss Surveys. Start Capturing Deal Signals From Calls.
Win/loss surveys have a structural timing problem: they collect buyer memory after the outcome, not the decision inputs during the deal. Competitor mentions, pricing responses, and stakeholder dynamics exist in call recordings as they happen. Extracting them as structured signals makes win/loss real-time - and far more useful for deal coaching and pipeline risk.
Conversation Intelligence Isn't Enablement Analytics. Here's What Is.
Sales enablement teams buy conversation intelligence to measure coaching impact, then find the dashboards don't produce what they need: consistent rubric scoring, queryable time-series data, and before-and-after skill lift metrics. Visibility into calls and measurement of skill development are different problems - and most CI tools only solve the first one.
Capacity Planning Lags Because Sales Data Misses the Act of Selling
Sales capacity models built on CRM events are structurally late. Stage labels and activity counts record what happened to deals, not what was happening inside them. The missing ingredient isn't more pipeline data - it's structured signals from selling conversations that show whether buyers actually understood, committed, and progressed.
AI Scorecards Don't Disagree. Your Prompt Does.
Inconsistent AI scorecards aren't an AI problem - they're a process failure. Freeform prompts ask the model to re-interpret evaluation criteria on every run, and that interpretation drifts with phrasing, model updates, and context. The fix is an evaluation contract: a locked schema with defined output types that produces the same result on the same call, every time.
Introducing the Semarize MCP
Today we're shipping the Semarize MCP. Connect Claude, Codex, or any MCP-compatible AI tool to your workspace and build evaluation schemas from inside a conversation: create Bricks, draft Kits, attach knowledge bases, and publish, without leaving the tool you're already working in.
Why Conversation Intelligence Doesn't Drive Behavioural Change (and What Does)
Eighteen months into a CI implementation, many teams find that call scores have improved but win rates haven't moved. The data is there. The dashboards are running. The coaching is happening. What's missing is the step where insight becomes a different behaviour in the next conversation - and CI alone doesn't close that gap.
Gong Captures the Transcript. Here’s What It Can’t Score.
Gong’s scoring runs against a fixed model — you can’t attach your product documentation, rate card, or qualification playbook to its evaluation layer. For four evaluations that matter — product accuracy, pricing audit, methodology A/B testing, and deal readiness scoring — knowledge grounding and KB isolation are the only architecture that works.
Overhiring Is a Measurement Failure, Not a Hiring Strategy
Sales teams don't overhire because of poor judgment. They overhire because CRM-driven capacity models are built on stage labels and activity counts - data that can't reveal whether buyers are actually progressing. By the time deal reality becomes visible, headcount decisions have already been made.
MEDDICC Scoring From Discovery Calls
Most MEDDICC data is stale before it reaches CRM. Reps update fields from memory after the call, introducing timing gaps and sampling bias that make qualification scores unreliable. Extracting MEDDICC signals directly from transcripts fixes the data freshness problem that better training never will.
CRM Enrichment From Sales Calls: The RevOps Data Ops Playbook
Most CRM enrichment stalls at 30% field coverage because the output is unstructured - reps updating from memory, summaries stored as notes. The fix is a structured extraction pipeline: transcript to consistent fields to CRM to automation triggers. This playbook covers the schema, the routing, and the implementation in Salesforce and HubSpot.
What Conversation Intelligence Is Missing
Most teams already have conversation data. The problem isn't volume - it's that transcripts sitting in Zoom Cloud or a shared Drive folder are locked in text no system in your stack can read. Semarize turns what was said into structured JSON your CRM, BI, and automations can consume directly.
Conversation Intelligence Doesn't Fail on Calls. It Fails on Knowledge.
Early CI tools were built on ML classifiers - talk ratios, question counts, keyword detection. LLMs changed what's possible. But they introduced a new risk: model knowledge. When scoring runs against what the AI infers from training rather than your pricing, ICP criteria, and qualification playbooks, outputs are plausible and wrong.
AI scorecards are theatre unless they measure customer understanding
Most AI call scorecards measure what the rep did - agenda set, questions asked, next step mentioned. That's measuring inputs. What actually matters is whether the buyer understood anything. The two are not the same thing, and the gap between them is where scorecard theatre lives.
Bricks and Kits: the mechanism for stable conversation evaluation
Freeform prompts produce inconsistent evaluation results - scores drift, output shapes change, and you can't tell whether coaching improved anything or whether the rubric moved. Bricks define a locked evaluation schema: one question, one output type. Kits group them into reusable evaluation workflows. The result is schema-stable conversation analysis you control.
Sales is human. Sales data is not.
CRM data captures events - stage changes, activity counts, timestamps. It doesn't capture the human act of selling. The evidence that explains why deals move or stall lives in conversations, not in fields a rep updated.
What is a Conversational Intelligence API?
Conversational intelligence gets applied to three very different things - deal intelligence, note-taking, and pattern-level analysis. Only one produces data your systems can act on. Here's what a CI API actually does and how the shift away from full-platform solutions is changing what's possible.
Why I Built Semarize
It's about time we looked at our conversations through a more scientific lens - This is why I've built Semarize, what it's for and what I want it to help people do.