The mistakes that lose the deal, by stage

A deal you lose at the proposal was usually already lost earlier, in a two-line email you sent within an hour of the first enquiry.

That is the awkward part of diagnosing lost work. The symptom shows up at the end. The defect is upstream.

So this is organized by stage rather than as a list of dos and don'ts. Five stages, one dominant failure at each, and what it costs in money rather than in vibes.

The deal we'll follow

One engagement, carried through all five stages, so the same money is on the table each time.

A €9,000 website rebuild. Four weeks of work, around 60 of your hours, about €1,500 in direct costs — stock, a plugin license, a subcontracted illustration. One decision-maker plus a finance approver you have never spoken to. That is an illustration, not a real client, and the arithmetic below is there so you can substitute your own numbers.

At €9,000, after the €1,500 of costs, that is €7,500 across 60 hours: €125 an hour. Hold on to that figure. It moves in stage four.

Stage one: you quote before you know what the job is

The enquiry arrives. It says something like "we need a new site, roughly what would that cost?" And you answer it, because answering questions is polite and because you want to seem easy to work with.

That is the single most expensive reflex in freelance sales.

A number you give before you understand the scope is a number derived from nothing, and it becomes the anchor for everything afterward. If the real scope turns out to be larger, every attempt to move the price upward reads as a bait-and-switch. If it turns out to be smaller, you have overpriced yourself out of a job you would have wanted.

Worse, you have taught them that the price is available without the conversation, which means the conversation now has no reason to happen.

The reply that works is short, gives a real range, and attaches the range to conditions:

Happy to look at this.

Rebuilds like this usually land between €7,000 and €14,000 depending on
how many templates there are, whether the content is being rewritten,
and who has to sign off. I can be specific after 30 minutes on a call.

Are you free Thursday or Friday morning?

Three things that line is doing. The range is wide enough to be honest and narrow enough to disqualify a €2,000 budget without an awkward second email. The three variables tell them what actually drives the price, which is the beginning of the discovery conversation whether or not you get the call. And the closing question names two specific times, because "let me know when suits" moves the work of scheduling onto the person with less incentive to do it.

Cut the range entirely if you genuinely cannot bound it. Say so, and ask for the call anyway. What you must not send is a single number.

Response time matters more here than at any later stage, and less than people claim. Being first is worth something. Being first with a bare price is worth less than nothing.

Stage two: you take the brief instead of testing it

On the call, most freelancers write down what the client asks for. Then they propose exactly that, at a price scaled to exactly that, and lose to someone who came back with a different shape of project.

The client's brief is a guess. They wrote it from a problem they can feel and a solution they read about. Taking it at face value is the polite version of not listening.

Four questions change the outcome of the call:

What happens if this works? The answer tells you what the project is actually for, which is usually a revenue or a hiring or a launch problem sitting behind the deliverable. It also tells you what it is worth, which is not the same as what it costs you.

Who else has to approve this, and what will they care about? The finance approver you have never met is the person who will hold the invoice. The second stakeholder nobody mentioned is the person who will request the revision round that wasn't priced.

What have you already tried? Prevents you proposing the thing that failed last year.

What has been set aside for this? The version of the budget question that gets answered. "What's your budget?" invites "we don't have one yet." "What's been set aside for this?" implies a number already exists somewhere, and people generally tell you.

If the answer is genuinely no number, give them a shape rather than a figure: "projects of this size usually run in the low five figures — does that put us in the same conversation?" You lose nothing and you find out in one sentence.

Whether the project will be profitable is a separate question from whether you will win it, and the questions that predict margin are covered in the project qualification post.

Stage three: you apologize for the rate

The proposal goes out with the right number on it and a sentence underneath that quietly destroys it.

The apology takes standard forms. "I know this might be more than you were expecting." "There's some flexibility here." "Let me know if the budget is tight and we can look at it." "I've tried to keep this as lean as possible."

Every one of those tells the buyer, before they have asked, that the number is not the number. The negotiation now starts below your price rather than at it, and you started it.

The mechanism is simple: a price stated as a fact gets evaluated. A price stated with an apology gets tested.

Two versions of the same paragraph:

Before:
Total is €9,000. I know that might be a bit more than you had in mind
— happy to talk if the budget is tight, I can probably strip some
things out.

After:
Total is €9,000, in three payments of €3,000 on signature, first draft
and acceptance. That covers the six templates we discussed, one round
of revisions, and handover with a short walkthrough. Quote valid until
17 October.

