SaaS product design in Mumbai

Give customers a clear route from signing up to completing the job they bought the product for. We design the workspace, permissions and status changes that make that first successful task repeatable.

Explore what we build
Line-art composition of Mumbai’s Gateway of India, Taj Mahal Palace, Chhatrapati Shivaji Maharaj Terminus, Bandra Worli Sea Link and Rajabai Clock Tower.

What the project can include

Working with teams in Mumbai

A Mumbai SaaS team selling to professional service firms may need to support workspace administrators, their colleagues and external clients. Each role needs a clear next step and visibility into who can see client documents. GreyBath delivers through remote workshops, reviews and handover.

Worked example

A Mumbai SaaS founder is designing a client onboarding product for accounting firms. An administrator creates a workspace, chooses a document checklist and invites a client. The invite goes to the wrong email address. The administrator revokes it, checks the audit entry and sends a corrected invitation. The intended client opens a limited view containing only their own requests, submits one document and sees which items remain outstanding. A usability test asks both roles to finish these tasks and explain who can open the uploaded file. The team uses the observations to revise invitations, permissions and empty states.

Who this service is for

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

SaaS founders with an early product

Test activation with target customers before committing the development team to a full feature set.

Product teams changing an existing workspace

Review invitations, role controls and account recovery with the customers and support staff affected by the release.

How we test the first release

  1. Review signup and activation

    Map how a customer joins, invites a colleague or client and completes their first useful task.

  2. Prototype roles and exceptions

    Test ordinary and failed invitations, incomplete setups and the status shown to each user.

  3. Hand over interaction rules

    Document access boundaries, empty states, notifications and acceptance criteria for the selected design.

Agree the project scope

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

Discuss your project
First customer journey

Agree the workspace, roles and steps the first prototype needs to cover. Share current support examples or customer feedback if available.

Security decisions and implementation

Identify permissions that need product and security review. Agree whether the engagement includes engineering implementation.

Questions before scoping

Ask us something else
Can you work on an existing SaaS product?

Yes. A focused engagement can redesign onboarding or a particular workspace while accounting for existing roles, data and navigation.

Can you prototype without production data?

Yes. Representative accounts and synthetic tasks can exercise permissions and status changes in a prototype.

Do you include usability testing?

Testing can be included. We agree the tasks, participants and decisions the sessions should inform when defining the scope.

Discuss your Mumbai SaaS product