Auxilium vs a general-purpose CRM
Plenty of ministries run on a general-purpose CRM — a nonprofit platform, a church management system, or a sales CRM someone bent into shape. These are capable products, genuinely better than Auxilium at the things a CRM is for: campaigns, donors, events, and a connector for every other tool you own.
None of that is the work of running a health share. The daily job is needs, claims, guidelines, and a ledger — and a CRM has no idea what any of those are. So somebody teaches it, one custom field at a time, and the ministry pays for that lesson every week thereafter.
What it costs to bend one into shape
Every row is a thing a sharing ministry does daily, the nearest object a CRM has for it, and the work that gap creates. None of it is difficult. All of it is permanent.
| What you actually do | What the CRM makes you call it | What that costs, every week |
|---|---|---|
| A family submits a medical need | A deal or opportunity, with a dollar value and a pipeline stage | Your dashboard reports a win rate on families’ medical bills. Staff learn to ignore the pipeline view, which is the view the CRM is built around. |
| Check whether a household is eligible | Several contacts, tagged or linked, with the rules in somebody’s memory | Eligibility genuinely lives at the household. Answering one question means opening four records and reasoning across them by hand, every time. |
| Decline a need under a published provision | A status change, and a note field | Nothing checks the provision cited against the document that was in force. Consistency is whoever happens to remember, and the gap only surfaces in a complaint. |
| Show where the money went | Contributions in the processor, disbursements in a bank export | They are joined in a spreadsheet, monthly, by one person. The share ratio is arithmetic that same person does by hand — and it is the number a journalist asks for. |
| Meet the turnaround you promised members | A task with a due date | A due date that passes is silent. Nobody is told, and the member cannot tell “being worked” from “lost”. |
| Record what a guideline says about a member | Custom fields: waiting-period end, pre-existing flag, guideline version | Typed by hand with nothing validating them. They drift, and a decision made on a drifted field is indistinguishable from one made correctly. |
The bill is not the licence. It is the standing tax on staff time, plus the fact that the whole arrangement lives in the head of whoever built it — so the real cost lands the month that person leaves.
The part that is worse than doing nothing
A spreadsheet at least looks like a spreadsheet. A configured CRM produces confident reports — a pipeline, a forecast, a conversion rate — built on objects that mean something else entirely. It is possible to run a board meeting off a chart that is measuring the wrong thing and looks completely authoritative doing it.
And every guideline change is a re-configuration: fields to add, reports to rebuild, staff to re-teach which of the forty custom fields still matter and which are dead. That work never appears on a budget line, because it is absorbed by the people who were meant to be looking after members.
Head to head
The first four rows are real CRM strengths and Auxilium does not attempt them. They are also, deliberately, not the daily work of a sharing ministry.
| Capability | Auxilium | Alternative | Notes |
|---|---|---|---|
| Breadth of general features | ✗ | ✓ | A mature CRM does far more things than Auxilium does. |
| Integration ecosystem | ✗ | ✓ | Established platforms have hundreds of connectors. Auxilium has an API. |
| Email and campaign tooling | ✗ | ✓ | |
| Donation and event management | ✗ | ✓ | |
| Households as the unit, not a contact tag | ✓ | ~ | Most CRMs model households as a grouping. Sharing eligibility genuinely lives there. |
| Contributions and disbursements on one ledger with a share ratio | ✓ | ✗ | |
| Sharing guidelines as versioned, dated, checkable rules | ✓ | ✗ | |
| Denials validated against those guidelines | ✓ | ✗ | |
| Claim intake validation (procedure codes, provider NPI, itemized bill) | ✓ | ✗ | |
| Turnaround commitments that escalate automatically | ✓ | ~ | Generic workflow tools can approximate this. Nobody configures it before the first crisis. |
How to actually decide
A CRM tracks relationships. Sharing ministries have a second problem sitting on top of that: a fiduciary one. Money comes in against a promise, goes out against published rules, and you have to be able to show the relationship between the two.
That is not a CRM shortcoming — it is simply not what a CRM is for, and configuring one to do it means building the ledger, the guideline model, and the escalation logic yourself, in a tool that has no opinions about any of them and will not tell you when your version of them is wrong.
If your pressing problem is communication, campaigns, and donor relationships, a good CRM is the better purchase and we would say so. Plenty of ministries should run both. If the problem is that needs stall where nobody sees them and nobody can show where the money went, that is the one Auxilium was built for — and it arrives already knowing what a household, a guideline, and a share ratio are.