How to evaluate design, performance, accessibility, intake paths, ownership and vendor proposals before your firm signs a website contract.
What a law firm website is actually for
A firm website has one commercial job: turn a referred or searching visitor into a consultation request. Everything else — awards, animations, photography — is instrumentation toward that job. This framing matters because it changes how you evaluate design. The question is never 'do we like it?' but 'does it move a worried person from reading to contacting us, on a phone, in under a minute?'
That visitor is usually in one of two states. The referred prospect is verifying you: they already have your name and are checking whether the firm looks as capable as the referral promised. The searching prospect is comparing you against three or four other firms in adjacent browser tabs. Good design serves both: it confirms competence instantly for the first, and makes contacting you easier than contacting the tab to the left for the second.
Evaluating design beyond taste
Taste is subjective; craft is not. When you review a design or a redesign proposal, look for hierarchy — can you tell within three seconds what the firm does, where it practices and what to do next? Look for typography that a 55-year-old can read comfortably on a phone, contrast that survives sunlight on a sidewalk, and navigation that names things the way clients name them ('Car Accidents', not 'Motor Vehicle Tort Litigation').
Then check the details that reveal whether a vendor sweats quality: do attorney bios read like humans wrote them, are practice pages substantive rather than two paragraphs of filler, does the site work identically on iOS and Android, and does every page have one obvious next step? A beautiful homepage wrapped around thin practice pages is decoration, not design.
Performance is a business metric
Speed is not a technical vanity metric. Every second of load time loses visitors who were ready to call, and Google uses page experience signals in ranking. A modern custom site should target sub-second loads on a decent connection; anything consistently above two or three seconds on a phone is a problem with a cost attached.
Ask every vendor two questions: what performance budget do you build to, and how will you prove it after launch? Serious teams answer with specifics — Core Web Vitals targets, image and font discipline, measured results on real devices — and put the numbers in the proposal. Vague assurances about 'fast, modern code' are worth nothing.
Accessibility is not optional
Law firms have been frequent targets of ADA website accessibility claims, and beyond legal exposure, an inaccessible site turns away exactly the clients who need counsel most. The working standard is WCAG 2.2 at level AA: sufficient color contrast, full keyboard navigation, screen-reader-friendly structure, visible focus states and forms that announce their errors.
Accessibility cannot be bolted on afterward with an overlay widget — courts and regulators have repeatedly found those insufficient. It has to be built into the design system: the components, the contrast ratios, the heading structure. Ask vendors whether AA conformance is a deliverable with an audit, or an aspiration. Only one of those answers is acceptable.
Intake paths: where design meets revenue
The most expensive mistake in law firm websites is treating the contact page as an afterthought. Every page a visitor might land on — a practice page, a bio, a blog post — needs a visible, low-friction path to contact: a tap-to-call number on mobile, a short form that asks only for what intake truly needs, and a clear statement of what happens after someone submits.
Think about the after-hours reality too. A large share of legal inquiries arrive evenings and weekends, when nobody is answering the phone. Design for that: prominent click-to-call, a form that sets response expectations, and — if your intake process supports it — chat or scheduling that captures the inquiry while the need is urgent. The firms that respond first usually get the case; the website is where that race starts.
Ownership: read this section twice
Some agencies build law firm websites on proprietary platforms you cannot leave: the design, the content management system, sometimes even the domain and the content itself are licensed, not owned. When the relationship ends, the site stays behind — or you pay a ransom to export a degraded copy. This is more common in legal marketing than in almost any other industry.
Before signing, confirm in writing: your firm owns the domain, the design files, the source code, the content, the analytics accounts and the ad accounts. The site should be built on technology any competent developer can take over. If a vendor hesitates on any of these, that hesitation is your answer. Our own position is simple — clients own everything we build, outright, from day one.
How to read a vendor proposal
A credible proposal names deliverables, not adjectives. Look for: a defined page inventory, a content plan (who writes, who approves, how attorney review cycles work), a performance budget, an accessibility standard, a timeline with milestones, and explicit ownership terms. A realistic custom build runs roughly 8–14 weeks depending on page count, integrations and how ready your content is — be suspicious of two-week promises and of six-month ones without explanation.
Price alone tells you little; scope tells you everything. A $15,000 proposal that includes copywriting, photography direction, technical SEO foundations and analytics wiring can be cheaper in the end than an $8,000 one that delivers pages you must fill, fix and instrument yourself. Ask every bidder the same ten questions — ownership, performance targets, accessibility standard, content responsibility, timeline, post-launch support, hosting, security, who does the work, and what happens if you leave — and compare the answers side by side.
Content: who writes your practice pages
The single biggest variable in a law firm website project is not the design — it is the words. Practice pages need to answer the questions real clients ask, in plain language, with jurisdiction-specific accuracy, and they need an attorney's review before publication. Decide before the project starts who writes, who reviews and how many revision cycles are included.
Be wary of proposals where content is an afterthought or an upsell. A beautiful site with thin, generic practice pages will be outperformed by a plain site with substantive ones — by visitors, by search engines and by the AI systems that quote sources they consider authoritative.
Security and hosting are part of the purchase
A law firm website handles confidential inquiries from day one, which makes security a procurement question, not an IT footnote. Ask where the site is hosted, how form submissions are encrypted and stored, who has administrative access, and how updates and patches are handled. Firms have been breached through outdated website plugins more often than through any other vector.
Custom-coded builds on modern managed infrastructure remove most of this risk by removing the attack surface: no plugin marketplace, no abandoned themes, no shared hosting neighbors. Whatever you buy, get the maintenance commitment in writing — an unmaintained site is a liability with your name on it.
The launch checklist
Launches fail in the details. Before the new site replaces the old: every old URL redirected to its new equivalent, analytics and call tracking verified end to end, forms tested from a real phone, page speed measured on real devices, and the XML sitemap submitted to search engines. A launch that skips redirects can erase years of accumulated search equity in a week.
Then plan the first ninety days: baseline measurements before launch, weekly checks after, and a scheduled review at the thirty-day mark. A website is not a deliverable that ends at launch — it is infrastructure that starts working at launch.
Designing for AI search and answer engines
A modern firm website now has a third audience beyond referred and searching visitors: the machines that summarize you. AI Overviews, ChatGPT, Perplexity and Copilot read your pages before a prospect ever does, and what they can parse determines whether your firm is cited when someone asks for a lawyer like you. Design decisions are visibility decisions.
The practical requirements overlap heavily with good craft: server-rendered pages whose substance lives in clean HTML, headings that mirror real client questions, direct answers in the first sentences of each section, and structured data that disambiguates your firm, attorneys and locations. What AI-unfriendly design looks like is also familiar: content locked inside sliders and accordions that never render, text baked into images, and practice pages too thin to quote.
Ask vendors how their builds perform as a citable source, not just as a brochure. A site engineered for answer engines earns citations that compound; a site that merely looks premium in a screenshot earns nothing the moment the tab closes.
The short version
Judge design by whether it converts referred and searching visitors, not by whether it wins a taste contest. Demand measured performance and WCAG 2.2 AA accessibility as deliverables, not aspirations. Treat intake paths as the point of the whole exercise. Own everything. And choose the vendor whose proposal answers hard questions with specifics — that habit will not stop at the proposal stage.
If you are evaluating a redesign now, our website design and development service page describes how we approach these exact questions — and we are happy to review a proposal you have already received, even if you do not hire us.
Law firm growth intelligence, monthly.
One concise email a month: what is changing in legal search, AI visibility and intake — and what to do about it. No spam, unsubscribe anytime.
We use your email only to send the briefing. See our Privacy Notice.
