User research
Customer interviews, journey mapping, competitive teardowns. The work before the work.
Service · UI/UX & Product Design
Design that earns its keep.
Research, wireframes, clickable prototypes and design systems — shaped to the operational system they'll ship inside. Not pretty pictures handed over the fence to engineering.
01Product & UX research
02Wireframes & flows
03Clickable prototypes
04Design systems
Typography 2 families
Aa Display
Newsreader
Regular · Italic · Medium
ABCDEFG · 0123456789
Aa Text / UI
Inter
The quick brown fox jumps over the lazy dog.
Regular · Medium · Semibold
H1 H2 H3 BodyLabel
Color 5 core
Apricot
Primary accent · CTAs
Moss
Secondary · italic accents
Forest ink
Headlines · text
Cream
Canvas · background
Blush
Tints · surfaces
The case for product design
Design is the cheapest place to fail.
A wrong screen in Figma costs an afternoon. A wrong screen in production costs a sprint. We use design to fail every assumption — fast, cheap, and reversibly — before engineering touches a line of code.
- Wrong screen in Figma
- ~4 hrs
- Reverse a decision before lunch.
- Wrong screen in production
- ~1 sprint
- Now engineering is paying for it.
- Iterations before build
- 5–12
- Bugs caught in design
- ~70%
What we deliver
Six artefacts, one integrated process.
Everything we ship plugs straight into the engineering pipeline — no "designer-to-developer" theatre.
Wireframes
Low-fidelity blueprints of every screen. We argue about flow before pixels.
Clickable prototype
Figma protos with real interactions you can test on customers before engineering.
Hi-fi UI design
Pixel-perfect interfaces with state coverage — empty, loading, error, success.
Design system
Tokens, components, patterns. Designed in Figma, mirrored in Tailwind. One source of truth.
Engineering handoff
Specs, redlines, Tailwind classes. Since we build too, the handoff is mostly already done.
Design systems · spotlight
One source of truth.
Every Noetic design ships with a system: colour tokens, type ramps, spacing scale, components. The same primitives live in Figma and in Tailwind, so changing a token updates everything everywhere.
- Token-driven
- Figma ↔ code parity
- Full state coverage
- Accessibility baked-in
Color tokens
moss
moss-2
forest
apricot
apr-2
cream
Type scale · Newsreader + Inter
Display Newsreader · 72
Heading Newsreader · 32
Body Inter · 17
OVERLINE Inter · 12
Button · primary / secondary / ghost
Primary Secondary Ghost
How we work
From customer interview to engineering handoff.
Five stages, six weeks of designed-and-tested work before engineering starts the build. Each stage has a named artefact — nothing handed over the fence.
- 01 · Week 1
Research
Customer interviews, JTBD framing, audit of what already works.
- 02 · Week 2
Wireframe
Low-fi flows. Get the structure right before the styling.
- 03 · Week 3
Prototype
Clickable. We test it with real customers before pixels get polished.
- 04 · Week 4–5
Hi-fi & system
Visual design with full state coverage; design system shipped alongside.
- 05 · Week 6+
Handoff & build
Tailwind-mapped specs. Or — since we build too — we just start shipping.
Featured · Product design
See the flows we've designed — and the products they shipped into.
Construction · DataConstruction Market Intelligence
Healthcare · AI PlatformAntenate Health
EdTechConfidence Learning
Activation
+58%
Support tickets
−42%
Time to first value
3min
CSAT post-redesign
4.7/5
Typical post-redesign outcomes, aggregated across recent product-design engagements.
Do you do design without development?
Yes. Plenty of clients engage us only for research, wireframes, prototyping, or a design system — then take it to their own engineering team. Handoff is part of the deliverable.
How long does a design engagement take?
A focused design sprint runs 4–6 weeks; a full design system + product UI typically runs 8–10 weeks. Bigger surfaces stretch further.
Do you work in Figma?
Yes — Figma is our default. You get the file, the variables, the components, and the prototype links. If you have an existing Figma library, we'll work inside it instead of imposing ours.
What's a "design system" — do I really need one?
If your product has more than ~10 screens or more than one engineer, yes. Tokens (colour, type, spacing) and shared components mean every new screen costs hours instead of days, and the product stays consistent as the team grows.
Do you do user research too?
Yes. Customer interviews, usability tests on prototypes, and competitive teardowns are baked into the front of every engagement.
How is your design different from a generic agency?
Because we ship the code, our design accounts for the whole operational system around the product — auth, billing, ops, integrations. You don't end up with a screen that engineering says "we can't build that."
Try a free tool before you brief us.
All tools Design first. Build second.
Let's design it first.
30 minutes. Bring your product idea or existing one — we'll talk through where research, prototypes, or a design system would save the most pain.