Why it exists
Most product teams already talk to customers. The trouble is everything around the conversation. The invitation goes out from someone's inbox, the notes live in a doc, the recording sits in Zoom, and the customer never hears what changed. After a few months the program depends on one person remembering to keep it going, and when they get busy it stops.
Mamabird puts the loop in one place. Your team publishes a session with an objective, an agenda and a seat count. Members join it from a portal with your name on it, and add it to their calendar from the same page. The notes and the recording land on the session. The recap goes back to everyone who took part, and stays in the portal under that session for anyone who looks later.
Four kinds of session, one community, and the loop closed every time without anyone having to remember.
How we think about it
Sessions, not surveysA survey tells you what people picked. Forty-five minutes with one customer, or a room of six, tells you why. The why is what you build from.
Ask for lessA ten minute concept review or a single interview is easier to say yes to than a quarterly board meeting. Smaller asks get more yeses, and more often.
Tell them what happenedA member who sees their words in a recap accepts the next invitation. One who never hears back stops opening the emails.
It stays yoursYour members, your logo, your address. Mamabird runs the sessions. The community belongs to you.
Who is building it
A small team in Seattle. We have run advisory boards and design partner programs ourselves, on spreadsheets and calendar holds, and watched them fade for the same reasons each time. Mamabird is the tool we wanted then.
Where it is
Early access, opening to teams in small groups. Join the waitlist and we will email you when your group opens. The blog has our notes on running a program in the meantime, and [email protected] reaches a person.
