{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/f3f4b2de18604505bfc24375528a5bf3\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/f3f4b2de18604505bfc24375528a5bf3-6101a2133b6cfe2d.gif","duration":2168.203,"title":"Pandium x Atlassian for Startups Interview","description":"Adam Gilleland recorded a customer interview with Cristina Pandium to capture Pandium’s journey and usage of Atlassian products for a startup-focused video and blog. Cristina described Pandium as a B2B integration platform and explained how Jira, Slack integrations, Loom, and release automation support engineering workflows and customer communication. Next steps are for Adam to edit and publish a 5–10 minute video with an accompanying blog, and for Cristina to send related YouTube videos and the “saspocalypse” series to Adam.\n\n Deadlines and blockers\n\nExternal timeline: publish video edits by end of week—Adam aims for **tomorrow** or by **Friday**; driven by marketing cadence and boss OOO. Roadblocks: Adam's travel backlog, review/approval cycles; minor delays expected.\n Next steps\n\nAdam will create a little page with what to read for the recording. Cristina will email Adam the video series. Adam will splice the recording and publish the video, aiming to release it by the end of the week (possibly tomorrow). Cristina will send Adam links to Pandium's YouTube videos.\nKey points and questions\n\n### Atlassian product adoption\n\n\n Jira has been restructured multiple times as the company evolved \n Jira serves as an archive of past ideas and decisions \n Jira helps answer customer questions about timelines and past work \n\n\n\n\n\n  17:06\n\n\n\n  Adam Gilleland, Atlassian for Startups: How are you leveraging Atlassian products and why adopt them early?\n  \n  Cristina Pandium - Integration infrastructure: Used Jira from the start for project management; enforces rigor and stores company history.\n\n\n\n\n### Ticketing and integrations\n\n\n Jira-to-Slack integration is used heavily to create tickets from Slack content \n Tickets are tagged with specific customers for visibility \n Team uses epics; they have not adopted sagas \n\n\n\n\n\n  21:30\n\n\n\n  Adam Gilleland, Atlassian for Startups: How did Jira help ticket hygiene and project processes?\n  \n  Cristina Pandium - Integration infrastructure: Hygiene was poor initially; process became robust as team grew and roles expanded.\n\n\n\n\n### Collaboration and release automation\n\n\n Pull requests are tagged to Jira tickets to track status \n DevOps automated deployment updates and release notes via integrations \n There are Jira power users who build helpful automations for the team \n\n\n\n\n\n  24:27\n\n\n\n  Adam Gilleland, Atlassian for Startups: How have Atlassian apps helped internal collaboration and feedback collection?\n  \n  Cristina Pandium - Integration infrastructure: They centralize operational tools, improving collaboration and making feedback traceable.\n\n\n\n\n### Startups program benefits\n\n\n They were Atlassian users before the startups program existed \n Program revealed additional tools Cristina did not know about \n Using established vendor tooling reduces founder overhead and support concerns \n\n\n\n\n\n  27:20\n\n\n\n  Adam Gilleland, Atlassian for Startups: What value did you see from the Atlassian for Startups program and why recommend it?\n  \n  Cristina Pandium - Integration infrastructure: Unified tools under one vendor, support, and startup discounts reduce operational burden.\n\n\n\n\n### Building in-house vs buy\n\n\n Building in-house often consumes engineering time better spent on product \n Teams may underestimate total costs like tool seats and design tooling \n There is a cultural impulse to build, but ROI is frequently unjustified \n\n\n\n\n\n  31:11\n\n\n\n  Adam Gilleland, Atlassian for Startups: Should founders build in-house operational tools or use existing products?\n  \n  Cristina Pandium - Integration infrastructure: Generally avoid rebuilding core ops tools; time and cost usually outweigh benefits.\n\n\n"}