A culture podcast made from a handbook page on remote work
A GitLab Handbook page on informal communication in a remote company (CC BY-SA) became a five-minute episode for the team. Hear it and copy the request.
How this was made. Audio and video overviews, slide decks, infographics and quizzes are made with Google's Gemini Notebook (formerly NotebookLM), on accounts that AutoContent operates. AutoContent has no agreement with Google. Google can limit or stop this access at any time.
The podcast
Informal Communication in an all-remote environment (The GitLab Handbook)
PodcastEnglish5 min 32 s
Transcript excerpt
Speech-to-text of the output, not edited and without speaker labels. It is part of the sample output.
And genuine connection doesn't always require eye contact or even speaking. Which explains the underlying logic of the team DJ Zoom room. I found this fascinating. You basically join, share computer audio, and just do heads down work. Yeah, rotating DJ duties without any pressure to actually speak. Right. It simulates the ambient noise of a coffee shop or a shared desk pod. You're creating a sense of shared presence without the heavy cognitive load of a conversation. It is all about finding different bandwidths of connection.
And we also use juice box chats, which are designed specifically for team members, kids and families to meet. Oh, wow. I love that. Just bringing the whole family in. And that cross-pollination is so critical for a healthy culture, it really extends to how we handle the messy reality of working from home, too. Like, the handbook explicitly encourages welcoming interruptions. A dog barking or a toddler wandering into the frame.
- Length
- 5 min 32 s
- Credits used
- 10 credits
- Cost on the Starter plan
- €0.29
- Generation time
- 5 min 8 s
- Format
- Podcast
- Job
- Company podcasts
- Language
- English
- Generated on
- 2026-11-04
This output used 10 credits, which is €0.29 on the Starter plan (€29 per month for 1,000 credits). Failed generations use none. Generation time runs from the request to the finished file; it depends on the sources, the options and the queue.
What came out, and what we would change
We sent the link to the GitLab Handbook page "Informal Communication in an all-remote environment" (CC BY-SA 4.0) and asked for an episode for the whole company: how a remote team keeps informal contact, how the practices work and why they matter, with no individual people named. With duration at short, the episode runs 5 min 32 s.
The page lists more than twenty practices, and the episode picks six: coffee chats, random pairing with the Donut bot, Juice Box Chats for team members' families, welcome interruptions on calls, the Team DJ Zoom Room, and community outings instead of video happy hours. It keeps the page's main point: informal contact builds trust, and trust helps people accept decisions.
The hosts add their own explanations. They call the problem "context collapse", a term that the page does not use and that usually means something else, and they talk about Zoom fatigue. They also overstate: the Donut pairing is random and optional, but the episode says that it forces contact across departments, and a team's volunteer hour becomes a personal permission.
We made this episode for the corporate podcast ideas page, with an onboarding episode from the same handbook. It took 5 min 8 s to generate and used 10 credits. The episode on this page is shared under CC BY-SA 4.0, like the handbook.
Guide for this job: Corporate podcast ideas.
The exact request
The body that was sent to POST /content/Create, unchanged, and the same request as curl.
{
"resources": [
{
"type": "website",
"content": "https://handbook.gitlab.com/handbook/company/culture/all-remote/informal-communication/"
}
],
"outputType": "audio",
"text": "An episode for the whole company about how we keep informal contact while we work remotely: the main practices on this handbook page, how they work, and why they matter. Do not name individual people.",
"duration": "short",
"language": "English"
}curl -X POST "https://api.autocontentapi.com/content/Create" \
-H "Authorization: Bearer $AUTOCONTENT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"resources":[{"type":"website","content":"https://handbook.gitlab.com/handbook/company/culture/all-remote/informal-communication/"}],"outputType":"audio","text":"An episode for the whole company about how we keep informal contact while we work remotely: the main practices on this handbook page, how they work, and why they matter. Do not name individual people.","duration":"short","language":"English"}'
# then poll until "status" is 100:
curl -H "Authorization: Bearer $AUTOCONTENT_API_KEY" "https://api.autocontentapi.com/content/Status/<request_id>"How we checked it
- Transcript
- We transcribed the output with Whisper large-v3-turbo and compared the transcript with the source.
- Language
- Detected en, requested en.
- Loudness
- -24.1 LUFS integrated, true peak -4.7 dBTP.
- Notes
- Review notes, against the handbook page: no statement contradicts the page. Additions: "context collapse" (not on the page, and not its usual meaning) and Zoom fatigue. Overstatements: the random, optional Donut pairing "forces" contact across departments, and a team's volunteer hour becomes a personal permission. Likely mishearing in the transcript: "click buster" for clique buster.
- Checked on
- 2026-11-04. Failed generations are run again and never published.
More examples
All examples- Podcast · EnglishCorporate podcast production by API: a real company episode3 min 50 s · 10 credits (€0.29 on Starter)
- Podcast · EnglishInternal company podcast: a weekly update made from a changelog5 min 36 s · 10 credits (€0.29 on Starter)
- Podcast · EnglishAn onboarding podcast for new hires, made from a handbook page4 min 56 s · 10 credits (€0.29 on Starter)