Prepared for Thrivent Financial operators

OpenNash builds on the systems Thrivent Financial already uses.

No rip and replace. We sit on top of existing ticketing, ERP, CRM, HR, data, document, scheduling, service, plant, branch, fleet, or workflow systems, then turn repetitive work into human-approved queues with source links and audit trails.

318
open roles reviewed from public career sources

0
roles with detail text available for mapping

7
OpenNash-relevant work signal buckets

158
locations or work areas represented

OpenNash point of view

Best first queue: advisor onboarding and client-service packets.
Why this should matter: Financial advisor, client service, compliance, technology, and operations titles point to advisor/member support work.
Practical pilot: Start with advisor onboarding, client service follow-up, account paperwork, or compliance review packets.

What this means

Thrivent Financial is an Financial services / insurance operator. The public hiring signal points to repetitive intake, review, routing, documentation, service, and exception work.
Financial services and insurance organization with advisors, member service, policy, claims, compliance, investment, and operations teams.
OpenNash should not sell another standalone tool. We should connect to the workflows staff already use and make the work easier to review.
The source list did not expose full job descriptions, so this page treats titles, functions, locations, and official role links as directional evidence.

Hiring signals

Top functions or categories

(blank)318

OpenNash work signals

Claims, billing, revenue, finance234

General operations support68

Operations, dispatch, supply chain7

AI, data, digital, analytics, cloud5

Quality, safety, compliance2

Customer, member, patient, or agent support1

Sales, orders, field service1

Where OpenNash fits

First wedge

Policy/admin packets, advisor support, compliance review, member service, claims, onboarding, and financial ops queues.

Start with one queue where staff are already reviewing documents, messages, exceptions, or handoffs.

Build on top

Keep the stack. Improve the workflow.

We integrate through APIs, files, inboxes, queues, exports, and human review screens before anyone talks about replacing systems.

Proof

Measure weekly.

Track volume, cycle time, rework, approval rate, and exception reasons so the operator can see whether the workflow is worth expanding.

Role evidence

This is a bounded view of public roles available from the official career source route. Search by title, function, location, role evidence, or OpenNash help angle.

Role	Hiring signal	Role evidence we saw	How OpenNash can help	Source