NOTE: Demo visuals include blurred data or synthetic placeholders to protect customer privacy.

The problem Jason picked up from GTM was simple to describe and stubbornly hard to solve. Reps need to know where a customer stands on engineering work before they walk into a conversation. The data lives in JIRA. The context lives in Salesforce. Getting the two to talk has been a years-long wish list item.

Before the briefing shipped, AEs and CSMs spent their meeting prep hunting for status. A customer would ask about an RFE, and the rep would promise to check on it. Preparation meant pinging PMs and support in Slack, reading half-stale tickets, and piecing together what to say.

GTM had looked at fixing this before. A prior attempt to build a custom JIRA-to-Salesforce integration was shelved because the engineering cost was too high. So the team made do.

Three specific frictions kept showing up:

1. Reps lost time chasing PMs and support over Slack to check whether a customer had open bugs, ARNs, or RFEs.

2. JIRA is complicated, and it is not a place you want a salesperson to go looking for customer status.

3. A prior heavy custom integration project had stalled on cost, leaving the workflow on pause for months.

Jason paired with Heron Bhatia on Glean's Nora Task, the agentic workflow tool inside Nora. He drafted a prompt, tested it against his own inbox, used a second AI to pressure-test the AE experience, and tuned the instructions until the output was clean.

The result is an email that lands in the rep's inbox ahead of a customer meeting, built on connections Nora already has to JIRA and Salesforce.

What the email does:

• Opens with an executive headline: account name, meeting time, account size, and expected close date.

• Lists the customer's open bugs and RFEs pulled from JIRA, including current status.

• Offers a short suggested talking-point summary that the rep can use or skip.

• Runs on a schedule, so the brief arrives before the meeting rather than after the ask.

• Ships entirely through a Nora Task prompt, with no custom integration code.

Pulling ticket status into the channel reps already work in replaces PM-chasing and JIRA-spelunking with a single read.

The value shows up in different places depending on who's benefiting. For AEs and CSMs, the email means walking into a customer meeting already knowing what's open and what's on track. For product and engineering, it means fewer drive-by Slack pings asking for ticket status. For GTM leadership, it means consistent pre-meeting research across the team without incurring a heavy integration cost.

Early wins:

• Reps stop saying "let me check on that" mid-meeting.

• PMs and support field fewer one-off status pings from GTM.

• Customer conversations start from shared context, not guesswork.

• The Nora Task pattern is now a template that other GTM workflows can copy without engineering lift.

Jason's next step is to scale the briefing from one-to-one to team-level aggregation, so the pattern works across account pods rather than individual reps.

The demo had barely ended when a peer asked Jason to share the task-builder piece because a few of his users wanted to copy the workflow. No rollout plan, no change management. A demo generating its own distribution is a strong signal that the underlying idea works.

This is what AI-native operations look like at Abnormal. Jason joined two months ago, paired with Heron for a week, and shipped a working GTM briefing that cleared a problem a heavier integration project couldn't. The briefing itself is useful. The pattern it proves, small prompt-led builds that ship fast and spread by word of mouth, is the bigger lift.