Web development · 9 min read

Fixed price or hourly? How US small businesses should contract an offshore development team

Fixed price, hourly or retainer? How US small businesses should contract an offshore dev team, with a 12-clause checklist covering IP, code and payments.

On this page
  1. What is the difference between fixed price, time and materials, and a retainer?
  2. When should a US small business choose fixed price?
  3. When is time and materials the better choice?
  4. How should milestone payments work on a software project?
  5. Who owns the code when you hire an offshore team?
  6. What should an offshore development contract include?
  7. How does Digital Architect contract with US clients?
  8. Frequently asked questions
  9. Sources

Choose fixed price when you can describe what you need in writing. Choose time and materials when the scope is genuinely unknown, and cap the hours. Use a retainer for ongoing work after launch. Whatever the model, insist on milestone payments, a written IP assignment, and code and accounts held in your name.

This article is general information, not legal advice. Have a US attorney review any contract before you sign it.

What is the difference between fixed price, time and materials, and a retainer?

They differ in who carries the risk of the work taking longer than planned.

Fixed price means one agreed price for a defined scope. US federal contracting rules describe a firm-fixed-price contract as placing "maximum risk and full responsibility for all costs" on the contractor. If the build takes longer, the vendor absorbs it.

Time and materials (T&M) means you pay for hours worked at agreed rates, plus any direct costs. The same federal rules allow T&M only when it is "not possible" to estimate the work accurately at the start. They also note it gives the contractor no built-in incentive to work efficiently. That is why those rules require a ceiling price and close oversight.

Retainer means a recurring fee, usually monthly, for a reserved block of time or availability. It suits maintenance, small changes and ongoing support.

Fixed priceTime & materialsRetainer
Best forA defined website, app or MVPResearch, unclear scope, rescue projectsPost-launch support and small changes
Budget certaintyHighLow unless cappedHigh per month
FlexibilityChanges need a written change orderHigh; redirect work any weekMedium; limited by hours included
Who carries riskVendor carries overrun riskYou carry overrun riskShared; the fee is due whether or not you use it
How you payMilestones tied to delivered workWeekly or monthly invoices for hoursFixed monthly fee, often in advance
Red flagVague scope with a suspiciously low priceNo hour cap and no weekly reportsFees with no record of what was done

When should a US small business choose fixed price?

Choose fixed price when you can write down what "done" looks like. Most marketing websites, booking sites, e-commerce builds and first-version apps fit this description.

Fixed price works because it forces both sides to agree on scope before money moves. That conversation is useful even if you never sign. If you cannot describe the scope yet, start with a short paid discovery phase. Then quote the build as a fixed price. Our article on how to scope an MVP walks through that step.

Watch for one trap. A fixed price on a vague scope just moves the argument to the end of the project. Ask for a written plan listing screens, features and exclusions before you agree to a number.

When is time and materials the better choice?

T&M fits work you cannot define in advance. Examples include fixing an unfamiliar codebase, integrating with an undocumented system, or running early experiments.

If you choose T&M, add controls:

  • A hard weekly hour cap. Upwork, for example, lets clients set a weekly limit on hourly contracts. Only hours within that limit are billable.
  • A total budget ceiling that requires your written approval to exceed.
  • Weekly reports showing what was done and what is next.
  • A review point after a few weeks to decide whether to convert remaining work to fixed price.

The risk with T&M is not the hourly rate. It is open-ended hours with nobody accountable for the total.

How should milestone payments work on a software project?

Split the price into milestones. Release each payment only after you have seen and checked that piece of work.

A typical structure ties payments to visible outcomes. Approved designs, a working staging build, and launch are common checkpoints. Avoid milestones like "50% of development complete." You cannot verify a percentage.

Escrow adds protection when you are working with someone new. On Upwork fixed-price contracts, the client deposits funds into escrow before work starts. You can fund the whole contract or only the first milestone. After the freelancer submits a milestone, you have 14 days to approve it or request changes. If you do nothing, the funds release automatically. Put review time on your calendar.

Who owns the code when you hire an offshore team?

Not automatically you. This is the most important clause in the contract.

Under US copyright law, the person who creates a work initially owns its copyright. A "work made for hire" is the exception. It covers employees working within the scope of their job. It also covers commissioned works, but only in nine listed categories, with a written agreement signed by both parties.

