I connected behavioral data, design, and delivery into one workflow. It won Best Use of AI at the Digital Experience Awards 2026.
Contentsquare reads what users do. Figma holds the design. Jira holds the work. Each piece was already solved on its own. The gap was between them, and closing it is what the award recognized.
View on LinkedInI had already written about the pieces separately. Claude reading analytics through Contentsquare's MCP server. Figma and Jira connected so tickets stop being written by hand. Each one removed real work from my week.
What none of them did on their own was close the loop.
The idea came from a simple question: how much of that work actually needs to be done by hand?
What the workflow does end to end
- Reads user behavior data from Contentsquare through MCP
- Identifies bugs and friction points along the journey
- Proposes design changes on the Figma file
- Generates the development tickets in Jira, organized into Epic, Story, and Task, ready for the team
Four systems that used to be four separate jobs, with a person carrying context between them at every step.
Where the human stays
The part I care about most isn't the automation. It's the boundary.
The system collects, synthesizes, and proposes. It doesn't decide what matters most, and it doesn't open work without confirmation. Prioritizing isn't reading data, it's deciding what counts, and that belongs to whoever knows the business.
The award didn't validate the tools. Every one of them is available to anyone. It validated the decision about where to stop.
How it got there
I posted about the project a month before. In the comments, the Contentsquare team suggested I enter the Digital Experience Awards. There was very little time, but I put the presentation together and submitted it.
It won Best Use of AI.
I've been studying AI seriously for a while now. I integrate it into every part of how I work and, more than that, how I think. The recognition tells me one thing: the direction is right.
Takeaway
The value wasn't in any single integration. It was in connecting systems that already had the answers and were never talking to each other, and in keeping a person on the gate where the workflow turns data into a business priority.
