Ben Franklin Close: Examples, Script, and When to Use It

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

The Ben Franklin close is a closing technique where you and the buyer list the reasons to buy in one column and the reasons not to buy in another, then weigh them together. It works best when a buyer says "I'm on the fence." The visible list replaces vague worry with specific points you can address, and the buyer reaches the conclusion on their own.

You've probably heard this one from a buyer: "I like it, but I need to think about it." That sentence usually hides a swirl of half-formed concerns. They can't tell you what's wrong because they haven't sorted it out themselves. The Ben Franklin close gives them a way to sort it, with you sitting next to them rather than across the table.

This guide covers where the technique comes from, how it compares to other closes, a step-by-step method, a copy-ready script and worksheet, examples by deal type, and the situations where you should leave it in the drawer.

Where the Ben Franklin Close Comes From

The name points to a real letter. On September 19, 1772, Benjamin Franklin wrote from London to the scientist Joseph Priestley about a difficult decision. Franklin declined to tell him what to do. He offered a method instead: divide a sheet of paper into two columns with a line, put the reasons for on one side and the reasons against on the other, and add to the lists over several days as new points occur to you.

Then comes the part salespeople tend to skip. Franklin weighed the reasons against each other. When he found one reason on each side that seemed equal, he struck both out. When one reason on one side matched two on the other, he struck out all three. He kept going until he could see where the balance lay. He gave the whole approach a name: "Moral or Prudential Algebra". The point was clearer thinking, not mathematical precision.

In sales, the method became known as the Ben Franklin close. Notice what the sales version kept and what they often drop. The original is a private reasoning tool you use over days. The sales version is a shared, compressed exercise done in one conversation. That difference matters, and we'll come back to it, because it's where the technique either feels respectful or feels like a trap.

What Makes It Different From Other Closes

Most closing techniques push the buyer toward a yes. The Ben Franklin close slows the conversation down and puts the evidence on the table. It's less a "close" than a structured decision aid, which is why it fits complex, considered purchases better than impulse ones.

Here's how it compares with the closes buyers and reps hear most often.

Technique Core move Best moment Main risk
Ben Franklin close List pros and cons together, weigh them, address the cons Buyer is undecided and can't name why Slow; exposes cons you haven't prepared for
Assumptive close Talk as if the decision is made, discuss logistics Strong buying signals, aligned stakeholders Feels pushy if concerns are unresolved
Alternative choice close Offer two "yes" options (plan A or plan B) Buyer is ready but needs help choosing a package Hides a "no" option; can feel manipulative
Summary close Recap agreed benefits, then ask for the decision Buyer has agreed to several value points Long recaps lose attention
Takeaway close Withdraw or limit an offer to test commitment Buyer is wavering on a real, limited offer Fake scarcity destroys trust
Puppy dog close Let the buyer try before committing Product is easy to trial Trial users who never activate
Trial close Ask a low-stakes question to test readiness Anywhere in the sales process Misreading a polite answer as commitment

Two things stand out. First, the Ben Franklin close is the only one in the list that deliberately invites the buyer to say negative things out loud. Second, it's the most honest about uncertainty. If the cons win, the list shows that, and you learn it before wasting three more weeks on a deal that was never going to close.

Why a Written Pros-and-Cons List Helps Buyers Decide

Undecided buyers aren't usually short on information. They're overloaded and unsure which concerns matter. A list helps in three practical ways.

It turns a fog into items. "I'm just not sure" becomes "implementation takes our team's time in Q4" and "we'd lose our old reporting." Items can be solved. Fog can't.

It shows the real weights. Buyers often discover that the one worry they keep circling back to is outweighed by four benefits they'd stopped noticing. Or they discover the opposite, which is useful to both of you.

It shifts ownership. When the buyer generates the reasons, they believe them. People tend to trust conclusions they helped build more than conclusions handed to them. If you want the longer reading on why, see our guide to closing psychology.

When to Use the Ben Franklin Close

Use it when the situation matches these conditions:

  • The buyer says some version of "I need to think about it" or "I'm torn."
  • You've covered the main value and the buyer isn't hostile, just unsure.
  • The decision is considered, such as a multi-month contract, a platform switch, or a hiring decision on your own side that affects their team.
  • You can name at least a few real benefits, and you're prepared to hear real objections.
  • You have 15 to 20 minutes and the buyer has time to engage.

Skip it when the buyer is clearly ready to sign (it adds friction), when the deal is tiny (a worksheet is overkill for a $40 monthly tool), when you suspect the cons list will be longer than the pros and you have no honest answer, and when a hidden stakeholder is the real blocker. In that last case, the exercise just produces a tidy list that the missing person ignores. Start with stakeholder alignment instead.

How to Run the Ben Franklin Close, Step by Step

This is the working method. Total time is roughly 15 to 20 minutes on a call or in a meeting.

Step 1: Name the situation and ask permission

Say what you're hearing, and propose a way forward. "It sounds like you see real value but a few things are holding you back. Would it help if we put it all on one page and looked at it together?" Wait for a yes. If the buyer declines, don't force it. Move to a different approach, such as a trial close to find out what's really going on.

