Customer Story

How Avalara turns Jira tickets into publish-ready pages with Gradial

Apr 8, 2026Gradial x Avalara
Avalara customer story
Customer StoryTechnologyMarketing Operations

The challenge

Avalara's distributed marketing team needed a faster way to publish blogs and limited-time landing pages without sending every request through a multi-day production queue. Marketers knew exactly what each page needed to say, but there was still a gap between marketing intent and digital execution.

Gradial gave Avalara a command center for marketing operations that could turn a Jira ticket into a structured, publish-ready page with governance built in, helping the team move faster while freeing marketers and production specialists to focus on higher-value work.

The bottleneck

Before Gradial, a blog or landing page request moved through multiple handoffs before anyone could begin building the page. From Jira ticket to live page, the average turnaround was about 4.5 days, with an SLA ceiling of 7 days.

That delay created real friction for a global team producing content at the pace of the business. The production queue grew along with the content footprint, but capacity did not scale with it.

The operating impact

4.5x faster

from Jira ticket to publish-ready page

< 1 day

target completion time for blogs and LTLPs

30 marketers

global team gaining publishing leverage

The shift

With Gradial embedded directly into the Jira workflow, Avalara is now targeting completion in under one day, a roughly 4.5x faster path from request to publish-ready page. A marketer submits the ticket, invokes Gradial, and the agent executes the page against the right template with approvals and write-back already built into the flow.

The shift is bigger than speed alone. The production team is no longer spending most of its time manually assembling pages that follow repeatable patterns. Instead, the role moves toward review, governance, and the work that actually benefits from human expertise.

Campaigns can move at the speed of the idea rather than the speed of the backlog.

Avalara

Partnership interview

Why it worked

Gradial worked for Avalara because it understood the operational reality of enterprise web publishing. It could apply the right template rules for blogs versus limited-time landing pages, execute accurately inside the systems the team already used, and keep governance attached to the work as it moved.

That made it possible to close the gap between what marketers wanted to launch and what production teams could realistically build in time.

What comes next

The next step is expanding the same model beyond new page creation into content updates, bulk changes, and broader asset and channel workflows. The foundation is now in place for a larger operating model where marketing teams can move at the speed of the business without inheriting the full burden of manual production work.

For Avalara, that makes Gradial more than a productivity improvement. It becomes infrastructure for how marketing execution happens going forward.