Marrowfield Design
Services & scope

Four ways I can help — pick the one that fits where you're stuck.

I keep my services deliberately simple. No retainers you forget about, no vague "strategy" line items. Each engagement has a clear shape, a clear price, and a real thing you keep at the end.

01

UX audit & teardown

A focused review of an existing product or a single painful flow. I go through it the way your users do, document where they stall, and hand you a prioritized list of fixes — the quick wins and the deeper ones, clearly separated.

  • Heuristic review
  • Flow walkthrough
  • Annotated screenshots
  • Prioritized fix list
  • 30-minute readout call
Typical timing
5 — 7 daysfixed scope
You keep: a written report and an annotated walkthrough your whole team can act on.
02

End-to-end product design

My main offering. We take a feature or flow from the fuzzy idea stage all the way to engineer-ready screens — research, structure, interface, prototype, testing, and a clean handoff. This is where the savings flows and patient portals on the home page came from.

  • User interviews
  • Information architecture
  • Interface design
  • Interactive prototype
  • Usability testing
  • Dev handoff
Typical timing
3 — 6 weeksper flow
You keep: tested, spec'd screens plus the research notes behind every decision.
03

Design system starter

For teams whose product has grown faster than its consistency. I build a lean, named set of tokens and components that a small team can actually maintain — not a 400-page library that rots in a month. Built in Figma, documented so engineers and designers stay in sync.

  • Color & type tokens
  • Core components
  • Usage docs
  • Naming conventions
  • Handoff workshop
Typical timing
2 — 4 weeksfoundation set
You keep: a documented kit and the conventions to grow it yourself.
04

Prototype & test sprint

You have an idea and a hunch it's good — let's find out before you build it. A tight sprint where I prototype the concept and put it in front of five to eight real users, then report back on what landed, what confused them, and what to do next.

  • Clickable prototype
  • Test script
  • 5 — 8 user sessions
  • Findings summary
  • Recommendation
Typical timing
1 — 2 weekssingle sprint
You keep: a tested prototype and an honest verdict on whether to build it.
How we work together

Three ways to start, depending on how sure you are.

Not every project needs the full treatment. Here's roughly where most clients land. Final numbers always come after a quick call — these are honest ballparks, not bait.

The Diagnostic

from €1,800

Best when something's clearly wrong but you can't name it.

  • Full UX audit
  • Prioritized fix list
  • Readout call
  • One round of follow-up questions
Start here
Most chosen

The Build

from €6,500

Best when you know the feature and need it designed properly.

  • End-to-end design of one flow
  • Research & testing included
  • Engineer-ready handoff
  • Two revision rounds
  • Two weeks of post-launch support
Plan a build

The Partnership

monthly · by arrangement

Best for teams who want a designer on call, ongoing.

  • Reserved days each month
  • Rolling design support
  • System upkeep
  • Priority scheduling
Let's talk
Before you ask

The questions I get most

Do you work with engineers directly?
Always, and gladly. I design with your build constraints in mind and write handoff specs that answer the questions engineers actually have — states, edge cases, spacing, behavior. I'd rather sit in your standup than throw screens over a wall.
What if I only have a vague idea?
That's a fine place to start — it's most of my work. The Diagnostic or a Prototype & Test sprint is usually the right first step. We turn the vague idea into something concrete enough to decide on, before you commit a budget to building it.
Do you take more than one project at a time?
No. I run one engagement at a time so the client I'm working with gets my full attention. It means I sometimes have a short waitlist — worth asking early if you have a date in mind.
Can you just make it look nicer?
I can, but I'll usually ask why first. A fresh coat of paint on a broken flow rarely fixes the thing that's actually bothering your users. If a visual refresh is genuinely all you need, I'll tell you honestly and we'll keep it small.
How do payments work?
A deposit to book the dates, the balance on delivery — split into milestones for longer projects. Everything is agreed in writing before we start, so there are no surprises on either side.

Not sure which one you need?

Most people aren't, and that's fine. Tell me what's frustrating you and I'll point you to the option that actually fits — even if it's the smaller one.

Ask me which to pick