New
Build vs Buy
bots / week running in production
week-over-week growth in one sprint
lines of bot infrastructure code written
MeetMinutes set out to build an AI notetaker that joins Zoom, Google Meet, and Microsoft Teams, transcribes the conversation, and pushes structured summaries to its users. The product hypothesis was clear. The engineering surface area underneath it was not.
Three platforms, three SDKs, three sets of edge cases. Zoom alone needed an On Behalf Of (OBF) token to capture audio cleanly. Teams needed the Real-time Media Stream pipeline. Google Meet needed browser automation that did not get flagged as a bot. Multiply that by failed joins, waiting-room handling, host approvals, and recordings retention, and the team was looking at a six-month detour from product to plumbing.
Rather than build a meeting bot platform inside a meeting notetaker company, the team evaluated buy-versus-build against a single metric: how quickly can we get a paying user a usable summary?
MeetStream gave them one HTTPS endpoint to schedule a bot, one webhook to receive the artifacts, and a transcription layer they could swap on the fly. The build path would have taken a quarter of engineering time. The buy path took an afternoon.
Within weeks of cutting over, MeetMinutes was running 185 bots per week across all three platforms. That number crossed 185 the same week they hit a +249% week-over-week jump, and it has only climbed since. The engineering team that would have been wiring up Zoom OBF tokens is shipping the AI features users actually pay for.
"We never had to think about bot infrastructure. That is the entire point. We picked up an API and shipped a notetaker."
One API across Zoom, Google Meet, and Microsoft Teams, no per-platform SDK glue.
Per-participant audio shipped on every platform, clean diarization without post-processing tricks.
Pay-as-you-go pricing at $0.35 per hour, costs scaled with revenue, not ahead of it.
Customer-side S3 storage on request, data residency without rebuilding the storage layer.
Shubham Pilivkar, Lead Developer at MeetMinutes
