# How Spintly uses DevRev

As published on [devrev.ai](https://devrev.ai/customers/spintly), July 2023. Captured by usedby on 2026-10-09.

- Company: [Spintly](https://www.usedby.ai/companies/spintly.md)
- Tool: [DevRev](https://www.usedby.ai/tools/devrev.md)
- Industry: [Cybersecurity](https://www.usedby.ai/companies/industry/cybersecurity.md)
- Teams: Developers

## What the story says

Spintly, a wireless cloud-based access control company, started with DevRev as a ticketing tool and now uses it to define its product by component and link tickets to those components. Issues are routed automatically to the right developer, and customer conversations, tickets and issues are kept in one place.

Summary written by usedby from the source page, in English. The figures are those of DevRev and Spintly, not ours.

> Initially, Spintly used DevRev as a ticketing tool. However, they soon discovered that the system was product-centric, allowing them to define their product and its features in great detail, even at the microservices level.

> The biggest pain point was being able to convey customer problems to our developers and having them prioritize and work on those issues.
>
> Rohin Parkar, CEO

Source: [devrev.ai](https://devrev.ai/customers/spintly), captured 2026-10-09.

## What usedby checked

We compared the story with its live page on 2026-10-09.

- Checked: the passage quoted above is copied word for word from the page, near the name of Spintly.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Spintly uses DevRev. Confirmed line. Latest check across sources: 2026-10-09.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/spintly-devrev · How we check: https://www.usedby.ai/methodology