You may not need much. But a screen list tells us what exists, not whether the journey makes sense. We normally review the critical flows, states, priorities, and dependencies before detailed interface work.

We do not assume it is. We look at the journey, behaviour, funnel data, usability, messaging, product rules, and other available evidence. Pricing, traffic quality, or the offer itself may be the real issue.

Yes. Existing user habits matter. We can improve a specific workflow, feature, or group of screens while preserving patterns that remain useful and familiar.

We will say so. Changing the interface is poor value if the actual problem sits in the product model, business process, technical behaviour, or proposition.

Not automatically. It becomes valuable when inconsistency is affecting usability, designers keep recreating patterns, or developers are implementing the same behaviour differently across the product.

Yes. We can work within your current product constraints and provide flows, interface states, component logic, prototypes, specifications, and design QA for implementation.