Sriganesh Srinivasan
← All work

SimpliSync.

Zoom meeting transcripts in, Jira updates out

2026 · Team of 3 · AI hackathon · Shipped

Problem
After a standup, someone has to remember every action item and blocker and type them into Jira. Updates lag behind the meeting, and dependency links get forgotten.
Built
A Next.js app where you paste a Zoom transcript. A locally run LLM turns it into structured updates for the tickets mentioned, you swipe to accept or reject each one, and the approved ones post to Jira as comments, subtasks and issue links.
Stack
TypeScript, Next.js, React, Tailwind, Ollama, Jira Cloud REST API
Outcome
Won SimpliSafe's company-wide AI hackathon.

What it does

  1. Paste a meeting transcript.
  2. Review what the agent pulled out for each ticket it heard about: updates, action items and who was involved. Edit or remove anything.
  3. Confirm each ticket by swiping to accept or reject it.
  4. Post. Approved updates land in Jira as comments, new subtasks and “is blocked by” links between issues.

The demo above runs on a sandbox Jira project with made-up tickets.

How it works

SimpliSync architectureA user pastes a Zoom transcript into a Next.js app. Its parse route sends the transcript to a locally running LLM through Ollama, which returns structured ticket updates. After the user reviews and approves them, a second route posts comments, issue links and subtasks to Jira Cloud.USERPastes a transcriptreviews, then acceptsor rejects each updateNEXT.JS APP · TYPESCRIPTReact UIpaste → review → swipe to confirm → results/api/parsetranscript → structured ticket updates/api/post-commentsapplies only the approved updatesOLLAMA · ON THE LAPTOPLocal LLMtranscript never leavesJIRA CLOUD · REST APITicket updatescomments, links, subtasks
Dashed: cloud. The transcript only goes to a model running on the same machine.

Two choices shaped it:

Next projectVitalLink →