When your proposal becomes the client's AI prompt

The most-repeated freelance story of the past year goes like this. A designer sends a detailed proposal, follows up, gets nothing. Follows up again, nothing. Weeks later the project is live, built by the client, following the proposal step by step, because it was pasted into a chat window and used as the plan.

That reads as a story about a bad client. It is a story about a document whose value changed.

A twelve-page scope breakdown used to be the cheapest thing you could give away, and it was safe because it was inert. The client could read every task, agree with all of it, and still be unable to do any of it. That gap was your business, and it closed. A specification written well enough for a developer is now written well enough for a model.

One situation runs through this post. An independent hotel group wants its own booking flow, to cut the commission it pays online travel agents. Illustration, not a real client. They ask for a full breakdown up front, because that is what they have always asked for and every supplier has sent one.

What got taken was the order of operations

Nobody stole a design in that story, and nobody stole code. What left was the decomposition.

Knowing a booking flow is fourteen pieces rather than five, which piece has to exist before the next makes sense, and that hold-and-release logic oversells the last room unless handled at the write: that is the expertise. The typing was never the expensive part.

Price your last unpaid scoping session. Four hours reading their existing flow, two on a call, three writing it up. Nine hours at your floor rate, producing the most valuable artifact in the engagement, sent with no terms attached and no expectation of payment. Defensible while the output was inert. A different trade now.

The proposal is two documents that got stapled together

Most proposals contain two things with different economics.

A commercial document: the outcome, the cost, the timing, the terms, and why you. Sales material, and it should go out fast and freely to anyone who asks.

A specification: task list in sequence, architecture, data model, edge cases, acceptance criteria. A deliverable with a price on it, and the first thing you build rather than something you send to find out whether you get to build anything.

Copy the split below and adjust it for your discipline.

One test draws the line: if a competent person with a model could act on the item, it is paid.

Paid discovery, and the sentence that makes a client accept it

Selling the specification is the correct structure for work whose main unknown is what the work is, and it was right before any of this. Pricing a job you've never done before covers the arithmetic and when the spread makes a fixed price indefensible.

Price it against hours, not against the build: estimate the discovery honestly, multiply by your floor rate, quote that figure. For the hotel booking flow that is roughly a week: auditing the existing flow, mapping rates and availability, listing edge cases, writing it up so a third party could execute it.

The client owns that document outright and can take it anywhere. Say so explicitly. It is the concession that makes the sale, and the honest position, because a plan they paid for is theirs.

The script:

Before I can give you a fixed price for the build, I need
to do the scoping properly — otherwise I'm either guessing
high to cover myself or guessing low and coming back to you
for more later.

So I'd do that as a small paid piece: [X days], [$Y]. You
get a written specification: task breakdown, data model,
the decisions that need making and my recommendation on
each. It's yours — if you take it to another supplier or
build it internally, it still works.

Go ahead with the build with me and I'll credit [$Y]
against the first invoice.

The opening paragraph is the argument, and it is about their exposure to a guessed number rather than about protecting your work. They already recognize that problem. "It's yours" then removes what they are suspicious of, since you are not selling a locked document.

The credit-back is optional and costs real money. Offer it once, capped by the validity window.

Now the signal. A client who declines paid discovery but still wants the full breakdown has told you what it is for. Sometimes that is innocent, because every supplier before you handed one over free. Either way the response is identical: commercial proposal today, specification quoted as phase one. If the answer is no, you found that out for one email rather than nine hours.

The clause, and what it actually does

Two things go in writing: a validity date, and a line about who owns the contents until something is signed. The date is ordinary commercial hygiene, nobody objects to it, and it lets you state the ownership line without it reading as an accusation, since both sit in one block. The quote generator puts a valid-until date on priced line items, and the proposal generator produces the branded document with scope, pricing and terms. Both run in the browser, no signup, no watermark.

The clause:

Ownership of this proposal

The scope breakdown, task sequence, technical approach and
estimates in this document remain the property of [Your
Name] until a signed agreement for the work described is in
place, and are provided so you can evaluate that engagement.

Share it internally with anyone involved in the decision.

It is not licensed for use, in whole or in part, to carry
out the work described — by you, by another supplier, or
through an automated tool — without a signed agreement or a
separate written license.

