How Jiminny eliminated integration maintenance with Recall.ai

Executive Summary

Challenge

Jiminny had built and maintained its own meeting capture infrastructure for eight years.

The first Zoom integration took approximately six months to build, followed by another six months of work to support Microsoft Teams and Google Meet. After launch, Jiminny still needed to account for frequent platform changes, unpredictable breakages, and fluctuations in meeting volume.

At least one engineer was dedicated to maintaining the infrastructure. During significant platform changes, three or four additional engineers might need to step in. The possibility of integration work also had to be considered during every sprint.

The impact extended beyond engineering. DevOps had to ensure that infrastructure could handle peaks in traffic, while customer success and support teams managed the customer impact whenever meeting capture failed.

Solution

Jiminny migrated its meeting capture infrastructure to Recall.ai.

Recall.ai now captures and processes meetings across Zoom, Microsoft Teams, and Google Meet. Jiminny uses that data to power the analysis, coaching, and revenue intelligence features its customers use.

Instead of maintaining the capture layer internally, Jiminny can rely on Recall.ai to manage changes across meeting platforms and provide high-quality meeting data.

Results

By moving to Recall.ai, Jiminny:

• Freed a dedicated engineering resource to work on its core product
• Removed recurring integration maintenance from sprint planning
• Reduced pressure on engineering, DevOps, customer success, and support
• Improved the reliability of its meeting capture experience
• Increased customer retention
• Gained a long-term technology partner rather than another software supplier

Jiminny maintained its own meeting integrations for eight years

When Jiminny was founded, there was no practical alternative to building its own video capture infrastructure.

Its first Zoom integration took around six months to develop. Supporting Microsoft Teams and Google Meet required another six months of engineering work.

The larger cost came after the initial development. Every meeting platform continued to change, which meant Jiminny’s engineering team had to continually update, repair, and maintain its integrations.

“We had to carry in every sprint planning for possible changes and surges,” said Dave Wilby, CEO of Jiminny.

At least one engineer was dedicated to maintaining the platform. When a meeting provider introduced a significant change, Jiminny sometimes needed to pull in three or four more engineers to resolve the issue.

After running this infrastructure for years, Jiminny decided that its engineering resources would be more valuable when applied to the product its customers were buying, rather than the systems required to capture the underlying meeting data.

Meeting integrations no longer take space in every sprint

With Recall.ai managing meeting capture, Jiminny no longer needs to reserve engineering capacity for the possibility that Zoom, Microsoft Teams, or Google Meet will change something.

The team can plan its sprints around product improvements instead of potential integration repairs.

“The biggest impact was that I could free up engineering resources to focus on what’s important to us,” Wilby said.

For Jiminny, that means investing more engineering time in analyzing revenue conversations, improving sales coaching, and helping customers understand what is happening across their pipelines.

Recall.ai did not only remove the work of running the infrastructure. It removed the uncertainty surrounding that work.

Using Recall.ai decreased pressure across engineering, DevOps, customer success, and support

The cost of maintaining meeting infrastructure was never limited to engineering.

Jiminny’s DevOps team had to make sure its systems had enough capacity to handle peaks in meeting volume. When the capture infrastructure experienced problems, customer success and support teams had to explain those problems, manage customer expectations, and help resolve their impact.

“One of the other hidden costs was in our support and customer success teams, who had to look after customers when we would have problems with the video capture,” Wilby said.

Those problems occur far less frequently now that Jiminny uses Recall.ai.

Engineering no longer owns every integration breakage. DevOps no longer has to manage the same infrastructure demands. Customer success and support spend less time responding to capture-related issues.

The result is less operational pressure across the company, not simply fewer engineering tickets.

More reliable meeting capture increased retention

Meeting capture is the first step in Jiminny’s product. When a call is missed or recorded incorrectly, Jiminny cannot provide the analysis and insights its customers expect.

By improving the reliability of that first step, Recall.ai has helped Jiminny provide a more consistent customer experience.

Jiminny considers the switch to Recall.ai a contributing factor in its increased customer retention.

This was not a decision made before Jiminny understood the work involved. The company had already spent eight years building, operating, and maintaining its own infrastructure.

That experience made the value of switching clearer. Jiminny knew exactly how difficult meeting capture was to manage internally and still determined that migrating to Recall.ai was worth it.

Recall.ai handles meeting capture so Jiminny can build its business

Jiminny evaluated Recall.ai as an infrastructure provider, but the relationship has become closer to a partnership.

“I don’t think of them as a supplier. I think of them as a partner,” Wilby said.

When issues occur, Jiminny can rely on Recall.ai to work alongside its team and resolve them. Recall.ai is accountable not only for delivering meeting data, but for understanding how the quality of that data affects Jiminny’s customers.

“Recall.ai has been a fantastic partner for us,” Wilby said. “It’s impacted the business in only positive ways.”

For companies maintaining their own meeting capture infrastructure, the decision is not only about whether a vendor can replace the technology. It is also about whether that vendor can be trusted with a foundational part of the product.

For Jiminny, Recall.ai provides both: high-quality meeting infrastructure and a team that helps Jiminny focus on building its business.

‍