Work / Legal, Maryland

A signed-off design, built so the firm can grow it themselves

A personal injury and criminal defense firm serving Maryland, Virginia and Washington DC. The design was finished and approved before the build began, and the real requirement was everything that happens after launch: new practice areas, new towns, new articles, all without a developer.

At a glance

IndustryLegal, Maryland
ServiceWebsite build
ClientLaw Offices of Alex Poberesky

The problem they came with.

What was actually going wrong, before anything was built.

The design was already signed off

An approved design is a promise. Building something that is nearly it is how a client ends up disappointed by a site that is technically finished.

The page count only grows

Practice areas multiplied by locations is not a fixed number. Hand-building each page would have meant the firm paying a developer every time it wanted to be found somewhere new.

One action, from any page

A visitor arriving on a page about one accident type, in one town, at eleven at night, needs the same single obvious next step as everybody else.

What we built.

Described by what it does for the business. How it is put together is a conversation we are happy to have, but it is not what this page is for.

Built to the design, not near it

The approved design was built faithfully, so what was signed off is what went live.

Templates rather than pages

Practice areas, locations and articles run on templates. The firm fills in the content and the page comes out consistent with the rest of the site.

The free case review, everywhere

Every page ends in the same action, so no visitor has to go looking for how to start.

The results

What is different about the way this business runs now.

The build was the easy half. What was really delivered is a site the firm can keep growing for years without coming back for permission.

Other work like this

Is something in your business working like this?

Describe what is taking the time, and we will tell you whether it is worth automating, including when the answer is no.