HAVE A REASON
TO BE THERE.
Pick one account. Write one thing about their business that gives you a reason to reach out. If the line could go to every company on your list, keep looking.
You don’t need a robot pretending to be you. You need more time for the work only you can do. Let’s talk about the calls, the follow-up, the content—and the small jobs AI can earn.
Start with the lessons ↓I want AI to take something off your plate. The follow-up you forgot. The notes you still haven’t put in the CRM. The customer question somebody has answered twelve times this week.
Here’s where I’d start: one inquiry, one named owner, one next step. Run it all the way through before you buy the next shiny thing.
— STEVE SCHMIDTPick one account. Write one thing about their business that gives you a reason to reach out. If the line could go to every company on your list, keep looking.
Ask what made the problem worth discussing now. Follow the answer. A useful conversation starts when you stop racing to the next question on your list.
Before you hang up, agree who does what next and when. In your follow-up, show what you heard and what you agreed. Give the other person something useful to respond to.
NOT EVERY GOOD CONVERSATION
NEEDS TO END IN A PITCH.
There’s no sales course or coaching package for sale here. Read something. Try it. Tell me what happened.
Keep the conversation going on LinkedIn ↗Questions worth asking about your sales, your customers, and what actually happened after the click.

You’re open. But on a customer’s phone, your business looks like a place that used to exist. Time for the stranger test.
Read the article ↗A front door in Sioux Falls. A new way to solve an old problem. And what an owner can show before a customer calls.
Read the illustrated story ↗Tell me what you’re working on, what you’ve tried, and where it gets stuck. It might be the question somebody else needs answered, too.
Start with a task you understand. Give AI accurate inputs. Check the result. Measure whether the whole job got easier—including the corrections. These are practical starting points from Steve Schmidt, not promises of a particular outcome.
Give it your own notes from one real customer question. Ask for three outlines, choose one, and write the opening yourself. Check every claim. Publish the useful answer even when there is no product mention.
Steve Schmidt · Practical field noteAnswer something a buyer asked this week. Explain one decision, show one example you have permission to share, and give the reader a next step they can try. Keep customer identities and deal details private unless cleared.
Steve Schmidt · Practical field noteRemove confidential details. Pull out the buyer’s question, the mistaken assumption, and the test that clarified it. Those are three different posts. AI can help organize them; it should not invent dialogue or the outcome.
Steve Schmidt · Practical field noteRecord which posts start relevant conversations. Ask new contacts what brought them in and save the answer in your CRM. Review those conversations alongside opportunities. Impressions alone do not show that a post produced a deal.
Steve Schmidt · Practical field noteChoose a schedule you can sustain without recycling empty advice. Start with one substantive post and time to answer comments each week. Add frequency when you have useful material. Track consistency and relevant replies before increasing output.
Steve Schmidt · Practical field noteStart with public business information you are allowed to use. Ask AI to summarize the company’s offering and list questions your research has not answered. Verify the summary against the company’s own site before making it part of an outreach message.
Steve Schmidt · Practical field noteA recognizable reason to connect. Mention the professional context you actually share or the specific work that prompted the request. Keep the first contact proportionate to the relationship. A connection acceptance is not permission for a canned pitch sequence.
Steve Schmidt · Practical field noteName the reason you reached out, then ask one question the person can answer without doing homework. Leave out invented compliments. Read the message aloud: if you would not say it to a person at an event, rewrite it.
Steve Schmidt · Practical field noteLinkedIn prohibits unauthorized tools that automate activity or scrape its service. Use approved platform capabilities and keep a person responsible for the conversation. A tool being commercially available does not establish that LinkedIn allows it.
Steve Schmidt · Practical field noteTrack relevant connections, two-way conversations, agreed next steps, and opportunities separately. Log the source and date. Each week, read a small sample of the conversations to see why people responded; a count of messages sent cannot explain that.
Steve Schmidt · Practical field noteAsk it to organize verified company facts and suggest three discovery questions. Practice the opening out loud. Keep the facts and questions beside you, rather than reading a generated speech. The buyer should hear a person listening.
Steve Schmidt · Practical field noteIdentify yourself and explain why you called that business. Keep the reason specific enough to test in a conversation. Ask a short question and pause. Do not pretend a stranger requested the call or that you have spoken before.
Steve Schmidt · Practical field noteRespect the answer. When appropriate, ask one brief clarifying question about fit or timing; do not turn a refusal into an argument. Record the reason and honor a request not to be contacted again.
Steve Schmidt · Practical field noteSeparate attempts, connections, substantive conversations, agreed next steps, and completed meetings. Review the list and the opening when connections turn into few conversations. Review fit and follow-through when conversations turn into few completed meetings.
Steve Schmidt · Practical field noteHave the campaign reviewed for the rules that apply to its audience, locations, calling method, and recording practices. Maintain suppression requests. The FTC’s telemarketing guidance is a starting resource, not a complete determination of every federal and state obligation.
Steve Schmidt · Practical field noteSupply a verified business fact and your actual reason for contacting the recipient. Ask for a short draft using only those inputs. Delete any sentence that implies personal knowledge you do not have. Verify the recipient and company before sending.
Steve Schmidt · Practical field noteA truthful subject, a clear identity, a relevant reason to write, and one reasonable question. Commercial email also needs the disclosures and opt-out handling required by applicable rules. Read the FTC’s CAN-SPAM guide before building a campaign.
Steve Schmidt · Practical field noteThere is no useful universal number. Agree on a limited sequence and stop conditions before sending. Make each follow-up add context or value, honor opt-outs, and review negative replies. More touches will not fix a list with poor fit.
Steve Schmidt · Practical field noteStart with delivery, replies, qualified conversations, and completed next steps. Review bounces and opt-outs separately. Open tracking can be affected by privacy features and automated activity, so an open rate is not a count of interested buyers.
Steve Schmidt · Practical field noteYes. The FTC states that its commercial-email rules do not make a B2B exception. Use its compliance guide for identity, subject lines, address, opt-out, and other requirements. Other jurisdictions and your email provider may impose additional rules.
Steve Schmidt · Practical field noteStart with one task: summarize approved notes, flag records without next steps, or draft a follow-up for review. Confirm the tool is permitted to access that data. Test the output against the original record before enabling any automatic updates.
Steve Schmidt · Practical field noteThe customer’s stated problem, the people involved, the current stage, a named owner, and the next agreed action with a date. Add source and value when known. Leave unknown fields unknown instead of letting AI fill them with guesses.
Steve Schmidt · Practical field noteExport a backup through the system’s supported process. Review duplicates, inactive opportunities, missing owners, and missing next actions in separate passes. Confirm merge rules before applying them. Start with a small sample and verify that notes and history survive.
Steve Schmidt · Practical field noteOnly use an automation when you can define the evidence required for a stage change and review mistakes. A positive-sounding email does not equal an agreed deal. Begin with suggested changes and an approval step.
Steve Schmidt · Practical field noteOpen opportunities by next action and age. Ask what the buyer agreed, what changed, who owns the next move, and whether the record still belongs in the forecast. Close the loop on last week’s commitments before adding new activity.
Steve Schmidt · Practical field noteChoose one repetitive task you already understand. Time it, write down what a good result looks like, and test AI on a non-sensitive example. Keep it if the total time—including corrections—improves and the result holds up.
Steve Schmidt · Practical field noteTry: “Using only these verified company notes, list three possible business questions. Mark assumptions as assumptions. Do not invent budget, buying intent, or personal details.” Then choose the questions that actually fit the conversation.
Steve Schmidt · Practical field noteDo not give it authority to invent pricing, discounts, delivery dates, contractual terms, or product capabilities. Supply approved information and escalation rules. Anything outside those bounds goes to a person who can make the commitment.
Steve Schmidt · Practical field notePick one workflow and compare time spent, corrections needed, and completed buyer next steps before and during a small trial. Include subscription and setup costs. A larger activity count is useful only if it helps the work you are trying to finish.
Steve Schmidt · Practical field noteUse AI to prepare, organize, and draft. Keep responsibility for what gets said and sent. Read the original customer message, check the facts, and answer the actual concern. Someone should be able to challenge the output and get a human response.
Steve Schmidt · Practical field note