A prospect gave your proposal to a cheaper freelancer: how to protect a detailed quote
A quote protects your work best when it describes the result, the price and the timeline without handing over the method: the detailed sitemap, the technical choices and the first mockups belong in a paid discovery phase. An ownership notice on the document gives you a recourse if there is a dispute.

What should a proposal show, and what can it keep back?
A proposal has to let the client compare and decide: what they get, by when, for how much, and why you. It doesn’t have to tell them how to build it. One test helps: if another freelancer could quote and build the project from your document alone, the document says too much.
| In the proposal | In the paid discovery phase |
|---|---|
| The goal, in the client’s words, and how you will measure it | The workshop that turns that goal into priorities and user journeys |
| The deliverables: six pages, a booking form, one training session | The page-by-page sitemap, with the content of each page |
| The technology by name, for example WordPress or Webflow | The plugin list, the data model, the integrations and the hosting setup |
| The phases of the project and their dates | The detailed task plan |
| Price, payment schedule, number of revision rounds | The audit of the current site: what to keep, fix or drop |
| Two or three past projects as references | A moodboard and first mockups made for this client |
The questions of the brief stay on the proposal side. Asking the right ones shows your expertise without giving away the answers. Our guide on how to write a client brief lists them, and the free client brief generator turns them into a form the client fills in before you quote.
How do you sell a paid discovery phase?
Offer it as a small fixed-price project with its own deliverable, and deduct its price from the main quote if the client signs within a set period. The client pays for something concrete, and you get paid for the thinking that took you the longest.
A discovery phase for a website or an app can include:
- a two-hour workshop with the people who decide;
- an audit of the current site or app;
- the sitemap and the main user journeys;
- a written recommendation: scope, technology and a budget range for the build.
An example, with figures chosen for illustration: a bakery website quoted at $8,000, preceded by a $900 discovery phase delivered in two weeks, credited in full if the client signs the build within 30 days.
Once paid, the discovery deliverable belongs to the client, and your contract should say so. If they take the sitemap to someone cheaper afterwards, you have been paid for it.
What should an ownership notice say, and where does it stop?
A short notice at the foot of the proposal states that the document remains yours, is provided only to evaluate your offer, and may not be reproduced, shared or used to carry out the project without your written consent. It discourages casual reuse and dates what you sent.
This proposal and its appendices remain the property of
[your business name]. They are provided to [client] solely to
evaluate this offer and may not be reproduced, shared with third
parties or used to carry out the project, in whole or in part,
without our written consent.
Version of [date], sent to [recipient email].The notice has a clear limit. Copyright protects the way ideas are expressed, not the ideas, systems or methods themselves, as the U.S. Copyright Office explains, and France’s INPI says the same (both pages checked on October 16, 2026). Your wording, your diagrams and your mockups can be protected. The idea of a six-page site with online cake orders can’t. The notice shows that the client knew the document wasn’t theirs to pass on, which can help in a dispute, but it doesn’t extend protection to the ideas.
What can you do if it has already happened?
Gather the evidence first, write once to the client, calmly, and only then decide whether a lawyer is worth the cost.
- Save the email that carried the proposal, with the PDF attached and its date.
- Note what was reused: your text word for word, your mockups, or only the general idea. Copied text and visuals make a stronger case than a similar structure.
- Write to the client. Say that the document was provided to evaluate your offer, ask them to stop using it, and propose a way out, such as invoicing the discovery work they used.
- If the amount at stake justifies it, ask a lawyer or your professional association what your options are where you work.
Whatever the outcome, mark the proposal as lost and record why, so you can adjust the next ones.
How do you mark the proposal as lost and keep the reason?
Set the proposal’s status to Declined and write the reason in a property of its own. After a few months, the reasons show which kind of proposal leaks.
---
type: proposal
client: "[[Bakery]]"
status: Declined
amount: 8000
sent: 2026-11-03
lost_reason: reused by another provider
---Group a BasesThe database feature built into Obsidian: tables, cards and Kanban boards made from the properties of your notes. No plugin to install.help.obsidian.md table on lost_reason and the pattern shows: price, timing, no reply, reuse. If reuse comes up twice, your proposals go into too much detail for the stage at which you send them. A proposal that gets no answer at all is a different case: follow it up before you mark it lost.
Questions
Is my proposal protected by copyright?
Its text and visuals can be, if they are original. In the US and in France, that protection starts when the work is created, with no registration required. The ideas, the structure of the project and your method are not protected.
Should prospects sign an NDA before I send a proposal?
You can ask for large projects, but many small clients won’t sign one at that stage. A paid discovery phase protects the same work with less friction.
Should I stop writing detailed proposals?
Keep the detail on results, price, timeline and conditions, since that is what clients compare. Move the how into the discovery phase.