01
Product language
Create one coherent visual, interaction, content, and behavioral system across the product.
Kris Haamer · Product, design and engineering
I turn product ambiguity into a coherent system people can use and teams can extend.
I connect product strategy, interaction design, frontend engineering, design systems, developer experience, documentation, motion, and AI-assisted delivery.
Best suited to ambitious product teams where the interface, brand, technical model, and customer experience still need to become one thing.
What I can own
One product language across every surface.
02
Customer product
Design onboarding, dashboards, workflows, settings, recovery paths, and trust-critical states.
03
Components in code
Turn decisions into reusable React and Next.js components, patterns, and accessible implementation.
04
Developer experience
Make APIs, technical concepts, documentation, examples, and integration flows easier to understand.
05
Brand in motion
Connect the product to launch pages, editorial systems, motion, demos, and public storytelling.
06
AI-assisted delivery
Use bounded AI workflows for research, documentation, quality checks, accessibility, and product signals.
Evidence, not adjectives
Built across research, systems, interfaces, and production.
Production product system
HAAM
An evolving Next.js platform spanning product tools, authenticated workspaces, localization, accessibility, performance, analytics, and AI workflows.
Explore the work →Financial AI research
Green Filter
A product direction based on 675 valid survey responses, 32 interviews, and 32 prototype tests around sustainable shopping, saving, and investing.
Explore the work →Public digital infrastructure
WiFi.ee
A long-running public Wi-Fi platform rebuilt across product architecture, maps, geospatial data, APIs, permissions, storage, and operational recovery.
Explore the work →Cultural platform delivery
Viirus Theatre
Expressive design connected to frontend engineering, CMS structure, multilingual content, accessibility, performance, and maintainability.
Explore the work →Early-team value
Responsibility without role-boundary theatre.
Useful when the team needs someone to make the judgment call, build the artifact, explain the decision, and stay responsible after launch.
Autonomy with visibility
Drive high-impact work independently while keeping decisions, trade-offs, and progress legible.
Founder empathy
Work comfortably with incomplete information, limited time, technical debt, and commercial pressure.
Working artifacts
Move from evidence and framing into prototypes, code, documentation, and production learning.
System-level craft
Care about visual detail alongside states, permissions, accessibility, performance, and maintainability.
Best fit
Bring me into the room where product, design, engineering, developer experience, and brand overlap.
That is where the product is hardest to explain, easiest to fragment, and most valuable to make coherent.
Start a conversation →