Once you're in — yes. Text or call anytime. Access itself is application-reviewed, not self-serve overnight.

Will my manager see what I tell Sara?

No. Sara reports to you. Nothing goes up the org chart unless you choose to share it.

Does she record my customer calls?

Never. No bot in the meeting. You reach out after — by text or call.

How is this different from Gong or Chorus?

Gong owns the recorded call — for your manager. Sara owns what happens after you hang up — for you.

What is a lead qualification framework?

A set of fields — usually budget, authority, need, and timeline, or a named variant — each scored and weighted, then summed into one number that decides whether a lead moves forward. The framework is the scoring structure; MEDDIC, BANT, and CHAMP are named versions of it.

How is a lead qualification framework different from a qualification checklist?

A checklist is the questions themselves, run once. A framework is what happens after: turning the answers into weighted points and adding them into a single score. The score is what gets forwarded to the next stage — the individual answers rarely travel with it.

Why doesn't a high lead score guarantee a good lead?

Because the score only reflects how the rep filled in each field, not whether the rep believed the answer while typing it. A rep who wants the lead rounds every ambiguous field up; a skeptical rep rounds the same fields down. The framework can't tell the two apart — it just adds whatever it's given.

FIELD NOTES

Lead Qualification Framework: The Score Justifies a Decision Already Made

A lead qualification framework turns three or four fields into one score. The score doesn't decide anything — it just gives a decision the rep already made somewhere official to live.

2026-09-14 · SARA — KEEL'S AI DEAL ASSISTANT · GETKEEL.IO

Three fields. Budget, authority, timeline.

The rep fills in all three. Lead score: 82.

Nobody asks whether the rep believed the answers while typing them.

What a framework actually scores

Not intent. Not fit.

Whichever fields the rep chose to fill in, weighted by whoever built the framework.

A framework built from four fields can only ever be as honest as the field the rep was most tempted to round up. Budget usually wins that title — "yes, they have budget" is the one answer nobody wants to be the reason a lead gets shelved.

The number that isn't a decision

An 82 doesn't feel like an opinion. It reads like a fact the fields discovered on their own.

But someone wrote the weights first. Budget worth 30 points, authority worth 25, timeline worth 20 — a judgment call a person made once, that a tool now applies for them every time. The score just launders that judgment into arithmetic.

MEDDIC questions makes the same point about a single letter in a named framework — every question has a fillable version and an honest version, and both produce the same checkmark. A framework's total score inherits that exact split. It just hides it behind a number instead of a checkbox.

What the framework is actually for

Not deciding whether to work the lead. Justifying the decision the rep had already half-made by the third field.

A rep who wants the lead fills in the generous version of every ambiguous answer. A rep who's already skeptical fills in the strict version of the same fields. The framework doesn't catch either one.

It just gives whichever read the rep started with somewhere official to sit.

Sales qualification process covers the same mechanism one stage later — every named process runs its checklist once, at intake, and never re-asks. A framework is the intake version of that same one-time trust, just compressed into a single number instead of a set of boxes.

Where the honest read actually happens

Before the fields get filled in. Whatever the rep actually thinks about the lead — said out loud or typed somewhere private — before it gets rounded into three checkboxes and a score.

Lead qualification checklist argues for re-running the checklist instead of trusting the first pass. The earlier fix is simpler: keep the rep's actual, unrounded read on record somewhere the framework can't flatten it, so the private version survives past the moment it gets converted into a number.

Where Sara sits

Sara's built to hold onto the rep's actual read on a lead — the version that exists before it gets rounded into a framework's checkboxes — so the private assessment survives past the moment someone needs an official score. Founders Club is invite-reviewed: apply at getkeel.io/founders.

The 82 that was actually a 40

A rep scored a lead 82: budget confirmed, authority present, timeline inside quarter.

Two weeks later, the same rep admitted the "confirmed" budget was a guess based on company size. The "authority" contact had said he'd loop someone else in. The timeline was the prospect's date, not an internal one.

The framework had reported 82 the entire time. Ask the rep directly, and their real number had been closer to 40 since the first call.

By the team at Keel. We're building Sara, an AI deal assistant for the moments that don't get recorded.

MORE IN THIS SERIES

Sales Qualification Process: Every Framework Checks Once, Never Again

BANT, MEDDIC, CHAMP — every sales qualification process runs the same checklist once. None of them re-check it after a deal stops looking qualified.

Lead Qualification Questions: The Answer Matters Less Than How Fast It Came

Most lead qualification questions test what a prospect knows. The one that predicts a close is whether they had to check with someone else first.

Lead Qualification Checklist: The Kind You Run More Than Once

Most lead qualification checklists get run once, at intake, and never again. Half the answers are stale by the time the deal reaches a forecast call.