Industries

Industry depth, not industry decks

Every industry page below is built the same way our engagements run: the real regulatory and operational constraints, the Salesforce architecture that fits them, the agents worth deploying first — and the evidence habit (Horus Eye reads the org before anyone proposes anything) that keeps recommendations honest.

Where we work

Six Practices

Nonprofits

Nonprofit CRM on Salesforce — NPSP and Agentforce Nonprofit — gift processing, membership with KemiCard — anchored by the NAACP program that won the 2022 Nintex Solution Innovation Award. Includes the NPSP migration guide.

Higher Education

Recruitment-to-advancement on one platform: admissions funnels, student success, alumni engagement — FASNY and campus-scale document automation included.

Government & Public Sector

Responsible AI for government: permit and records agents, DocGen at housing-authority scale, audit trails and human escalation by design.

Financial Services

Credit unions to capital markets: compliant client onboarding, service agents with guardrails, and the data trust that regulators expect.

Energy & Utilities

Field service at grid scale, outage communication, and asset-centric data models — built from programs like ATCO.

Manufacturing

Quote-to-cash that survives the price book, dealer and distributor portals, and service that knows the installed base — Cummins-grade patterns.

What every industry engagement shares

The Common Spine

Industry nuance changes the data model and the compliance posture; the method stays constant. We start with evidence — a Horus Eye read of the org you actually have — then architecture before automation, automation before agents. Documents ride along at every stage through our Nintex DocGen practice, and when a platform decision looms (like NPSP to Agentforce Nonprofit), the recommendation comes with findings attached, including “not yet.”

How to use these pages

Reading Order

Each industry page answers the same four questions, in the same order, so you can compare your situation against it quickly: what the Salesforce data model looks like when it is built for this industry rather than adapted to it; which compliance and data-residency constraints shape the architecture before any feature conversation starts; where AI and agents are earning their keep in this sector today — and where they are still a demo; and what our own delivery history in the sector looked like, named clients included. Start with your own industry — but the neighboring pages are worth a skim, because the hardest problems travel: a manufacturer wrestling with quote-to-cash will recognize half of the financial-services page, and a university advancement office will find the nonprofit page describes its donor data almost exactly. If your industry is not listed, the method still applies; the evidence-first assessment works on any org, and the industry nuance enters through the people we staff rather than a template we load. One more pattern worth knowing before you dive in: in every sector below, the engagements that went best began with the smallest honest scope — one revenue line, one donor program, one service region — proven end to end before anything was generalized. The industry pages are written to help you pick that first scope well.

Talk to someone who knows your industry

Clients from the NAACP to Cummins to ATCO — and the architecture scars to prove it.

Try Horus Eye Book an AI Strategy Workshop