A law firm is offered a custom website and a cheaper template-based option. Both proposals promise a modern design, good performance, and more inquiries. Which one is worth buying?
The answer depends on what the firm needs the site to do. “Custom” describes an approach to building it, not proof that the finished website will be faster, more useful, or more successful.
Before comparing prices, show each team what the current site makes difficult. What can't visitors find? What can't staff update? Which contact requests go to the wrong place? Then ask them to explain where custom work would help and where an existing component would do the job well.
Key takeaways
- Choose custom features to solve a demonstrated requirement, rather than treating custom code as a quality guarantee.
- Evaluate realistic content and visitor tasks at phone, intermediate, and desktop widths before approving layouts.
- Define ownership, contact delivery, accessibility testing, search continuity, and maintenance before launch.
Define the problem behind the redesign
Maybe prospective clients can't find the relevant practice area. Perhaps attorneys struggle to update biographies. The contact form may route different matters to one unmonitored inbox. Or the site may have changed repeatedly until navigation no longer makes sense.
You may be able to repair some of those problems on the current platform. Others may need a larger redesign because the way the site is organized, or the system behind it, prevents the change. Ask the team to show you which is which before agreeing to start over.
For a hypothetical firm with several practice groups, the key requirement could be routing inquiries to appropriate intake teams while presenting each group clearly. That requirement is more useful than “a site that looks premium.”
Specify the visitor's tasks
Describe what people should be able to find and do. A prospective client may need the service explanation, relevant attorney credentials, jurisdiction, and contact route. A referring lawyer may have a different question. A recruit may need another path.
Use those tasks to evaluate proposed navigation and page layouts. Ask the designer to demonstrate the path with realistic content before polishing visual details. A beautiful layout containing placeholder text can conceal a heading or comparison that won't fit the real material.
Try the layout on a tablet as well as a phone and desktop. A set of columns may become hard to follow well before the screen reaches phone size. Decide when the content needs a different arrangement, rather than shrinking everything until it fits.
Compare the build options by the requirements
A well-implemented template can support clear pages and good performance, while a custom build can become slow or difficult to maintain. To compare them fairly, look at the actual implementation and the team's ability to deliver the requirements.
Ask how editors will update pages, whether a necessary integration is supported, and what ongoing maintenance involves. A custom intake feature may deserve investment; a completely custom content editor may create unnecessary support dependence.
Clarify licensing and ownership. Organization-controlled domain and hosting access matter, but third-party fonts, components, plugins, and photography may have separate terms. “You own everything” needs enough detail to be meaningful.
Treat content as part of the project
Inventory useful existing pages before design begins. Identify what can stay, what needs revision, and who verifies facts. Have attorneys review legal explanations and advertising claims under the applicable professional rules.
ABA Model Rule 7.1 addresses false or misleading communications. The firm's jurisdictional requirements determine the actual review needed. Neither custom code nor a stock disclaimer establishes compliance.
Use genuine qualifications, permitted case information, and accurate service descriptions. Don't ask a designer or copywriter to invent distinctions the firm hasn't established.
Plan contact and measurement carefully
Decide which information an initial inquiry needs and where it will go. A form that screens every legal detail may burden visitors and collect more sensitive information than the first contact requires.
Send agreed test inquiries and confirm who receives them. The form's success animation only shows what the visitor saw; it doesn't prove intake got the message. Agree on who watches for delivery failures and who can fix the routing.
Agree on what analytics can collect and share. A connection to practice-management software doesn't justify unrestricted transmission of confidential information. Measurement should support the decisions the firm needs without pretending it captures every channel and signed matter perfectly.
Make accessibility a defined requirement
Agree on the technical standard and what the team will test. The Web Content Accessibility Guidelines (WCAG) 2.2 Level AA may be an appropriate target for the project. Have the firm's legal requirements assessed separately, because one scan, or a promise to meet a standard, can't guarantee a private firm's legal compliance.
Use manual task tests alongside tools. Can a keyboard user navigate, understand the page, and submit an inquiry? Can someone enlarge text without losing essential controls? W3C's review guidance provides an introduction to checking those experiences.
Protect the existing search paths
Create a URL inventory and preserve useful addresses wherever possible. For an approved URL replacement, plan a permanent redirect to the relevant destination and update internal links, canonical references, and sitemap entries together.
After launch, test the public site. An old address that changed should use a permanent 301 or 308 redirect straight to the relevant replacement, which should load successfully with a 200 response. Check that important content survived and try the forms. You can't guarantee unchanged rankings, but you can catch avoidable migration failures.
Agree on maintenance responsibilities and review the site against the original tasks. A good design decision should have a reason beyond whether it's custom. Morpheus Consulting Inc. can help define the requirements and evaluate the practical build options.
