Hourly or fixed price on Upwork for an automation or AI-built app?

The short answer

On a fixed-price contract you pay for a result. Each milestone is funded before the work starts and released after you approve what was submitted, or after the review window runs out. On an hourly contract you pay for time. You are billed every week for the hours the freelancer logged, and you can question the hours but not the quality.

For a non-developer, that difference decides it:

• Building something with a clear result (a workflow, a chatbot, a finished feature): use fixed price with milestones, each ending in a test you run yourself.
• Open-ended fixing or investigating (an AI-built app that breaks in ways nobody understands yet): hourly with a weekly cap can be fairer to both sides, for a short, defined period. Then switch to fixed price once the problem is understood.

What you are actually paying for

The question to ask is not “which is cheaper” but “what triggers the money”.

I have paid for work both ways. On fixed-price work, the payments went out at set points in time. On milestone work, I released each payment after checking what that stage had produced. The difference is what triggers the money: a date, or a result you have looked at. An hourly contract adds a third trigger: time spent.

	Fixed price (milestones)	Hourly
What you pay for	A submitted piece of work	Hours logged in the week
When you pay	You fund each milestone before work starts	Every Monday, for the week before
Your lever	Approve, or request changes	Weekly hour limit; dispute hours
What a dispute is about	Whether the submitted work should be paid	Whether the hours were worked, not whether the work is good
Who carries the risk of overruns	The freelancer, within the agreed scope	You

How fixed price works on Upwork

From Upwork’s help center, checked October 2026:

• You fund each milestone up front, at least $5 per milestone. The money sits as work in progress.
• The freelancer submits work for your approval before the funds are released.
• You have 14 days to review a submission. You can approve, request changes from the workroom, or pay a different amount. If you do nothing, the funds are released automatically.
• Each resubmission starts a new 14-day window. Requesting changes is not a loss of time on your side.
• If a submitted milestone goes unpaid, the freelancer can open a dispute. You then have five days to respond, and an Upwork agent can propose a non-binding resolution. Binding arbitration is a further, paid step.

The practical reading: fixed price puts your protection in the approval click, and 14 days is enough to watch an automation over several scheduled runs. Use it. The acceptance checklist for unattended automations is the test to run in that window.

How hourly works on Upwork

From the same help center:

• The billing week runs Monday to Sunday, UTC. You are invoiced on Monday at noon UTC and charged automatically.
• You can review the hours from Monday noon until Friday, and you can dispute hours within five days after the billing period ends.
• A dispute is reviewed against the freelancer’s Work Diary. Upwork says you cannot dispute over work quality.
• You can set a weekly hour limit on the contract.
• Hourly Payment Protection is a freelancer protection. It covers time tracked with Upwork’s desktop app, within the weekly limit, on a verified account. Upwork says clients are refunded for hours that do not qualify, such as time added manually.

So the hourly protections are about whether the hours are real. Nothing in the hourly process checks whether the automation runs. That part is still yours to test.

Which to choose for your project

For AI-built apps, the investigation step is common. The AI-built app handover checklist lists what to check once the fix is delivered, and the one-off fix or ongoing developer guide covers whether to keep the same person on afterwards.

An example: fixing an app built with an AI tool

Say you built a booking app with an AI coding tool. It works, but every time you change one screen, something unrelated breaks, and you do not know why. You cannot write “done” yet, because nobody knows what is wrong.

A reasonable split looks like this:

1. Hourly, one or two weeks, with a weekly cap. The developer reads the code, finds why changes break other parts, and writes a short note at the end of each week: what they found, what they recommend, and a fixed-price quote for the fix.
2. Fixed price, one to three milestones. The fix itself, with a test per milestone: “change the booking screen text; the payment screen still works; the three test bookings still go through.”
3. Monthly terms after that. A small retainer or a per-fix rate for the next breakages, agreed before the last milestone is approved.

The hourly part buys understanding, and you limit its size with the weekly cap. The fixed-price part buys a result, and you protect it with the review window.

How to set up each so it protects you

Fixed price. Three to five milestones, each with:

1. What exists at the end (“the workflow writes one CRM record per test enquiry”).
2. The test you will run (“ten real enquiries, sent through the real form”).
3. What counts as a pass (“ten records, correct owner, no duplicate when I resend one”).
4. The revision time if it fails, before the next milestone is funded.

The fixed price or milestones guide has a three-stage split for an automation with an AI step.

Hourly. Four lines in the contract terms or the first message:

1. A weekly hour limit you can afford to lose if the week produces nothing.
2. A short written note at the end of each week: what was tried, what was found, what is next.
3. A point at which the work becomes a fixed-price quote (“once the cause is found, quote the fix”).
4. Everything committed to your repository or exported to your account as it goes.

Either way, agree maintenance before the contract ends. The maintenance guide has the six lines.

Where it goes wrong anyway

• Hourly for a build with a clear result. You carry every overrun, and the dispute process cannot help if the work is poor.
• Fixed price with milestones that are only dates. “Week 1, week 2” with no test is a payment plan. The approval click needs something to check.
• Approving to keep things moving. If the test fails, the milestone is not done. Request changes; the resubmission gets a new 14-day window anyway.
• No weekly limit. An hourly contract without a cap is an open tab.

Wrap-up

Pay for results when you can name them, and for time only when you cannot yet. Fixed price on Upwork gives you a 14-day window to test each milestone before the money moves; hourly gives you a weekly look at the hours but no say on quality. Choose the one whose lever you will actually use. When you are ready, post the project on Upwork and set the contract type in the job post.