Product and account model
Define who buys, who sets up the workspace, who performs the work and which information crosses each boundary.
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
01 / What we build
Define who buys, who sets up the workspace, who performs the work and which information crosses each boundary.
Build the onboarding and first task flow, including incomplete data and permission errors.
Identify the agreed first release, later features, activation signals and the screens engineers need.
City context, honestly stated
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.
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.
Where it fits
Bring the people who use, review and maintain the first release into the scope discussion.
Validate a customer workflow before committing development time to the full roadmap.
Improve onboarding, user roles and account administration in an existing product.
How we work
Map the first customer’s needs, roles and current tools.
Test account setup, the first task and what a user sees when they cannot continue.
Decide what engineering will implement for the pilot and identify open product questions.
The proposal sets the first workflow, delivery responsibilities and the evidence needed before rollout.
Discuss your projectReview how customers are invited, which roles are needed and how features or limits are assigned.
Use representative customer data and agree which completed task indicates that onboarding worked.
Yes. We can use current usage, support issues and user interviews to prioritise the part of the product to redesign.
Yes. The design can include both roles and test the information and actions each account can access.
Yes. Discovery can end with a documented customer problem, prototype and proposed release scope.
Start with one workflow