Valid until [date].

The first paragraph attaches ownership to a signature rather than to a promise of good behavior, so it stops applying the moment they hire you. A clause that survives the engagement makes procurement slow down.

The internal-sharing permission is there because a rule the client breaks by eleven the next morning is worse than no rule. Proposals get forwarded; permit what happens anyway and the rest keeps its authority. "Through an automated tool" then names the scenario without accusing anyone, and reads as a term rather than a suspicion.

Be clear about what this achieves. It is a deterrent and a basis for a conversation. Almost no freelancer litigates a proposal, since the cost exceeds the fee by a wide margin, and copyright generally protects how a document is written rather than the plan it describes, which is the part that matters here. Anyone determined to take your breakdown will take it. What the clause stops is the accidental version, where a decent client's ops lead pastes the document into a chat window without treating it as a decision. Worth six lines, not insurance. This is not legal advice; where the sums are large, have a lawyer in your jurisdiction read it.

In the contract template it sits beside your IP terms, where the contract generator takes custom clauses and Worklyn's contracts add e-signature.

Tooling matters less than the split, though it is not neutral. Most proposal software prints one long document containing everything you type, which is the format this post argues against. Bonsai starts at $15 per user per month. Whether your stack holds the commercial document and the priced spec as two artifacts, then converts only the signed one into a contract and an invoice, is the question the Bonsai alternative comparison is built around.

Show judgment, not the build order

Withhold everything and you lose to whoever showed more, because clients do not reward caution and a vague proposal reads as inexperienced.

Detail and judgment are different, and clients respond to judgment. Naming what will go wrong, and why you would build against the obvious approach, proves you have done this before. A numbered task list does not, because anyone with a model produces one in forty seconds.

Before:

Phase 2 — Booking engine (weeks 3–5)
2.1 Availability model: rooms, room types, rate plans,
seasonal overrides
2.2 Search endpoint, date-range and occupancy filters
2.3 Hold logic: 15-minute cart hold, released by a job
2.4 Concurrency guard on the last available room
2.5 Payment intent created before hold expiry
2.6 Cancellation windows and partial-refund rules

After:

The booking engine is where this either works or produces
support tickets for a year, and two decisions drive it.

First, whether a held room is a real reservation or a soft
hold. The obvious implementation oversells your last room
when two people book within the same few seconds, which is
the failure the OTAs never have and your guests notice.

Second, whether cancellation rules live in code or as data
your front desk can edit. In code, every seasonal policy
change comes back to me as a paid change request, and I'd
rather it didn't, even though that's slower in week three.

Both decisions, and the sequence they sit in, are in the
specification. That's phase one.

The second version is shorter and wins more work. It proves familiarity with a specific failure mode, tells the client something about their business they did not know, and declines a change-order revenue stream in front of them. It hands over no build order.

The same principle governs the rest of the document, and what belongs in a proposal and what to cut goes through it section by section. When the price question lands before any of this exists, answering the rate question is the earlier conversation.

What changed on the client's side

This is the same repricing running through the rest of freelance work, and independent sources agree on its shape. Writing and coding job posts fell 21% in the eight months after ChatGPT's launch, relative to manual-intensive work. Across 1.8 million Freelancer.com posts, software integration carried 3.82 times higher budgets than content generation. Upwork's Future Workforce Index 2026 reports generative-AI creative production with contract starts up 90% year over year while earnings per contract fell 13%, against complex AI-augmented work up 45%.

Execution got cheap. Specification and judgment did not. Your proposal has been sitting on the wrong side of that line, given away free, while the work it describes gets billed.

The next thirty minutes, and the rest of the month

In the next 30 minutes: open the last proposal you sent and draw a line through it. Above the line is commercial, below is specification, and the part below took most of the writing time. Then paste the clause and a validity date into your template.

This month: quote paid discovery on the next three inquiries that want a full breakdown before committing. Track how many accept and what the decliners were worth. If all three accept, your price is low. If none do and they were serious buyers, look at the framing before the price. Either way you have replaced nine unbilled hours per pitch with revenue or an early no.

Worklyn keeps the commercial proposal and the priced specification as separate documents that convert into a contract and then an invoice without retyping, so the scoping you sell ends up on an invoice instead of in an email.