Software Costs
How to Hire a Web App Developer: A Contractor's Guide
How to hire a web app developer as a non-technical owner: a sizing rule, cost math from wage data, the contract clauses on code ownership and red flags.
In this article
- How to hire a web app developer: size the work before you pick a model
- What does a web app developer actually cost in the US?
- Is cheap development really more expensive? Run the break-even
- Who owns the code? The law is less intuitive than the contract implies
- The ten clauses that decide whether you get burned
- Day-one account setup, and the 14-point readiness checklist
- How to vet a software partner before you commit the budget
- Red flags, ranked by what they cost you
- Worker classification: don't accidentally hire an employee
- When not to hire a developer at all
- What to do next
- Frequently asked questions
- Sources
The short answer on how to hire a web app developer, when you are a contractor and not a technologist, is that the rate you negotiate matters far less than the paperwork you sign and the accounts you own. People rarely get burned because a developer was expensive or cheap. They get burned because, nine months in, the copyright still belongs to the developer, the code lives in someone else's account, the domain is registered to a person who no longer answers email, and nobody can deploy the software without that one person's laptop. For a business whose dispatch, quoting or invoicing runs on it, that is not an IT problem. It is an operations problem.
All four of those are fixable in a single afternoon before work starts. None of them are fixable afterwards.
This article is for the owner or general manager of a contractor thinking about commissioning software, whether that is a replacement for part of a field service platform, a customer portal, or the glue between the tools you already pay for. It gives you a sizing rule that picks your hiring model from the volume of work rather than your budget. Cost math built from federal wage data so you can tell a real quote from a fantasy one, including a break-even model for the offshore question that probably contradicts what you have read. The contract clauses that control who owns the code, with the statutes behind them. A day-one account setup list. And a 14-point handoff checklist you can run before every payment.
Key takeaway: A "work made for hire" clause does not, by itself, transfer the copyright in software. Software is not one of the nine commissioned-work categories in the Copyright Act, so you need an express written assignment signed by whoever owns the rights. Check your contract for the word "assigns" today.
How to hire a web app developer: size the work before you pick a model
Most buying advice starts with your budget. Start instead with the volume of engineering work you expect over the next two years, because that is what determines whether a hiring model is sustainable. For a contractor, a rough guide: a single connection between two tools is small, a customer portal or a replacement for one module of your platform is medium, and replacing the whole stack of subscriptions that runs the company is large.
| Model | Fits when | Your job | Main failure mode |
|---|---|---|---|
| Freelancer, fixed scope | Under ~400 hours over two years; one clear deliverable | Write the acceptance test | They disappear mid-project; nobody else knows the code |
| Senior contractor or small team | 400–1,200 hours; you have someone internal who can review | Specify, review, accept | You become the de facto project manager by accident |
| Agency or managed team | 400+ hours and nobody internal to review | Set outcomes and budget | You pay for process you cannot see; the senior who sold it never works on it |
| In-house | 1,200+ hours a year on something core to revenue | Recruit, manage, retain | A single hire with nobody to review their work |
Two things in that table catch people out.
The first is the internal reviewer. If nobody on your side can judge an estimate or say "this is not done," then a contractor engagement quietly converts into an agency engagement where you are supplying the project management for free and doing it badly. Clutch's own comparison makes the same distinction in softer language: agencies bring project managers and QA, freelancers do not. That is the real product difference, and it is worth paying for when you lack it. For most contractors the reviewer is the office manager, not the owner, and she needs hours set aside to do it.
The second is that "in-house is cheaper" is usually false at small volumes, for reasons the next section makes concrete.
What does a web app developer actually cost in the US?
There are two useful anchors: what the market quotes, and what the labor actually costs. Compare them and most pricing confusion disappears.
What the market quotes
Upwork publishes its own rate bands on its web developer cost page: "Web Developers on Upwork Cost $15–$50/hr," broken down as $15–$25 an hour for entry level, $30–$50 for intermediate and $50–$200 for expert. That is a marketplace with a global supply base, so treat the low end as a statement about geography and seniority rather than a benchmark for anyone local.
What the labor costs
Federal data gives you a floor that no US vendor can go under for long.
- The median annual wage for web developers and digital designers was $99,520 as of May 2025, or $47.85 an hour, according to the BLS Occupational Outlook Handbook.
- Software developers, a more senior and more application-focused category, had a median annual wage of $135,980 over the same period, with QA analysts and testers at $104,300 (BLS).
- Wages are not the whole cost. Benefits averaged 30.0 percent of total compensation for private industry workers in June 2026, with total compensation at $46.89 an hour against $32.82 in wages and salaries (BLS Employer Costs for Employee Compensation).
Grossing up the median web developer wage for that benefits share gives a fully loaded employer cost of about $142,000 a year, or $68 an hour across 2,080 paid hours. Doing the same for a software developer gives about $194,000, or roughly $93 an hour.
Key takeaway: Paid hours are not productive hours. Subtract about 15 percent for holidays, vacation and sick time, then about 20 percent of what remains for meetings, administration and learning, and 2,080 paid hours becomes roughly 1,414 productive engineering hours. At $142,000 loaded, that is about $101 per productive hour for a mid-level in-house web developer.
That number reframes everything. An in-house mid-level developer costs about as much per hour of real work as a mid-tier agency, and you carry the recruiting, management and retention risk on top. In-house wins when you have enough work to keep the person busy for years and the accumulated product knowledge is itself valuable, not because the hourly math is better. A 20-truck contractor rarely has that much software work.
It also tells you what a US agency quote has to clear. If direct loaded labor is $68 to $93 an hour and a developer bills roughly 70 percent of their paid hours, direct labor per billed hour is already $98 to $133 before any sales, project management, QA, tooling or profit. A US-based agency quoting $75 an hour with US-based engineers is either not paying median wages, subcontracting the work elsewhere, or not making money. Any of those is worth knowing before you sign.
The benefits percentage above is an all-industry private-sector average, not a technology-sector figure, so treat it as an approximation. The direction of the error is conservative: tech benefits packages tend to be richer, not thinner.
A rate card you can budget against
For a typical business application of the kind a contractor might commission (logins and roles, 10 to 15 screens, two integrations such as accounting and your field app, reporting, and a payment flow) plan on 1,000 to 1,400 hours of engineering, plus design and QA. Here is what that costs at different rates.
| Blended rate | 1,000 hours | 1,400 hours | Who quotes here |
|---|---|---|---|
| $25 | $25,000 | $35,000 | Offshore marketplace, entry level |
| $50 | $50,000 | $70,000 | Offshore senior, US junior |
| $100 | $100,000 | $140,000 | US senior freelancer, small US team |
| $150 | $150,000 | $210,000 | US agency |
| $200 | $200,000 | $280,000 | US agency, specialist or regulated domain |
Add 10 to 20 percent of the build effort per year for maintenance, dependency upgrades and small changes. If the build is meant to replace a subscription, run the arithmetic against that subscription before you hire anyone: our guide to what building and running office software really costs walks through it, and the Stack Audit does it for your actual bills. If what you are weighing is a platform you can configure instead of a build from scratch, our Retool vs custom internal tools comparison shows where per-seat pricing overtakes building.
Is cheap development really more expensive? Run the break-even
The standard warning is that a cheap build costs more once you count the rewrite. Run the arithmetic and that turns out to be a weaker claim than it sounds, which is worth knowing because it explains why so many sensible people keep hiring at $28 an hour.
Take 1,200 hours of work. A competent US team at $130 an hour costs $156,000. Now suppose a $28-an-hour team needs 30 percent more hours for the same output, so 1,560 hours at $28 is $43,680. Let f be the fraction of that output a US team later has to rebuild at $130 an hour.
| Fraction rebuilt | Cheap build | Rebuild cost | Total | vs. $156,000 |
|---|---|---|---|---|
| 0% | $43,680 | $0 | $43,680 | Saves $112,320 |
| 25% | $43,680 | $39,000 | $82,680 | Saves $73,320 |
| 50% | $43,680 | $78,000 | $121,680 | Saves $34,320 |
| 72% | $43,680 | $112,320 | $156,000 | Break-even |
| 100% | $43,680 | $156,000 | $199,680 | Costs $43,680 more |
On money alone, the cheap route stays ahead until roughly 72 percent of it has to be thrown away. Assumptions: a 1.3x hours multiplier, rebuild work priced at the US rate, and no change in scope. Move any of those and the break-even moves, so treat this as a model for your own numbers rather than a finding.
So where does the money actually go wrong? Three places, none of them the hourly rate.
Calendar time. If the software saves or earns $20,000 a month, six months of extra delay costs $120,000, which is more than the entire rate difference above. Write down what a month of delay is worth to you before you optimize for rate. For a contractor there is a second clock: your busy season. A project that slips from February to July is not five months late, it is a year late, because it cannot go live until the peak is over.
Your attention. Cheap engagements consume senior management time in specification, review and rework coordination. That time has a real cost and it does not appear on any invoice.
Total loss. The genuinely expensive outcome is not a bad build; it is no build. You cannot get the source code. The copyright was never assigned. The cloud account is in someone else's name. You pay full price a second time and lose the year. That failure mode is governed entirely by the contract and the accounts, which is why the rest of this article is about those. If you are already taking a system back from a previous developer, the handover checklist in our guide to replacing the system your business has outgrown lists what to get into your company's name first.
Who owns the code? The law is less intuitive than the contract implies
This is the question buyers get wrong most often, and the answer sits in three sections of the Copyright Act.
Copyright starts with the author, not the payer. Under 17 U.S.C. § 201(a), "Copyright in a work protected under this title vests initially in the author or authors of the work." Paying an invoice does not move it.
"Work made for hire" has two halves, and only one of them helps you. Section 101 defines a work made for hire as, first, "a work prepared by an employee within the scope of his or her employment"; and second, a work "specially ordered or commissioned" in one of nine listed categories (a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas) and only "if the parties expressly agree in a written instrument signed by them."
Read that list again. Computer software is not on it. Software commissioned from an independent contractor cannot be a work made for hire under the second half, no matter what the contract says. And whether your developer is an "employee" for this purpose is not something you get to label: in Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), the Supreme Court held that a court "first should ascertain, using principles of general common law of agency, whether the work was prepared by an employee or an independent contractor," weighing factors such as skill, who supplies the tools, where the work happens, payment method, benefits and tax treatment. An outside developer working from their own equipment on their own schedule will land on the contractor side of that test. The U.S. Copyright Office covers the same ground in Circular 30.
So you need an assignment, in writing, signed. Section 204(a) is blunt: "A transfer of copyright ownership, other than by operation of law, is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed or such owner's duly authorized agent."
None of this is legal advice, and the drafting should go through your counsel. But it does tell you exactly what to search your draft agreement for: the word assigns, in the present tense, covering copyright in all deliverables. A contract that only says "all work product shall be a work made for hire" can fail on the single asset you were buying.
Ownership is not all-or-nothing: data, instance and the people who run it
For a business that is not buying code to maintain itself, "who owns it" splits into three questions, and a good vendor answers each separately. Your data: exportable in standard formats, free, whenever you ask. The software built for you: whether you hold the copyright, or a perpetual license, and whether you can have the source code. The thing that runs it: if the vendor operates the system with its own tooling, those tools are theirs, and you rent them.
Our own answer, so you can compare it with anyone else's: with Fleurant AI the client owns their data and their software instance, and rents the agent fleet that operates it. Data export in standard formats is free at any time; on cancellation there are 60 days of read-only access plus a full export; source code escrow is available on request. We spell this out because the lock-in in an operated model is real, and a smart buyer should ask about it before signing with us or anyone else. Whatever you hire, get the equivalent three answers in writing.
What changes when the developer uses AI coding agents?
Most code written in 2026 passes through an AI coding assistant or agent at some point, and that affects how much of it copyright protects. In its January 29, 2025 report on copyrightability, the U.S. Copyright Office concluded that AI outputs can be protected "only where a human author has determined sufficient expressive elements," and that "the mere provision of prompts" does not qualify (U.S. Copyright Office, NewsNet 1060). The same report confirms that using AI to assist creation, or including AI-generated material in a larger human-authored work, does not bar protection for the human contribution.
For a buyer, three practical consequences follow. First, your assignment clause still matters: it transfers whatever rights exist, including in human-written and human-modified code, the architecture and selection of components. Second, some machine-generated portions may carry no copyright for anyone, so lean on confidentiality terms and on keeping the repository private, rather than on copyright alone. Third, ask the vendor to disclose which AI tools they use, confirm that a human reviews and tests every change, and keep the commit history that shows it. None of this is legal advice.
Three more ownership traps in ordinary contracts
Assignment conditioned on payment. This is the market standard, and it is reasonable, but you should know it applies to you. Upwork's Optional Service Contract Terms, in the version we reviewed in October 2026, state that "Upon Freelancer's receipt of full payment from Client, the Work Product … will be the sole and exclusive property of Client," and that "If payment is made only for partial delivery of Work Product, the assignment described herein applies only to the portion of Work Product delivered and paid for." Practical consequence: in a payment dispute, you own the paid-for parts and nothing else. Keep milestones small so a disagreement never strands a large unpaid chunk of your project, and never pay everything up front: a payment schedule tied to working modules is the single best protection you have.
Chain of title. An agency can only assign rights it holds. If its own engineers or subcontractors never signed assignments, the agency has nothing to give you. The same Upwork terms handle this by requiring that a freelancer who subcontracts "has entered into agreements with any such employees and subcontractors on confidentiality and intellectual property at least as strong as those in these Optional Service Terms." Ask for that representation and warranty by name.
Pre-existing and open-source components. Every real application includes third-party code. You need to know what, under which licenses, because some licenses obligate you to release your own source. Upwork's terms require a "bill of materials that identifies all Background Technology and other third-party materials" with the name, version, license and how each is used, and bar code whose use would require that the work product "be disclosed or distributed in source code form" unless agreed. Copy that requirement into your own agreement and ask for the bill of materials at every milestone, not at the end.
The ten clauses that decide whether you get burned
Hand this list to whoever reviews your contracts.
| Clause | What it must do | What happens without it |
|---|---|---|
| 1. IP assignment | Present-tense assignment of copyright in all deliverables, plus a duty to sign further documents | You paid for software you do not own |
| 2. Chain of title | Warranty that the vendor holds the same rights from staff and subcontractors | The vendor cannot assign what it never owned |
| 3. Open-source bill of materials | Itemized third-party components with licenses; no copyleft obligations without consent | You discover a license that forces disclosure of your own code |
| 4. Background technology license | Perpetual, irrevocable, royalty-free license to the vendor's reusable components | Your app depends on a library you must keep paying for |
| 5. Confidentiality with DTSA notice | Standard confidentiality plus the whistleblower immunity notice | You forfeit exemplary damages and attorney fees (below) |
| 6. Accounts and credentials | Vendor works in accounts you own; all credentials delivered on request | Hostage negotiation over your own domain |
| 7. Acceptance and security standard | Written acceptance criteria naming a security baseline | "Done" becomes an opinion |
| 8. Data handling terms | What the vendor may do with your customers' personal information, and what happens to it at the end | A compliance gap you inherit |
| 9. Exit and transition assistance | Paid transition hours at a pre-agreed rate, triggered by either party | The handoff costs whatever they decide it costs |
| 10. AI tool use | Disclosure of AI coding tools, human review of every change, no client data or secrets in tools without approval | Code of uncertain provenance and your data in someone else's model logs |
Three of these deserve a closer look because almost nobody gets them right.
The confidentiality clause nearly everyone drafts wrong
If your agreement governs the use of trade secrets or confidential information, federal law requires you to include a specific notice. 18 U.S.C. § 1833(b)(3) provides that "An employer shall provide notice of the immunity set forth in this subsection in any contract or agreement with an employee that governs the use of a trade secret or other confidential information," and that if the employer fails to do so, "the employer may not be awarded exemplary damages or attorney fees" in a Defend Trade Secrets Act action against that person. Critically, the statute defines "employee" to include "any individual performing work as a contractor or consultant for an employer."
In plain terms: your developer NDA needs a short paragraph telling the developer they are immune from liability for confidentially reporting a suspected legal violation to a government official or attorney, or for filing a trade secret under seal in court. Leave it out and you keep the confidentiality obligation but lose two of the remedies that make it worth enforcing. It costs one paragraph.
Acceptance criteria with a security baseline
"The vendor shall use industry best practices" is unenforceable. Name a standard. The OWASP Top 10:2025 lists the categories an application review should cover, among them Broken Access Control, Security Misconfiguration, Software Supply Chain Failures, Cryptographic Failures and Injection. The FTC's Start with Security guide makes the same point to businesses from the enforcement side: train engineers in secure coding, test for common vulnerabilities using frameworks like OWASP, verify that privacy and security features actually work, and make sure your service providers implement reasonable security measures, including verifying compliance rather than taking it on contract language alone. You do not need to understand the list. You need the contract to say the vendor will be tested against it, and to see the result.
Data handling, if you hold customers' personal information
A contractor's system holds names, addresses, phone numbers, gate and alarm codes and sometimes payment details. A developer who touches that data needs written terms on what they may do with it, who else can see it, how fast they must tell you about a problem, and what happens to it when the project ends: not just an NDA. Card data belongs with your payment processor and should never be stored in the application you commission. Privacy rules vary by state, so which laws apply to you is a question for your counsel, but the structural point holds everywhere.
Day-one account setup, and the 14-point readiness checklist
The paperwork protects you legally. Owning the accounts protects you practically, and it is faster.
Do this before work starts, yourself:
- Create the source-control organization in your company's name, then invite the vendor as a member with write access. Not the reverse. GitHub does support transferring a repository later, with issues, pull requests, history and redirects intact, but it needs administrator access on the source side. In other words, it needs the vendor's cooperation. Start in the right place and you never need it.
- Open the cloud account under your company billing. Give the vendor scoped access, not the root credentials. This also means the spend is visible to you from the first day rather than arriving as a line item on an invoice.
- Register the domain yourself, at your own registrar. Changing the registrant later can trigger a transfer lock: ICANN's Transfer Policy provides that "The Registrar must impose a 60-day inter-registrar transfer lock following a Change of Registrant," though a registrar may let the holder opt out beforehand. A 60-day window where you cannot move a domain is a bad thing to discover during a vendor dispute, and ICANN has approved reforms that would change this process once implemented, so check the current text when it matters.
- Stand up a secrets vault you control and require that API keys, signing certificates and database credentials live there rather than in a developer's password manager.
- Open analytics, payment processor and transactional email accounts in your company's name, then grant access. These are the quiet ones. People remember the repository and forget that the payment account and the sending domain reputation are also assets.
Then run this at every milestone, not at the end:
The last three items are the ones that separate working software from a demo. A new engineer should be able to clone the repository and run the application locally from the written instructions. Deployment should be a scripted pipeline rather than a person with a laptop. And someone should have restored the database from a backup and written down how long it took. If any of those three is a "no," you do not have a deliverable yet, whatever the demo looked like.
How to vet a software partner before you commit the budget
Portfolios tell you what a vendor has been near, not what they did. Here is what to substitute, in language a non-technical owner can use.
Ask what happens in your busy season. "If dispatch breaks on the hottest Saturday of July, who answers, and how fast?" A vendor with a written response commitment is telling you something. A vendor who says "we're always available" is not. Ask for the commitment in the contract, with its limits stated: next business day for ordinary issues and a few hours for urgent ones is honest; 24/7 from a two-person shop is not.
Ask for a walkthrough, not a demo. Request 45 minutes on a real project, with permission: the history of changes shows incremental work rather than three giant drops, tests exist and run, and the written instructions make sense to a stranger. You do not need to read the code; watch how they talk about it.
Ask how they would find out they were wrong. Good answers involve a prototype, a trial run on real jobs or a conversation with your dispatcher. Weak answers go straight to a technology choice.
Ask for the estimate behind the estimate. A number with no breakdown is a guess. Ask which parts they are confident about and which they are not, and what would make the uncertain parts worse. Vendors who name their own risks have been burned before and learned something.
Call a reference that did not go well. Ask directly: "Tell me about a project that went badly and what you changed." Then ask to speak to that client. Refusal is informative; so is a candid account. Ask us the same thing: Fleurant AI has no client in your trade to put you in touch with yet, which is why the Stack Audit exists. It costs $2,500, takes one to two weeks, is credited in full against a build started within 90 days, and shows you your own numbers before you commit to anything.
Check how they handle AI-written code. The right answer from a vendor is neither "we don't use it" nor "it writes most of our code." It is a review and testing policy: who reviews generated code, what tests must pass, and how the origin of the code is tracked.
Then buy a small piece of the real work. A paid one-to-two-week engagement on a genuine slice of your project beats every other signal combined. You see their questions, their estimate against reality, the shape of their work, and whether the handoff artifacts exist. If the trial produces something you can run and a specification you understand, you have learned what six reference calls cannot tell you.
Red flags, ranked by what they cost you
| Red flag | What it usually means | Cost if ignored |
|---|---|---|
| Won't work in a repository you own | They treat delivery as leverage | Total loss of the asset |
| No "assigns" language in the contract | Template copied without legal review | You do not own what you paid for |
| Fixed price for a vague scope | The margin is in the change orders, or in cutting quality | Budget doubles, trust gone |
| Wants most of the money up front | Your cash is funding their next project | You hold the risk for the whole build |
| The senior who pitched never appears again | You bought a sales team | Quality falls off a cliff after kickoff |
| No written acceptance criteria | Nobody has defined done | Endless final 10 percent |
| Estimate arrives without questions | They are guessing, or they will build the wrong thing | Rework priced as new work |
| Proposes cutting over in your peak season | They have not asked about your business | Dispatch breaks when you can least afford it |
| Resists a paid trial | They cannot survive close inspection | You find out at month six |
| Pressure to skip legal review | Deliberate | Everything above at once |
Worker classification: don't accidentally hire an employee
One more thing worth 10 minutes of attention. If you engage a contractor full time, direct their hours, supply their equipment and integrate them into your team, you may have created an employment relationship regardless of what the agreement says.
The IRS weighs three categories of common-law factors: behavioral control ("Does the company control or have the right to control what the worker does and how the worker does his or her job?"), financial control (who provides tools, how payment works, expense reimbursement), and type of relationship (written contracts, benefits, duration, and whether the work is integral to the business). The agency is explicit that there is no "magic" or set number of factors, and that you have to weigh the entire relationship. Either party can ask for a determination using Form SS-8 (IRS).
Practically: keep contractor engagements organized around deliverables and statements of work rather than hours and attendance, and confirm your own situation with your counsel or payroll advisor before you structure a long full-time engagement as contracting. Note that the test for employment is also the test that decides work-made-for-hire status, so answering it clearly helps you twice.
When not to hire a developer at all
Four honest cases where the right answer is to stop.
You have not validated the problem. If you cannot name the specific task someone does today, how long it takes, and how often, you are not ready to commission software. Spend two weeks watching the work instead.
Off-the-shelf covers 80 percent of it. Custom software earns its keep on the parts of your business that are genuinely yours. Our guide to replacing spreadsheets with custom software lays out the specific conditions that justify a custom build and the cheaper options to try first. If the real problem is that your tools do not talk to each other, connecting what you already own is a smaller project than commissioning anything.
Your software bill is small. Below roughly $1,500 a month in subscriptions, replacing software does not pay back in a sensible time, whoever builds it.
Nobody internally will own it. Applications need a person who decides what changes and answers questions. Without that, a well-built app decays into a system nobody trusts within a year. Name the owner before you name the vendor.
What to do next
Hiring a software partner well comes down to four decisions, in this order. Size the work and pick the model from the volume, not the budget. Price the work against the labor floor so you can recognize a quote that cannot be real. Get the paperwork right: an express assignment, chain of title, a bill of materials, confidentiality with the DTSA notice, data handling terms, rules for AI tool use, a payment schedule tied to working modules and a priced exit. Own the accounts from day one and run the handoff checklist at every milestone.
Do those four things and the worst realistic outcome is a project that disappoints you, which is recoverable. Skip them and the worst outcome is a project that takes your money, your year and your source code, which is not.
If you want a second opinion on a scope, a quote or a contract before you sign it, talk to a specialist. A specialist replies within one business day, and the first step with us is the Stack Audit rather than a build. Bring the statement of work you were sent; the gaps are usually in the same three clauses. If you already know you want to replace part of your stack, see how the Operations Stack works.
If you'd like one clear, practical take on the software that runs your business each month, subscribe to the Fleurant AI Briefing: one email a month, unsubscribe any time.
Frequently asked questions
Should I hire a freelancer, an agency, or an in-house developer?
Size the work first. Under about 400 engineering hours over two years, a freelancer on a fixed scope is usually right. Between 400 and 1,200 hours, a senior contractor works only if someone on your staff can write down what done looks like and accept the work; if nobody can, you need an agency, because you are buying project management too. Above roughly 1,200 hours a year of steady work on something core to revenue, hiring in house starts to win on knowledge retention rather than price.
Who owns the code when you pay someone to build software for your company?
Not automatically you. Copyright vests first in the author under 17 U.S.C. § 201(a), and the "work made for hire" rule only makes you the author if the developer is your employee: computer software is not one of the nine commissioned-work categories in § 101. To own a contractor's code you need an express written assignment signed by the owner, which § 204(a) requires.
Do I own code a developer writes with AI coding tools?
You own whatever copyright exists, if your contract assigns it, but there may be less of it. The U.S. Copyright Office concluded in January 2025 that AI output is protectable only where a human author determined sufficient expressive elements, and that prompts alone are not enough. Human-written and human-modified code stays protectable. Ask vendors to disclose AI use, keep human review and commit history, and rely on confidentiality terms as well as copyright.
How much does it cost to hire a web app developer in the US?
Published marketplace rates for freelance web developers run $15 to $50 an hour on Upwork, with experts quoted at $50 to $200. A US in-house mid-level web developer works out to roughly $101 per productive hour once you gross up the BLS median wage of $99,520 for benefits and subtract non-productive time. Agency rates have to clear that same labor floor plus overhead.
Is offshore development actually cheaper once you count the rework?
Often yes, on money alone. The break-even model in this article shows that a $28-an-hour team stays cheaper in dollars than a $130-an-hour US team until roughly 72 percent of its output has to be rebuilt. What cheap builds really cost you is calendar time, your own attention, and the specific disasters where you end up with nothing: no assignment, no repository access, no deployment. Those are contract and account problems, not rate problems.
What should I own before the developer writes a single line?
The source-code repository, under an organization your company owns, with the vendor as a member rather than the owner. The cloud account, billed to you. The domain, at a registrar you log into. The secrets vault. The payment, email and analytics accounts. Set these up yourself on day one. Collecting them afterwards is the single most common thing that turns an ordinary project into a dispute.
How do I check a developer is any good before committing a big budget?
Buy a small piece of the real work. A paid one-to-two-week engagement on a genuine slice of your project tells you more than any portfolio: you see their questions, their estimates against reality, and whether the handoff artifacts exist. You do not need to read code yourself. Ask someone to show you the commit history, the tests and the written instructions, and judge whether a second engineer could run it.
Sources
- 17 U.S.C. § 101 — Definitions (work made for hire), Legal Information Institute, Cornell Law School
- 17 U.S.C. § 201 — Ownership of copyright, Legal Information Institute, Cornell Law School
- 17 U.S.C. § 204 — Execution of transfers of copyright ownership, Legal Information Institute, Cornell Law School
- Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), Legal Information Institute, Cornell Law School
- Circular 30: Works Made for Hire, U.S. Copyright Office
- 18 U.S.C. § 1833 — Exceptions to prohibitions (Defend Trade Secrets Act immunity notice), Legal Information Institute, Cornell Law School
- Web Developers and Digital Designers: Occupational Outlook Handbook, U.S. Bureau of Labor Statistics
- Software Developers, Quality Assurance Analysts, and Testers: Occupational Outlook Handbook, U.S. Bureau of Labor Statistics
- Employer Costs for Employee Compensation, June 2026, U.S. Bureau of Labor Statistics
- Web Developer Hourly Rates: How much does a web developer cost?, Upwork
- Optional Service Contract Terms, Upwork
- Independent contractor (self-employed) or employee?, Internal Revenue Service
- OWASP Top 10:2025, Open Worldwide Application Security Project
- Start with Security: A Guide for Business, U.S. Federal Trade Commission
- Transferring a repository, GitHub Docs
- Transfer Policy, ICANN
- NewsNet Issue 1060: Copyright Office releases Part 2 of AI report (copyrightability), U.S. Copyright Office
- When to Hire a Freelance Web Developer vs. a Web Development Company, Clutch