The short answer
To do freelance programming, you choose a specific service you can deliver reliably and show proof of it with a portfolio. Then you find clients through your network, outreach, marketplaces or content. Before any coding starts, agree the scope, price and terms in writing. After that, the job is delivering in visible milestones, getting paid on schedule, and turning good projects into repeat work and referrals.
This guide assumes you can already code and walks through each stage in order. If you’re still building skills or haven’t had a paying client yet, start with our guide on becoming a freelance developer without experience.
1. Decide what you’ll sell
“I’m a developer” isn’t an offer. Clients hire people to solve a problem, so describe what you do in terms of that problem:
- “I build and maintain websites for local service businesses.”
- “I set up and customise Shopify stores.”
- “I automate repetitive data tasks with Python.”
- “I build MVPs for early-stage startups using React and Node.”
A focused offer makes everything else easier: your portfolio is more relevant, your marketing is clearer, and your estimates get more accurate because you repeat similar work. You can broaden later. Many freelancers find they get more work, not less, once they narrow their focus.
Pick something that sits where these overlap:
- Skills you already have, or can build quickly
- Work that clients actually pay for (look at job posts and talk to potential clients)
- Projects you’re happy to do repeatedly
2. Package your proof: portfolio, GitHub and a simple site
Clients want to see that you’ve done something like their project before. At a minimum, have:
- Two or three relevant projects, live where possible, ideally with a short write-up of the problem, your approach and the result
- A tidy GitHub profile with readable code and sensible README files. Technical clients and agencies may look at this.
- A simple personal site listing your services, your work, and how to contact you
- A clear LinkedIn profile whose headline says what you do and for whom
Testimonials from past clients or colleagues, even informal ones, add a lot of credibility once you have them.
3. Find clients
Most freelancers combine several channels. Expect some trial and error before you learn which ones work for your service.
Your network and referrals
Former colleagues, employers, friends and acquaintances are often the quickest route to a first project, because trust already exists. Tell people specifically what you do. Later, referrals from satisfied clients often become the most reliable source of work.
Direct outreach
Identify businesses with a visible problem you can fix, such as a slow or broken website, an outdated checkout, or a manual process. Send a short, personal message that names the specific issue and links to a relevant example of your work. Keep it brief and low-pressure. Response rates are usually low, so this works best done consistently over time.
Marketplaces and talent networks
Upwork, Freelancer.com and Fiverr let you reach clients who are already looking to hire. They come with competition, fees and platform rules, but they can provide early work and reviews. Some vetted networks screen developers and match them with clients. They’re harder to join but may offer better-paid projects. On any marketplace, tailored proposals that respond to the specific job post generally do better than generic ones.
Content and community
Writing about problems you’ve solved, sharing projects on LinkedIn or X, answering questions in developer communities, contributing to open source, or attending local meetups can all bring inbound enquiries. This channel usually takes a while to build but can keep paying off for years.
4. Run a proper discovery call
Before quoting, talk to the client to understand what they need. Many software project problems trace back to unclear requirements, and a good discovery conversation is the cheapest place to fix that.
Useful questions:
- What problem are you trying to solve, and why now?
- Who will use this, and what must they be able to do?
- What exists already (site, codebase, hosting, accounts, tools)?
- What does “done” look like to you?
- Is there a deadline, and what drives it?
- Who makes decisions and approves the work?
- Do you have a budget range in mind?
Listen for vague requirements, unrealistic deadlines, or a client who can’t say who makes decisions. These don’t always mean you should walk away, but they should shape your scope and price. For larger or unclear projects, some freelancers sell a short, paid discovery or planning phase before committing to a full quote.
5. Write a proposal and agree a contract
A proposal restates the client’s problem in your own words, then sets out what you’ll deliver, by when, and for how much. Keep it readable for a non-technical person. Offering two or three options at different scopes can help clients choose without haggling over a single number.
Pricing is a big subject of its own. Our guide on how much to charge as a freelance web developer covers hourly, fixed-price, retainer and value-based models and how to calculate a sustainable rate.
What the contract should cover
A written contract protects both sides. It doesn’t need to be long, but it should be clear about:
- Scope: what’s included, and explicitly what isn’t
- Deliverables and milestones: what you’ll hand over, and roughly when
- Price and payment terms: deposit, milestone payments, due dates, late-payment terms
- Revisions: how many rounds are included
- Change requests: how new requests are quoted and approved
- Client responsibilities: content, access, feedback within a set time
- Intellectual property: when ownership of the code passes to the client (commonly on full payment) and any third-party or reusable components you keep rights to
- Confidentiality, if relevant
- Ending the agreement: what happens to work and payment if either side stops
Templates are a reasonable starting point. For high-value projects, or if you’re unsure about liability or IP clauses, it can be worth having a lawyer review your standard contract once.
6. Deliver the work
Milestones and communication
Break the project into milestones the client can see, such as a design or prototype, a working core feature, and a completed build. Each milestone gives the client something tangible and a chance to give feedback early, when changes are cheap.
Good communication often matters as much as good code:
- Send short, regular updates on what’s done, what’s next, and any blockers
- Raise problems as soon as you spot them, along with options
- Put important decisions in writing, even if they were made on a call
- Use a staging environment so clients can review before anything goes live
Handling change requests
Clients will ask for things that weren’t in the original scope. That’s normal and can be good business, as long as you handle it consistently. Acknowledge the request, explain whether it’s in scope, and if it isn’t, give a quote or timeline impact for approval before doing the work. Small favours are fine occasionally, but say they’re favours so expectations don’t drift.
Handoff
A clean handoff makes you look professional and reduces support headaches later:
- Transfer all accounts, credentials and repositories the client should own
- Provide brief documentation: how to deploy, how to update content, key configuration
- Walk the client through the finished work
- Confirm in writing that the project is complete
7. Get paid
Cash flow is one of the most common difficulties for freelancers, so make payment straightforward:
- Ask for a deposit before starting fixed-price work, especially with new clients
- Tie further payments to milestones so you’re never far ahead of what you’ve been paid
- Invoice promptly, with clear payment instructions and a due date
- Follow up politely but firmly on late invoices
- Consider pausing work if payments fall significantly behind, and state this in your contract
Using invoicing or accounting software makes it easier to track what’s outstanding and keeps records for tax time.
8. Turn one project into ongoing work
Finding new clients takes time and effort, so repeat work from existing clients is valuable. Ways to encourage it:
- Offer maintenance or support. Websites and apps need updates, security patches and small changes. A monthly retainer can cover this.
- Suggest sensible next steps at handoff, based on what you learned during the project.
- Check in occasionally with past clients to see how things are going.
- Ask for referrals and testimonials when a project goes well.
Over time, a base of repeat clients can make freelance income noticeably more predictable.
9. Handle the admin
The business side is easy to put off and painful to catch up on. Basics worth setting up early:
- A separate bank account for business income and expenses
- A simple system for tracking income, expenses and receipts
- Setting aside a portion of each payment for taxes, since freelance income usually has no tax withheld
- Finding out whether you need to register as self-employed or make advance tax payments where you live
- Checking whether you need a business licence or insurance for the work you do
Rules vary by country and region. An accountant who works with self-employed people can save you time and help you avoid mistakes.
Using AI coding tools as a freelancer
AI coding assistants can speed up routine work like boilerplate, tests, documentation and first drafts of functions, which can make freelancing more efficient. They don’t replace fundamentals. You still need to understand, review and debug everything you deliver, because the client is relying on you, not the tool. Before pasting a client’s private code or data into a third-party tool, check your contract and the client’s expectations about confidentiality.
For a broader look at the role itself, including the pros and cons and who it suits, see our guide to what a freelance developer is.