Questions to Ask Before Signing a Web Dev Contract
You've found a developer. They seem legit. Now comes the contract.
Most people skim it, sign it, and hope for the best. Then six months later they're stuck in a dispute about who owns what, what "done" means, or why they're being charged extra.
Ask these questions before you sign anything.
Scope & Deliverables
1. "What exactly is included in this price?"
You need a specific list. Vague scope = surprise bills later.
Good answer: "The price covers a 5-page website with these specific pages, mobile responsive design, contact form, basic SEO setup, and deployment. Here's the detailed spec document."
Bad answer: "Everything you need for a website."
2. "What's NOT included?"
The things not mentioned are where disputes happen.
Good answer: "Content writing, stock photos, ongoing maintenance, and major changes after sign-off are separate. Hosting is X per month."
Bad answer: Silence or "we'll figure it out as we go."
3. "How many revision rounds are included?"
Unlimited revisions sounds nice until the developer starts dragging or charging.
Good answer: "Two rounds of revisions at each milestone. Additional rounds are billed at X per hour."
Bad answer: "Unlimited revisions!" (They'll either rush you or the relationship will sour.)
Payment & Timeline
4. "What's the payment schedule?"
Protects both sides. You don't overpay upfront; they don't work for free.
Good answer: "30% upfront, 30% at design approval, 40% at launch. Invoices due within 14 days."
Bad answer: "100% upfront" or "Pay whenever."
5. "What happens if the timeline slips?"
Delays happen. Know the policy.
Good answer: "If I cause the delay, no penalty. If it's due to waiting on your content/feedback, timeline adjusts accordingly. Major delays we'll discuss."
Bad answer: No acknowledgment that delays are possible.
6. "What if I need to cancel mid-project?"
Life happens. Know the exit terms.
Good answer: "You keep what's been built. Payments made are non-refundable since they cover work completed. We can pause for up to X weeks."
Bad answer: "You can't cancel" or no cancellation terms at all.
Ownership & Access
7. "Who owns the code when we're done?"
This bites people constantly. Some agencies retain ownership and charge you to leave.
Good answer: "You own all custom code upon final payment. I retain rights to reusable components and frameworks."
Bad answer: "We retain ownership" or "It's complicated."
8. "Will I have admin access to everything?"
You should control your own domain, hosting, and CMS.
Good answer: "Yes. You'll have full admin credentials for hosting, domain registrar, CMS, and any third-party services."
Bad answer: "We manage that for you" (hostage situation waiting to happen).
9. "Can I take this to another developer later?"
You should be able to leave without being held hostage.
Good answer: "Absolutely. I'll provide documentation and help with handoff."
Bad answer: "You'd need to start over" or "Our code only works with our systems."
Post-Launch
10. "What support is included after launch?"
The first month always has bugs. Know what's covered.
Good answer: "30 days of bug fixes for issues with work delivered. New features or changes are separate."
Bad answer: "We'll handle it" with no specifics.
11. "What does ongoing maintenance cost?"
Websites need updates, security patches, backups. Know the ongoing costs.
Good answer: "Maintenance packages start at X per month and include Y. Or you can pay hourly when needed."
Bad answer: "We'll discuss that later."
12. "What documentation will I receive?"
If you or a future developer needs to understand the system.
Good answer: "You'll get admin guides, a list of all logins, and technical documentation for the codebase."
Bad answer: "It's pretty self-explanatory."
The Contract Itself
Make sure the contract includes:
- Detailed scope of work (or attached specification)
- Timeline with milestones
- Payment schedule tied to milestones
- Revision policy
- Ownership and IP transfer clause
- Cancellation terms
- Warranty/support period
- What happens if either party goes dark
Bottom Line
Five minutes of awkward questions beats five months of legal disputes.
Get everything in writing. If they say it but it's not in the contract, it doesn't exist. And if they won't put something in writing, ask yourself why.