Skip to main content
Start a project
Start a project
Instagram

About

Where exceptional design and serious engineering meet.

AMPDUO Studio is a technology company. We design and engineer software for clients, and we build products of our own — which keeps us honest about what it takes to ship something people rely on.

01Company philosophy

Software should earn the trust people place in it.

Who are we?
AMPDUO Studio is a design and engineering company. We work as one team across product strategy, interface design and software engineering.
Why do we exist?
Too much important software is hard to use, hard to maintain or excludes the people who depend on it. We exist to build the opposite.
What do we believe?
That design and engineering are one discipline, that accessibility is a baseline, and that quality shows up in the details users notice.
What do we build?
SaaS products, custom software, web platforms and design systems for clients — and proprietary products of our own, starting with healthcare operations software.

02What we believe

Four principles we don't negotiate on.

The best interfaces remove decisions. We design until the obvious path is the right one.

Well-structured code and consistent design make every future release faster and safer.

Products should work for people using keyboards, screen readers, slow networks and small screens.

Focus states, error messages, empty states and load times are where users decide whether to trust you.

03How we work

Small senior teams, short cycles, visible progress.

  1. 01Discover
  2. 02Define
  3. 03Design
  4. 04Build
  5. 05Validate
  6. 06Launch

Every engagement moves through the same six stages, with concrete outputs at each one. You see working software every sprint, share a single backlog with us, and get estimates we are prepared to defend.

04Design + Engineering

One discipline, not two departments.

  • Designers who understand the platform

    Interfaces are designed with real constraints — data, performance, states and edge cases — in view.

  • Engineers who care about craft

    Spacing, motion, focus states and error messages are engineering concerns, not decoration.

  • A shared design system

    Tokens and components link design files to production code, so what ships matches what was designed.

  • Joint reviews

    Design reviews include engineers; code reviews include designers when the change is visible.

Accessibility

Accessibility is not an add-on.

We design and engineer interfaces with accessibility considered from the first sketch — in the design system, the components and the code — rather than audited in at the end.

We don't make blanket compliance claims. Conformance is assessed per product, against a stated standard, with documented testing.

  1. WCAG 2.2 AA as the baseline

    The Web Content Accessibility Guidelines are our design and acceptance criteria, not an afterthought.

  2. Semantic HTML

    Real buttons, links, headings, landmarks and form controls — so assistive technology understands the page.

  3. Keyboard navigation

    Every interaction works with Tab, Shift+Tab, Enter, Space, Escape and arrow keys where expected.

  4. Screen reader support

    Tested with screen readers, with meaningful names, states and announcements.

  5. Color contrast

    Color tokens validated for contrast in every theme — and color is never the only signal.

  6. Visible focus states

    A clear, consistent focus indicator on every interactive element.

  7. ARIA where appropriate

    ARIA fills genuine gaps in HTML. It never replaces native semantics.

  8. Reduced motion

    Animation respects the reduced-motion preference and never carries essential meaning.

Technology

A deliberate stack, chosen for longevity.

We favor mature, well-supported technology with strong typing, excellent tooling and a healthy hiring market — so what we build stays maintainable after we hand it over.

  • FrontendServer-rendered React applications
  • FrontendComponent-driven interfaces
  • FrontendType safety across the stack
  • FrontendEnterprise application frontends
  • FrontendUtility-first styling
  • FrontendToken-driven stylesheets
  • BackendAPIs and services
  • BackendRelational data, done properly
  • BackendAuth, storage and Postgres
  • InfrastructureCloud infrastructure
  • InfrastructureEdge deployment for web apps
  • DesignDesign and prototyping
  • QualityEnd-to-end and accessibility tests

Frontend

  • Next.jsServer-rendered React applications
  • ReactComponent-driven interfaces
  • TypeScriptType safety across the stack
  • AngularEnterprise application frontends
  • Tailwind CSSUtility-first styling
  • SCSSToken-driven stylesheets

Backend

  • Node.jsAPIs and services
  • PostgreSQLRelational data, done properly
  • SupabaseAuth, storage and Postgres

Infrastructure

  • AWSCloud infrastructure
  • VercelEdge deployment for web apps

Design

  • FigmaDesign and prototyping

Quality

  • PlaywrightEnd-to-end and accessibility tests

05Team

The people behind the work.

Content pendingTeam profiles will be added here. Add real team members in /src/data/company.ts.

06Timeline

Milestones.

Content pendingCompany milestones will be added here. Add real, dated milestones in /src/data/company.ts.

Have something worth building?

Tell us what you're working on. We'll help turn the idea into a product people can trust.

Start a conversationExplore our products