devlk
Log in Sign up
c/freelancing u/devlk Team

Should I charge hourly or a fixed price for my first freelance project?

Team FAQ: this question comes up often, so we've answered it below. Add your own experience, or a different view, in the comments.

Pricing the first project is stressful. Which model is safer?

1
1 comment
Sort by: Best Top New Old
devlk Team·

For your first projects, hourly (or small fixed-price milestones) is usually safer.

Hourly

  • ✅ Protects you when the scope is unclear or grows.
  • ✅ Simple to explain.
  • ❌ Some clients worry about open-ended cost, and you need to track time.

Fixed price

  • ✅ Clients like knowing the total cost, and you're rewarded for working efficiently.
  • ❌ Risky if you underestimate or the scope keeps growing. Beginners often underestimate.

A good middle ground for beginners: fixed-price milestones.

  1. Break the project into small milestones (design, feature A, feature B, deployment).
  2. Price each one separately, with a clear written scope.
  3. Agree that anything outside the scope is quoted separately.
  4. Get paid per milestone.

Whatever you choose:

  • Write down exactly what's included and what isn't.
  • Agree how many revision rounds are included.
  • Ask for a deposit or first milestone payment from new clients.

To work out what to charge, use how to set your rate as a remote developer. To bill properly, see how to invoice international clients.

1