When a Web Developer Fails to Deliver
Hiring a web developer and receiving nothing — or receiving a barely functional product — is more common than most people realize. The technical nature of web development makes it difficult for non-technical clients to evaluate progress until it is too late.
Common Scenarios
- Abandoned projects: The developer collected a deposit, produced some initial work, then became unresponsive and stopped working
- Perpetual "almost done": The developer kept promising the site was nearly finished for weeks or months, but a working product never materialized
- Non-functional delivery: The developer delivered something, but it does not work — broken features, security vulnerabilities, or code that crashes under basic usage
- Template fraud: The developer charged custom development rates but delivered a slightly modified WordPress theme or page builder template worth a fraction of the price
- Technology mismatch: The developer built the project in a technology stack different from what was agreed upon, resulting in a product that does not meet your requirements
- Subcontracting without disclosure: The developer outsourced your project to unvetted third parties without your knowledge, resulting in poor quality work
Evaluating What You Actually Received
Before writing your demand letter, assess what the developer delivered versus what was promised:
Functional Assessment
- Does the website load and display correctly across browsers and devices?
- Do all contracted features work as specified?
- Is the admin panel or CMS functional and usable?
- Are forms, payment processing, and integrations operational?
- Does the site meet basic performance and security standards?
Code Quality Assessment
If possible, have another developer review the delivered code:
- Is it custom code or a pre-built template with minor modifications?
- Is the code maintainable and well-organized?
- Are there security vulnerabilities?
- Does the code follow modern development standards?
Deliverables Checklist
Compare what was promised against what was delivered:
- Pages and sections specified in the contract
- Custom features and functionality
- Mobile responsiveness
- SEO implementation
- Analytics integration
- Documentation and training
- Source code and repository access
What to Include in Your Demand Letter
Contract and Payment History
Document the full agreement and every payment made:
- Date of the contract or agreement
- Project scope and specification reference
- Total contracted price
- Payment schedule and amounts paid
- Total amount paid to date
Promised vs. Delivered Comparison
Create a clear side-by-side accounting:
- Feature X: Contracted and paid for, not delivered
- Feature Y: Delivered but non-functional
- Feature Z: Delivered as a pre-built plugin, not custom development as billed
Communication Timeline
Document the developer's pattern of missed deadlines and excuses:
- Original completion date per the contract
- Each deadline extension with the developer's stated reason
- Dates you followed up and the developer's responses
- Date the developer became unresponsive (if applicable)
Refund Demand
Calculate your refund based on the gap between payment and value received:
- Total amount paid
- Fair value of usable work received (if any)
- Cost to hire a replacement developer to complete or redo the work
- Additional costs incurred due to the delay (lost revenue, expired marketing campaigns, extended hosting costs)
- Total refund demanded
Deadline and Consequences
Demand a refund within 14 days. State that failure to comply will result in:
- Small claims court filing
- Complaints to the Better Business Bureau and relevant licensing boards
- Negative reviews on platforms where the developer solicits clients
- Reporting to the state attorney general if the conduct constitutes fraud
Industry-Specific Tips for Clients
- Get an independent code review: Pay another developer $200-$500 to review what was delivered. Their written assessment serves as expert evidence in court and helps you accurately value any usable work
- Preserve all evidence: Screenshot the developer's portfolio claims, Upwork or freelance platform profile, and any credentials they represented. If they claimed expertise they do not have, this supports a fraud claim
- Check for template fraud: Search for the visual design of your website on ThemeForest, TemplateMonster, or WordPress theme repositories. If your "custom" site matches a $50 template, document this
- Document the business impact: Calculate lost revenue, delayed launches, or marketing spend that was wasted because the website was not delivered on time
Timeline for Resolution
- Day 1: Send demand letter via email and certified mail to the developer's business and personal address
- Days 3-7: Developer response window
- Day 14: Refund deadline
- Day 15: File disputes on freelance platforms (Upwork, Fiverr) if applicable; file BBB complaint
- Day 30: File small claims court petition
When to Escalate Beyond Small Claims
Most services-not-rendered disputes with web developers involve amounts between $2,000 and $20,000, fitting comfortably within small claims limits. However, consider escalating when:
- The amount exceeds small claims limits: Large application builds or e-commerce platforms may involve $25,000-$100,000+
- Fraud is involved: If the developer misrepresented credentials, used template fraud, or took payments with no intention of delivering, report to the state attorney general
- Multiple victims exist: If other clients have had the same experience, a pattern of fraud strengthens each individual claim
- Business damages are significant: If the failed project caused substantial revenue loss, an attorney can pursue consequential damages beyond the contract value