What you'll learn

  1. Quick answer
  2. Pricing when you have no track record
  3. Scope: the thing that actually costs you money
  4. Getting paid
  5. Warning signs in a client
  6. Protecting your time and your degree
  7. FAQ

Quick Answer

Charge per project rather than per hour when you are slow. Write down what is included, what is not, and how many revisions are covered. Take part payment upfront and the rest before final handover.

Pricing when you have no track record

Charge per project, not per hour. As a beginner you are slow, so hourly billing punishes you for inexperience and forces you to justify every hour. A fixed price also gives the client certainty, which makes them more willing to say yes.

To reach a number, estimate the hours honestly, multiply by a rate you would be content with, then add fifty percent. That buffer is not padding — it covers the revisions, the meetings, the deployment problem and the week the client goes silent and then wants it urgently.

Do not price at the bottom of the market hoping for volume. Very low prices attract the most demanding clients, and it is much harder to raise a price with an existing client than to set it correctly at the start.

One below-rate project to obtain a reference and a live link is a reasonable investment. Two is a pattern.

Scope: the thing that actually costs you money

Scope creep is the single biggest reason student freelancers end up underpaid. It never arrives as a big request; it arrives as a series of small ones.

"Can we add a contact form?" "Can it also send WhatsApp messages?" "Can you make it work on my phone too?" Each sounds trivial. Together they double the work at the original price.

The fix is a written scope before starting. It does not need to be a legal contract — a clear email works:

  • What is included, listed concretely. "Five pages: home, about, services, gallery, contact. Contact form emails to one address."
  • What is not included. "Content and images provided by client. No blog, no payment integration, no ongoing maintenance."
  • How many revision rounds are covered. Two is standard.
  • What happens for extra work. "Additional features quoted separately."

Then when a new request arrives, you have a pleasant answer: "Happy to add that — it's outside the original scope, so it would be an extra X. Shall I quote it?" Most clients accept this immediately. What causes friction is having no agreement to point at.

Getting paid

Structure payment so you are never far ahead of the money.

A workable split for small projects: 40% upfront, 30% at an agreed milestone, 30% before final handover. The upfront portion filters out clients who were never serious, which is valuable by itself.

The most important rule: hand over the final deliverable after the final payment. Show the work on your own hosting, record a demo video, share screenshots — but transfer the code, the domain or the production deployment once you are paid. Leverage disappears the moment they have everything.

This is not distrust; it is the standard arrangement in professional work, and stating it plainly at the start is normal. Clients who object to any upfront payment at all are the ones most likely not to pay.

Send a simple invoice with a number, date, description and total. It looks professional and gives you a record.

Warning signs in a client

  • Vague about what they want and reluctant to write it down. This becomes endless revisions.
  • "This is simple, shouldn't take long." Frequently precedes a request that is neither.
  • Promises of future work as a reason to reduce your price now. The future work rarely arrives.
  • Wants everything before any payment.
  • Urgency with no deadline reason. Manufactured pressure is usually a negotiating tactic.
  • Asks for free work to "prove" yourself beyond a small sample.

You are allowed to decline. A bad client can consume a month you needed for placements, and the money rarely compensates. Saying "I don't think I'm the right fit for this" is complete and requires no justification.

Protecting your time and your degree

Set a weekly cap in hours and hold to it. Freelance work expands to fill whatever is available, and a client's urgency will always feel more concrete than your own coursework.

Agree communication boundaries early — a response within a working day is professional, and being available at midnight sets a permanent expectation you will regret.

Keep every finished project in your portfolio with permission, since a live client project is stronger evidence than a personal one. Ask for a short written reference immediately on completion, while they are pleased and it is fresh.

And keep perspective: the purpose of student freelancing is income plus experience, not a career shift away from the work that gets you a first job. See earning while studying for the wider trade-offs.

Frequently Asked Questions

How much should I charge as a student freelancer? Estimate the hours, apply a rate you are content with, and add fifty percent for revisions and unforeseen work. Prefer per-project pricing while you are still slow, since hourly billing penalises inexperience.
Should I take payment upfront? Yes, typically thirty to fifty percent. It filters out clients who were never serious and means you are never working far ahead of the money. It is standard practice, not distrust.
What do I do if a client keeps asking for changes? Point to the agreed number of revision rounds and offer to quote the extra work. This is why the scope must be written down before you start.
What if a client refuses to pay at the end? This is why the final deliverable transfers after the final payment. Demonstrate the work without handing over the code, domain or production deployment until you are paid.
Can I show client work in my portfolio? Ask permission, and most clients agree. If the work is confidential, describe the problem and your approach without naming them or showing identifiable screenshots.