Day 16: Write a Sales Script and Objection Handler

The Point Of Today

Founder-led sales is not about becoming slick.

It is about becoming useful in a conversation where the buyer is trying to decide whether a problem is worth solving now, whether your approach is credible, and whether the next step is worth their time. A good sales call is not a performance. It is a structured conversation.

Many entrepreneurs make the same mistake on early calls: they explain too much too soon. They are proud of the product, nervous about silence, and eager to prove value. So they pitch before the buyer has described the problem in their own words.

Today you will build a script that keeps discovery at the center. The goal is not to read from it word for word. The goal is to create a reliable structure you can internalize.

Discovery Is The Sale

Discovery is not a warm-up before the real pitch.

Discovery is where the buyer discovers whether the problem matters enough to act. If you ask thoughtful questions, the buyer starts connecting their own pain, cost, urgency, and desired outcome. That is more persuasive than any feature explanation.

Strong discovery questions are open and specific:

• "Walk me through how this works today."
• "Where does it usually break down?"
• "What happens when it breaks?"
• "Who else is affected?"
• "How are you measuring this today?"
• "What have you already tried?"
• "Why is this a priority now?"
• "What would need to change for this to be worth solving?"

Avoid leading questions like, "Wouldn't it save time if you had an automated system?" That teaches you very little. The buyer can agree politely without feeling real urgency.

Present Only After You Understand

A good demo is selective.

Once you understand the buyer's priorities, show only the parts of the product that connect to those priorities. A full tour often weakens the sale because it distracts from the problem that matters.

A simple presentation structure works:

1. Reflect the buyer's situation.
2. Name the cost or risk of the current approach.
3. Show the product workflow that addresses that specific issue.
4. Explain the outcome.
5. Ask whether that maps to how they would use it.

This keeps the buyer engaged. It also gives you immediate feedback. If the workflow does not map to their reality, you learn that while still in conversation.

Objections Are Diagnostic Signals

An objection is not always a no.

It is often a request for clarity. "It is too expensive" might mean the buyer does not understand value, lacks budget, compares you to a cheaper alternative, doubts implementation, or is not the right fit. If you respond before diagnosing, you may answer the wrong concern.

Use a calm question first:

"When you say expensive, are you comparing it to budget, another option, or confidence in the outcome?"

For timing:

"What would need to happen for this to become a priority?"

For an existing solution:

"What is working well with the current approach, and where does it still create friction?"

For "I need to think about it":

"Of course. What part feels unresolved right now?"

These questions keep the conversation honest. They also prevent the founder from discounting, over-explaining, or chasing a deal that was never real.

End With A Committed Next Step

Sales calls often die because they end vaguely.

"I will send over more information" is not a next step. "Let me know what you think" is not a next step. A committed next step includes an action, owner, and date.

Examples:

• "I will send the proposal by Thursday. Can we review it together Friday at 2?"
• "You will confirm the implementation owner by Monday, and I will send the onboarding plan today."
• "Let us run the pilot with one team for two weeks and review results on the 15th."

If the buyer avoids committing, that is useful information. It may mean they are not convinced, not the decision-maker, not urgent, or not a fit.

Listen For Buying Intent

Buying intent often appears before the buyer says yes.

Green flags include:

• Asking about implementation.
• Asking who needs to be involved.
• Discussing budget timing.
• Comparing you to a specific alternative.
• Asking what happens after signing.
• Sharing internal constraints.
• Using language like "when" instead of "if."

When these signals appear, slow down. Ask a follow-up question. Do not rush past intent because you are trying to finish the script.

Today's Practice

Run the prompt and edit the script until it sounds like you.

Before your next call, write the discovery questions on a note. During the call, aim to listen more than you speak. After the call, review three things:

• Did the buyer describe a real problem?
• Did you connect the demo to their priorities?
• Did the call end with a committed next step?

Founder sales improves through repetition. The script is not there to make you robotic. It is there to keep you calm enough to listen.