IceBear

Release readiness for fintech & regulated products

See what QA can’t.

IceBear reviews your critical product flow before release and finds UX, accessibility and interface issues your users should never see.

  • One critical product journey
  • Expert review supported by automation
  • Prioritised report in 5–7 working days
IceBear

Release Readiness Review

Northstar Pay

Release 2.14
18 July 2026

Release recommendation

Ready with conditions
2
Critical
5
Important
11
Minor
34
Passed

When to use it

Before an important release.

Release Readiness is built for teams that already have something real to review and are approaching a meaningful release, redesign or workflow change.

  • Launching a new critical workflow
  • Redesigning checkout, onboarding or account setup
  • Changing a complex enterprise workflow
  • Introducing AI into an existing user journey
  • Shipping something you cannot afford to debug after launch

Scope

One journey. Reviewed properly.

The pilot covers one important end-to-end journey rather than spreading attention across an entire product.

  • Onboarding → first successful outcome
  • Search → evaluate → decide
  • Configure → review → submit
  • Upload → AI analysis → human review
  • Checkout → payment → confirmation

A narrow scope lets the review go deeper into interaction states, recovery paths, accessibility and decision points — instead of producing a shallow list of observations across the whole product.

A release can pass QA and still fail its users.

Functional testing confirms that a feature works. It does not always reveal inaccessible controls, unclear error recovery, missing states, inconsistent interactions or visual regressions.

IceBear reviews those gaps before they become production incidents, customer complaints or audit findings.

QA tells you whether it works. Release Readiness asks whether it works for the user — whether they understand the action, notice the result, can recover from failure and can make the right decision with the information in front of them. It complements QA. It does not replace it.

Accessibility

Keyboard navigation, focus behaviour, semantics, labels and screen-reader support.

Interaction and usability

Feedback, validation, error recovery, unclear flows and preventable friction.

Interface consistency

Components, spacing, typography, responsive behaviour and visual regressions.

Critical states

Loading, empty, error, success, timeout and interrupted journeys.

A report your whole delivery team can use.

Every finding is prioritised, evidenced and written to support a decision — not to create another backlog nobody understands.

Critical

Payment confirmation cannot be completed by keyboard.

The final confirmation action is not reachable in the expected focus order. Keyboard users may be unable to complete the payment journey.

Location
Payment / Review / Confirmation
Why it matters
This blocks completion of a critical user journey and creates an accessibility failure.
Recommended fix
Move the action into the logical DOM and focus order. Verify the complete journey using keyboard-only navigation.

Evidence

Confirmation screen

Mobile payment review step, focus indicator absent on the primary action.

Focus order trace

Tab sequence skips from amount field directly to footer navigation.

DOM observation

Confirm button rendered outside the form's tab sequence via a portal.

Open the full sample report

How the pilot works

Three steps, one decision.

  1. 01

    Choose the release journey

    Select one important flow with approximately 8–15 screens or meaningful states — onboarding, identity verification, payment, account opening, insurance quotation or a customer-service request.

  2. 02

    IceBear reviews the experience

    We inspect agreed desktop and mobile states using automated checks and expert UX and accessibility analysis, under confidentiality. No production access or real customer data is required.

  3. 03

    Decide and act

    You receive the prioritised report and a 60-minute review session with clear recommendations for the release.

Martin Puškáč, founder of IceBear

Martin Puškáč

Founder, IceBear

  • Nielsen Norman Group UX Certified
  • IBM Enterprise Design Thinking Practitioner

Reviewed by a product designer, not just a scanner.

IceBear is led by Martin Puškáč, a senior product designer and design consultant with experience across banking, investment, insurance and enterprise digital products — including past work with Credit Suisse. His focus: making complex systems easier to navigate, easier to trust, and easier to make decisions in.

The review combines repeatable automated checks with contextual product judgement. Automation helps uncover and organise evidence. Expert analysis determines what matters for the release.

Founding pilot

Help shape a better release-review process.

IceBear is looking for a small number of fintech and regulated product teams to test and refine this service on a real upcoming release.

The pilot includes

  • Review of one critical journey
  • Desktop and mobile checks
  • UX and accessibility analysis
  • Visual evidence for important findings
  • Prioritised release-readiness report
  • 60-minute results session
  • Notes on what is worth re-checking before future releases
  • Confidentiality by default, NDA available on request

Benefits for founding partners

  • Founder pricing for future reviews
  • Direct collaboration with the reviewer
  • Influence over the future workflow
  • An invitation to try future monitoring features, if they ship

Probably not the right fit if…

  • You need discovery across a whole product rather than one journey
  • The product is still an early concept with nothing real to review
  • You need formal WCAG certification or a conformance audit
  • You need functional QA, performance or security testing
  • You want a redesign rather than a release-risk review

€950 excl. VAT

Founding pilot pricing applies while the review format is still being refined with the first client teams.

Best suited to established product teams with a staging environment and an upcoming release.

A small number of pilot projects will be selected.

Apply for a pilot

Make the next release decision with better evidence.

Apply with one critical product journey. IceBear will confirm whether the pilot is a suitable fit and define the review scope before work begins.