---
title: "Logikcull Achieves 5x Faster Development with Temporal"
description: "Logikcull transformed its backend with Temporal, boosting e-discovery efficiency, scalability, and development speed through streamlined workflows and microservices."
canonical: "https://temporal.io/resources/case-studies/logikcull.md"
source: "https://temporal.io/resources/case-studies/logikcull"
resource_type: "Case Study"
published: "2024-08-08"
industry: "High Tech"
sdk: "TypeScript"
platform: "Self-Hosted"
company_size: "51-250"
use_case: "Date pipeline"
---

# Logikcull Achieves 5x Faster Development with Temporal

> Temporal has been a perfect fit because it simplifies complex business flows and helps us think about them in a way that logically makes sense, which translates to our code as well.

Logikcull, a leading e-discovery platform, transformed its backend architecture and improved development efficiency by adopting Temporal.

## Challenges Before Using Temporal
Before implementing Temporal, Logikull faced significant backend architecture challenges:
- Limited Observability: The team had some insight into queues and job processes but lacked a high-level overview of their entire pipeline.
- Inconsistent Development: They needed a seamless and consistent way to build new services to enhance team efficiency.
- Tooling Sprawl: Their backend relied on various tools and technologies, including a Ruby monolithic application using different background job processes like Sidekiq.
- Transition to Microservices: Although they had started moving towards microservices, their monolithic codebase was tightly coupled, leading to a slowdown in their CI/CD pipeline.

## Why Logikcull Chose Temporal
Logikcull chose Temporal for several reasons:
- User Interface and Metrics: Logikull appreciated Temporal's user interface and comprehensive metrics, which eliminated the need for internal tooling.
- Scalable Services: Temporal allowed them to break components out of their pipeline into standalone services, enabling independent scaling.

## Logikcull Use Cases for Temporal
>Temporal Workflows have been integral to our feature development.

Logikcull is using Temporal for two main use cases:
- Audio Redaction Workflow: They needed a reliable workflow for audio file redactions, which Temporal handled seamlessly.
- Improved Processing Pipeline: Temporal was used to update their document processing pipeline, moving a logical step earlier in the process. This improved the user experience by accurately representing document processing progress.

## Benefits of Temporal for Logikcull
Since adopting Temporal, Logikull has seen numerous benefits:
- Faster Development: Working with Temporal has significantly increased their development speed compared to their monolithic codebase.
- Reusable Patterns: Temporal helped establish foundational patterns, making development easier and more consistent.
- Simplified Business Flows: Temporal simplified complex business flows, making them easier to understand and implement in code.

Logikcull has streamlined its backend processes, enabling faster and more efficient development.

## Related resources

- [How Town scaled to 1.5 billion monthly Actions with Temporal](https://temporal.io/resources/case-studies/town.md) — Case Study
- [How StackAI cut its indexing failure rate from 20% to below 0.1% with Temporal](https://temporal.io/resources/case-studies/stack-ai.md) — Case Study
- [BFI Finance rebuilds loan origination with Durable Execution for its digital partnership business](https://temporal.io/resources/case-studies/bfi.md) — Case Study