Website Payment Structures: Deposits, Milestones, and Retainers

Payment structure might seem like a minor detail, but it significantly impacts project risk for both parties. Understanding standard practices helps you evaluate proposals and protect your investment.

Common Payment Structures

Most web development projects use one of these payment models:

For more insights on this topic, see our guide on MVP Development Cost: How Much to Build a Prototype.

1. Deposit + Final Payment (50/50)

The simplest structure: half upfront, half on completion.

• When it works: Small projects, established relationships
• Deposit: 50% to begin work
• Final: 50% on launch
• Pros: Simple, easy to administer
• Cons: Large payments, limited checkpoints

2. Milestone Payments

Payments tied to specific project phases or deliverables.

• When it works: Medium to large projects
• Typical structure: 25% deposit, 25% after design, 25% after development, 25% on launch
• Pros: Spread out payments, clear progress checkpoints
• Cons: More invoices to manage

3. Progress Billing (Monthly)

Monthly invoices based on work completed.

• When it works: Long projects, ongoing development
• Structure: Invoice for hours/work each month
• Pros: Predictable monthly expenses, flexibility
• Cons: Requires trust, less cost certainty

4. Retainer

Fixed monthly fee for ongoing access and work.

• When it works: Ongoing maintenance, continuous development
• Structure: Set hours per month at discounted rate
• Pros: Priority access, cost predictability, discounted rates
• Cons: Unused hours may not roll over

Standard Deposit Amounts

What's typical and why developers require deposits:

• 25-30%: Common for larger projects ($20,000+)
• 50%: Standard for most projects ($5,000-$20,000)
• 100%: Sometimes for very small projects (under $2,000)

Why Developers Require Deposits

• Reserves their time and capacity
• Covers initial planning and setup costs
• Demonstrates client commitment
• Protects against project abandonment
• Cash flow for business operations

When to Be Cautious

• 100% upfront: Unusual for projects over $2,000
• No contract: Always get payment terms in writing
• Vague milestones: Know exactly what triggers each payment
• No deliverables before payment: You should see progress

Milestone Payment Breakdown

For a typical website project, here's a reasonable milestone structure:

4-Milestone Structure

1. Project kickoff (25%): Paid to begin, covers discovery and planning
2. Design approval (25%): Paid when you approve the visual design
3. Development complete (25%): Paid when core functionality works
4. Launch (25%): Paid when site goes live

3-Milestone Structure

1. Project kickoff (40%): Covers discovery, planning, and design
2. Development complete (30%): Core site is built and functional
3. Launch (30%): Final testing, content, and go-live

Retainer Agreements Explained

Retainers are monthly commitments for ongoing work. Here's how they typically work:

What's Included

• Set number of hours per month (e.g., 10, 20, 40 hours)
• Priority response times
• Discounted hourly rate (10-20% off standard)
• Regular check-ins and reporting

Typical Retainer Pricing

• 5 hours/month: $500 - $750
• 10 hours/month: $1,000 - $1,500
• 20 hours/month: $2,000 - $3,000
• 40 hours/month: $4,000 - $6,000

Hour Rollover Policies

• No rollover: Use it or lose it (most common)
• Partial rollover: Up to 25-50% carries forward
• Full rollover: Unused hours bank (rare)

Payment Methods

How to actually pay for web development:

• Credit card: Convenient, provides some protection, 2-3% fees often passed through
• ACH/bank transfer: No fees, slower processing
• Check: Traditional, slow clearing
• Wire transfer: Fast for large amounts, fees apply
• PayPal: Common for smaller payments

What Should Be in Your Payment Contract

Ensure your agreement clearly specifies:

• Total project cost: Or hourly rate and estimate
• Payment schedule: When each payment is due
• Payment triggers: What defines milestone completion
• Late payment terms: Interest or penalties
• Refund policy: What happens if project is cancelled
• Scope change process: How additional costs are handled
• Deliverables ownership: When you own the work

Red Flags in Payment Terms

Watch out for these warning signs:

• No written agreement: Never pay without a contract
• Demanding 100% upfront: Unusual and risky
• No milestones or checkpoints: You need to see progress
• Vague scope: Unclear what you're paying for
• No ownership clause: Ensure you own your site
• Holding site hostage: Some developers won't hand over work until final payment - make sure terms are clear

Negotiating Payment Terms

Most developers are open to reasonable negotiation:

• Request more milestones: Breaks up larger payments
• Ask about retainer conversion: Projects that become ongoing work
• Discuss cash flow timing: Align payments with your revenue cycles
• Inquire about discounts: Paying in full upfront sometimes earns 5-10% off

Related Reading

• Ongoing Website Costs: What to Budget After Launch
• Domain Name Costs: Buying, Renewing, and Premium Domains
• SSL Certificate Costs: Free vs Paid Options