According to law firm Amundsen Davis, custom software is not one of those nine categories. Writing "work made for hire" into a contractor agreement may therefore not transfer ownership. You need a written assignment of copyright. The US Copyright Office notes that a transfer "generally must be made in writing and signed by the owner of the rights conveyed."

Cross-border work adds another layer. A DLA Piper article warns that work-for-hire principles "may not exist" outside the US. It adds that broad assignment clauses are not always enforceable under local law. Its practical advice is to sign every needed document while the relationship is active. Chasing a contractor later is much harder.

Ownership also covers more than code. Domains, hosting, app store listings and analytics should be registered to your business. ICANN states that the domain registrant assumes "sole responsibility for the registration and use" of the domain. If your developer is the registrant, they control it.

What should an offshore development contract include?

Use this checklist when you review a draft. Each item is a clause or an attached document.

  1. Scope and acceptance criteria. Attach the written plan. Define how each milestone is tested and accepted.
  2. Price and payment schedule. List each milestone, its amount and what triggers payment.
  3. Change process. New requests need a written change order with price and timeline impact before work starts.
  4. IP assignment. A present-tense assignment of all rights in code, designs and documentation to your company, effective on payment.
  5. Further assurances. The developer agrees to sign any extra documents needed to record your ownership.
  6. Subcontractors. Anyone else who touches the work signs the same assignment and confidentiality terms.
  7. Open-source and third-party components. The vendor lists them, with licenses, before delivery.
  8. Source code access. The repository lives in your account from day one, not only at handover.
  9. Accounts and credentials. Domain, hosting, app stores, email and analytics are registered in your business's name.
  10. Confidentiality. A nondisclosure clause covering your business information, data and unreleased product.
  11. Warranty period. A defined window after launch during which the vendor fixes defects at no charge.
  12. Termination and handover. If either side ends the contract, you receive all work paid for to date, plus credentials.

Ask your attorney which governing law and dispute venue to name. For more on choosing a vendor, see our guide to hiring an offshore agency.

How does Digital Architect contract with US clients?

We work fixed price by default. It starts with a free 30-minute call. Within 5 to 7 business days, you receive a written plan. It covers what we will build, in what order, how long it takes, and a fixed price. Payments are split into milestones and released after you have seen the work. You get a weekly progress link. Every screen is designed in Figma before we write code. You own the code, design files, domain and accounts, all set up in your name. Bigger new features are quoted upfront the same way. Extra ideas go on a written phase-2 list instead of quietly growing the bill. This is how we built Build-Hive, a UK construction SaaS for web, iOS and Android. Its core platform was built in 12 weeks. You can read the full steps in our process.

Frequently asked questions

Is fixed price more expensive than hourly?

Sometimes the quoted number is higher, because the vendor is carrying the overrun risk. Compare the total you are likely to pay, not the rate. An hourly project with no cap can easily end above a fixed quote.

Do I need a separate NDA before sharing my idea?

A short NDA before detailed discussions is reasonable and common. Once you sign the main contract, its confidentiality clause should cover the rest of the project. Make sure that clause also binds any subcontractors.

Can I switch from time and materials to fixed price later?

Yes. A common pattern is a short T&M or paid discovery phase to define the scope. The build is then quoted as a fixed price. Agree on this path in writing at the start.

What happens if the developer disappears halfway through?

That risk is why the contract checklist matters. If the code sits in your repository and the accounts are in your name, another team can pick up the work. Milestone payments mean you have only paid for work you have already seen.

Planning a website or app and want a fixed price before you commit? Talk to Digital Architect. Book a free 30-minute call and get a written plan with a fixed price within 5 to 7 business days.

Sources

Want it done for you?

Skip the reading. Talk to the person who wrote it.

Book a free 30-minute call with Arjun and leave with a first read of what to fix.

WhatsAppBook a free call

Free · No obligation

Let's talk about your project

Book a free 30-minute call with Arjun, the founder, or leave your number and we'll call you back.

Step 1 of 2 · A few questions

30 minutes on Google Meet with Arjun, the founder. Free, with no obligation. Your answers help him come prepared.

Times from 11 am to 11:30 pm IST, every day. We use your details only to arrange this call. Privacy policy