UI and UX design for Pune product teams.

Design interfaces for people who need to get through a complicated task quickly. We turn interviews and operational records into prototypes your users can test and your engineers can build.

Explore what we build
Original line-art composition of Pune landmarks including Shaniwar Wada, Aga Khan Palace, Sinhagad, Parvati Hill and the Pune Okayama Friendship Garden bridge.

What the project can include

Working with teams in Pune

For Pune engineering suppliers around Pimpri-Chinchwad and Chakan, the interface may have to serve a line operator, a supervisor and a quality engineer using different devices. We can scope the work around their shared decisions and the conditions each role works in. GreyBath delivers through remote workshops, reviews and handover.

Worked example

Consider a supplier designing a tablet interface for its shift handover. An operator starts to report a jammed fixture, but the connection drops before they can attach a photograph. The prototype should let them save the fault locally, show that the image is pending and make the handover visible once the device reconnects. The incoming supervisor should be able to accept the handover and assign the fault without re-entering it. We would test the flow with both roles, including a case where the pending report already exists on the server. The agreed result is a single visible fault with a named owner.

Who this service is for

Bring the people who use, review and maintain the first release into the scope discussion.

Industrial product teams

Improve internal tools that operators and supervisors use during a shift.

Software teams

Bring consistency to an existing product with role-based screens and shared components.

How we test the first release

  1. Choose the decision

    Pick one high-friction task and agree what its successful completion looks like.

  2. Test the full task

    Ask each role to attempt the task using the same example and record where understanding breaks down.

  3. Prepare the handoff

    Agree changes with engineering and document the states each role needs to see.

Agree the project scope

The proposal sets the first workflow, delivery responsibilities and the evidence needed before rollout.

Discuss your project
Access to users

Agree which roles can join sessions and how workflows can be observed without exposing sensitive records.

Engineering constraints

Review supported devices, component libraries and application states before committing to the prototype.

Questions before scoping

Ask us something else
Can you work with an existing design system?

Yes. We can audit the components used in the target workflow and extend them when the workflow needs a new state.

Can the research include tablet or shop-floor users?

Yes, subject to access and device availability. We agree the conditions to test, including glare, connectivity and shared-device sign-in where relevant.

Can we scope UI and UX design separately from development?

Yes. The design scope can end with a tested prototype, approved screens and implementation criteria.

Review a workflow