Use cases¶
Four people who would each get something different out of spOken. Find the one whose problem sounds like yours; the features named are the ones worth learning first.
Maya, who has been meaning to start a podcast¶
Three episodes planned, none recorded. The blocker was never the idea.
Maya has a subject and a dozen people willing to talk about it. What she doesn't have is a recurring evening free at the same time as any of them, or the patience to learn an editor.
She writes a form with four questions, sends the link to all twelve, and lets them answer over a fortnight from wherever they are. The answers stack up in Responses while she does nothing. When enough have come in, the Mixroom puts them behind her intro and between two pieces of music, and the podcast page gives her a feed she can hand to Apple Podcasts.
Leans on: audio steps · the closing screen · the Mixroom · podcast pages.
Sam, comms lead at a forty-person company¶
Needs customer voices for a launch, and cannot ask customers to join a call.
Sam's customers like the product and would happily say so. They will not, however, book a slot in a calendar to do it.
One form goes out in a newsletter. Each question accepts a recording or a written answer, so the ones who hate hearing themselves still take part. The email step collects a verified address, so Sam can go back for permission before anything is published, and a design system makes the whole thing look like the company rather than like a survey.
Leans on: the advanced media recorder (audio or text) · verified email · design systems · lock answers after submit, so a quote can't change after it is approved.
Théo, running an agency of six¶
Five clients, each with their own shows, and nothing may leak between them.
Théo's problem is not collecting audio; it is keeping five clients apart while six colleagues work across all of them.
Each client is a team. Forms, mixes and files shared with that team are visible to everyone on it and to nobody else, and a new hire gets a client's whole history the moment they are added. Each client's shows publish from their own domain, so nothing carries Théo's branding.
Leans on: teams · sharing · design systems per client · podcast pages on custom domains.
Dr Okafor, running a study across four time zones¶
Interviews with participants she will never share a working hour with.
The recording is the data. Scheduling is the obstacle, and a missed slot can mean losing a participant entirely.
Her form asks its questions in a fixed order, saving each answer as it is given, so a participant who closes the tab halfway resumes rather than restarts. Lock answers after submit makes a submission final, which is what her protocol requires, and verified email ties each response to a reachable address without a login.
Leans on: per-step saving · lock answers after submit · verified email · exporting responses.
If none of these is you, the shape usually still fits: you need something from people who are not in the room, and the calendar is what is stopping you.