Every product manager has lived the same small nightmare. A key customer emails a complaint. Sales mentions a request on a call. Support closes a ticket. Someone drops a screenshot in Slack. Three weeks later, in a roadmap meeting, nobody can remember whether four people asked for the feature or forty. The loudest voice in the room wins. Cycle was built to end that argument.
Founded in Paris in 2019, Cycle was a software company with an unglamorous but universal target: the mess of customer feedback that piles up inside every growing product team. Its promise, printed plainly across its homepage, was "your feedback hub, on autopilot." The app pulled feedback out of the tools where it already lived - Slack, Intercom, Zendesk, Gong, sales calls, support threads - and used AI to tag it, group it by feature, and connect it to the roadmap. The point was not to store feedback. It was to make a decision out of it.
01 / THE PROBLEMScattered information, loud opinions
Mehdi Boudoukhane, Cycle's founder and CEO, had been a product manager himself before he started the company, and his diagnosis was blunt. "The issue we are trying to solve is an issue that every product manager faces," he told TechCrunch. "Product information is scattered across many different products." That scattering is the real tax. Feedback exists, but it lives in ten places, in ten formats, owned by ten people, and none of it is counted.
The stakes are higher than a tidy inbox. Cycle framed the problem in a single startling number when it announced its move to Atlassian.
That distinction - shipping versus knowing what to ship - is the whole thesis. Teams have gotten very good at building. Cycle bet the harder, more valuable problem was deciding, and that the raw material for good decisions was already sitting in the company's own conversations, unread.
02 / THE PRODUCTA hub, not another inbox
At the center of Cycle sat a collaborative, rich-text document editor - closer to Notion than to a ticket queue. Product managers wrote requirement docs there, and feedback attached itself directly to the features it referenced. Around that core, Cycle layered the parts that did the quiet work: smart auto-tagging that sorted incoming feedback by product area and topic, two-way integrations with Linear, GitHub, Jira and Notion, and a call-recording bot that could join Google Meet, Microsoft Teams and Zoom meetings to capture what customers said out loud. When a feature finally shipped, Cycle could notify the people who had asked for it - closing the loop that most teams leave dangling.
It was enough to become a daily habit. By the company's own account, some product managers spent around three hours a day inside the tool - the kind of stickiness that separates a utility from a tab you forget to open.
03 / THE CUSTOMERSWho ran their feedback through it
Cycle aimed at product-led companies - the ones where the product itself is the growth engine and feedback comes fast and constantly. That audience took it seriously. Its customer list included the corporate card company Brex, the French neobank Qonto, the health insurer Alan, and the buy-now-pay-later firm Alma.
Reviews leaned on two themes: speed - turning feedback into something actionable "incredibly quickly" - and the team behind it, repeatedly described as attentive and hands-on with the companies that adopted the tool. For a category that lives or dies on whether people actually keep feeding it data, that support mattered.
04 / THE MARKETLighter than the incumbent
Cycle did not invent the feedback-management category. It walked into a market that already had Productboard at the enterprise end and a crowd of tools like Canny, Dovetail and Enterpret filling in around it. Its wedge was weight. Where Productboard could feel heavy and process-first, Cycle positioned itself as lighter and more collaborative - built so that the whole company, not just the product team, would participate in reading the customer.
| Cycle's angle | |
|---|---|
| Core unit | Collaborative doc editor, not a rigid form |
| Feedback capture | Auto-pulled from Slack, Gong, Zendesk, calls |
| The AI job | Auto-tag and rank - do the boring sorting |
| Who it's for | Whole company, product-led teams |
| Feel | Light and fast vs heavier incumbents |
05 / THE MONEYSmall round, notable names
Cycle came out of Hexa - the Paris startup studio formerly known as eFounders, the same shop behind Front, Aircall and Spendesk. In February 2023 it announced a $6 million seed round led by Boldstart Ventures, with SV Angel, BoxGroup, The 20VC Fund, Base Case and Hexa joining, plus more than 60 operator angels drawn from Google, Stripe, Dropbox, Meta and Webflow. The business ran on the familiar B2B SaaS model: subscription seats sold to product, design and engineering teams, priced up as teams grew and used more of the AI and integrations.
06 / THE EXITAbsorbed into Jira
In September 2025, Atlassian acquired Cycle App, Inc. The plan was not to run it as a separate product. Cycle's AI feedback engine would be rebuilt directly inside Jira Product Discovery - Atlassian's tool for the fuzzy, early stage of product work - and the entire Cycle team would join Atlassian. Jira Product Discovery already reached more than 20,000 customers, and Cycle's job was to give it a sharper way to prioritize: not just what people want, but who raised it, why it matters, and how many are affected.
The standalone Cycle app was sunset on October 31, 2025. In one sense that is the end of the story - another indie tool folded into a platform. In another, it is the point. Atlassian did not buy a user base; it bought a team and an engine, and moved both to where 20,000 companies already work. The feedback hub disappeared as a website and reappeared as a feature.
What Cycle leaves behind is a clean argument about product work: the scarce skill is not building, it is knowing. For six years, a small team in Paris made a tool that treated the voice of the customer as data worth counting rather than anecdotes worth quoting. That idea now lives inside one of the most-used product suites in software.