Skip to content
Nordwell

Services

Six things, done properly

We stay narrow on purpose. Everything here is delivered by the people you meet in the first call — we do not subcontract and we do not staff juniors on unfamiliar work.

Product strategy

Find the version of the product worth building.

Typically 3–5 weeks

Research, positioning and roadmap work for teams deciding what to build next. We pressure-test the idea against real users and real constraints, then write down what we learned so the whole team can act on it.

What you get

  • Stakeholder and user interviews
  • Opportunity map and problem statement
  • Prioritised roadmap with sizing
  • Success metrics and instrumentation plan
Talk about product strategy

Product design

Interfaces that feel obvious the first time you use them.

Typically 6–12 weeks

End-to-end interface design: flows, wireframes, high-fidelity screens and prototypes. Every state gets designed — empty, loading, error and the awkward ones in between — so engineering never has to guess.

What you get

  • User flows and information architecture
  • High-fidelity screens for every state
  • Interactive prototype for testing
  • Annotated handoff in Figma
Talk about product design

Design systems

One source of truth your designers and engineers both use.

Typically 8–14 weeks

We build token-driven component libraries that ship as code, not just as a Figma file. Accessibility, theming and documentation are part of the component, not a follow-up ticket.

What you get

  • Design tokens for colour, type and space
  • Documented React component library
  • Figma library kept in sync with code
  • Contribution guide and governance model
Talk about design systems

Web engineering

Production front-ends built to outlive the project.

Typically 8–20 weeks

TypeScript, React and Next.js work delivered in two-week cycles. We write the tests, wire up the pipeline and leave a codebase your team can extend without calling us.

What you get

  • Typed, tested React application
  • CI/CD pipeline and preview environments
  • Analytics and error monitoring
  • Architecture notes and handover sessions
Talk about web engineering

Performance & accessibility

Fast for everyone, usable by everyone.

Typically 2–6 weeks

An audit and a fix programme, in that order. We measure against Core Web Vitals and WCAG 2.2 AA, prioritise by user impact, then do the work alongside your team.

What you get

  • Core Web Vitals and Lighthouse audit
  • WCAG 2.2 AA conformance report
  • Prioritised remediation backlog
  • Regression budgets wired into CI
Talk about performance & accessibility

Brand & marketing sites

A site that sounds like you and converts like it means it.

Typically 5–9 weeks

Positioning, art direction and a marketing site built for the people who have to update it. Editable content, clean analytics, and page speed that does not undo the ad spend.

What you get

  • Messaging framework and voice guide
  • Art direction and visual identity
  • Responsive marketing site build
  • SEO fundamentals and page-speed budget
Talk about brand & marketing sites

How we work

The same five steps, every time

Scope changes between projects. The shape of the engagement does not.

  1. 01

    Discover

    A week of interviews, analytics archaeology and competitive teardown. We leave with a written problem statement everyone actually agrees on.

  2. 02

    Define

    Flows, information architecture and a prototype thin enough to test but real enough to argue about. Scope gets cut here, not later.

  3. 03

    Design

    Interface design in a component-driven system, with tokens, states and edge cases handled before a single line of production code.

  4. 04

    Build

    Two-week cycles, working software at the end of each, deployed behind a flag. Your engineers pair with ours the entire way.

  5. 05

    Ship & hand over

    Launch, instrument, then transfer everything — repos, design files, documentation and the decisions behind them.

Not sure which of these you need?

Most projects start as one thing and turn out to be another. Describe the problem and we will tell you honestly what it looks like from here.

Start a conversationhello@nordwell.example.com