What the person hiring you is actually worried about

You lost a project you were plainly qualified for, and the reply said they had decided to go another way. Nothing in that sentence tells you what happened, so most people conclude it was the price.

It usually wasn't.

This is inference, not testimony

Nobody was interviewed for this post. There are no quotes, no anonymous confessions, no "one hiring manager told us." What follows is structural analysis: a description of what the person on the other side of your proposal is measured on, what happens to them personally when a freelance engagement goes wrong, and what they can therefore be expected to select for.

That is a weaker claim than an interview, and a more reliable one. Incentives are visible from the outside. Opinions aren't.

Their downside is much bigger than their upside

Take a buyer of the kind most freelancers actually deal with: a manager two levels below the person who signs, holding a budget line for the quarter and a delivery date that was already promised to somebody else. (Illustration, not a case study.)

If you do excellent work, they get a modest amount of credit, shared with the team. If you disappear in week three, they own it alone. They own the missed date, the explanation upward, the scramble to replace you, and the fact that they were the one who vouched for an outsider.

So they are not shopping for the best work available. They are shopping for the lowest variance that clears the bar. That is the single idea this post keeps returning to, because all four of the things below are versions of it.

Once you see it, the strange parts of the process make sense: why they ask for references from work that is obviously weaker than your best; why they want a call before a proposal; why the person who followed up on Tuesday morning beat the person whose work was better.

Worry one: that you will vanish in week three

This is the big one, and it is mostly what the discovery call is for.

The signals they read are not the ones you think. They are not judging your enthusiasm. They are judging whether your plan has dates in it, whether the first checkpoint arrives soon enough that a problem would surface early, and whether you have said anything at all about what happens if you are ill.

What neutralizes it is a milestone schedule with real calendar dates and a first checkpoint inside the first week. Not because the first week's output matters, but because it converts a four-week leap of faith into a five-day one.

Milestones and payment
1. Kickoff + content audit ....... Mon 12 Oct €2,500 on signature
2. First full draft .............. Mon 26 Oct €2,500 on delivery
3. Revisions + handover .......... Mon 09 Nov €2,500 on acceptance

If I am unavailable for more than two working days, I will tell you the
same day and we will agree a revised date in writing. No milestone slips
without a written note from me first.

Line by line: the dates are Mondays because a slipped Monday is visible on the same working week and a slipped Friday isn't. The first milestone is close, which is the entire point. Payment is attached to each milestone, which is doing two jobs at once — it reassures them that you have a reason to keep moving, and it stops you carrying four weeks of unbilled work before a single invoice goes out.

Cut the unavailability sentence if you are subcontracting and can genuinely name cover. Replace it with the name.

If you want the schedule to look like a document rather than an email, the proposal PDF generator runs in the browser with no signup and no watermark, which is enough for a small engagement.

Worry two: that you will turn out to need managing

Every hour they spend managing you comes out of a week that is already full. A freelancer who needs three unscheduled calls and a daily thread costs more than the invoice says, and the buyer knows it before you do because they have been through it.

The counterintuitive fix is to ask for more, in writing, up front.

A short list of what you need from them, with dates, reads as competence rather than as neediness. It also converts an open-ended obligation into a finite one, which is what they actually want.

What I need from you
- Brand assets and current copy ........ by Fri 09 Oct
- One named approver for the draft ..... by Fri 09 Oct
- Feedback on the draft ................ within 4 working days

I will send one written update every Friday. Between updates I don't
need meetings. If a dependency lands late, the following milestone
moves by the same number of days and the fee does not change.

That last sentence is the one to keep even if you cut everything else. It tells them delay is not free, without threatening them, and it is the clause that saves you when the draft sits with an approver for two weeks.

One named approver is worth arguing for. Two approvers with different opinions is the most reliable cause of a revision round nobody priced.

Worry three: your invoice is a problem for someone they have never introduced you to

This is the risk freelancers underrate most, because it doesn't feel like a risk. It feels like admin.

