The gap between a client saying yes and the project actually starting is where deals quietly stall or unravel — the fix is a fixed, fast sequence: contract, deposit, kickoff call, in that order, ideally completed within a few days of the yes. Momentum built by a strong proposal doesn't survive a slow, improvised handoff.
Most proposal advice stops at "and then you close the deal," as if a yes is the finish line. It isn't — it's the start of a process that, done badly, can lose a client who already said yes.
Why This Gap Matters as Much as the Proposal Itself
The same psychology that makes fast proposals close better applies here: a prospect is at their most engaged right after they say yes, and that engagement decays if the next steps drag. A client who agreed to move forward on Monday but doesn't get a contract until the following week has time to get cold feet, get distracted by other priorities, or start wondering if they moved too fast. The proposal follow-up cadence gets a client to "yes" — this stage is about not losing what you just won.
The Sequence, Step by Step
| Step | Timing | What happens | |---|---|---| | 1. Contract sent | Same day as the yes | Formal agreement covering scope, price, timeline, revisions, payment terms | | 2. Deposit invoice sent | Same day, alongside the contract | Typically 30-50% upfront, tied to contract signature | | 3. Contract signed + deposit paid | Within 1-3 days | This is the real commitment point — treat it as the actual close | | 4. Kickoff call scheduled | Immediately after deposit clears | Confirms scope details, sets expectations, collects assets | | 5. Project starts | Within a week of the yes | Work begins while the client's engagement is still high |
Compressing this into days rather than weeks matters more than most freelancers assume. A client who verbally agrees but then waits two weeks for a contract has effectively re-entered the same readiness decay that governs the original proposal — day 1 enthusiasm doesn't hold indefinitely, whether it's about opening a proposal or following through on a yes.
The Contract: What It Needs to Cover
A proposal sells the project; a contract protects it. At minimum, it should lock down:
- Scope, matching exactly what was in the proposal — no vaguer, no broader
- Price and payment schedule, including what happens if the client cancels partway through
- Timeline, with milestone dates, not just a total duration
- Revision limits, so "unlimited changes" doesn't become an implicit expectation
- What happens if the client goes unresponsive mid-project — a clause covering delays caused by their side, not just yours
If you're building this from scratch, see web design contract essentials for the full breakdown of what to include and what to avoid — it's the natural next document after the proposal itself.
The Deposit: Why It Should Move at the Same Speed as the Contract
Sending the deposit invoice separately, days after the contract, adds an unnecessary extra step that gives the client another point where they could stall. Send both together — contract and deposit invoice in the same message — so signing and paying feel like one action instead of two separate decisions spread across a week.
A deposit also does something beyond securing cash flow: it converts a verbal or written "yes" into a financial commitment, which is a much stronger signal of a real close than an email reply. Treat the deposit clearing, not the "yes" itself, as the actual moment the deal is won.
The Kickoff Call: Don't Skip It, Even for Small Projects
Even on a small project, a short kickoff call — 15-20 minutes — is worth the time. It surfaces misunderstandings about scope before they turn into mid-project disputes, and it sets a communication rhythm (how often you'll update them, what you need from them and by when) that prevents the client from going quiet on you mid-project the same way a stalled prospect goes quiet on a proposal.
What to Collect on the Kickoff Call
- Logo files, brand colors, existing marketing materials
- Login access to any existing domain, hosting, or website
- A list of pages/content they're responsible for providing, with a deadline
- Confirmation of the primary point of contact if it's a business with multiple decision-makers
Getting this list nailed down at kickoff — rather than chasing it piecemeal over the following weeks — prevents the single most common cause of project delays: waiting on the client for assets nobody asked for clearly upfront.
Why This Stage Deserves the Same Discipline as Outreach
Freelancers spend real effort tightening cold outreach and proposal follow-up sequences, then let the post-yes handoff run informally — a contract "whenever I get to it," a kickoff call scheduled loosely. That inconsistency costs deals. Industry estimates put 36% of freelancer time in admin tasks that connected tools could automate; sending contracts and invoices on autopilot the same day a client says yes reclaims a meaningful chunk of that time while also protecting the deal itself.
The same discipline that makes the cold email follow-up sequence that actually works effective — a fixed cadence instead of an improvised one — applies here. A "yes" isn't a finish line you can relax at; it's a handoff that needs its own fixed process.
Where This Fits
This stage sits right after the proposal does its job — for the send-speed and follow-up discipline that gets you to a yes in the first place, see how fast should you send a proposal after first contact and how to follow up after sending a proposal.
Where Runvax Fits
Runvax tracks a prospect through every stage of this process — Found, Contacted, Interested, Proposal, and finally Won — so the moment a client says yes, the deal moves into a stage you can see against your running pipeline and won value, instead of living only in your inbox. Try Runvax free to manage the full journey from first contact to signed deal in one place.