Step 2: Draw two columns

Use a shared screen, whiteboard, or a plain document. Label the left column "Reasons to move forward" and the right column "Reasons to hold off." Neutral labels matter. "Pros and cons" is fine, but "Reasons to buy" and "Reasons not to buy" can sound loaded.

Step 3: Let the buyer fill the first column

Ask: "What would be the best outcomes if this works?" Write their words, not yours. If they struggle, prompt with things they said earlier: "You mentioned reporting takes a full day each month. Should that go on the list?" Aim for four to six items.

Step 4: Fill the second column honestly

Ask: "And what worries you or makes you hesitate?" Then stay quiet. This is the hard part. Don't defend, interrupt, or reframe. Write every concern down, including price, timing, risk, change fatigue, and "my boss isn't convinced." If the buyer stops at two items, ask "What else?" once. Real concerns often arrive on the second ask.

Step 5: Add anything the buyer missed, openly

If you know of a real benefit they didn't list, such as a faster onboarding path or a contract term, offer it: "Can I add one I think matters?" If you know of a real downside they missed, say so too. A seller who volunteers a con earns a lot of credibility. This is also where an existing business case pays off, because you can drop its numbers straight into the left column.

Step 6: Weigh and cancel, Franklin style

Now do what Franklin did. Go through the lists and ask which items offset each other. "You listed 'takes team time to set up' and 'saves 10 hours a week afterward.' How do those compare?" Strike out pairs that balance. Ask the buyer to rank what's left by importance. You aren't doing arithmetic, you're helping them see what remains.

Step 7: Solve the remaining cons

Pick the heaviest remaining con and work on it. Some can be solved ("Let's put a phased rollout in the plan"), some can be reduced ("Here's how customers usually handle that"), and some are real and stay. Use your objection handling framework for the common ones. Cross off what you resolve, in front of the buyer.

Step 8: Ask which way the balance leans

Don't announce a conclusion. Ask: "Looking at the page, where do you land?" If the balance favors moving forward, ask for the next step. If it doesn't, ask what would need to change, or agree on a clear point to revisit. Either answer is progress.

Step 9: Capture and send the page

Send the list afterward in a short follow-up. It becomes a record the buyer can show their boss, which helps if the decision needs internal approval from people who weren't on the call.

Ben Franklin Close Script You Can Copy

Adapt the wording to your own voice. These are the lines, in order.

Stage Script line Purpose
Open "It sounds like there's real value here, but something's keeping you from a clear yes. Want to put it all on one page and look at it together?" Gets permission, lowers pressure
Frame "I'll draw two columns. Reasons to move forward on the left, reasons to hold off on the right. I'll write what you say." Sets the structure
Pros "If this works the way you hope, what changes for your team?" Buyer states benefits in their own words
Cons "And what makes you hesitate? Anything counts, big or small." Surfaces concerns without defense
Prompt "What else? Sometimes the real one comes last." Gets the hidden objection
Add "Can I add two I think belong here?" Contributes honestly to both sides
Cancel "These two seem to offset each other. Do you agree, or does one weigh more?" Weighs reasons, Franklin style
Solve "Of what's left, which one worries you most? Let's see if we can fix it." Targets the real blocker
Decide "Looking at the page, where do you land?" Lets the buyer conclude
Next step "Then the next step is [action]. Does Thursday work, or would Friday be better?" Moves forward without pressure

Pros-and-Cons Worksheet Template

Copy this into a shared document before the call. Fill it live with the buyer. The "Weight" column uses a 1 to 3 scale chosen by the buyer, where 3 means "matters a lot."

Reasons to move forward Weight (1-3) Reasons to hold off Weight (1-3) Action to resolve Owner
(buyer's words) (buyer's words)
(buyer's words) (buyer's words)
(buyer's words) (buyer's words)
(buyer's words) (buyer's words)
(added by seller, with permission) (added by seller, with permission)

Below the table, add three lines:

  • Items struck out as offsetting: ______
  • Heaviest remaining concern: ______
  • Buyer's conclusion and agreed next step: ______

Examples by Deal Type

These scenarios are illustrative, written to show the pattern rather than describe real customers or results.

Example 1: Mid-market software renewal

A finance director is reviewing a renewal for a reporting platform. She likes it but says the budget is tight.

The list she builds: Pros are "monthly close is two days faster," "auditors like the trail," and "team already knows it." Cons are "cost is up this year" and "we might consolidate tools."

The rep suggests striking "cost is up" against "two days faster at close," asks her to estimate what those two days are worth, and offers to review the ROI calculation with her. The tool-consolidation concern stays, so they agree to map which features the other tool would need to replace. The outcome isn't a forced yes. It's a specific, dated next step.

Example 2: New-logo enterprise deal

A VP of operations wants to switch vendors but fears disrupting a busy quarter. The rep uses a shared screen and the worksheet.

Cons: "migration risk," "training time in Q4," "IT bandwidth." The rep handles each separately: a phased rollout starting in January, vendor-led data migration, and a named IT contact. Two cons remain after the discussion. The VP says the January start makes the Q4 worry disappear, and the call ends with a kickoff date.

