# Founder-led sales calls: a structure A six-part structure for a first sales call run by a technical founder, a note template, and what the U.S. wiretap statute says about recording. Canonical URL: https://worldenterprise.org/insights/founder-led-sales-calls-a-structure/ Last updated: 2026-10-10 Publisher: World Enterprise, run by World Enterprise Group Incorporated If you are the only person building the product, you are also the person on the first sales calls. Engineers often treat those calls as a presentation problem: show the product, answer questions, hope for a yes. A better model is a protocol with defined inputs and outputs. Before the call you know what you need to learn, during the call you collect it in a fixed order, and afterward you write down what happened so that the next call starts from data. This article describes one such structure. It is an editorial method, not a standard, and it assumes you already have a short list of real people to call. The earlier article on [your first ten customers](https://worldenterprise.org/insights/your-first-ten-customers-a-founder-led-sequence/) covers how to build that list. ## The six parts | Part | Purpose | Output you keep | |---|---|---| | 1. Prepare | Decide what this call must settle | One sentence, written before dialing | | 2. Open | Set the frame and ask permission | Agreement on the agenda | | 3. Discover | Learn the current habit and its cost to them | Their words, in notes | | 4. Show | Walk through only what answers what they said | A list of questions they raised | | 5. Qualify | Learn who decides, how, and what blocks a decision | Names, steps, constraints | | 6. Close | Agree one specific next step | A dated action for each side | The order matters. Showing the product before discovering the habit is the most common error among technical founders, because the product is the part you know best. Reversing the order costs nothing and changes what you hear. ## 1. Prepare: one sentence Write the purpose of the call as one sentence in the form "After this call I will know whether ___." A first call might settle whether this person has the problem in your [positioning statement](https://worldenterprise.org/insights/a-one-page-positioning-statement/), or whether the person who has it is also the person who pays. A later call might settle what a pilot would have to include. If you cannot write the sentence, the call is not ready to book. Spend ten minutes on the person's company: what it sells, how large it appears to be, and who else is on the team. Public sources are enough. The point is to ask better questions, not to recite what you found. ## 2. Open: frame and permission Say who you are in one sentence, why you asked for the time, and how the call will run. For example: "I am building a tool for studios that chase clients for files. I would like to hear how you handle that today, show you a short walkthrough if it seems relevant, and then agree what, if anything, to do next. Does that work?" The final question is real. A person who says the agenda does not suit them has given you information, and you can adjust or end the call politely. If you want to record the call, this is also the point to ask, and the section on recording below explains why that matters. ## 3. Discover: the current habit Use the same kind of questions as in a research interview. They ask about specific past events, not opinions about the future. Good prompts for this part: - "Tell me about the last time this came up. What happened?" - "What did you do first? Who else was involved?" - "What do you use today for that, and what do you like about it?" - "What does it cost you when it goes wrong, in whatever terms matter to you?" Listen for the person's own vocabulary and write it down verbatim. Those words can end up on your landing page. If the answers stay vague, ask for the last specific instance. The [customer discovery interviews article](https://worldenterprise.org/insights/customer-discovery-interviews-without-false-positives/) explains why questions about the past produce more reliable answers than questions about what someone would do, and the [customer interview guide](https://worldenterprise.org/library/customer-interview-guide/) has a longer list. For a technical product, add a short environment check: which systems they use, who maintains them, and what a new tool would have to connect to. These answers will decide whether a pilot is possible at all. ## 4. Show: only what they asked for Pick the one or two parts of the product that answer what the person described in part 3, and show those. Narrate it in their terms: "You said the files arrive by email; this is where that same message would land." Stop after each piece and ask what is missing. A feature tour that ignores what was said tells the buyer you were not listening. If the product is not ready for what they need, say so. A buyer who is told what the product cannot do yet can decide with accurate information, while a demo that implies more than exists leaves the buyer to find out later. How a customer meets the product in a trial or self-serve form is its own subject, covered in the article on [trials, demos and self-serve](https://worldenterprise.org/insights/trials-demos-and-self-serve-how-a-customer-first-meets-the-product/). ## 5. Qualify: the decision, not the interest Interest and the ability to buy are different things. Before closing, find out: - **Who decides.** Is it the person on the call, or someone else? - **How the decision is made.** A card on a personal account, a purchase order, a security review, a contract with legal? - **What would block it.** An existing tool, a budget cycle, a policy about where data may live. - **What they would need to see.** A reference, a trial, a written summary of what you offer. Ask directly and without apology: "If this looked right to you, what would have to happen on your side before you could use it?" Money comes up here, and the questions it raises, such as what to charge and how to package it, belong in the [pricing article](https://worldenterprise.org/insights/pricing-a-first-saas-value-packaging-and-the-questions-to-ask/). This article takes no position on what any price should be. ## 6. Close: one next step with a date End with a single next step that both sides agree to and that has a date: a second call with the person who decides, a pilot scope sent by a certain day, or a decision not to proceed. A non-answer such as "let's stay in touch" is itself a result, and it goes in the notes as one. The close is not a push. If the right next step is that the product does not fit, say that and ask who else might have the problem. ## Write the note within the day Technical founders already keep logs, and a call is worth logging. A compact template: - Date, person and role. - Purpose sentence (from part 1). - Their current habit, in their words. - Cost to them, in their terms. - What was shown, and what they asked next. - Decision maker, process and blockers. - Agreed next step and date. - Surprises. Fill it in while the call is fresh, and review a few notes together after every handful of calls. Patterns in the "surprises" line often show a segment you did not expect, or a feature nobody asked about. ## Recording a call: what the statute says Founders often want to record calls for later review. The U.S. federal wiretap law has a provision on this, and the primary text is short. Under 18 U.S.C. 2511(2)(d), "It shall not be unlawful under this chapter for a person not acting under color of law to intercept" a communication "where such person is a party to the communication" or "where one of the parties to the communication has given prior consent to such interception". The provision then carves out interception "for the purpose of committing any criminal or tortious act". That describes the federal rule only. This article does not address state laws, laws in other countries, or rules that apply to particular kinds of conversations, any of which may differ, and the people you call may be in places where the rule is different. What a call recording tool should say at the start, and where recordings may be stored, are questions for counsel. Telling the other person that you would like to record and asking whether that is acceptable is a courtesy that also gives you a record of their answer. ## What this article cannot tell you This article does not tell you what to say to a particular buyer, how many calls it takes to learn what you need, or what a call will produce. The six-part structure is an editorial method, not a framework from a named body, and a different order may suit your product. The one cited source is the text of a U.S. federal statute section, read on 2026-10-10, and quoting a few clauses is not a legal opinion. It is general information, not legal or financial advice. Recording, consent, privacy and the handling of what buyers tell you on a call depend on where you and they are, so ask a qualified lawyer who knows those places before you rely on any recording practice. ## Sources - 18 U.S. Code 2511. Legal Information Institute, Cornell Law School.