SaaS product design for Pune teams.

Turn a product idea or a complex release plan into a workflow a customer can try. We define what the first account needs to achieve, then test the screens, account boundaries and handoffs that make it possible.

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

Pune has an established software cluster around Hinjawadi. Teams building B2B products for customers in several locations can use a design pilot to validate what users do in the product, what their administrators manage and which setup steps belong to support. GreyBath delivers through remote workshops, reviews and handover.

Worked example

Imagine a SaaS team planning a tool that tracks calibration dates for equipment at different customer sites. A new customer administrator imports a spreadsheet of devices, assigns one site coordinator and asks that coordinator to verify a due date. One row is missing an equipment ID and must go to a review queue. The coordinator should see the correct site and know what requires action. We would test this sequence before expanding into subscriptions or dashboards. A successful pilot lets both roles reach the first completed verification with a clear view of the incomplete import.

Who this service is for

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

Early-stage software teams

Validate a customer workflow before committing development time to the full roadmap.

Established SaaS teams

Improve onboarding, user roles and account administration in an existing product.

How we test the first release

  1. Choose a pilot account

    Map the first customer’s needs, roles and current tools.

  2. Prototype the activation path

    Test account setup, the first task and what a user sees when they cannot continue.

  3. Agree the build boundary

    Decide what engineering will implement for the pilot and identify open product questions.

Agree the project scope

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

Discuss your project
Account and subscription assumptions

Review how customers are invited, which roles are needed and how features or limits are assigned.

Data import and success

Use representative customer data and agree which completed task indicates that onboarding worked.

Questions before scoping

Ask us something else
Can you improve an existing SaaS product?

Yes. We can use current usage, support issues and user interviews to prioritise the part of the product to redesign.

Can you cover administrator and end-user screens?

Yes. The design can include both roles and test the information and actions each account can access.

Can we stop after product discovery?

Yes. Discovery can end with a documented customer problem, prototype and proposed release scope.

Define your SaaS pilot