Strategy before design
What the site has to prove, to whom, and in what order. Agreed before anything is styled, so design review is about design rather than about what the pages are.

Norml Studio’s Florida office is in Fort Myers, about seventy-five miles south of Sarasota — close enough to sit in a room when it matters, far enough that we will not claim to be your neighbour. What we bring is the work: architecture, a design system, a build, and a site you own afterwards.
A few clients we’ve worked with










We do not have an office in Sarasota and are not going to draw one. Norml Studio’s Florida office is in Fort Myers — about 75 miles north of our Fort Myers office — and we work up the Gulf coast from it. The distance changes how easy it is to meet, not how the work runs.
The design was strong at launch and has not moved since, because changing it means opening a file only the designer has.
Each partner, service or location was added as a one-off page, so the site now has four visual languages.
The enquiry form drops into a shared inbox and whoever opens it first retypes it somewhere else.
A referral looks the firm up, finds a site that looks like the last redesign but not like the business today, and draws a conclusion.
Search traffic arrives and nobody can say which service it converts in, because conversion is one number.
The same scope we run everywhere. What is different about this market is not the discipline — it is that clients here are unusually design-literate, so the thing that separates studios is what happens after the pretty screens.
What the site has to prove, to whom, and in what order. Agreed before anything is styled, so design review is about design rather than about what the pages are.
A page per service and per real situation a client arrives with, not one page called Services. Which pages exist, what each has to prove, and how someone finds the one that describes their own problem.
Components, states and responsive rules rather than a stack of static screens. This is the part that decides whether the site still looks considered in three years, and it is the part most engagements skip.
WordPress your team can edit, or a Next.js front end where the job needs one. A new service page or a new partner should not need a designer.
The form, the qualification and where the enquiry goes — routed into your CRM with the right owner and immediate notification, the pattern we built for Metroplex Homebuyers, whose forms had been running separately from their CRM with manual routing eating hours a day.
Search Console, analytics and conversion tracking configured at launch, per service rather than as one number.
The files, the design system, the accounts in your name, and a session with your team. Nothing about the site should depend on us staying.
The exact scope depends on the page count and the stack. A typical engagement hands over the following:
A page map covering every URL, its job, and what links to it.
A Figma design system with components, states and responsive rules.
Page content written against what the business actually sells.
A built site on WordPress or Next.js that your team edits without a developer.
An enquiry route wired into your CRM, with the right owner and notification.
A redirect and launch plan, so an existing site keeps the traffic it has.
Analytics and Search Console configured on day one, tracked per service.
Every account and file in your name, plus a handover session.
The same services we run everywhere, in the order a website usually needs them. Each one can be taken on its own.
Our process
We read the analytics, the current site and how enquiries actually arrive. Not a questionnaire. You get the diagnosis first.
[ 01 ]Page map and URL plan, agreed before design starts. A sitemap you can argue with.
[ 02 ]Wireframes, then the system in Figma. Components and states, not screenshots.
[ 03 ]The site, then the enquiry routing behind it. Editable by your team.
[ 04 ]Redirects, analytics, Search Console, speed, then the files and the session that make you independent.
[ 05 ]