The SE Loop — Rebuilding Certainty, Not Just Answering
Feel‑Felt‑Found handles the words in an objection. This handles what the objection actually signals about three certainties, borrowed — carefully — from Jordan Belfort's looping technique.
An objection answered and left behind is a coin flip: sometimes the room moves on convinced, sometimes it moves on because nobody wanted to push further, and the doubt just goes quiet instead of resolving. Jordan Belfort's "looping" technique, adapted here for a discipline built on honesty rather than pressure, treats an objection as a signal that certainty has dropped in one or more of three places at once — not just in the specific feature being questioned.
The three certainties
| Certainty | What the buyer is actually checking |
|---|---|
| The product | Does its design hold together, and will it actually produce the outcome |
| The salesperson | Does this specific person have relevant experience worth trusting |
| The company | Is this vendor a credible fit for a customer shaped like them |
A question like "don't we lose control of our own codebase?" sounds like a single product objection. It's rarely only that — it's a buyer checking whether the design decision is sound, whether you understand why it was made, and whether a company like yours has actually shipped this for a customer like them. Answer only the literal feature question and two of the three certainties stay exactly where they were.
The five‑step loop
- Probe — one clarifying question before answering anything: "what would your team actually need codebase access for?"
- Validate — acknowledge the concern is reasonable, without conceding the point: "that's completely fair to flag"
- Answer honestly — name the real trade‑off. A technical buyer can smell a dodge from three time zones away, and a caught dodge costs more certainty than the trade‑off itself ever would
- Rebuild certainty — spend fifteen to twenty seconds deliberately withdrawing from the certainty bank below, rather than moving straight past the objection
- Return to the demo — resume flow only once the doubt has actually been addressed, not once you've stopped talking about it
Prepare the withdrawal before you need it: the 3×3
The certainty bank isn't improvised live — it's nine lines, prepared before the call and held in reserve for exactly this moment rather than narrated as part of the planned demo flow:
A worked example: a hospital‑network developer's "no codebase control?" objection, handled in sixty to ninety seconds by probing what access was actually needed for, validating that their development model made the question reasonable, naming the trade‑off as intentional and explaining why, then rebuilding certainty with one customer pain point that matched theirs, one personal experience with a similarly regulated team, and one sentence on the company's philosophy toward exactly this trade‑off.