Example 3: Small business owner, services contract

A salon owner is considering an annual booking and payments contract. She says, "I'm not sure it's worth it."

The rep keeps it simple: a four-line list, no weights. She names "fewer no-shows" and "less time on the phone." The con is "I've never used software for this." They strike "never used software" against a free setup call. She books the call. Simple deals need a simple version of the technique.

Handling the Most Common Cons

Certain concerns show up on almost every list. Here's how to respond to each without turning the list into a debate.

Con the buyer lists Honest response approach What to avoid
"It's too expensive" Tie cost to a number the buyer owns; offer phased scope Discounting before understanding the gap
"Not the right time" Ask what has to be true for timing to work; propose a later start date Inventing urgency
"Takes too much effort to switch" Break the switch into small steps with owners Minimizing real work
"My team won't adopt it" Offer a pilot group or training plan Promising adoption you can't control
"I'm not the only decision-maker" Add the other person to the next meeting Going around the buyer
"Competitor X is also in the running" Ask which criteria matter most and compare on those Attacking the competitor

If a con is real and you can't fix it, say so. A list that ends with "this isn't a fit right now" is a success, because you've protected a relationship and saved a failed implementation.

Do's and Don'ts

Do Don't
Ask permission before starting Spring the worksheet on a buyer who wants to leave
Write the buyer's words, not your paraphrase Rewrite their concerns into softer language
Let silence work after asking for cons Rush to defend after each item
Volunteer a real downside Hide a con you know matters
Strike out offsetting items together Cross out items without the buyer's agreement
Keep it to one page and one conversation Stretch it into a multi-meeting ordeal
Send the list afterward as a record Use the list as leverage later
Accept a "no" or "not yet" that the list supports Argue with a conclusion the buyer reached

When the Ben Franklin Close Backfires

A few failure patterns are worth knowing.

The loaded list. If you fill the pro column with ten items and the con column with one, the buyer sees what you're doing. It reads as manipulation. Keep the balance honest.

The wrong decision-maker. A single contact who can't sign will produce a clean list that dies in committee. If you suspect that, check whether the person in the room has authority, and map who else shapes the decision before you run the exercise again.

Ethics: Keeping the Technique Honest

The Ben Franklin close is one of the more ethical closing techniques because the buyer does the reasoning. You can keep it that way with a few rules:

  1. The buyer authors the list. You contribute only with permission.
  2. You never remove a concern the buyer cares about because it's inconvenient.
  3. The weights belong to the buyer, not to you.
  4. If the balance favors waiting, you honor it.
  5. The page you send afterward matches the page you built together.

If you're building a wider approach to closing, our closing strategy overview shows where a decision-aid technique fits alongside tools that push for commitment.

Key Facts

  • What it is: a closing technique that lists reasons to move forward and reasons to hold off, then weighs them with the buyer.
  • Origin: a letter Benjamin Franklin wrote to Joseph Priestley on September 19, 1772, describing what he called Moral or Prudential Algebra.
  • Franklin's core move: strike out reasons that offset each other until you can see where the balance lies.
  • Best fit: considered purchases where the buyer is undecided and can't say why.
  • Poor fit: ready buyers, tiny deals, and situations where the real blocker is a missing stakeholder.
  • Time needed: about 15 to 20 minutes.
  • Rule of thumb: the buyer writes the list, you contribute with permission, and you honor the result.

Ben Franklin Close FAQ

What is the Ben Franklin close?

It's a closing technique where you and the buyer list reasons to move forward and reasons to hold off, then weigh them together. It works best with undecided buyers, because it turns vague hesitation into specific points you can discuss and solve.

Where does the Ben Franklin close come from?

It's based on a letter Benjamin Franklin wrote to Joseph Priestley on September 19, 1772, describing a pros-and-cons method he called Moral or Prudential Algebra. Sales trainers adapted it into a shared, one-conversation closing exercise.

What's the difference between the Ben Franklin close and a summary close?

A summary close has the seller recap benefits and ask for a decision. The Ben Franklin close has the buyer build both columns, including the downsides, so the buyer reaches the conclusion rather than hearing it.

Is the Ben Franklin close manipulative?

It isn't if you keep it honest. The buyer writes the list, you add points only with permission, and you accept the result even if it favors waiting. It becomes manipulative when you stack one column, hide known downsides, or push the buyer to a conclusion.

When should you not use the Ben Franklin close?

Skip it when the buyer is ready to sign, when the deal is too small for a worksheet, when you have no honest answer to the likely cons, or when the real blocker is a stakeholder who isn't in the room.

How long does a Ben Franklin close take?

Usually 15 to 20 minutes on a call or in a meeting. Keep it to one page and one conversation, and send the completed list as a short follow-up so the buyer can share it with other decision-makers.


Learn More

About the author

Calvin D.

Calvin D.

Head of Enterprise Solutions

Calvin D. is Head of Enterprise Solutions at Rework, writing for sales directors and CROs. Calvin covers how B2B companies choose and implement software, buy SaaS, migrate data, and run the sales process, plus deal closing and pipeline management, with a focus on decisions that still hold up as the sales organization grows.