The actual conversation: objections, contracts, and getting to yes

#1. Why this lesson is narrow, on purpose

Everything up to this point in the course — finding the prospect, getting the meeting, running the free diagnostic — has been preparation for a conversation that, for a first-time founder, usually lasts less than ten minutes and gets improvised badly. This lesson is about that conversation specifically: what a real prospect actually objects to, what to say back, how to ask for the sale, and what paperwork and payment mechanics you need in place before the money can move.

This is deliberately the narrow version. This platform's Sales course builds the full mechanism library behind objection handling — SPIN's situation/problem/implication/need-payoff sequencing, the Challenger sale's insight-led reframe (teaching the buyer something new about their own problem before proposing a fix), MEDDPICC's qualification discipline (a checklist for scoring how real and how winnable a complex deal actually is) — and if you're selling into a company with a multi-stakeholder buying committee, a formal procurement process, or a six-figure contract, that's where the deeper mechanism lives. This lesson's four objections are a strict subset, built for a different buyer entirely: a single owner-operator with the authority to say yes on the spot and no procurement process at all. A trained rep's problem is usually navigating a committee; a first-time founder's problem is almost always one of four things — the price feels high, they think they already have this covered, the timing feels wrong, or they don't yet have a reason to trust someone with no track record. This lesson covers those four, and nothing else.

#2. The four objections, and why they're the ones that actually show up

Price. "That's more than I expected to pay." The most common objection, and — per the pricing research behind this course — the one first-time founders mishandle worst, almost always by discounting before anyone has actually pushed back.

"I already have something." A competing tool, a spreadsheet, a DIY workaround, or an incumbent vendor the prospect is already paying for, however badly it's working. This is the objection Marlowe's own close runs into, and it is worth taking seriously as a specific, answerable claim rather than dismissing it as a brush-off.

Timing. "Let me think about it," "check back next quarter," "we're mid-renovation right now." Some of these are real, checkable facts about the prospect's calendar. Most of them, examined honestly, are a polite exit — and the two versions require opposite responses.

Trust and credibility. The objection nobody says out loud: you've never done this before, why should I hand you my money. This is the objection every other objection is sometimes secretly standing in for, and it is the one a first-time founder is least equipped to argue their way out of directly — because arguing for your own credibility is exactly what makes it worse.

#3. Objection one: price

The single most common mistake a first-time founder makes with a price objection is discounting before it happens — quoting a number, then immediately hedging it ("but obviously we can work something out") before the prospect has said a word. Owen Van Syckle, a practitioner who writes specifically about this failure mode, names it "pre-emptive discounting" and diagnoses it correctly: [Directional] — a named practitioner's own account from direct founder-coaching experience, not a controlled study, but the mechanism he names is worth taking seriously on its own logic — "you are not reacting to the market. You are reacting to your own uncertainty." His worked math on the cost of this habit (discounting 5–10% across a run of deals) is illustrative, not measured, but his fix is concrete and checkable in your own next conversation: state the price, then stop talking, and only move on scope — what's included — not on the number itself, if a real objection actually lands.

There's a real mechanism underneath "state your price and stop talking," not just folk wisdom. Ariely, Loewenstein, and Prelec's 2003 study in the Quarterly Journal of Economics — [Established], peer-reviewed, and the primary source is publicly available — found that an arbitrary number entering a person's head before they judge a price becomes the reference point every subsequent judgment gets measured against, even when the number has nothing to do with the actual value of the thing being priced. The practical implication for a sales conversation is direct: the first number said becomes the anchor, which is the entire argument for stating your own price first and clearly, rather than asking "what were you thinking of paying" or floating a hedged range. Once you've said $600, backing off to $450 before anyone's objected doesn't just cost you $150 a month — it resets the anchor down, and every later conversation about price in that relationship starts from the new, lower number.

