Northstar Digital
What we do

Services

Six disciplines that combine into one delivery team. Most engagements use two or three of them, led by the person who scoped the work.

Every project starts with the same question: what has to be true for this to work commercially? The answer usually spans more than one discipline, which is why we do not sell design and engineering as separate contracts.

Web Development

Marketing sites and content platforms that load fast, rank well and stay editable by your own team.

  • Core Web Vitals budgets enforced in CI
  • WCAG 2.2 AA as a contract term
  • Editor training and written handover

Software Development

Customer portals, internal tools and integrations built on boring, well-supported technology.

  • Typed end to end, tests where they earn their keep
  • Runs on your infrastructure, not ours
  • Written architecture decisions

UI/UX Design

Interface design and design systems for dense, regulated products with demanding users.

  • Prototype the three journeys that carry the business case
  • Component library your engineers can implement
  • Tested with keyboard and screen reader

Digital Strategy

Evidence-led planning that ends with a prioritised roadmap and a defensible business case.

  • Analytics, interviews and a technical audit
  • Prioritised roadmap with effort ranges
  • Written business case you can present

Branding

Identity systems built for B2B credibility and delivered as working, documented assets.

  • Verbal and visual identity together
  • Delivered as production-ready assets
  • Guidelines short enough to be followed

Consulting

Technical due diligence, architecture review and fractional leadership, by the day.

  • Written findings, ranked by risk
  • No recommendation that requires hiring us
  • Available within two weeks
Process

The same four phases, whatever the discipline

Phase boundaries are where you can change your mind cheaply. We make them explicit rather than letting scope drift.

  1. Discovery

    Two weeks of interviews, analytics review and a technical audit. You leave with a written problem statement and a prioritised scope.

    1–2 weeks

  2. Design

    Wireframes, then a component-level design system. We prototype the three journeys that carry the business case before anything is built.

    2–4 weeks

  3. Build

    Two-week increments on a staging URL you can use from day one. Accessibility and performance budgets are checked in CI, not at the end.

    6–14 weeks

  4. Launch and iterate

    Migration, monitoring and a four-week hardening window. Then a quarterly review of what the data says to change next.

    Ongoing
Questions

How engagements are structured

Who owns the code and the designs?
You do, from the first commit. Repositories live in your organisation where possible, and design files are transferred at the end of each phase.
How do you handle accessibility?
WCAG 2.2 AA is written into the statement of work. We test with keyboard and screen reader during development, and automated checks run in continuous integration so regressions fail the build.
What happens after launch?
A four-week hardening window is included in every project: monitoring, bug fixes and the small changes that only surface under real traffic. After that you can move to a retainer or take it in-house.
Next step

Tell us what you are building

A 30 minute call is usually enough to tell whether we are the right studio for the problem. No pitch deck, no obligation.

Book an intro call See our work
Next step

Tell us what you are building

A 30 minute call is usually enough to tell whether we are the right studio for the problem. No pitch deck, no obligation.

Book an intro call See our work