How to evaluate a web/AI development agency before you sign
Questions about process, IP ownership, post-launch support, and how to verify past work — agency-agnostic advice.
The short answer
Evaluate an agency on process clarity, verifiable past work, communication cadence, IP ownership, and post-launch support — not on slide decks or vague “we do everything.” A good partner asks hard questions, puts scope in writing, and lets you talk to past clients.
This guide is agency-agnostic. Use it whether you are comparing us, a Bangalore shop, or a freelancer collective.
Before the first call
Do this homework so calls are productive:
- Write a one-page brief — goal, audience, must-haves, budget range, timeline.
- List 3–5 reference sites you like (for quality bar, not to clone).
- Know your non-negotiables — e.g. you must own the code, Hindi support, WhatsApp integration.
- Shortlist 2–4 agencies max — more than that and you cannot compare fairly.
Questions about process
Ask explicitly:
- What happens between signing and design start?
- How many revision rounds are included?
- Who is your day-to-day contact — account manager or the person doing the work?
- How do you handle feedback — tool, cadence, turnaround time?
- What is your QA process before launch?
- How do you manage scope changes — written change orders or verbal?
How to verify past work
Portfolio screenshots lie. Verify like this:
- Visit live sites — check mobile speed, forms, broken links.
- Ask for 2–3 references in a similar industry or project size — call them.
- Ask what the agency actually did vs what was template/client in-house.
- Check case studies for metrics — traffic, conversion, time saved — not only aesthetics.
- Search the agency name + reviews; red flags in communication often show there.
IP, code ownership, and access
Get clear written answers:
- Who owns source code, design files, and content at project end?
- Will you receive Git repo, hosting credentials, domain access?
- Are third-party licenses (fonts, stock, plugins) included and transferable?
- For AI projects — who owns prompts, workflows, and fine-tuned configs?
- What happens if you leave — export path and handover checklist?
Post-launch support
Launch is not the finish line:
- What is included in the first 30 days after go-live?
- Retainer options — hours, response time, what counts as a bug vs new feature.
- Who handles hosting, SSL, backups, security updates?
- Training — will your team know how to update content?
- SLA for downtime or critical bugs — especially for e-commerce or portals.
Red flags
- Fixed price with zero discovery for a complex build.
- No written scope or contract.
- Refuses references or only shows Dribbble mockups.
- Guarantees #1 Google ranking as part of development.
- 100% upfront payment demand.
- Vague on ownership — “we host it for you” with no exit plan.
Next steps
Use our briefing guide to prepare your one-pager, then run this checklist on every finalist.
We welcome reference calls and written scope before any commitment — that is normal due diligence.
Need help with this?
We build what this guide describes.
Tell us about your business and timeline — honest scope and quote, usually within one business day.
Contact Zulo Labs