How we built Bolo Studio: speak a social media idea in Marathi, Hindi or English, and get a brand-ready post, approved on Telegram and published on schedule.
9:04 PM: the idea
Meera runs a small sweet shop in Pune. Diwali is four days away. While closing the shop she thinks:
"We should post about our dry-fruit boxes, with the ₹499 offer, in Marathi and English."
Normally that idea dies right there. She has no designer. Her nephew "does Instagram" when he's free.
A good Marathi caption, a design in the shop's colours, checking the price is right, posting at the
right time: all of that is tomorrow's problem, and tomorrow is busy too.
Millions of small businesses in India are in the same place. They have the ideas. They don't have
the hours.
9:05 PM: she just says it
Meera opens her shop's Telegram work group and speaks the idea. Wispr Flow turns her voice into
text, Marathi and English mixed, the way she actually talks, and she tags @bolo-writer.
9:06 PM: the agents get to work
Inside that Telegram group are AI agents, connected through Switch:
| Agent | What it does |
|---|---|
| bolo-writer (Claude Code) | Writes the headline and captions in the chosen languages, following the shop's Brand Kit |
| bolo-designer (Claude Code) | Picks the layout and builds the design in the brand's colours, fonts and logo |
| bolo-publisher (our own agent) | Connects the rooms to Bolo Studio, sends approvals and posts |
They reply right in the group, so Meera's team sees the work happen in the chat they already use.
9:08 PM: Brand Guard checks everything
Before anyone sees it, Brand Guard checks the post against the shop's rules:
- Is the price written correctly, with "onwards*"?
- Is the required call to action there?
- Are any banned words used?
- Is the caption the right length for each platform?
If something fails, the AI fixes it and tries again. Only a clean post moves forward.
9:09 PM: approval on Telegram
The finished image and captions land in the shop's approvals group on Telegram. Meera's partner
reads it on the phone and replies with one line:
approve #p5acbd
or change #p5acbd: make the price bigger, or reject #p5acbd. Nobody needs to log in anywhere.
9:10 PM to 8:00 AM: Drafts, then live
The approved post waits in Drafts. At the scheduled time (8 AM, when Meera's customers are
scrolling) Bolo publishes it to Instagram, Facebook and LinkedIn through their official APIs.
Only posts that are actually live appear on the calendar.
Want a reel instead? Bolo writes the scenes, Sarvam AI speaks the voiceover in Marathi or Hindi, and
Remotion renders the video.
How it's built
Voice (Wispr Flow) ─► Telegram work room ─► Switch ─► bolo-writer / bolo-designer (Claude Code)
│
▼
Bolo Studio (Next.js) ─► Brand Guard ─► design render (Playwright)
│
Telegram approvals room ◄── bolo-publisher (Switch agent)
│ approve
▼
Drafts ─► scheduler ─► Instagram · Facebook · LinkedIn
| Part | Technology |
|---|---|
| Studio web app | Next.js, TypeScript |
| AI writing and design | Claude (Claude Code agents, or the company's own Claude/OpenAI key) |
| Agent rooms | Switch, bridged to Telegram |
| Voice input | Wispr Flow, plus the browser mic |
| Voiceovers | Sarvam AI (Marathi, Hindi, English) |
| Reels | Remotion |
| Data | MongoDB Atlas |
| Hosting | AWS EC2 with Docker Compose and Caddy (automatic HTTPS) |
Running on AWS
We kept deployment to one command. A single EC2 t3.large runs three containers: the web app,
the Publisher, and Caddy for HTTPS. Images and reels render on the same server, data lives in
MongoDB Atlas, and daily EBS snapshots back up the disk.
git clone <repo> bolo-studio && cd bolo-studio
bash infra/aws/deploy.sh
What we learned
- Meet people where they already are. Small business owners live in Telegram and WhatsApp, not dashboards. Putting agents inside the chat made the product feel natural.
- Voice changes everything for non-English speakers. Speaking Marathi is faster and more natural than typing it.
- Guardrails beat raw generation. Brand Guard catching a wrong price matters more than a clever caption.
- Agents need clear jobs. Separate writer, designer and publisher agents were easier to debug than one agent doing everything.
Try it
- Live demo: https://studio.kmrnx.me/
- Code: https://github.com/sanskarjoshiii/bolo-studio.
Built for the Switch hackathon by Team Bolo, Pune. #HowISwitch






Top comments (1)
The Brand Guard detail is the part I'd steal first — checking the ₹499 price and the "onwards*" wording before anything goes out matters far more than a clever caption, especially for a Diwali offer where a wrong price would be expensive. I also liked the approval flow: a partner replying "approve #p5acbd" from Telegram means nobody has to learn a dashboard. The lesson about separate writer, designer, and publisher agents being easier to debug than one do-everything agent rings true — did you find one of the three agents needed the most guardrail retries in practice?