From an unclear UX problem to clear priorities, coherent design and a handoff your team can build from. Each stage produces something you can inspect, and ends at a decision that is yours.
You don’t have to start with an audit. We reuse the research you already have, and a task you can already name can start straight away.
Discovery
The product direction or the cause of an existing problem is unclear. We clarify the questions and useful scope before committing to a full programme.
Evidence
Interviews, analytics or an audit already exist. We use what holds and research only the gaps.
Scope
You know which product area to create or change. We agree the piece and start there.
We work through roles, data, scenarios, permissions and constraints with the people who own the product and the people who own the code — not from a marketing description of it.
The decision point
You confirm which scenarios are in scope, and which questions must be answered before design starts.
We separate the facts from the assumptions in what you already believe, then choose the method that fits the question: observation, interviews, an expert review, or a study of one flow.
The decision point
You agree which findings are accepted as the basis for the work, and which need more evidence first.
We weigh importance, the strength of the evidence, the effort involved and whether engineering can realistically take it now. Anything deferred is recorded with the reason.
The decision point
You approve the order, including what is deliberately not being done yet.
We design the scenarios and their states — error, empty, loading, permission — keep the brand and technical constraints that are justified, and test feasibility with your engineers while the design is still changeable.
The decision point
You sign off the flow and the component behaviour, not just the visual appearance.
We agree the handoff set and any implementation support. Within that scope, we answer engineering questions and check what was built against what was specified. If development slips, we agree a smaller batch, limited support, or a pause.
The decision point
You decide the delivery batches and whether continued support is worth buying.
Scope, assumptions and revision points are agreed in named pieces. A new requirement is estimated before it is accepted, not absorbed silently and reported at the end.
The decision point
You accept or decline each change, and can stop, pause or resequence at any piece boundary.
A stakeholder asks for a new capability while design is already underway.
Effort and impact are estimated against current scope — not waved through.
Taking it on moves something else. That cost is made explicit, not hidden.
The order is re-cut, and the reasoning is written down beside it.
New acceptance criteria are agreed, so “done” still means something.
We own the work from initial scope through final delivery, keeping quality.
What we own
You support the work with product context, access, and timely decisions.
What we need
We use AI to speed up the mechanical parts of the work while keeping decisions in human hands.
How we use it
67% Faster to the aha moment
Median time to a team’s first savings insight, old vs new
17 Hours saved every week
Daily analysis down from 45 minutes to 20, across eight media buyers
You can bring a clear brief — or a product that feels harder to use than it should. We will discuss the situation, the useful scope and a realistic next step.
Usually 4–6 weeks for an agreed scope; the scope, the access we get and any added research set the exact timing. Some teams start with a UX audit to understand what’s wrong and what to prioritize. Others come to us with a product challenge ready to solve. From there, we can take on a focused project or work with you continuously as the product evolves. We agree on the scope upfront, so there are no surprise invoices.
Both. We've worked with pre-launch startups and with enterprise platforms that have GDPR, HIPAA and WCAG to deal with. Most of what we do is SaaS, fintech and AI products, but really it comes down to whether you have a product behind a login that needs to turn sign-ups into active, paying users.
Yes, and often that's the setup. We can embed a senior product designer into your team, work in your tools and coordinate with your engineers. We agree the responsibilities and handoff upfront; design-system work and implementation support are included when they are part of that scope.
Yes. A UX audit finds the friction your team keeps working around and gives you a clear order of fixes. We review the agreed workflows, use available analytics to locate drop-offs and show the interaction changes that make the next step easier. You can implement the plan with your team or keep ANODA alongside you through the redesign.
We start from what you already know. If the problem or product direction is unclear, we clarify it through an agreed audit or research scope. If useful research or a defined task already exists, we start there. We then agree the flows, states and handoff needed for the work; design-system work and implementation support are scoped separately when needed. Success criteria and any measurement plan are agreed with your team.
Yes. We work remotely with US and UK teams regularly, shifting our hours to overlap with yours and joining your standups. Where your company is based has never been the thing that holds a project up.
