Vetting a custom website design company properly means going beyond the portfolio — checking proposal red flags, confirming specific contract clauses, and asking reference-call questions that reveal how the company actually behaves under pressure, not just what their finished work looks like. A polished portfolio tells you they can produce good final output. It tells you almost nothing about whether the process getting there will be smooth, on-time, or within budget.
What to Look for in the Portfolio (Beyond "Does It Look Good")
Anyone can showcase their five best projects. What's more revealing is whether the portfolio includes examples similar to your project specifically — same rough size, same industry, same level of functional complexity. A design company with a beautiful portfolio of restaurant websites isn't necessarily a safe bet for a complex B2B software company's site, even if the visual craft is genuinely excellent.
Ask how many of the portfolio pieces are still live and actively maintained by the client. A portfolio full of sites that no longer exist, or that the original client abandoned shortly after launch, is worth asking about directly.
Red Flags in a Proposal
A handful of specific patterns show up disproportionately often in proposals that lead to problematic projects:
- No defined number of revision rounds. "Unlimited revisions" sounds generous but often comes with unstated limits, or signals a company that hasn't scoped the work carefully enough to know how many rounds it should actually take.
- Vague timeline language. "4-8 weeks" with no milestone breakdown gives the company enormous room to slip without technically breaking the proposal.
- No mention of who owns the final files. If a proposal doesn't address what happens to source files and code if you want to leave, that's worth asking about directly before signing.
- Pressure to sign quickly. A legitimate company is rarely in a rush to get a signature before you've had time to review terms properly.
Contract Clauses Worth Checking For
Beyond price and timeline, a handful of contract terms genuinely protect you if something goes wrong later:
- File and IP ownership — explicit confirmation that you own the final design files, code, and content upon full payment.
- Kill fee or cancellation terms — what you owe if the project is cancelled partway through, and what you receive for work already completed.
- Defined revision scope — exactly how many revision rounds are included and what counts as a revision versus a new request.
- Post-launch support window — a specific timeframe (not "ongoing support" left undefined) during which launch-related bugs are fixed at no additional cost.
Reference Call Questions That Actually Reveal Something
Most reference calls ask "were you happy with the work" and get a predictably positive answer, since companies choose their own references. More useful questions get past that:
- "Did the project finish on the original timeline? If not, what caused the delay?"
- "Did the final cost match the original quote, or were there change orders? What triggered them?"
- "If you needed something changed after launch, how responsive was the team?"
- "Would you hire them again for a second project?" — a more revealing question than "were you satisfied," since it implicitly asks about the whole experience, not just the final output.
How Many Portfolio Examples Is Reasonable to Expect
For a company that's been operating for a reasonable amount of time, 5-10 strong, relevant portfolio pieces is a reasonable baseline to expect. For a newer company or a small, focused team, fewer examples isn't automatically disqualifying — what matters more is whether the examples they do have are genuinely comparable to your project and whether they can speak specifically about the decisions behind them, not just show a finished screenshot.
Putting This Into a Repeatable Process
If you're evaluating more than one company, it's worth using the same checklist and questions across all of them so you're comparing apples to apples rather than being swayed by whichever pitch was most polished. Our broader guide to shortlisting website development companies covers how to structure that comparison process end-to-end.
Frequently Asked Questions
What red flags should I look for in a custom website design company's proposal?
Watch for undefined revision limits, vague timelines with no milestones, no mention of file/IP ownership, and pressure to sign quickly. Each of these individually isn't necessarily disqualifying, but several together are worth taking seriously.
Should I ask for client references before hiring a design company?
Yes, and ask specific questions beyond "were you satisfied" — whether the project finished on time and on budget, and how responsive the team was to post-launch requests, reveal more than a general satisfaction question.
What contract clauses protect me when hiring a website design company?
Explicit file/IP ownership terms, clear cancellation/kill-fee terms, a defined number of revision rounds, and a specific (not vague) post-launch support window are the clauses worth confirming before signing.
How many portfolio examples should a design company be able to show?
5-10 strong, relevant examples is a reasonable baseline for an established company. For newer or smaller teams, fewer examples can be fine if they're genuinely comparable to your project and the team can speak specifically about the work.