Read a sample: 1. Negotiating Without a Salary
The client likes your work. After a short conversation, they ask, “What would you charge?”
You know you should have an answer, but the request is still blurry. They want a new website, though you do not know how many pages it needs. They mention a deadline, but not who will supply the content. They ask for “a few revisions,” without explaining who will review the work or how decisions will be made.
A number offered too quickly may become an agreement to do more work than you expected. A long silence may feel uncomfortable, especially if you are eager to win the project. Neither reaction means you are bad at negotiation. It means you have reached a point where a useful question may be more valuable than a quick quote.
For a freelancer, negotiating compensation is rarely just a discussion about a rate. It is a conversation about the work, the time it may require, the responsibilities on each side, and the conditions under which you will be paid. The fee matters, of course. So do the details that determine what that fee is meant to cover.
This chapter introduces a way to see those details before you make a proposal. We will follow one hypothetical project from the first inquiry to a written agreement, then use it to map the decisions you will make in your own work.
When an employee accepts a salary, the compensation is usually attached to an ongoing role. The employer defines a position, and the employee receives pay under the terms of that employment. Depending on the arrangement, the employer may also provide equipment, administrative support, paid time off, or benefits.
Freelance work can look very different. A client generally pays for a defined service, a period of availability, or work completed under an agreement. The freelancer may be responsible for finding clients, preparing proposals, buying equipment, keeping records, and managing gaps between projects. Those responsibilities take resources even when they do not appear on a client invoice.
That distinction makes a simple salary-to-hourly comparison incomplete. In a hypothetical example, a freelancer invoices $1,200 for a project. That $1,200 is project revenue, not a salary payment that can automatically be treated as money available for personal spending. Business costs, taxes, and the time spent finding and managing the work all matter when deciding whether the fee supports the freelancer’s goals.
The client may not see those underlying calculations, and you do not need to justify every expense in a negotiation. But you do need to understand them for yourself. A rate that sounds generous when compared with an employee’s hourly wage may be less attractive once it has to support the rest of a freelance business.
Freelance arrangements also vary. Some clients supply software or materials; others expect you to use your own. One assignment may occupy you steadily for months, while another requires a short burst of work followed by an uncertain search for the next client. The point is not that freelance revenue is inherently better or worse than a salary. It is that the numbers serve different purposes and need to be evaluated in context.
In the next chapter, you will build a planning benchmark that accounts for the work and costs your fees need to cover. For now, keep the distinction clear: the amount a client pays is the starting point for your calculation, not the final measure of what you earn from the engagement.
Imagine that Maya is an early-career freelance web designer. A small specialty food shop contacts her after seeing a site she designed. The owner, Elena, writes:
> “We need to refresh our website before our new shop opens. Can you send me a price?”
Maya could answer immediately with a fee for a website. But “website” is a category, not a workable description of this particular job. A modest refresh might mean updating text and images on a few existing pages. It might also mean a new design, online ordering, product photography, copywriting, and coordination with several people.
Maya replies:
> “Thanks for getting in touch. I’d be happy to learn more about the refresh. Could you tell me what you want the site to help customers do, which pages or features you have in mind, and when you’d like it ready? Once I understand the work, I can suggest a scope and fee.”
This answer does three things. It shows interest, asks for information that will affect the work, and gives Elena a clear next step. It does not promise a price before Maya understands what she would be pricing.
You can use the same approach in almost any service business. A writer needs to know more than “we need articles.” A bookkeeper needs to know more than “our records need help.” A consultant needs to know more than “we want a strategy.” The first task is to turn a broad request into a shared understanding.
A client may experience the project as one purchase: a website, a report, a campaign, or a set of photographs. To quote and deliver it responsibly, you need to see the smaller decisions inside that purchase.
Start with the outcome. What is the client trying to accomplish? Elena wants customers to find the new shop and understand what it sells. That outcome gives Maya a basis for discussing what belongs in the project. It does not mean…