I Used to Get Stuck at the Proposal Stage
At 10 p.m. last Wednesday, Sister Zhou in Hangzhou received my second proposal. She asked, “Could we start with part of it?” I stared at the chat for half an hour, then added 800 yuan. The work wasn't difficult; the client hadn't understood the delivery boundaries, and I hadn't spelled them out in advance.
Later, in a shared workspace in Nanshan, Shenzhen, I came across freelance consultant Lin Ran using a “one-page quote” to win work. She put everything on one page: services, number of deliveries, number of revisions, and how out-of-scope work would be charged. After sending it to clients, her communication time dropped from 30 minutes to 10. The tool isn't mysterious. The key is to write down the price and scope first, then have the client confirm them.
What This Method Actually Is
I see it as “confirming before quoting.” The point isn't the software; it's getting both sides to agree to the same promise. At minimum, the page should cover four things: what you'll do, when you'll deliver, how many revisions are included, and how to price requests added on the fly. End with a line like, “I'll begin once this is confirmed.” When the client replies, “Proceed according to this page,” both sides have an easy-to-find record.
Sister Zhou tried it too. She labels every new request as “outside the original scope.” Her tone became a little more direct, but she no longer has to rely on memory when debating what was included. When I first started building a personal IP or taking on small projects, I'd send a one-page text brief. Once clients became familiar with it, I'd turn the same content into a PDF. No method fits everyone, and there's no rush to upgrade as a team grows.
What It Costs to Replicate Today
The cost is almost zero: use an existing document tool, 0 yuan. Organizing it carefully takes about 30 minutes, plus another 15 minutes before your first client-facing send. The technical barrier is minimal: being able to use text and a table is enough; no coding required. The first step isn't downloading a tool. It's opening your document app, creating a new page, and titling it “Service Scope and Fee Confirmation.”
If you want to spend another 20 minutes, you can make two versions: one for individual clients with a more relaxed tone, and another for company clients that adds invoices, payment timing, and acceptance criteria. My old mistake was quoting first and adding boundaries afterward. I switched to confirming the scope before discussing the total price, and rework dropped noticeably. I might test it on a real project first without building a complete system. If you're not ready now, that's fine too; use it when a dispute becomes likely.
How I'd Set It Up at Different Stages
If you're just starting: I'd make a one-page pricing brief and clearly state, “Here is exactly what I will deliver.” It doesn't need to look polished. The simpler the template, the easier it is to keep using.
If you have one or two clients: I'd add a project number, payment timing, and out-of-scope pricing. After each conversation, I'd send the final approved version back to the client.
If you're scaling up: I'd split core services and add-ons into separate packages, then use a questionnaire to collect requirements. I'd also retain pricing versions and approval records so the team can work from them. Not everyone needs specialized tools; writing down the rules first is often more useful than switching software.