What hidden work should I include in a freelance quote?

Review discovery, meetings, project administration, QA and testing, deployment, revisions, handoff and other delivery work that is necessary but easy to omit from the first estimate.

Should I add a generic buffer instead?

A contingency buffer can cover genuine uncertainty, but known work is clearer when estimated explicitly. Separate expected work from uncertainty so you can explain and review the quote later.

How do I improve future estimates?

Compare planned and actual hours by category after delivery. Repeated differences can reveal which activities you routinely underestimate.

Free checklist · no signup

Price the work around the work

The obvious deliverable is rarely the whole project. A website may take 30 build hours, but the commercial reality can also include discovery, calls, testing, deployment, revisions and handoff. If those hours are predictable, make them visible before the quote instead of hoping a generic margin absorbs them.

Build a free project quote See the full pricing workflow

This is a planning checklist, not a rule for inflating quotes. Include work you reasonably expect to perform; use a separate contingency for genuine uncertainty.

Seven categories to check before you send the quote

1 · Discovery and clarification. Brief review, requirements calls, research, technical investigation and the time needed to turn an ambiguous request into a workable plan.

2 · Meetings and communication. Kickoff, status calls, stakeholder reviews, written updates and decision follow-up. A recurring 30-minute call can become meaningful project time.

3 · Project administration. Scheduling, file organization, access coordination, invoices, approvals and other operational work needed to keep delivery moving.

4 · QA and testing. Browser/device checks, content review, bug fixing, acceptance testing and verification after changes. Testing is delivery work, not an optional afterthought.

5 · Deployment and handoff. Production release, configuration, migration, documentation, training, credentials handoff and final verification.

6 · Included revisions. Define how many review rounds the price includes and estimate the time they are likely to consume. New deliverables should go through change control rather than silently becoming another revision.

7 · Closeout and learning. Final acceptance, outstanding payment, archive/handoff, support boundaries and a short planned-versus-actual review that improves the next estimate.

Turn the checklist into a quote

Estimate the known categories first. Then add direct project costs and a deliberate risk buffer for uncertainty. PracticalKit's free browser workflow keeps the estimate, scope, payment structure and post-project review connected so the assumptions can be checked after delivery.

Calculate the quote Price added scope later

When a reusable workbook helps

A one-off calculator is enough when you only need today's number. If you want to retain the baseline, quote, payment structure and actual project result for reuse, the prepared Pro XLSX is designed for that continuity. You can inspect the real five-sheet sample before deciding whether the planned $19 one-time product is useful; public checkout is not active.

Inspect the Pro XLSX sample

Frequently asked questions

What hidden work should I include?

Start with discovery, meetings, administration, QA/testing, deployment, revisions and handoff, then add any service-specific work your delivery history shows you repeatedly perform.

Should I just add a buffer?

Use explicit estimates for known work and a separate buffer for uncertainty. That makes the quote easier to explain and the post-project review more useful.

How do I improve the next quote?

Record actual hours by category and compare them with the plan. Patterns across several completed projects are stronger evidence than one unusually easy or difficult job.

All free tools · Pricing retrospective · Pro preview