Product audit
We figure out what you actually need before you spend on it.
Complex technology, made tangible.
Karda is an independent product design studio for founders and companies building in AI, deep tech, consumer hardware and beyond. Interfaces, working prototypes and the story around them, from 0 to 1.
The hardest part of complex technology is the part people touch.
Good technology rarely fails in the lab. It stalls when it meets people: an investor who can’t picture it, a partner who can’t see where it fits, a customer who gives up at setup, a team that never adopts it.
Karda works in that gap. I design the layer people actually touch — the interfaces, the onboarding, the product around your technology — and the prototypes that let people believe in it before it ships.
What I help you do.
Make your vision believable
Let investors, partners and pilot customers try it before it ships.
- Website or landing page
- Deck
- Demo flow
- Working prototype
Make your product usable
Turn complex technology into a product people can actually run.
- Interface design for web, mobile or operator software
- Hardware UX
- Design systems
- Build-ready specs
Make it last
Find what stops people using it, and fix that first.
- User research and testing
- Service design
- Onboarding and setup flows
- Prioritized fixes
Two ways in, depending on your stage.
Fixed project
Scope and timeline agreed up front, 2 to 6 weeks.
- A written scope, agreed together
- Technical deep dive into your stack
- Interface design, system, prototype
- A plan for what to test or build next
Starting at
€6,500
Embedded design
Available January 2027
A senior product designer in your team.
- Days per month, in your tools and rituals
- Direct work with your team and engineers
- Continuous research, design and build
- AI-native systems that grow with the product
- Monthly review of next moves
Not ready for a full project? Start with your most pressing problem.
Landing page or deck
One focused piece for your next raise, pilot or launch.
Let’s talk about what you’re building.
Which one fits, and what it costs, comes out of that call. Most founders aren’t sure what they need — we work it out together.
Me, from the first call to the last file. Karda is a one-person studio with 8+ years of product design across telecom and energy, on interfaces used by millions of people. No account manager, no junior taking over once the contract is signed.
That’s the job. Every engagement opens with a technical deep dive into your docs, specs and landscape — the same reading an early hire would do. I won’t match your physicists on the physics, but I will understand the constraints well enough to design against them rather than around them.
No. Deep tech is where the work is sharpest, but the pattern — hard technology, a narrow window to make it legible — shows up in consumer hardware, industrial software and research tools too. If the product is complex and the stakes are real, it’s in scope.
A 30-minute intro call. We talk through what you’re building, where you are, and what’s blocking. From there I scope the smallest engagement that moves you forward — a fixed project, something smaller if that doesn’t fit yet, or embedded work once it opens in January 2027.
Two to six weeks, sized to the problem. It opens with framing and a technical deep dive, then design. The last stretch builds a working prototype or a production-ready interface, and a plan for what comes next. Scope, deadline and price are fixed before it starts.
Embedded engagements open in January 2027. Days per month are set before starting, two months minimum. I work in your tools, with your engineers, on your cadence. Some engagements have an end date, some do not. Either way the arrangement is reviewed every month and stops at the end of the current month if the work is done. Until January, a fixed project is the way in.
It usually does. On a fixed project the price is fixed and the scope is a priority order, so a change means something moves down the list, not a new invoice mid-flight. On embedded work the scope is set each month, so change is the default.
Both, within reason. I ship working front-end prototypes and production interfaces in React — enough that your engineers get something runnable rather than a spec to interpret. Backend and infrastructure stay with your team.
Only where it touches the product: a wordmark, a type and colour system, the visual language of a site or a deck. Full brand strategy and naming are better served by a studio that does nothing else.
Yes, and most of the work does. I’ll sign yours or send a simple mutual one. It means the public portfolio is thinner than the real one — ask on the call and I’ll walk you through what I can show.