When a Website or App Project Falls Apart
Website and app projects go wrong in predictable ways: the developer disappears mid-project, the site launches broken, or — most frustrating — the work is finished but you can't get access to the files, domain, or hosting account you paid for.
The three usual disputes
- Non-delivery — money paid, little or nothing built.
- Substandard delivery — the site exists but doesn't do what was contracted (broken checkout, no mobile layout, missing pages).
- Access withheld — the work is done but the developer holds the domain, hosting login, source code, or CMS admin access hostage over a fee dispute.
The third is often the strongest case, because it's concrete and easy to prove.
What matters most
- The scope document. A proposal, statement of work, or even a detailed email thread listing deliverables is the backbone of your case.
- Payment records and the payment schedule, including which milestones were tied to which payments.
- Who owns what. Many contracts specify that source code and assets transfer on final payment. If you paid in full, that clause is your argument.
- Domain registration records. A WHOIS lookup or registrar record showing the domain is registered under the developer's account, not yours, is compelling evidence.
- A comparison of promised vs. delivered. Screenshots of the live site next to the contracted feature list.
Getting access back
Sometimes the practical remedy matters more than money. Small claims courts award money, not orders to hand over accounts — so:
- Ask for the cost to rebuild or recover what you can't access, supported by a written quote from another developer
- Include domain transfer or recovery costs, if applicable
- Registrars also have their own dispute processes for domains registered on a client's behalf; that path can be faster than court
Calculating your claim
- Amounts paid for work not delivered
- The quoted cost to complete or rebuild the project with another developer
- Documented business losses that are direct and provable — a launch date missed with a paid ad campaign already running, for example. Speculative lost revenue rarely succeeds.
Before filing
A firm, factual message that lists the specific unmet deliverables, references the scope document, and sets a deadline for delivery or refund resolves many of these. Independent developers depend on referrals and portfolios, and most would rather return a deposit than litigate.
This article is for general informational purposes and isn't legal advice. Contract terms and ownership provisions govern these disputes — review your agreement before filing.