Book a diagnostic

Product and brand design for founders and product teams

Verne designs products and brands that customers understand on first use. We watch real people use what you have, fix the screens where they stall, build a design system your engineers can ship from, and shape a brand that fits the company you are. Designers and engineers work in one team, so decisions survive the handoff.

Book a design reviewTry the example below

One quote form, before and after

Drag the handle across a request-a-quote form. The numbered notes come from watching people use the old one, which is where a redesign should start.

A drawn example of a common fix. Before on the left, after on the right.

What watching people found

  1. 1Twelve required fields before anyone has talked to you
  2. 2The email is asked for twice
  3. 3The grey button reads as disabled, so people wait

What changed

  • Three fields, asked in the order people think
  • Labels sit above fields and stay visible
  • One main button at full contrast

12fields became3

What design covers

  • Research

    Interviews and usability sessions with your real customers, before anything is drawn.

  • UX and UI

    Interfaces tested with real users, so your product feels obvious from the first tap. If it needs a manual, we redesign it.

  • Design systems

    Components, tokens and rules your engineers build from, so each new screen matches the last.

  • Prototypes

    Clickable flows people try before any production code is written.

  • Brand identity

    Logo, type, colour and voice, with guidelines your team can apply alone.

  • Motion

    Movement that explains a change on screen, and stops when a visitor asks for reduced motion.

For your engineers

Tools

Figma with variables and component libraries; prototypes in Figma or in code; design tokens exported to CSS and native apps.

Accessibility

WCAG 2.1 AA as the floor: 4.5:1 text contrast, visible focus, a label on every field, 44px targets and reduced-motion fallbacks.

Handoff

Each component specified with its states (hover, focus, disabled, error, loading), built in the app or a component workbench, and reviewed against the design before merge.

How design hands off to engineering

Designers sit in the team that builds the screens. Each component is designed and coded once, with the same name in the design file and in the code.

We test with five to eight people a round, and run rounds until testers finish the main task without help. Accessibility checks run in both places: contrast, labels, focus order and tap targets.

The field app technicians switched off

A Dutch facilities company gave 300 technicians a tablet app for job reports. Six months later, most still wrote on paper and typed it up at night.

The app worked in the office. It failed on a roof in February.

  1. Go where the work isDesigners spent four days with technicians on site: gloves on, screen glare, one bar of signal, a ladder in one hand.
  2. Fix what they sawTouch targets grew to the size of a gloved thumb, the main actions moved to the bottom of the screen, contrast held up in direct sun, and reports saved offline.
  3. Test with the scepticsThe five technicians who had refused the app tested every version. A change shipped when they could finish a report on site.
  4. Hand over a systemEngineers built the components into the client's design system, with the field rules written down for the next team.
field-audit/job-report-step-3.txt
Screen: Job report, step 3 of 5Tap target "Add photo"     28 × 28 px    gloved thumb needs ≥ 56Text contrast in sunlight  2.9 : 1       outdoors needs ≥ 7 : 1Save without signal        fails         queue and retryPrimary action             top right     move to thumb zoneDelete beside "Add photo"  4 px apart    separate by ≥ 16 px
  1. Session logs64% of abandoned reports stop at the photo step.
  2. DesignerWatched it on a roof: a gloved thumb hits Delete next to Add photo. Targets doubled and pulled apart.
  3. Your field supervisorApproved after the five technicians who had refused the app each finished a report on site.

Sectors

Questions about product and brand design

Can you redesign something that already exists?

Yes. We review the current product, find where users struggle and propose changes before any design work is agreed.

Do we get the design files?

Yes. Design files, the component library and the brand guidelines are handed over with the code, in accounts your team owns.

Do you design for other languages and scripts?

Yes. We set type and layouts for each script your users read, including right-to-left languages, and test each language with native readers.

Book a design review

Send a link to the screen or flow customers struggle with. We watch people use it and return the problems ranked by how many people they stop.

Book a design reviewChoose another practice