The second version is not more confident. It is more specific, which is what confidence looks like on paper. It also names what the price buys, which is the only defence against a client mentally comparing your figure to a number they invented.

You can only write the second version if you know your floor — the rate below which the project is a loss once tax reserve, non-billable time and fixed costs are counted. The rate calculator works that backward from the income you need, the hours you can actually bill, and the weeks you intend to take off. A floor you have calculated is a fact. A floor you have felt is a negotiating position.

What belongs in the proposal document itself, and what to leave out of it, is its own post. The thing to fix at this stage is the tone of the sentence containing the number.

One more proposal-stage habit worth breaking: sending the proposal and letting the tool it was written in become the end of the trail. If the proposal, the contract and the invoice live in three places, the numbers drift between them and the client notices. That gap is the argument on the Bonsai alternative page — proposal software that stops at the proposal leaves the money side to be retyped.

Stage four: you discount before anyone asks you to

The client goes quiet for four days. You assume it is the price. You email offering 10% off.

Run the arithmetic on the deal we've been following. €9,000 fee, €1,500 of direct costs, 60 hours: €7,500 over 60 hours, €125 an hour. Take 10% off the fee and the costs don't move. €8,100 minus €1,500 is €6,600 over the same 60 hours: €110 an hour.

A 10% cut in price is a 12% cut in what you actually earn per hour, because the discount comes entirely out of the part you keep. On a project with heavier direct costs the effect is larger. Measuring that gap on projects you have already finished is what the effective hourly rate calculator is for, and it is a more useful number than your quoted rate.

The other cost is permanent. The discounted price is the price they will remember when they come back for the next project, and the one they will quote to whoever they refer you to.

When a discount is genuinely asked for, trade rather than cut. Every one of these preserves the rate:

Notice what each trade does: it changes what they get or when you get paid, not what an hour of your time is worth. The number on the page can move. The rate underneath it should not.

And if the four days of silence had nothing to do with price, which is the usual case, you have just paid €900 for a delay in their legal review.

Stage five: you leave the next step to them

"Let me know what you think" is where deals go to die.

A proposal with no named next action decays. Nothing dramatic happens; it just moves down the pile behind things with dates on them. Two weeks later the internal enthusiasm that generated the enquiry has dissipated and the answer is a soft no that never gets sent.

Close on a specific action, a specific date, and a stated consequence: "I'll hold the mid-October start until Friday the 10th — after that the next slot is early November." That is not pressure if it is true. Say it only when it is.

The second thing about this stage: the close is not the "yes." The close is the countersigned contract and the deposit clearing. Between the verbal yes and the money there is a legal review, a purchase order, a vendor setup, and a finance approver who has never heard of you. Deals die in that gap regularly, and they die quietly.

So attach the paperwork to the yes rather than after it. Send the contract the same day, with the deposit invoice, and start when the deposit lands rather than when the enthusiasm peaks. Worklyn's contracts go out for e-signature from the agreed proposal, which mainly removes the two days it takes most people to retype the scope into a second document.

The failure that runs through all five

Every stage above has the same shape underneath it: you are trying to be easy to deal with, and easy is being purchased with your margin.

Answering the price question immediately is easy. Accepting the brief is easy. Softening the number is easy. Offering the discount is easy. Leaving the next step open is easy.

The alternative is not being difficult. It is being specific — about the range, about what drives it, about what the price includes, about what you need and when. Specificity reads as competence to a buyer and as respect for their time, which is why it wins deals that friendliness loses.

If several stages are leaking at once, diagnose before you fix, because adding more leads to a pipeline that converts badly just makes the problem more expensive, and the stage-by-stage version of that diagnosis tells you which joint to look at first. Where freelance work actually comes from covers which channels are worth the hours in the first place.

The next 30 minutes, and the next month

In the next 30 minutes: open the last proposal you sent and search it for the apology. Look for "flexible," "happy to," "I know," "just," and "hopefully." Delete each one and read the paragraph again. That is the version you should have sent.

This month: write the three-line first reply once and keep it where you can reach it — range, the variables that drive it, two named times for a call. Then, on the next three enquiries, do not name a single number until after the call. Compare what those three proposals are worth against the three before them. If the average is higher, the reflex was costing you the difference all along.

Worklyn turns the agreed proposal into the contract and the deposit invoice without retyping, so the gap between a client's yes and money in the account is a day rather than a fortnight.