The advice to go quiet after stating a price, and to respond to a real objection with a question rather than an immediate defense of the number, is standard, widely repeated sales-training practice — [Speculative], since no specific controlled study behind either claim turned up in the research for this course, and it should be taught as a practical heuristic, not evidence-based technique. But the logic behind it is sound on its face: a price objection is frequently a value objection wearing a price costume — the prospect hasn't been convinced the problem is worth solving at that number, not that the number itself is wrong — and "help me understand what feels off" gets you the real objection instead of forcing you to guess at it.

#4. Objection two: "I already have something"

This is the objection to take most seriously, because unlike price it can mean two completely different things, and the two require opposite responses.

The first version is real: the prospect genuinely doesn't have the problem you think they have, or the tool they're using genuinely solves it well enough. If that's true, pushing harder is wasted effort — the honest move is to let the no stand and move to the next prospect. Rob Fitzpatrick's The Mom Test (2013) gives you a test for which version you're in: [Speculative] as a framework — a single-author practitioner heuristic, not a peer-reviewed study of its own — but its central distinction is worth using because it's checkable in the room. Fitzpatrick separates facts (what the prospect actually does, today) from compliments and fluff (how they feel about it, or what they'd hypothetically do). This isn't just Fitzpatrick's opinion — it maps onto an independently studied phenomenon: social desirability bias, documented directly in consumer research by Fisher (1993, Journal of Consumer Research) — [Established], peer-reviewed — where people systematically shade their answers toward what feels acceptable to say to the person asking, rather than what's actually true. Applied to "I already have something," the move is to ask a fact question: what do you still do by hand, around the tool, that it doesn't do for you? An answer full of specific, concrete behavior (reconciling receipts on a Sunday night, re-entering numbers before a tax deadline) is a real gap you can name. A vague or defensive answer ("it's fine, I just haven't gotten around to it") is closer to a polite exit than a real objection — and April Dunford's positioning framework (Obviously Awesome) supplies the honest name for that outcome: sometimes a pitch fails not because the offer is wrong but because you're pitching a best-fit customer's product to someone who isn't best-fit — [Directional], a named practitioner's methodology verified via her own site and book summaries rather than a peer-reviewed instrument, but a useful alternative to assuming every "no" is a failure of persuasion.

The second version — the one Marlowe actually runs into — is that the incumbent tool is real but incomplete: it does one narrow thing (tracks transactions) and leaves the actual hard part (reconciliation, the monthly close, catching errors before they compound) sitting undone in the owner's own evenings and weekends. That's not a "we already have this" objection at all — it's a scope-mismatch, and the honest response is to name specifically what the $40 tool is (a ledger) against what it isn't (a bookkeeper who reconciles it and closes the books), using the prospect's own answer to the fact-question above as the evidence, not your own claim about the tool's limitations.

#5. Objection three: timing

"Let me think about it" is the hardest objection in this course to read correctly, because the same four words mean two opposite things depending on what follows them. Fitzpatrick's Mom Test frames this precisely: [Speculative] as a specific claim, but logically sound — founders are structurally more likely to get a polite false yes than an honest no, because people are socially reluctant to reject someone to their face. A real timing objection is checkable against a fact: "our fiscal year closes at the end of Q2, come back after that" is specific, has a date attached, and can be verified later. A fluff timing objection has no date, no specific trigger, and no way to check it: "let me think about it" with nothing else attached is very often a no wearing a maybe's clothes, precisely because saying no outright feels ruder than deferring.

The honest move — the one that matches this platform's rule against manufactured urgency — is not to manufacture a false deadline to force a decision. It's to ask a direct, specific question that turns fluff into a fact: "is there something specific you want to check, or a date that makes more sense — or is now just not the right fit?" That question gives a genuinely-not-ready prospect room to name a real constraint, and it gives a polite no permission to actually say no, which is more useful information than a maybe that never resolves. If a real, honest constraint comes back — a renovation, a slow season, an actual calendar fact — the right response is to offer the smallest, lowest-commitment next step that fits it, not to abandon the deal. That's the same time-boxed, named-exchange logic behind the design-partner model Bessemer Venture Partners has documented in B2B: free or reduced access during a defined period, in exchange for a named conversion point later — [Established], a named venture firm's own published account of a real, disclosed pattern — not an open-ended "check back sometime," which both YC's own guidance and Bessemer's own structure independently flag as the version of a deferred close that tends to go nowhere.

#6. Objection four: trust and credibility with no track record

This is the objection underneath every other objection, and it is the one a first-time founder is instinctively worst at handling, because the instinct is to argue for your own credibility directly — and arguing for your own trustworthiness is one of the least trustworthy-sounding things a person can do.

The relevant research here is old and unusually well-replicated: Hovland and Weiss's 1951 paper in Public Opinion Quarterly, and the broader source credibility theory it founded (Hovland, Janis & Kelley, 1953) — [Established], peer-reviewed, and confirmed as holding up across five decades of subsequent research by Pornpitakpan's 2004 meta-analysis in the Journal of Applied Social Psychology. The model identifies two dimensions a listener scores a source on: expertise (is this person a credible authority on the claim) and trustworthiness (do I believe this person is honest, independent of expertise — which includes a read of their motive). The non-obvious implication for a first-time founder: not having sales training is not automatically a disadvantage here. A polished, scripted pitch pattern-matches to "salesperson," which primes suspicion of motive; an obviously first-person, unscaled process (you personally doing the work, not a CRM sequence) reads as someone with something real to lose from a bad fit — closer to the trustworthiness dimension Hovland's model actually measures. The specific claim that "a prospect assumes a founder wouldn't waste time on a poor-fit deal" is asserted repeatedly across founder-led-sales writing without a controlled study behind it — [Speculative] as a standalone claim, though a direct, plausible application of Hovland's much better-evidenced dimension, not an invented idea.

Yuri Sagalov, writing on Y Combinator's own blog about enterprise pilots, makes the expertise/motive point concretely from the buyer's side: prospects "actually prefer to pay you because then they know that you are on the hook for something" — [Established], a named founder's own published essay on a platform's own site. That's the mechanistic reason the free diagnostic matters at the close, not just at the outreach stage: it's not a favor, it's how a person with no track record generates the evidence a track record would otherwise provide. The work itself becomes the credential.

That mechanism has a real edge to it, worth naming rather than ignoring: a diagnostic specific enough to be persuasive is also specific enough to act on without paying the person who found it. A prospect who now knows exactly what's broken — a named dollar figure, a named cause — can, in principle, fix it themselves or take the finding to a cheaper provider instead of converting. [Speculative] — a well-known risk in freelance and consulting sales practice generally, not a claim tied to a specific study. The practical answer isn't to hold the finding back, since a vague diagnosis wouldn't generate the credibility this section is about in the first place; it's to keep the finding and the fix as two separate things. Give away what's broken. Sell the labor of actually fixing it and keeping it fixed every month after. Marlowe's close in section 10 does exactly this: the audit names the problem for free, but fixing it — "first month includes fixing the miscategorization and cleaning up what I just found" — is part of the paid engagement, not thrown in alongside the free diagnosis.

#7. Closing without pressure: the actual ask

Everything above is diagnosis. At some point you have to actually ask for the sale, and this course's stated rule against dark patterns — manipulative sales or design tactics that pressure someone into a decision rather than earn it — applies directly here: no fake urgency, no manufactured scarcity, no invented deadline. What replaces it is a real, specific ask and, if one genuinely exists, a real deadline — not a fabricated one.

Steli Efti, who bootstrapped Close (formerly Close.io) to a profitable, venture-free SaaS business and has written extensively and publicly about outreach, states the specific-ask principle directly: [Directional] — a named practitioner's consistent, repeated teaching point, not a controlled study — "cold emails make sense when you have something specific to offer and something specific to ask for." The same logic applies to a close: "would you like to move forward with this?" is vague and easy to defer. "I can start Monday at $600 a month, first month covers a full books audit and close — do you want to go ahead?" is a single, answerable question. If you genuinely have limited capacity — you can only take on one more client this month — say that plainly, because it's true, not because it creates pressure; if it isn't true, don't say it, because a fabricated deadline is exactly the dark-pattern move this course rules out, and a first-time founder gets caught in exactly these small dishonesties more easily than an experienced closer, because the relationship is new and has nothing built up to survive the trust hit.

After the ask, go quiet again, for the same reason as after the price: the silence is the prospect's room to actually decide, not yours to fill with more selling.

#8. The practical minimum: a written agreement

A first client does not need a lawyer-drafted contract. It needs a short, specific written agreement that both people sign, because a verbal handshake creates ambiguity that costs real money later — what exactly was promised, at what price, starting when, cancellable how. Across the template providers that converge on the same basic structure for a freelance or solo-service agreement — Bonsai, Wise, and PandaDoc all publish some version of the same skeleton — [Directional], a consistent pattern across multiple independent template vendors, not a single primary-sourced legal standard, so treat the structure as reliable and adapt the specific wording to your own situation — the load-bearing elements are: who the two parties are (full names, contact details); what's actually being delivered, specifically enough that both sides would agree later whether it happened (for Marlowe: monthly bookkeeping and a monthly close, not "accounting services"); the price and when it's due (monthly, on the 1st, by invoice); how either side exits (30 days' written notice, no penalty, is a common and reasonable default); and who owns what happens if something goes wrong (a basic confidentiality clause covers financial data specifically). One page is enough for a deal this size. The point of writing it down isn't legal armor — it's that a written scope is the single easiest way to prevent the slow scope-creep that kills the margin on a $600/month engagement, because "can you also just quickly look at payroll" gets a different answer when there's a document both people can point back to.

#9. Getting paid as a brand-new solo operator

You do not need a registered company, a business bank account with years of history, or a merchant-services relationship — a bank or payment processor's approval to accept card payments — to take your first payment. Stripe's own documentation for freelancers and sole operators — [Established], a platform's own published documentation — confirms that Stripe Invoicing is available to individuals and sole traders with no prior processing history: you verify identity and provide bank details, there's a free tier with no monthly fee (you pay a transaction fee only when the client actually pays), and you can generate and send a professional invoice with an embedded payment link in minutes, no code required. The one practical thing to plan around: standard payouts land in about two business days after a successful charge, but a brand-new account can see a longer initial delay — Stripe's own guidance notes this can run up to about a week before the account's payout history normalizes — so don't plan your own cash flow assuming the first payment lands the same week it's charged.

For a service like Marlowe's, invoiced monthly rather than project-by-project, an invoice with a card-payment link is the simplest version: it works before you've registered a formal business entity in most jurisdictions (check your own local rules specifically — this isn't legal or tax advice), it gives the client a clear paper trail for their own books, and it puts a due date on the relationship without you having to chase a check. Accepting an informal payment — a personal Venmo or a cash handshake — is understandable for a first deal, but it blurs the line the written agreement in section 8 is meant to draw, and it leaves you with no record if a dispute ever comes up.

With a client you have no track record with yet, collect payment before you start the deliverable work, not after. Marlowe's invoice in section 10 is due on signature, and that isn't just a detail of that one script — it's the general rule for a first, unproven relationship: you don't yet know this client pays on time, and they don't yet have a finished month of work to judge you against. Framing it as how you always invoice a new client, rather than as a special condition applied to them, keeps it from reading as distrust. If a payment is late anyway, treat it as a fact to check before it's a fight to have: a short, direct follow-up ("just checking — the invoice for [month] went out on the 1st, did it come through okay on your end?") resolves most cases, since a missed email or an expired card causes far more late payments than a client who's simply decided not to pay. If a real non-payment drags past 30 days despite two direct follow-ups, pause further work until the account is current — continuing to deliver service against an unpaid invoice only compounds the exposure, and the 30-day notice clause in section 8's agreement gives you the contractual room to stop without it being a breach on your side.

#10. Marlowe's full close, start to signed agreement

Marlowe is an invented example used throughout this course — a solo bookkeeper leaving a corporate accounting job to freelance for small, owner-operated local businesses. The numbers below are the same ones used everywhere else in this course: $600/month, a boutique gym as the first client, a free books audit as the hook, and a $40/month software subscription as the incumbent tool.

Marlowe's first prospect is the boutique gym, reached through a former colleague's cousin — a weak tie, not a stranger, which matters for how much trust already exists walking in. The free audit has already happened: Marlowe spent two hours going through the gym's books in the software the owner already uses, and found three months of miscategorized expenses that had been quietly overstating the gym's tax liability — the same finding referenced earlier in this course. The close happens at the end of that same conversation.

Marlowe: "So here's what I found — nothing catastrophic, but about $340 in expenses have been miscategorized over the last three months, which means you've actually been overstating what you owe in taxes. Here's what I'd do going forward: full monthly bookkeeping and a proper close, every month, for $600. First month includes fixing the miscategorization and cleaning up what I just found. I can start this week."

Gym owner: "That's... a lot more than what I'm paying now. I've got the app — it's like $40 a month."

Marlowe doesn't defend the number immediately, and doesn't discount. This is the price objection wearing an "I already have something" objection's clothes — worth separating before responding to either.

Marlowe: "That app's a ledger — it logs what came in and went out. What does it do about the stuff I just found — three months of expenses miscategorized in a way that's been costing you at tax time?"

Gym owner: "Nothing, I guess. I just... haven't had time to go through it properly. I do a rough pass on Sundays, usually."

That's the fact this course's framework is built to surface: not a vague "it's fine," but a specific, checkable behavior — unpaid Sunday hours, and $340 in miscategorized expenses that had already gone unnoticed for three months. Marlowe uses it directly, without inventing anything or attacking the app.

Marlowe: "So right now the $40 a month is actually costing you your Sunday afternoons, plus whatever slips through when you don't catch it — like the $340 in miscategorized expenses. What I'm charging isn't instead of the app, it's for the part the app was never built to do: someone actually closing the books every month and catching things like this before they add up. That's a fraction of what a full accounting firm would charge you for the same thing."

Marlowe stops talking. The owner is quiet for a moment — the room to actually think, not filled with more pitching.

Gym owner: "Okay — what happens if it's not working out after a couple months?"

Marlowe: "Thirty days' written notice, either direction, no penalty. I'll send over a one-page agreement tonight — scope, the $600 monthly price, invoiced on the 1st, and the notice terms. You can pay by card through the invoice link, no bank details to hand over to me directly. Sound good to start?"

Gym owner: "Yeah — let's do it."

Marlowe sends a one-page agreement that evening covering exactly what was said out loud — monthly bookkeeping and close, $600/month, invoiced on the 1st, 30 days' notice either way, basic confidentiality on the gym's financial data — and a Stripe invoice for the first month, due on signature. No discount was offered. No deadline was invented. The close took about ninety seconds once the real objection surfaced, because the objection was answered with a fact the owner supplied, not an argument Marlowe had to win.

The same shape applies outside bookkeeping. A solo SaaS founder closing their first paying pilot hits the same four objections in different clothes: "that's a lot for a beta product," "we already use [incumbent tool]," "let's revisit after our next funding round," and the unspoken "why would I trust my data to a two-person company." The framework — state the price and hold it, separate a real objection from a polite exit with a fact-question, offer the smallest honest next step rather than a manufactured deadline, and let disclosed, specific work stand in for a track record you don't have yet — doesn't change with the product.

#11. Worksheet: pre-write your own close

Before your next real conversation, fill this in against your own business. Write your actual answers, not a generic template — the value of this exercise is having the real sentence ready before you need it, not after.