Changing a software contract mid-stream is rarely about the software. It’s about timing, paperwork, and who on the vendor side actually has the authority to say yes. Altru is no different. Organizations usually want to change their agreement for a handful of reasons: fewer or more user licenses, dropping or adding a module, a budget cut, a different payment schedule, or questions about payment processing. The path to each one looks a little different, and the single biggest factor is where you are in your contract term.
What follows is general guidance from the administrator’s side of the table. We aren’t Blackbaud and can’t speak to the terms in your specific agreement, so treat this as a way to prepare, not legal advice.
Start with the document you actually signed
Before you call anyone, pull your current agreement, every amendment, and your most recent invoice. Your finance office or executive director usually has the signed copies. Read for these items and write them on one page:
- Term dates. When the current term started and when it ends.
- Renewal language. Whether the agreement renews automatically, and for how long.
- Notice requirements. How far in advance you must give notice to change or not renew, and how that notice has to be delivered (email, letter, a specific address).
- What you’re paying for. User counts, modules or services, and any separately priced items such as hosting, support tiers, or training.
- Price increase terms. Whether annual increases are capped or spelled out.
- Payment processing. Whether your agreement ties you to a particular processor, and whether that’s a separate agreement with its own term.
That one page tells you what you can realistically ask for. Often Blackbaud’s position simply reflects what the contract says, and the window to change it opens at renewal, not in the middle of a term.
Know which kind of change you’re asking for
Adding something
Adding users or services is usually the easiest conversation, because it increases the contract. Expect an amendment or order form rather than a rewrite.
Reducing something
Cutting users, dropping a module, or lowering the total is harder mid-term. Many software agreements commit you to a fixed amount for the term, so a reduction may only take effect at renewal. Ask directly whether a reduction can apply now, at the next renewal, or not at all under your current terms, and get the answer in writing.
Changing payment timing
Moving from annual to quarterly billing, or shifting the billing date to match your fiscal year, is a common and reasonable request. Have your finance office explain the reason in plain terms; a fiscal-year alignment is easier to approve than a vague request for relief.
Leaving or not renewing
If you’re considering not renewing, the notice deadline matters more than anything else. Missing it can mean another full term. Put the deadline on several calendars, not just yours, and send notice early in whatever form the contract requires. Even if you end up staying, giving notice on time keeps your options open.
Find the right person
Support staff fix technical problems; they generally can’t change contracts. Contract questions usually belong with your account or renewals contact. If you don’t know who that is, ask support to route you, and ask for the name and email of the person who owns your account.
When you reach them, send a short written summary rather than relying on calls:
- Your organization name and the account or contract identifiers from your invoice.
- Exactly what you want changed, with numbers (“reduce from X users to Y”).
- When you want it to take effect.
- Why, in one or two sentences.
- A date you need a response by, especially if a notice deadline is close.
Keep every reply in a single folder. If a call produces an answer, follow up with an email that restates it (“Confirming what we discussed today…”) so there’s a written record.
When the answer is no
Sometimes the honest answer is that your contract doesn’t allow the change until renewal. A few things are still worth doing:
- Ask what would be possible at renewal, and get a draft quote early. Renewal is when you have the most room to adjust scope.
- Escalate politely if you aren’t getting responses. Ask your contact who their manager is, or who handles escalations. Keep the tone factual and reference your dated emails.
- Bring in your board treasurer or legal counsel if the dollar amount is significant or the contract language is unclear. A second reader often spots options a busy administrator misses.
- Talk to peers. Other museums, zoos, and gardens on Altru have been through renewals, and user groups and regional associations are good places to ask how similar requests went.
Clean up your own side first
Contract talks go better when you know what you actually use. Before renewal, take inventory: which staff log in regularly, which features nobody touches, and which tasks you’ve moved to spreadsheets or other tools. That list supports a request to reduce users, tells you what you’d lose by dropping a module, and makes clear what you’d need to replace if you ever did leave. It also helps you separate “the contract is the problem” from “our setup is the problem.” Sometimes a frustrating workflow can be fixed through configuration or training without changing the agreement at all.
Quick answers
Can we reduce our Altru users mid-contract?
It depends on your agreement. Many software contracts lock the committed amount for the term. Ask your account contact, and get the answer in writing.
What’s the most common mistake?
Missing the notice deadline before an automatic renewal. Find that date now and put it on a shared calendar.
Who should sign off on a contract change?
Whoever has signing authority at your organization, usually the executive director or finance lead. Don’t let an amendment get signed by someone who hasn’t read the original agreement.
