The first quote should be rational, not perfect
There is no single correct price independent of scope, client and market. The goal is a logical model that covers costs, protects against uncontrolled scope and is understandable to the buyer.
Combine cost calculation, time estimation, risk analysis and value assessment. Competitor prices alone are not enough.
Four layers of price
- cost — what delivery truly costs you
- time — billable and non-billable hours required
- risk — uncertainty, responsibility and pressure
- value — what the outcome changes for the client
A simple starting formula
Project price = estimated hours × baseline rate + direct costs + risk buffer + optional value adjustment.
This is a starting point, not an automatic rule. As the service becomes repeatable, you can move away from visible hours and sell packages.
1. Separate the price floor from the selling price
The price floor is the amount below which the project no longer covers your time, costs and risk. The selling price may be higher because it also reflects client value, demand, specialization and responsibility.
What to include
- minimum delivery cost
- target margin
- outcome value
- risk and responsibility
- specialization level
- market conditions
Practical note
Do not negotiate below the price floor. If the budget is lower, reduce scope instead of subsidizing the project with your time.
2. Calculate annual business cost, not personal spending alone
A freelance rate must also finance tools, taxes, contributions, leave, illness, sales, administration and periods without client work. A personal monthly budget is not the full business cost.
What to include
- owner compensation
- taxes and contributions
- software and equipment
- accounting and banking
- sales and marketing
- leave and illness
- financial reserve
Practical note
Upwork’s current rate guidance also starts from monthly expenses and the number of hours you realistically plan to bill.
3. Estimate the real number of billable hours
Not every working hour can be sold to a client. Leads, calls, proposals, internal revisions, learning, invoicing and organization consume part of the month.
What to include
- production hours
- discovery and meetings
- sales and follow-up
- administration
- learning
- leave and breaks
- buffer
Practical note
Working 160 hours per month does not mean billing 160 hours. Non-billable time is often especially high for beginners.
4. Calculate a baseline hourly rate
A baseline hourly rate is useful even when the final offer is project-based. Divide annual costs and target compensation by realistic billable hours, then add a safety margin.
What to include
- annual financial target
- annual costs
- billable hours
- reserve
- margin
- price rounding
Practical note
Example: if you need $30,000 per year and plan 1,000 billable hours, the baseline is $30/hour before risk and value adjustments.
5. Estimate the project bottom-up
For a first quote, estimating individual stages is more reliable than guessing the entire project. List tasks, time, costs and dependencies, then add them with a buffer.
What to include
- discovery
- research
- production
- testing and quality control
- meetings
- revisions
- implementation
- administration
Practical note
Asana lists bottom-up estimation among core methods for forecasting time, cost and resources. It takes effort but reveals hidden stages.
6. Add a buffer that matches uncertainty
The less you know about the client, technology, scope or dependencies, the greater the estimation risk. The buffer should reflect uncertainty rather than be a random percentage.
What to include
- incomplete brief
- new tool
- third-party dependencies
- short deadline
- unclear approval process
- many stakeholders
Practical note
A three-point estimate—optimistic, most likely and pessimistic—helps incorporate uncertainty deliberately.
7. Choose the right pricing model
Hourly, project, package and retainer pricing solve different problems. The model should match scope predictability, workflow and client expectations.
What to include
- hourly for uncertain scope
- project-based for a clear outcome
- package pricing for repeatable services
- retainer for ongoing availability
- day rate for intensive sprints
- hybrid for project plus maintenance
Practical note
Stripe notes that services are commonly billed hourly, project-based or on retainer; the model should support margin and cash flow.
8. Build packages around outcomes
A package should help the client choose a scope level rather than hide an arbitrary block of hours. A simple structure is minimum, recommended and expanded.
What to include
- clear outcome
- differences between tiers
- number of deliverables
- deadline
- revisions
- post-delivery support
- add-ons
Practical note
Packages do not need to be artificial. When one option is clearly appropriate, present one recommendation with optional extensions.
9. Price revisions and the approval process
Revisions create cost even when the client uses only part of the allowance. Include the number of rounds, feedback method and response deadline.
What to include
- number of rounds
- scope of one round
- single feedback owner
- feedback deadline
- changes after approval
- rate for additional rounds
Practical note
A revision round is not unlimited ideation. It should move the work toward the previously agreed outcome.
10. Separate add-ons from the base scope
Rush delivery, extra formats, implementation, data migration, consultation and maintenance should not disappear inside one price. Add-ons improve clarity and protect margin.
What to include
- rush delivery
- additional versions
- implementation
- training
- licences and purchased assets
- maintenance
- extra meetings
Practical note
The base offer must work on its own. Add-ons should not hide elements required to deliver the promised outcome.
11. Protect against scope creep inside the quote
Project pricing works only when the included scope and change process are clear. A vague quote turns a fixed price into an unlimited service.
What to include
- deliverable list
- out-of-scope items
- assumptions
- client dependencies
- change procedure
- price and deadline impact
- approval before work
Practical note
Asana defines scope creep as uncontrolled expansion of requirements that leads to delays, budget overruns and overload.
12. Adjust price for value and consequences
The same amount of time can create different value. Fixing a sales-blocking error, producing urgent campaign material or building a system used by thousands may justify more than a low-responsibility task.
What to include
- impact on client revenue
- time saved
- cost of alternatives
- error risk
- number of users
- urgency
- strategic importance
Practical note
Value-based pricing does not mean taking an arbitrary share of client profit. Scope, proof and a rational explanation are still required.
13. Do not discount without an exchange
A discount should change something for both sides. Reduce price for less scope, a longer deadline, prepayment, case-study permission or higher volume—not simply because the client asks.
What to include
- smaller scope
- fewer revisions
- longer deadline
- prepayment
- volume package
- ongoing work
- publication permission
Practical note
Do not imply that the original price was arbitrary. Every change should have a visible business reason.
14. Protect the deposit and payment schedule
Price is only one part of a quote. Payment timing matters too. Small services may use full prepayment, while larger work may use a deposit and milestones.
What to include
- deposit percentage
- work-start condition
- milestones
- payment deadline
- final-file condition
- late payment
- cancellation
Practical note
Stripe notes that deposits help fund initial resources and reduce nonpayment risk. Refund and cancellation terms should be explicit.
15. Show the logic without exposing every internal hour
The client should understand the relationship between scope, responsibility and price. They do not need your complete internal cost calculation.
What to include
- project goal
- scope
- deliverables
- timeline
- assumptions
- price and payments
- options
- quote validity
Practical note
Instead of defending every hour, show what the client receives, which risk you accept and which conditions enable delivery.
16. Test price in the market, but not randomly
The first price is a hypothesis. After each proposal batch, analyze responses, lead quality, objections, delivery time and effective rate instead of reacting to one “too expensive.”
What to include
- proposals sent
- response rate
- calls
- won projects
- loss reasons
- actual time
- margin
- client satisfaction
Practical note
No sales may result from the offer, proof, prospect list or process—not only price.
17. Update pricing after real projects
After delivery, compare estimates with reality. Record which stages were underestimated, which questions should have been asked earlier and which extras should become paid.
What to include
- estimate versus actual time
- effective rate
- costs
- revisions
- client delays
- scope changes
- outcome value
- stress level
Practical note
Raise prices when work sells consistently, demand rises, responsibility increases or effectiveness improves. Do not wait only for a new calendar year.
Simple quote template
- project goal
- base scope
- deliverables
- out-of-scope items
- timeline
- revision rounds
- price
- add-ons
- payment schedule
- quote validity
First seven-day plan
- day 1 — calculate annual costs and billable hours
- day 2 — calculate the baseline rate
- day 3 — break the service into stages
- day 4 — define buffer, revisions and add-ons
- day 5 — build one or three options
- day 6 — prepare quote and brief templates
- day 7 — test the quote on a real example
30-day plan
- week 1 — cost model and scope
- week 2 — first proposals and calls
- week 3 — objection analysis and communication improvements
- week 4 — compare estimates with actual time and update pricing
Minimum pricing sheet
- stage
- task
- optimistic hours
- most likely hours
- pessimistic hours
- direct cost
- risk
- final price
Common mistakes
- random pricing
- dividing personal costs by every hour in the month
- ignoring sales and administration
- no buffer
- unlimited revisions
- hidden add-ons
- discount without changed terms
- no deposit
- pricing without a brief
- no post-project review
How to respond to “too expensive”
- ask what the client is comparing against
- return to the expected outcome
- check whether scope is clear
- offer a smaller option
- remove add-ons
- change deadline or payment schedule
- do not discount automatically
When to raise the price
- you consistently win most relevant proposals
- availability is limited
- projects carry more responsibility
- the old price does not cover full cost
- you have specialization and proof
- quality and speed improved
Key conclusion
A good first quote is not the lowest number the client accepts. It is the price at which a clearly defined project can be delivered well and on time without hidden self-subsidy.
Start with costs and a baseline rate, but add risk, scope, revisions, payment terms and outcome value.
Briefstreak can organize the data required for pricing—scope, budget, deadline, requirements and client answers. It reduces guessing but does not replace calculation.
