How I win a client in 10 minutes after a call
Stop panicking and start closing more
Intro
When I first started hopping on client discovery calls I was super nervous. Oh my God. I could remember having this feeling of uncertainty, “what is gonna happen on the call”, I was wondering if I’d eventually win the client or not.
I used to take notes manually, I used to come unprepared to the call, I used to do so many small mistakes that, if avoided, could’ve led to better results, more clients and eventually more sales.
Now I have a repeatable strategy for each call I do. It’s like you keep repeating the same exercise over and over again until you become good at it.
The first 5 minutes are usually small talk, where are you from, how long have you been in the field, and then I tell the person what the next 30 minutes look like so nobody wonders where this is going.
After that I ask 4 questions, more or less in this order: what is the problem and how long has it been going on, why does it matter to you right now, what has stopped you from fixing it so far, and on a scale of 1 to 10 how big a priority is this. The last one usually shows me the intent of the person and their seriousness.
While they answer I listen for 2 things. The exact words they use for their problem, and any number they say out loud, like a budget, a deadline or the hours it costs them. Those two go straight into the proposal.
So the approach is stupidly simple: just listen, show real interest and ask questions. What I realized though after dozens of calls taken and many mistakes learned is that clients honestly care about themselves, being heard and their problem being solved.
Your job on the call is to listen and increase their trust towards you. There are many ways of doing so and one possible way is well explained in this article, so check it out if interested: How to close a $4k deal in 1 prompt.
But now what do you do after the call, you guys discussed everything, agreed on some terms, timelines etc., but there is clearly nothing concrete established yet.
So let’s assume you hopped off a good client call and the client is keen to move forward with you. Awesome. What do you do now? Well, let me show you what I did, what worked and what didn’t.
Problem
So as a usual practice in the agency world, freelancing, coaching or consulting business you send a proposal.
Thing with proposals is that it is hard to craft a good one and I’m being serious right now:
You don’t know how to price the build or consultation: hourly/fixed, long-term/short-term commitment, what is your hourly rate, why would the client pay you this much?
You start overthinking every section of the document. What should you include, what should you exclude from the scope?
You research your competitors, find out they do more than you for the same price and panic.
Sometimes this process really took me 1-3 hours to do from start to end just because I was sitting there and overthinking every single step.
Meanwhile the client was sitting on the other side with their inbox and the other people they talked to this week. The call ended warm, and every hour without a proposal makes it a little bit colder and harder to eventually sell. After 2 days you’re writing to someone who already half forgot what they told you.
There’s an old study from MIT on web leads that found the odds of qualifying a lead drop 21 times between 5 and 30 minutes. This is about qualification, but human psychology can be applied to this side as well.
Solution
So I got tired of doing this job myself and repeating the same research and thinking process over and over again, so I decided to guess what: automate it.
The result is a proposal document I send the same day, usually within 10 minutes of hanging up. I read it through and agree on the price with my AI agent.
It has the same 7 sections in the same order every time, and each one gives the client something specific:
Overview. Shows them you listened, in 2 or 3 sentences written to them.
Objectives. Their goals in their own words, so the first thing they read is their own problem.
Scope of Work. What they get, phase by phase, with a line on what is out of scope so nobody is surprised later.
Approach and Timeline. When they get it.
Pricing. What it costs and how payment works.
Client Dependencies. What you need from them to keep the dates, and who owns each item.
Next Steps. How to say yes.
Because the order is the same every time, the client always knows where to find the price and I always know where to check it.
Now I run 1 claude skill that does that for me, and the whole pipeline with the review takes about 10 minutes total.
In practice
Total proposal creation time: 10 minutes. You need Claude on Pro plan at least so you have access to Claude Code, and your call recorder app connected to Claude through the connectors section. Without one, the skill asks you for the transcript.
Step 1: Install the skill, once (2 minutes)
Open Claude Code in any folder, paste the block below and press enter. It saves the proposal skill on your computer, so you never paste it again.
Create a Claude Code skill for me. Save everything between the START and END lines below, exactly as written, to ~/.claude/skills/proposal/SKILL.md (create the folders if they do not exist). Do not change a word. When it is saved, reply with one line: Skill saved. Then stop.
=== START ===
---
name: proposal
description: >-
Turn a client call into a finished client-facing proposal. Pulls the transcript
from the user's call recorder app, writes the proposal and hands it over as a
clean black and white PDF. Use when the user says "write the proposal for [client]",
"turn this call into a proposal", "proposal for [client]" or pastes call notes
and asks for a proposal.
---
# Client Proposal
Turns the notes from one client call into a proposal the client can read in 3 minutes. It is the polished continuation of what the client said on the call: same story, more detail on what will be built.
## Settings (edit these 3 lines to make it yours)
LOGO: none. To use one, put its file path here and embed it in the header as a base64 image so the file stays self-contained.
FONT: Inter or any other cool font you decide
VALID FOR: 30 days
## Get the call notes
Ask the user for the client name if it was not given. Then find the call yourself before asking for anything. Look at the tools you have connected. If one of them is a call recorder or meeting notes app (Fathom, Fireflies, Granola, Otter, Read.ai and similar), use it to find the most recent call with that client (match on the client name or the attendee email) and read the full transcript, not only the summary. If several calls match, take the latest one and tell the user which call you used (title and date). If you find no recorder app, or no call for that client, ask the user to paste the full transcript or their notes. Do not write anything before you have the call. The call is the source of truth for scope, phases, risks and pricing.
Read it for 2 things: the exact words the client uses for their problem, and every number they said out loud (budget, deadline, hours lost).
If the price, the dates or the company name are missing from the call, ask the user for them in one message before writing. Never invent a price, a date or a name. If the user does not have a number yet, write TBC.
## Write the proposal
Sections, in this exact order:
1. Overview: 2 to 3 sentences addressed to the client. What we understood they need and what we propose.
2. Objectives: 3 to 5 outcomes, in the client's own words from the call.
3. Scope of Work: one subsection per phase, each describing in real detail what gets built. Write it fully. End with an explicit Out of scope line.
4. Approach and Timeline: how the work runs (phased, with a demo at the end of each phase), plus a timeline table with dates. TBC where no date was agreed.
5. Pricing: a price table by phase, a total, any optional add-ons priced separately, the monthly retainer if there is one, and the payment schedule.
6. Client Dependencies: what we need from the client to keep the dates, with an owner for each item.
7. Next Steps: the exact actions to start, and how to say yes.
No "Prepared by" line and no "Why us" section. Do not mention anything internal, like risks we carry or our read on the client.
## Build the proposal file
One single HTML file with inline CSS and one Google Fonts link for the font. The look is clean black and white, nothing else.
- Page: white background, text #111, A4 with 18mm top and 16mm side margins (@page). Set print-color-adjust: exact so the black table header prints.
- Font: the FONT setting above, loaded from Google Fonts (weights 400 to 700), with -apple-system, Helvetica Neue and Arial as fallbacks. Body 10.6px, line height 1.55.
- Header: the logo if one is set, then the title "Proposal: [project]" at 25px bold, then "Prepared for: [client]" and "Date: DD Mon YYYY" in small text.
- Each of the 7 sections is its own section block with a 1px light gray line (#dcdcdc) above it. Section headings are bold black at 13.5px. Phase titles in Scope of Work are bold at 11px. No color anywhere except black, white and grays.
- Tables for the Timeline and the Pricing: full width, header row solid black with small white uppercase text, light gray (#e6e6e6) lines between rows, a bold total row with a #f3f3f3 fill, prices right aligned.
- Footer: "This proposal is valid for [VALID FOR setting] from the date above." in small gray text (#8a8a8a).
- Use break-inside: avoid on tables and phase blocks so nothing splits across pages.
## Build the PDF
Save the HTML as proposal-[client]-[DD-MM-YYYY].html in the folder Claude Code was opened in. Then make the PDF from it with Chrome in headless mode: find Google Chrome or Chromium on this computer and run it with --headless --disable-gpu --no-pdf-header-footer --print-to-pdf=proposal-[client]-[DD-MM-YYYY].pdf and the file:// path of the HTML.
Open the PDF and check it: black and white only, light gray lines between sections, tables readable, no section cut in half across pages. If not, fix the HTML and run it again. If there is no Chrome or Chromium on this computer, skip the PDF and tell the user to open the HTML and print it to PDF from the browser.
## Hand it over
Tell the user the path of the PDF (and the HTML), which call you used, and every TBC left in it. Tell them to check the price, the dates and the company name before sending. Do not send it anywhere.
## Style rules
- No em dashes and no en dashes anywhere. Use commas, colons, parentheses or "to" for ranges.
- Company voice: always "we", never "I". "We work", "we deliver", "we will build".
- Plain words. Short paragraphs. No filler.
- Polished, professional and dense with concrete detail. The Scope of Work reads as a detailed continuation of the call, not a bullet list of feature names.
- Every fact comes from the call. If the call does not cover it, ask, or write TBC.
=== END ===It answers “Skill saved.” If it asks to create the file, say yes. The skill is gonna hand you a very rough type of proposal but you can customize the template for your own liking, adding brand colors and your logo of course.
Step 2: Run it after a call (10 minutes)
Open Claude Code and type: write the proposal for [client name].
It finds the call in your recorder app and reads the full transcript. If it finds no recorder app, it asks you to paste the transcript. It asks once for any price, date or name the call did not cover, then it writes the proposal and turns it into a PDF.
You get the PDF back, saved in the folder you opened Claude Code in, with the list of anything left as TBC. Read the price, the dates and the company name, then send it.
Don’t build anything more around this yet. Run it on your next 3 calls, put your logo in the settings at the top of the skill and rename the sections to fit how you work.
Talk soon,
Ilya


Discussion about this post