Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

WordPress development for agencies, built to your designs and handed back to your team

We take on WordPress work for agencies: whole sites and single tickets, for your clients or for your agency's own sites. Your designs and copy become a working theme, your review rounds decide what changes, and the finished code goes back to your team with documentation it can maintain.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml handles the build: theme, blocks, content types, custom code, staging and QA. Your agency keeps the client relationship, the creative direction and the approvals. Work can arrive as a whole site, as wireframes that need page designs first, or as a single ticket, and support can continue after launch.

What your agency can hand us

Each request starts from decisions your team has already made: the design, the copy and what the client approved. The parts below can be taken alone or combined in one project.

Solution
Websites
Platforms
WordPress

Builds from your Figma files and copy

Approved Figma files and copy become a custom WordPress theme with reusable blocks and editing fields. Missing states, such as error messages, empty fields and phone layouts, go to your designer as a list before the build, so nobody has to guess them in code.

Page designs from your wireframes

When your team supplies wireframes, messaging and copy without final designs, our designers create the pages in Figma within the brand you provide. Your creative lead approves them before development, and each approved section is then built as a block.

Content types and custom code

Custom post types, taxonomies and fields for what gets published, such as case studies, resources or job listings, plus PHP and JavaScript for behavior the design needs beyond standard blocks. Forms are connected to the CRM or inbox each project uses.

Tickets on sites you already run

Single tickets or overflow work on WordPress sites another developer built. We read the theme and plugins before changing anything, follow the conventions already in the code, keep each change in its own commit and note what changed and why.

Your review rounds and client relationship

We report to your project lead and work through the review and approval rounds your agency already runs. Questions for the client go through you, and we stay out of client conversations unless you bring us in.

Working alongside your developer

If your agency has its own WordPress developer, we agree who owns which parts of each site and work in the same Git repository under your branching and code review rules, so changes from both teams are reviewed before they reach staging.

Handback your team can maintain

At handover the code sits in your repository with a short guide to its templates, blocks and fields, an editing guide for whoever publishes on the site, and a list of plugins and licenses. Accounts created for us are removed or passed to you.

Repeatable launches and support after them

The launch checks agreed on the first project, covering forms, tracking, redirects and production settings, become the checklist for every later launch. After launch, fixes and new pages continue under a monthly plan or as separate projects.

“Norml Studio's professionalism and responsiveness were impressive.”
Josiah BallHOMEECClutch review ↗
“They were proactive in suggesting improvements we hadn't considered.”
Lucas SeyhunThe Farm SohoClutch review ↗
“They delivered what they said they would, on time.”
Gaius CooperStreamline Pump SolutionsClutch review ↗
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
Emma EstefaMetroplex HomebuyersClutch review ↗
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
Bret MillerDoor Knock ProClutch review ↗
“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”
Saima AhmedGoPetZenClutch review ↗

What we need from your agency

Designs, wireframes and copy

Figma files or wireframes, the approved copy and the brand guidelines, with a note on which parts are final and which are still open.

Repository and site access

Invitations to the Git repository, the staging site and the WordPress admin in our team's own names, which you can revoke at any time.

Your standards and definition of done

Coding conventions, the browsers and devices you test on, any accessibility requirements in the client's contract, and what a ticket must show before you accept it.

One lead who approves

A project lead who collects comments from your team and the client and approves each round, so change requests reach us from one place.

Account ownership on each project

Who holds hosting, the domain, paid plugin licenses and analytics for each site, your agency or the client, and who carries out the launch.

For ticket work, the ticket and your usual handoff

The ticket with its expected result, and the way your team normally receives finished work, such as a pull request or a staging link.

How work with an agency runs

  1. A real project or ticket first

    The first site or a single ticket shows how questions, reviews and QA move between our teams, so no separate onboarding phase is needed.

  2. Files and code review

    We go through the designs, copy and any existing code, then agree the templates, blocks and fields with your lead before the build.

  3. Build on staging or in a branch

    Your team can follow the work there between review rounds, and nothing reaches the live site before your approval.

  4. Review rounds through your lead

    Feedback arrives through your project lead in rounds. Changes are made on staging and listed per round, so you can pass the list on to the client.

  5. Launch on the agreed checklist

    Your team or ours launches, as agreed. The launch checklist is then run on the live site, and its results are recorded for your team.

  6. The next site and changes after launch

    After handback, the next site or ticket starts with the same conventions and review route, and changes after launch are tested on staging and logged before release.

Max Tymoshyn, founder of Norml Studio

Let's chat

“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

Questions from agencies

How do you check the build against our designs and copy?
Each template is compared with its Figma frame at every width your designer drew, using the approved copy rather than placeholder text. Headings, button labels and form messages are checked against the copy document as well. Each review round starts after these checks pass.
How do you handle custom functionality in a design?
Usually as custom blocks, PHP and JavaScript in the site's own code. A plugin is used where a maintained one already does the job, and it is chosen with you, since your team inherits its updates and license. Anything that changes the agreed scope goes to your lead before it is built.
Can you work on sites built with Elementor or another page builder?
Yes. Tickets on a builder site usually stay in the builder already in use, so your team keeps editing the way it does today. When a site has outgrown its builder, we can propose moving it to a custom theme in stages, scoped as separate work.
What happens if the existing code is hard to change?
Before starting, we tell you what the ticket touches and what is risky in that part of the code. The ticket itself stays within its scope. If a cleanup would make later tickets easier, we describe it as separate work for you to approve.
Can you take urgent work?
Yes, when the code and the deadline allow it. We look at the ticket, the code and the date first, and confirm whether we can meet it before any work starts.
Who owns the code when the work ends?
The code goes into the repository you name, your agency's or your client's, with its documentation, so nothing stays only on our side. Ownership terms are written into our agreement with your agency.
What falls outside this arrangement?
Discovery and strategy with your client, brand creation, and marketing material such as decks, social graphics and print pieces are scoped separately. Member areas, payments or booking flows need their own discovery before they are built. Hosting and paid plugin licenses are not included unless the agreement says so.
Each case study covers the starting point, what we built and what changed after launch.

See more of our WordPress work

See all case studies