


We define a maintenance scope around the actual platform, hosting and enquiry functions. The work records updates, checks and follow-up issues so the firm knows what was handled and what still needs a decision.
A few clients we’ve worked with




















Website maintenance for law firms: update and recovery plan, website checks, maintenance record.
A live website keeps changing after the project ends — plugins, browsers, integrations, content. Unowned, it degrades quietly until something visible breaks.
Recurring checks on the systems that matter catch a broken form or a failing integration while it is still cheap.
An agreed way for work to enter and be prioritised means small changes stop depending on who someone knows.
Keeping the stack current is maintenance. Recovering from a compromise is a project.
Agree these work areas with the firm before implementation. Access, content approval and any external-system requirements are recorded in the scope.
“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“Norml Studio's professionalism and responsiveness were impressive.”
The deliverables correspond to the work areas agreed for this engagement.
Explore the wider scope behind the website.
Explore the scope, deliverables and process for each part of the website.
Our process
Review the firm’s current website and the inputs needed for website maintenance. Confirm the responsible people, access and acceptance criteria.
Inventory the components covered by the agreement. Establish the backup, restore and update process supported by the hosting setup. Check agreed pages and enquiry journeys after relevant changes. Review reported failures and distinguish content requests from technical maintenance.
Document completed work, unresolved issues and changes needing separate scope. Agree who receives incidents and which response arrangements apply. Record open decisions and the next action for each one.
No account layer between you and them. These are the Norml specialists this work runs through.

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedWebsite 2.0 combines strategy, design, development and launch in one engagement.