From lead to contract in one calm thread: a tour of the handoff
A new inquiry should become a signed contract without anyone retyping a name, a price or a deliverable. Here is how the rooms in Meadow Desk hand the work to each other.
Most of the tools a small studio uses are good at one room each. One captures leads, one writes proposals, one signs contracts, one tracks the project. The cost is at the doorways: every time the work moves rooms, someone copies the client’s name, the price and the deliverables by hand, and something changes slightly in the copy.
We built Meadow Desk around the doorways. This post walks through what happens between a form submission and a signed contract, and what deliberately does not happen.
The lead arrives with its own context
A lead comes in from a hosted lead form, an email or a manual entry. Whatever the source, it lands with the same shape: who they are, what they asked for, the budget range they mentioned, and the date. There is no separate CRM to sync. The lead is already a row on the same desk the project will later live on.
The proposal starts from the lead
From the lead you choose a template and the proposal opens with the client details, the inquiry text and the budget already placed. You write the deliverables, the rounds and the price, the sections that keep scope creep out. When you send it, the client gets a link, and you see when they open it and how far they read.
The contract inherits the proposal word for word
When the proposal is accepted, the contract is generated from it. The deliverables section, the revision rounds, the payment schedule and the not-included list are the same text. Nothing is retyped, so nothing can drift. The client e-signs it by private link or in the client portal, and the project is created from the contract with its milestones already dated and its invoices already scheduled.
- Lead → proposal: client details and inquiry carried over.
- Proposal → contract: deliverables, rounds, schedule and exclusions copied verbatim.
- Contract → project: milestones dated and invoices scheduled from the payment plan.
The best integration is the one you never configure because the two things were never separate.
An early design principle for Meadow Desk
What deliberately does not happen
Nothing is sent without you pressing send. The proposal does not auto-follow-up, the contract does not auto-remind, the project does not start a timer. Automation lives at the doorways, where copying is boring and error-prone. Judgment stays with you.
Was this useful?
Meadow Desk
Notes from the desk
Meadow Desk is a calm workspace for freelancers and small studios: clients, proposals, tracked time and invoices in one place. We write here about the parts of studio work the desk touches: proposals and pricing, scope, tracked time, invoices and the clients behind them.
More notes from the desk
The best free tools for freelancers in 2026
A practical list of free tools for freelancers: pricing, proposals, contracts, invoicing, time tracking, scheduling and taxes, with what each free plan covers.
The quiet invoice: getting paid on time without chasing anyone
Late payments are rarely about the client being difficult. They are about the invoice arriving at the wrong moment, in the wrong shape, with nothing attached to it that explains why it exists. Here is a sequence that fixes it.
Scope creep starts in the proposal: writing one that protects the project
Every “small extra” a client asks for mid-project was already possible on the day you sent the proposal. The document just failed to say no in advance. This is how to structure a proposal so the boundaries are agreed before the work begins.