Practice-area architecture
A page per practice area and per real situation a client arrives with, not one page called Services. Which pages exist, what each one has to prove, and how someone finds the one that describes their own problem.

Norml designs and builds websites for law firms — the practice-area architecture, the design system, the build, and the intake path behind it. Because in legal the site is not a brochure. It is the first hour of the client relationship, and most of them lose the client in it.
A few clients we’ve worked with










Every practice area gets the same page, so the person with a specific problem never sees their problem described.
The enquiry form drops into an inbox, and whoever opens it first retypes it somewhere else before anyone calls back.
A visitor in the middle of a bad week has to work out whether you handle their situation, what it costs, and what happens next, from a page that answers none of it.
The attorney biographies are the most complete pages on the site, and the practice pages are the thinnest.
Traffic arrives from search and paid ads, nobody can say which practice area it converts in, and the budget is set on a guess.
Seven things, in the order we do them. Web design for a law firm starts with the cases you actually want and the enquiries you actually get; Norml can take the whole scope or work beside your marketing team and your intake staff.
A page per practice area and per real situation a client arrives with, not one page called Services. Which pages exist, what each one has to prove, and how someone finds the one that describes their own problem.
The form, the qualification, and where the enquiry goes. We build conditional forms that adapt to the situation described, then route straight into the practice-management or CRM system with the right owner and immediate notification — the same pattern we built for Metroplex Homebuyers on Zoho, including staged email and SMS follow-up.
Written for someone deciding whether to call, in their words rather than the firm’s. Reviewed by your attorneys, who stay the authority on every statement about the law.
Components, states and responsive rules, so the tenth practice-area page looks like the first and a new attorney biography does not need a designer.
WordPress, on a theme your team can actually edit — including replacing a page-builder site that has become too slow and too fragile to change.
Where the current site already brings in cases, we rebuild in slices and check traffic and tracking at every step before the next one ships. That is how Diet vs Disease came off a page builder onto a custom theme with its organic and paid traffic running throughout.
Conversion tracked per practice area, so you can finally see which work the marketing is actually buying, plus the technical and content SEO to earn the traffic. For The Farm Soho the same discipline produced a content system of 500-plus indexed pages an editor manages without touching code.
The exact scope depends on the number of practice areas and offices. A typical engagement hands over the following:
A page map you can hand to anyone — every URL, its job, and the practice area it serves.
A Figma design system with components, states and responsive rules.
Practice-area and attorney page templates written against the work you actually take.
A built site on WordPress your team edits without a developer.
Intake forms wired into your practice-management or CRM system, with routing and follow-up.
Conversion tracking per practice area, connected to your ad accounts.
A staged migration plan with redirects, so a site that already earns keeps earning.
A handoff session and the files, so nothing about the site depends on us staying.
The services a firm usually buys together, in the order they matter. Each one can also be taken on its own.
Our process
We read the analytics and the ad accounts, and we follow one real enquiry from the search to the callback. Not a questionnaire. You get the diagnosis — where the client is lost and what it costs.
[ 01 ]Practice-area structure, URL plan, and what each page has to prove. A sitemap you can argue with before anything is designed.
[ 02 ]Wireframes first, then the system in Figma. Practice, attorney and intake templates, not a stack of static screens.
[ 03 ]The site, then the intake and routing behind it. Editable by your team without a developer.
[ 04 ]Redirects, analytics, Search Console, speed, and conversion tracking live per practice area from day one.
[ 05 ]