Their side: many organizations raise a purchase order before work starts, and accounts payable will not pay an invoice that cannot be matched to one. If your invoice arrives without the PO number, or in a different legal entity's name from the contract, or without the tax treatment their system expects, it does not get rejected loudly. It sits. Somebody will chase it in a month.

The buyer has been on the receiving end of that. They have had a supplier email them personally, three times, about an invoice they have no authority over.

Four questions on the call remove the whole category:

• Do you raise a purchase order for this, and does the PO number need to appear on the invoice?
• Which legal entity is the contract with, and is that the same entity the invoice goes to?
• Is there a fixed payment run, and what is the cut-off to make it?
• Which address do invoices go to, and should the project contact be copied?

The last two are pure time-to-cash. A client on a monthly payment run with a cut-off on the 25th will pay a 26th-of-the-month invoice roughly three weeks later than a 24th-of-the-month one, on identical terms.

Say in the proposal that you will quote their PO number on every invoice and that your invoices carry your registered entity, tax number and the applicable VAT treatment. It is two lines and it removes you from a category of supplier they have suffered.

This is also where general accounting software tends to let freelancers down: it is built around the year-end return rather than around producing a document that survives a purchase-order match, which is the comparison the Xero alternative page is about.

Worry four: that you cannot be set up as a supplier before the start date

Onboarding lag is invisible until it eats your start date, and then it eats your first payment too.

Depending on the client, getting you into their system can mean a tax form, a supplier portal registration, a verification call to confirm your bank details, a certificate of insurance, and occasionally a security questionnaire. Two weeks of that on top of 30-day terms is a 44-day gap between agreeing the work and seeing money.

The tax form is the part most non-US freelancers get wrong. US clients need a W-9 from US persons and a W-8BEN or W-8BEN-E from everyone else, and the wrong one, or a missing one, triggers backup withholding on your fee. The mechanics of getting through vendor setup without losing a fortnight are in the vendor onboarding post.

What to put in the proposal is a single line offering the pack: tax form, bank details on letterhead, insurance certificate, entity details, available the day the contract is signed. Buyers who have onboarded suppliers before will notice that sentence. Buyers who haven't won't, and it costs you nothing.

Getting the invoice itself out on day one of the payment window rather than day four is the other half of the same problem, which is what Worklyn's invoicing is built around — invoices generated from the contract and the tracked hours rather than retyped at month end.

Removing risk is what lets you stop competing on rate

Here is the money argument, and it is the reason any of this matters beyond winning one job.

A buyer choosing between two freelancers with comparable work will take the cheaper one, because they have no other basis for the decision. A buyer choosing between one freelancer with comparable work and one who has already answered the four questions above is not making a price comparison any more. They are choosing between a known quantity and an unknown one, with their own quarter on the line.

That is the only reliable route to being the more expensive option and still winning. It is not confidence and it is not positioning. It is having removed the four things that could go wrong for them personally.

Your portfolio gets you shortlisted, not chosen

Worth saying plainly, because a lot of effort goes into the wrong artifact.

The portfolio decides whether you make the list. Past a certain threshold of obvious competence, it stops discriminating — everyone on a three-person shortlist can do the work, or they wouldn't be on it. What separates them is entirely the risk profile.

If you are losing at the shortlist stage, work on the portfolio. If you are getting to the final two and losing, the portfolio is not the problem and more of it won't help.

The next 30 minutes, and the next month

In the next 30 minutes: open your last three proposals and check whether any of them contained a calendar date, a named dependency, or a sentence about invoicing. If all three are scope and price, you have been sending the buyer a document that answers a question they weren't asking.

This month: assemble the onboarding pack once and keep it in one folder. Tax form completed and signed, bank details on letterhead, insurance certificate if you carry one, registered entity and tax number. It takes an afternoon and you will send it for years. Then add the four procurement questions to whatever you use for discovery calls, so they get asked before the proposal rather than after the first invoice goes missing.

Worklyn's proposals carry milestones and payment terms straight through into the contract and the invoice, so the dates the client agreed to are the dates that get billed.