How tl;dv Drives Expansion Revenue and Offloads Maintenance with Paragon
Customer Company Size
Startup
Region
- Europe
Country
- Germany
Product
- Paragon
- Zoom
- Google Meet
- Slack
- Salesforce
- HubSpot
Tech Stack
- API Integration
- CRM Platforms
- ATS Platforms
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Productivity Improvements
- Customer Satisfaction
- Revenue Growth
Technology Category
- Application Infrastructure & Middleware - API Integration & Management
- Platform as a Service (PaaS) - Connectivity Platforms
Applicable Industries
- Software
- Professional Service
Applicable Functions
- Business Operation
- Sales & Marketing
Use Cases
- Remote Collaboration
Services
- System Integration
- Software Design & Engineering Services
About The Customer
tl;dv was founded in 2020 with a strong belief in the future of asynchronous work. In just two years, the company has grown rapidly, amassing over half a million users, including big names like Cloudflare, Hello Fresh, and Zalando. At its core, tl;dv addresses the problem of information silos that arise from meetings. Meetings can be expensive and inefficient, and with the majority now held remotely, scheduling across time zones has become challenging. tl;dv enables users to seamlessly record, index, transcribe, and share key moments from video calls, allowing colleagues to catch up on key topics asynchronously in minutes. This makes it easier to keep everyone on the same page in a fraction of the time. Users can timestamp key moments and create clips within the app, making it easy to share important insights with clients, investors, and other stakeholders. These timestamps are searchable, ensuring that action points are not forgotten. Co-founder & CEO Raphael Allstadt emphasizes that the future of work is not only remote but async-first, and tl;dv is excited to fuel that movement.
The Challenge
The business value for building out integrations was clear for tl;dv, but they faced a consistent problem. Initially, they attempted to build a Slack integration in-house but lacked the engineering resources to justify dedicating significant efforts on integrations without slowing down the development of their core product offering. Prior to becoming aware of Paragon, tl;dv had built Zoom and Google Meet integrations in-house, as these integrations were essentially the backbone of their product, and they needed to understand their APIs inside and out. However, while integrations with platforms like Slack, Salesforce, or HubSpot are still extremely important product features for them to build, they knew it wouldn’t make sense to have their developers spend weeks learning each platform’s API documentation. Additionally, maintaining each integration would cost them approximately a week per year, which would quickly add up as they scale to dozens, if not hundreds, of integrations in the future. As a result, tl;dv knew that the logical decision was to buy, not build.
The Solution
tl;dv began their search for a solution by using Google and speaking to their investors. They became aware of Paragon after a friend, also a founder, recommended it. As they explored Paragon, Raphael and his team were impressed by how developer-oriented Paragon’s solution is compared to competing products, which were often internal automation platforms like Tray and Workato. Beyond the product itself, the customer success and support that Raphael and his team experienced gave them even more confidence in partnering with Paragon. Raphael anticipated that building in-house would take a minimum of 4 weeks to build a single integration. However, with Paragon, the tl;dv team was able to create the Slack integration they needed in just a few days, followed by Salesforce and HubSpot. This resulted in a 75% reduction in engineering resources required to build an integration and allowed them to get the integrations into their customers’ hands 4x faster. These integrations were some of their most requested features and are paid features, driving MRR growth for tl;dv.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
SET Creative Ditches Google Vault for Datto Backupify
When Kienholz first started at SET, the staff was using Microsoft Outlook for email with no form of data backup. It became apparent that something needed to change as the staff was often burdened with trying to recover emails from departed employees. Kienholz transitioned the team to Google’s Gmail and implemented Google Vault for backup purposes. While SET employees quickly adjusted to Gmail, which many use for personal email, the same could not be said for Google Vault. “Unlike most Google products, Vault was not user friendly at all. It’s very hard to search for items. We never really figured out how to do a restore either,” explained Kienholz. Due to SET’s work with high-profile brands, projects often go through many rounds of revisions right down to the eleventh hour. This means that every bit of information - especially data living in project managers’ emails - is crucial to delivering clients a polished design at deadline.
Case Study
Infosys achieves a 5–7 percent effort reduction across projects
Infosys, a global leader in consulting, technology, and outsourcing solutions, was facing significant challenges in application development and maintenance due to its distributed teams, changing business priorities and the need to stay in alignment with customer needs. The company used a mix of open source, home-grown and third-party applications to support application development projects. However, challenges resulting from distributed teams using manual processes increased as the company grew. It became more and more important for Infosys to execute its projects efficiently, so they could improve quality, reduce defects and minimize delays.
Case Study
Arctic Wolf Envelops Teamworks with 24x7 Cybersecurity Protection and Comprehensive Visibility
Teamworks, a leading athlete engagement platform, faced rising cyberthreats and needed enhanced visibility into its network, servers, and laptops. With software developers connecting from all over the world, the company sought to improve its security posture and position itself for future growth. The company had a secure platform but recognized the need for a more proactive solution to identify gaps within its technology infrastructure. Data exfiltration and malicious access were top concerns, prompting the need for a comprehensive security upgrade.
Case Study
Sawback IT and Datto Save Client From a Costly Mistake
Ballistic Echo, a software development house, faced a critical challenge when human error led to the deletion of thousands of lines of unique code. This incident occurred before the code was pushed to source control, resulting in significant loss of time, revenue, and work. The previous file-level backup solution they used was slow and inefficient, making it nearly impossible to manually recreate the lost work. The need for a more reliable and efficient business continuity solution became evident to avoid such disasters in the future.
Case Study
Opal Helps Customers Shine Thanks to Datto
SP Flooring & Design Center faced a ransomware attack that encrypted and locked their files. The attack was initiated through a compromised service account set up by an outside vendor. The ransomware infection was isolated quickly, but there was a concern about the extent of the data at risk. The company had backups in place but was unsure of how much information was compromised. The situation required immediate action to prevent further damage and restore the affected data.
Case Study
Zapier Aggregates Multiple Analytics in a Single Dashboard with the New Relic Platform
Zapier, a company that enables non-technical users to push data between hundreds of web applications, was facing a challenge in automating and provisioning servers for optimal performance. The company's environment consisted of 50 Linux servers on the Amazon Elastic Compute Cloud (EC2), a Django application split across several servers, and a backend consisting of a dynamic number of celery task workers fed by messages published to a RabbitMQ cluster. They also maintained a number of internal web services on nginx in front of Gunicorn and Node.js processes. Redis handled simple key and value stores, with logging handled by Graylog2 and ElasticSearch. However, they realized that no level of automation would be sufficient without an effective monitoring solution in place. They needed a tool that could provide immediate alerts when something was breaking and could be easily implemented into their environment.
