The Sprig blog
What we are learning, written down.
Notes on meeting records, speaker attribution, and building a product that refuses to claim more than it can show. Everything here is written by the people who build and sell Sprig.
Searches titles, summaries, topics, authors, section headings, and the first 1,200 characters of each post.
4 posts
- If there are no moments, the answer is flagged unverifiedA week later nobody can tell whether a commitment was made, hedged, or invented by a model. You open those moments. If there are none, the answer is flagged unverified.
- How we publish this blogPosts are Markdown files in the product repository, published by opening a pull request. Here is the whole workflow, including the checks that stop a broken post reaching the site.
- A summary you cannot check is a rumour with better formattingMeeting summaries are confident, readable, and impossible to verify. We treat an uncited claim as a defect rather than a rough edge, and this is what that costs.
- Why Sprig does not send a bot to your meetingEvery meeting recorder eventually ships a bot that dials into the call. We decided not to, and the reasons are about consent and audio quality rather than engineering effort.