How to Price a First Freelance Project

Before quoting a price, describe the point at which the job is finished. One draft and one revision is a different commitment from “until everyone’s happy.” Estimate the time for the whole job, including meetings, revisions, and delivery, before you put a number in front of the client.

A practical example

Imagine a client wants a two-page guide. Before putting a price beside “write guide,” list the jobs the client will not see: collecting the source material, resolving conflicting comments, and handing over the final file.

Illustrative estimate for one guide
Work included Hours
Briefing and source review 2
Writing and editing 4
One consolidated revision 2
Communication and delivery 1

Nine hours at an internal target of $50 an hour gives $450. Add $30 for an agreed project expense and the illustrative quote is $480, before any applicable taxes. The rate is an assumption, not a market benchmark. At eleven hours, the same fee leaves $450 after the expense, or about $41 per hour before overhead and taxes.

“$480 covers one two-page guide using the source material you provide, one round of combined feedback, and delivery of an editable file. Interviews, design, and further revisions are not included. I’ll quote any extra work for approval before starting it.”

If you cannot tell whether the sources are usable, ask to see them before offering a fixed fee. You can also quote a short discovery phase rather than padding every line to cover an unknown. After delivery, compare the actual hours in each row with your estimate. The row that ran over is the one to investigate next time.

Define the scope before you price

A price is only meaningful when both sides agree on what it covers. Write down the deliverables, the number of revisions included, the platforms or formats involved, and the dates that matter. Then list what is excluded, such as hosting, content writing, or training after launch. A short scope statement turns a vague request into a set of items you can estimate one by one.

If the client cannot describe the outcome, ask them to describe a finished project in plain terms. You can then propose a scope that matches that picture, and the quote will be easier to defend.

Estimate the effort for each task

Break the scope into tasks and estimate the hours for each one. Include discovery, planning, production, review, and handover. Many beginners price only the visible work and forget the time spent on messages, file transfers, and revisions. A simple way to test your estimate is to imagine doing the work on an ordinary week. Would the schedule hold, or would the project spill into the following month?

For example, an illustrative project might include four hours of planning, twelve hours of production, and three hours of review. Those hours give you a starting point before you consider risk.

Add a margin for uncertainty

First projects carry more risk than repeat work. You may not know the client’s approval process, the state of their existing files, or how long their feedback will take. Add a margin to cover that uncertainty. Some freelancers add a fixed percentage, while others add a contingency for specific risks, such as unfamiliar software or a tight deadline. Whichever method you choose, make the margin visible enough that you can explain it if asked.

Avoid padding the price so heavily that the client cannot justify it. The aim is a fair estimate that accounts for what you genuinely do not know.

Turn hours into a price

Choose a rate you can defend, then multiply it by your estimated hours. Suppose your target rate is forty dollars an hour and your estimate is nineteen hours. The base price would be seven hundred and sixty dollars before any margin. Adding a fifteen percent contingency brings it to about eight hundred and seventy-four dollars. These figures are only an example. The point is to show how each assumption affects the final number.

Consider whether a fixed price or an hourly rate suits the project. A fixed price can work well when the scope is clear. An hourly rate may be safer when the client is still deciding what they want.

State your assumptions in the quote

A quote should say what it assumes. Examples include the number of revision rounds, the client providing content by a certain date, and the use of a specific file format. If an assumption changes, the price can change with it. Writing assumptions protects both sides, because the client can see what they are buying and the freelancer has a clear basis for any change request.

Explain the quote simply

When you send the quote, explain how you reached it in a few sentences. You might describe the main deliverables, the phases of work, and the number of revisions. Avoid a long justification. A clear, short explanation builds confidence, and it invites the client to discuss which parts matter most to them.

Check the numbers after the first project

Once the project is finished, compare the actual hours with your estimate. Note which tasks took longer and which were quicker than expected. Use those notes for your next quote. Your first project is the start of a record, not a final verdict on your pricing. Over several projects, your estimates will become more reliable.