Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Web app development for agencies, planned with your lead and built in your repository

When a client project needs a web application, dashboard, API, integration or AI feature, our engineers can take that part on. We work out the technical questions with your lead, write the answers down as a plan and a task list, and build in your repository.

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's team handles technical discovery, planning and the build on your studio's client projects and hands the work back documented. We work under an agreement with your studio, which keeps the client relationship and the commercial terms.

What we can take on in a client project

A project can use all of these parts or only some. Discovery and the plan can come before anyone decides who builds, and we can also build from a plan your own engineers wrote.

Solution
Websites
  • Technical discovery through your leadWe work through the client's goals with your lead: who will use the product, what it has to do, which systems and data it touches, and what constrains it. When your lead brings us into a call with the client, we cover the technical questions.
    01
  • A written plan and task listThe findings become a plan in plain language: architecture, integrations, data, risks and trade-offs, and the questions still open. A task list follows, with each task described well enough for your engineers or ours to start on it.
    02
  • Web applications, dashboards and APIsInternal tools, customer portals and dashboards, with the APIs and databases behind them, built in the repository your studio names. The code follows that repository's conventions, branching and review rules, so your engineers can work in it next to ours.
    03
  • Integrations and AI featuresConnections to the client's CRM, payment or data systems through their APIs, and AI features inside the product, such as search, document handling or an assistant that answers from the client's own content. Each one is tested with sample data before users see it.
    04
  • Release safeguardsVersion control with a branch for each task, QA, a staging copy for review and an automated deployment pipeline. We follow your studio's setup where one exists and add the missing parts where it doesn't.
    05
  • Notes after every technical conversationAfter each call or technical discussion, your lead receives written notes: what was decided, what is still open, any blocker we see coming, and the next steps with an owner for each. They are written so your lead can forward them to the client unchanged.
    06
  • Handover of code, documents and accessWhen the work ends, the code sits in the repository you named, with setup instructions, a short architecture note and a list of the services and accounts the application depends on. Access issued to our team is then closed.
    07
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

What we ask your studio for

  • A lead who owns the accountA person at your studio who runs the client account, brings us the client's questions and approves the plan and each release. Client decisions reach us through them.
    01
  • What the client has already sharedBriefs, designs, call notes or recordings, existing documentation and decisions already made, so discovery starts from what is known.
    02
  • Access to code and servicesAccess to the repository, staging and the services the product uses, issued to each of our team members by name, so your studio can remove it at any point.
    03
  • Coding and review conventionsCoding conventions, branching and review rules, your definition of done, and any security or data-handling terms in the client's contract.
    04
  • Rules for client contactWhether we join client calls, whose name appears on shared documents, and which topics stay with your studio, such as budget, contract terms and new work.
    05

How a project moves between your studio and our team

  1. [Briefing with your lead]

    Your lead takes us through the client, the project and what has been agreed so far. We read the existing material and list what we still need to know.

    Step 01
  2. [Questions to your lead, then the client]

    We settle what we can with your lead and the material. The remaining questions go to the client through your lead, or in a call your lead sets up.

    Step 02
  3. [Sign-off on the plan]

    Your lead reviews the plan and task list. Anything that needs a client decision is marked for the client, and building starts only on approved tasks.

    Step 03
  4. [Build in the agreed order]

    Tasks are built on branches, reviewed under your rules and shown on staging. A change to the plan goes to your lead before the work continues.

    Step 04
  5. [Release]

    Each release goes out once your lead approves it, through the checks and pipeline set out in the plan.

    Step 05
  6. [Handover or the next stage]

    At the end of the agreed scope the work is handed over. If the client wants more, the next stage starts from the same plan and notes.

    Step 06

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

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

From the Norml blog.

Questions about working on your client projects

Can someone from your team lead technical calls with our client?
Yes, for the technical part of a call your lead arranges. We agree the questions with your lead beforehand and send notes afterwards. Your lead stays the client's contact for scope, budget and priorities.
Can we hire one of your engineers part time instead?
No. Norml works as a team under its agreement with your studio, and each project gets the people its work needs. We don't place individuals on a studio's staff or commit to where the people on a project are based. Times for client calls are agreed per project.
What if our client contacts your team directly?
We pass the message to your lead and reply only once your lead has agreed the answer, so the client hears one position. Commercial terms, scope changes and new work stay between your studio and the client.
What happens when discovery turns up work nobody planned for?
We write it down with its effect on the plan and send it to your lead before any work on it starts. Your studio decides whether and how to take it to the client.
Can we start with discovery and a plan only?
Yes. Discovery can end with the written plan and task list, and your own engineers can build from it. If we build it later, the work starts from that plan.
Will you suggest further work to our client?
Not directly. If we see something the client may need later, such as a reporting view or another integration, it goes into the notes for your lead, and your studio decides whether to raise it.
Which AI features can you add to a client's product?
Features that work from the client's own data, such as search, document classification, summaries or an assistant for customers or staff. The plan records which model and provider to use, what data may be sent to it and what happens when an answer is uncertain.
Do you build native mobile apps?
No. We build web applications that work in a phone's browser and APIs that a native app can call, while native iOS and Android development stays with another team. Mobile app UX and UI design is a separate service of ours.
Do you take on WordPress projects too?
Yes, as a separate service: WordPress development for agencies, which covers themes, blocks and tickets on WordPress sites under its own process.
Where do prices and timelines come from?
We agree them with your studio for each project, once discovery has shown what the work involves. Your studio then sets its own terms with the client.

Read our development case studies

See what each client started with, what we built and which systems the work connected.

See all case studies