gaganb.pageResume

Hey! I’m

Gagan N Bangaragiri

I turn questions into things people can actually use.

A few things I’ve made
>MUSO CHECKPOINTFLYOPEN
poke around.FIG. 01 · THE DESK
On the screen: Muso
FIG. 02 · ON MY DESKCurrently building · Muso
MUSO / SHARED WORKSPACE

A place to
work together

Muso is a shared workspace where teams talk through ideas, share work, and bring in AI when they choose. Conversations, decisions, and the work that follows stay connected. Follow a team as they share a sketch, agree on a direction, and shape a proposal together.

Start the story
Muso / follow the thread
A TEAM AT WORK IN MUSO

The welcome
experience for Sprout

Ava leads product, Ben builds, Cleo designs. They're shaping the first thing new Sprout users will see. Cleo brings a sketch, Ben checks what will work, and Ava keeps them focused. They start in Message only: a conversation with each other, without an AI reply. When they want a hand, they can invite the shared assistant into that same conversation.

Muso is still being built. What follows is an example, not a live demo.

Scroll to follow their story
SPROUTShared Studio / #welcome

  1. Talking it through

  2. AvaProduct

    New Sprout users need a welcome experience. Four steps, no more.

  3. BenEngineering

    Starting with the first plant feels right, that's the moment people sign up for. Photo diagnosis is out of scope for this version, that's a big engineering job.

  4. CleoDesign

    Before anyone asks the assistant anything, they should see what it knows, the plant list, where the plants live, the notes they've written. People ask different questions once they know what the AI can see.

  5. CleoDesign

    I've put a first sketch in our shared files. Ben, could you check the steps before I take the design further?

  6. CLEO SHARED A FILE

    Welcome sketches

    01Plant02Place03Care04Ask

    In the workspace’s shared files

  7. BenEngineering

    The four steps work. One thing to cover: people might have a home garden and an office garden. They need a way to switch if they land in the wrong one.

  8. CleoDesign

    Good catch. Let's keep that in the proposal so it doesn't get lost when we fill in the details.

  9. AvaProduct

    So: first plant in, one garden, and what-the-assistant-sees explained early.

  10. Keeping a decision

  11. AvaProduct

    Let's keep the boundary we just agreed: one plant to start, one garden, no photo diagnosis. It'll save us arguing about it later.

  12. CleoDesign

    Agreed. Saving it as a team decision.

  13. AVA’S RECAP

    Welcome experience for new Sprout users: four steps. Start by adding a first plant to one garden. Photo diagnosis out of scope. What the assistant knows is shown before the first request.

  14. Team decision

    One plant to start, one garden, no photo diagnosis.

  15. Saving a decision doesn't start any work. It keeps it for when someone chooses to.

  16. The brief

  17. AvaProduct

    We have enough to work from. Shall we ask the shared assistant for a first draft here, so we can all review it?

  18. AvaProduct

    I’m thinking one page: the four steps, what Sprout’s assistant knows, and a way back if someone lands in the wrong garden. Everything we’ve agreed is in this conversation.

  19. THE TEAM’S BRIEF

    One-page welcome proposal.

    The recent Room conversation, including the decision the team kept above.

    Not includedThe sketch file and private drafts. Shared files are not included automatically.

  20. BenEngineering

    One page keeps it honest. Cleo can check the design; I'll check the recovery path.

  21. AvaProduct

    Ava sends with Shared model · public responseAssistant, please turn our conversation so far into that one-page proposal. Keep the boundary we agreed above.

  22. Draft, review, done

  23. AssistantAI

    I’ve used the discussion and the decision above. Here’s a first draft for everyone to review.

  24. FIRST DRAFT

    Welcome experience

    1. Add your first plant.
    2. Tell us where it lives, light and humidity.
    3. Set up its care schedule.
    4. See what the assistant knows about your plants before asking your first question.

  25. AvaProduct

    Back to Message only · team conversationI've saved this as our shared proposal and requested a review. Cleo, Ben — let's check it before we pass it on.

  26. Ava saved Welcome proposalVersion 1 · review requested

  27. CleoDesign

    On Welcome proposal · version 1I've left a comment on the proposal. Ben's point about the wrong garden is missing. Ben, could you add the way back?

  28. BenEngineering

    I've updated the proposal. After the first step, you can go back to the garden picker if you're in the wrong place. Cleo, does that cover it?

  29. BEN SAVED VERSION 2

    After step 1, if the garden doesn't look right, a return to the garden picker appears.

  30. CleoDesign

    Yes, that covers it. I've resolved my comment and approved this version.

  31. AvaProduct

    I've shared the reviewed proposal here in our room. The sketch, the decision and both versions are here for the team to come back to.

What Muso adds

Cleo brought the sketch. Ben checked the details and revised the proposal. Ava kept the work focused and shared the result. They brought in the shared assistant when they wanted a draft, then carried on reviewing together. Muso is the shared place that keeps their conversation, files, decisions and reviewed work together — so the next person can pick up where they left off.

Read about Muso
Beyond the projects

There’s a person behind them

A little about me, the questions I follow, and how a project changed the way I think about making things.

Meet Gagan