Key Takeaway
Pricing freelance work well is less about finding the right number than about the right structure: match fixed-price, time-and-materials or retainer billing to how clear the scope is, put the scope and revision limits in writing, and position yourself as a specialist so clients cannot compare you on price alone. This article deliberately quotes no rates, because published figures disagree and go stale quickly.
Freelance pricing is one of the topics Indonesian developers struggle with most consistently. The default strategy, setting a low price to win work and planning to raise it later, tends to stick, because clients anchor on the first number they see. I've watched classmates and senior developers navigate this, and the pattern I noticed is that the developers who do well rarely win on price. They win on structure: a clear pricing model, a written scope, and a niche that makes direct price comparison hard. This guide is about those three things, and it intentionally leaves out rate figures.
Domestic and International Clients Price Work Differently
Indonesian freelance developers usually serve two quite different markets: domestic clients (Indonesian businesses and individuals) and international clients, often found through global platforms. They differ in more than budget. Domestic SME clients tend to think in total project cost and expect to negotiate, while international clients on platforms are more used to time-and-materials contracts, milestones and written scope. Rather than trusting a published rate table, look at what comparable profiles show on the exact platform and niche you are targeting, on the day you are pricing. That is the only market data that applies to you.
Reading the Market Without a Rate Table
Platforms such as Upwork, Arc.dev and Toptal show you the competition directly: profiles with similar skills, similar time zones and similar track records. Compare yourself with that set rather than with country averages, which mix junior generalists with senior specialists and hide the spread that actually matters. Notice what the strongest profiles in your niche emphasise. It is usually specific outcomes, a focused skill set and evidence of delivered work, and that, more than the number on the profile, is what clients are buying.
Fixed Price vs. Time and Materials: When to Use Each
Time-and-materials billing, where the client pays for the time actually worked, suits work where the scope is unclear, requirements will evolve, or the client understands iterative development. A fixed project price suits work where the scope is well defined, requirements are stable, and you can estimate the effort with confidence. With domestic SME and individual clients, a fixed price is often necessary because they focus on the total cost and are less familiar with time-based billing. With international clients on platforms, time-and-materials billing with a contract cap is often the safest structure for both sides. Whichever you choose, build an explicit contingency into fixed-price estimates, because scope additions described as small changes are common.
Choosing a pricing model
──────────────────────────────────────────────────────────────
Situation Model that usually fits
──────────────────────────────────────────────────────────────
Scope written down and stable Fixed project price
Scope unclear or still evolving Time and materials, with a cap
Ongoing maintenance after delivery Monthly retainer
Client fixated on the total cost Fixed price per milestone
New client, no shared history Small paid first milestone
──────────────────────────────────────────────────────────────
Whatever the model, write down:
- what is in scope, and what is explicitly out of scope
- how many revision rounds are included
- what triggers extra billing, and how it is billed
──────────────────────────────────────────────────────────────Before any client conversation, work out your own floor: the lowest price that still covers your living costs, the taxes you owe, and the hours you will spend on work you cannot bill, such as proposals, admin and revisions. Treat that floor as a line you will not cross, not as your target. Your target should reflect the value of the outcome to the client and what comparable specialists in your niche ask.
Positioning: Escaping the Price Competition
The freelancers who do best tend to escape price competition by positioning themselves as specialists rather than generalists. 'I build websites' competes on price. 'I build Next.js applications with Coretax e-Faktur integration for Indonesian SMEs' has far fewer direct competitors. Local knowledge of Indonesian business regulations, local payment methods and the language is an advantage that foreign developers cannot easily replicate. Pair it with domain expertise such as fintech, ERP or healthcare, and you are selling outcomes rather than hours.
Indonesian-Specific Pricing Challenges
Several factors make pricing harder for Indonesian freelancers. The culture of bargaining (tawar-menawar) means clients often expect to negotiate, so leave room above your floor. The expectation of ongoing free support after delivery (revisi tak terbatas, unlimited revisions) has to be scoped out explicitly in the contract. Partial or late payment is common with some SME clients, so a payment schedule with an upfront deposit protects you. And budgets differ between client types and regions, so one price rarely fits every client.
# Freelance contract essentials for Indonesian developers
SCOPE_DOCUMENT_TEMPLATE = """
Project: [Name]
Client: [Company / Individual]
Scope: [Exact features — numbered list]
Explicitly OUT of scope:
- SEO optimization
- Mobile app (web only)
- Email marketing integration
- Ongoing hosting management
Revisions included: [N] rounds of feedback per deliverable
Additional revisions: billed as agreed in [section]
Payment schedule:
- Deposit before work begins: [agreed share]
- At approved mockup / staging delivery: [agreed share]
- At final delivery + handover: [agreed share]
Maintenance after delivery: separate retainer agreement
"""
# Enforce the scope document: "small changes" cost hours you won't bill
# without it. Reference it politely but firmly when requests expand.
My Approach to Pricing at the Time
At the time of writing I was a part-time developer still in school, and my focus was my part-time job rather than freelance work. From observing the market and researching this post, my plan for contract work was to aim at international clients from the start, for their clearer scope expectations and more established contract norms, rather than competing on price in the crowded domestic market. A strong English-language portfolio and GitHub presence was the prerequisite, which is why I invested in them before I needed them.
The most common reason freelance developers end up earning less than they planned is unlimited revisions and uncontrolled scope creep. Clients, especially SME owners, often don't distinguish between revisions (correcting what was specified) and new features (adding what wasn't in scope). Without a written scope that says what is included and what triggers extra billing, every small change costs you unpaid hours. Use a simple scope document and refer back to it when requests expand. Charging for extra scope is not rude; it is professional.
Platforms and Channels for Indonesian Freelancers
The main channels Indonesian developers use for freelance work are: Upwork, an open marketplace that is useful for building an early track record; Arc.dev, a marketplace that vets developers before listing them; Toptal, a highly selective network that screens applicants heavily and is worth targeting once you have senior experience; direct LinkedIn outreach, which carries no platform fees and suits specialised niches; and local Indonesian platforms such as Projects.co.id, which connect you with domestic clients and help you build Indonesian references. Each channel attracts a different type of client, so where you look shapes the work you get as much as how you price it.
The Long Game: Building Recurring Revenue
The most stable freelancers I've seen aren't constantly hunting for new projects: they have a small number of long-term clients on retainer. A retainer is a recurring fee for a defined number of hours or deliverables. The most natural path to one is a successful project that creates ongoing needs: build a client's web app, then maintain and update it; implement an ERP module, then provide ongoing customisation and support. Recurring work smooths out the feast-or-famine cycle and lets you be more selective about new projects.
Update: I've since graduated from Swiss German University and now work full-time as an AI Forward Deployed Engineer at Commsult Indonesia. This post reflects where I was at the time of writing.